Michael Tokarev via Postfix-users:
> And while it's definitely true there's no encoding specified for the
> GECOS field in /etc/passwd, the common practice over last couple decades
> is to use utf8 in there. Also we've $LANG at submission which can be
> used too. Or failing that, we can tell postfix which encoding our
> GECOS field is, like using gecos_charset = foo.
>
> Shouldn't postfix at least try to generate valid email message in
> such case?
To send messsages with 8bit UTF8 headers:
1 - Use Postfix default settings:
smtputf8_enable = yes (assuming compatibility_level > 0)
smtputf8_autodetect_classes = sendmail, verify
With this, Postfix will detect UTF8 in headers and will require
that the message is transmitted as SMTPUTF8. This limits the
destinations that the message can be sent to.
2 - Encode headers before invoking the Postfix sendmail command.
This will increase the number of destinations that the message
can be sent to.
3 - Wait until IETF issues guidelines for converting messages (and
envelopes) from SMTPUTF8 to legacy format.
4 - Invent our own conversion guideline: if "smtputf8_enable = no",
encode Postfix-generated headers: From:, Date:, Message-ID.
Should this use RFC 2047/2231 for an entire header, or punycode
for substrings that contain a domain name, or what? How are
people expected to reply to an RFC 2047 encoded From: address?
Wietse
_______________________________________________
Postfix-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
