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
In this old comment I claimed that message headers are supposed to always be 7 bit, but today I learnt of RFC6532 which permits UTF-8-encoded header values.
Sup should expect to see mails with UTF-8 headers if it's running at a site which supports RFC6531 for transmitting Unicode mail (for example, Postfix has supported this since 2014).
There is also a corresponding new MIME type message/global which is like message/rfc822 but the headers are allowed to have UTF-8. In practice I haven't ever run across that, but Sup should treat it the same as message/rfc822 while also accepting UTF-8 in its headers.
The text was updated successfully, but these errors were encountered:
danc86
added a commit
to danc86/sup
that referenced
this issue
Apr 22, 2022
In this old comment I claimed that message headers are supposed to always be 7 bit, but today I learnt of RFC6532 which permits UTF-8-encoded header values.
Sup should expect to see mails with UTF-8 headers if it's running at a site which supports RFC6531 for transmitting Unicode mail (for example, Postfix has supported this since 2014).
There is also a corresponding new MIME type
message/global
which is likemessage/rfc822
but the headers are allowed to have UTF-8. In practice I haven't ever run across that, but Sup should treat it the same asmessage/rfc822
while also accepting UTF-8 in its headers.The text was updated successfully, but these errors were encountered: