You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Neither of them allows using the option in RCPT TO; thats why the Postfix would complain the unsupported option in response.
I checked the implementation and found the root cause of this issue is in the function smtp_mail_envelope_header(): the lib should append SMTPUTF8 only in MAIL FROM.
Maybe we need to maintain a boolean to indicate if there is a need to use UTF-8 support because any non-ascii address used in sender or recipients would require UTF-8 support.
The text was updated successfully, but these errors were encountered:
The behavior of SMTPUTF8 support of the library isn't compliant with RFC 6531.
If one of recipients uses i18n email address, the smtp connection will fail.
sample code (based on
example_sample.c
):Postfix v3.6 is running background and if we ran the test, we have following smtp logs
SMTPUTF8
option only in commandMAIL
,VRFY
andEXPN
, see https://datatracker.ietf.org/doc/html/rfc6531#section-3.1SMTPUTF8
option inMAIL
andVRFY
commands https://www.postfix.org/SMTPUTF8_README.htmlNeither of them allows using the option in
RCPT TO
; thats why the Postfix would complain the unsupported option in response.I checked the implementation and found the root cause of this issue is in the function
smtp_mail_envelope_header()
: the lib should appendSMTPUTF8
only inMAIL FROM
.Maybe we need to maintain a boolean to indicate if there is a need to use UTF-8 support because any non-ascii address used in sender or recipients would require UTF-8 support.
The text was updated successfully, but these errors were encountered: