Hi Wietse, et al., Thank you for your explanation. I now understand that you do not have any plans on supporting this feature due to interoperability concerns.
Would you be willing to accept external patches to add RFC 6531 functionality? (Admittedly, this is a bit of an academic question -- I'm starting to see some IDNs in email, and wanted to find out the status of international email addresses in general. I now have that answer.) I didn't intent to start a discussion if RFC 6531 is good or bad, but now that we have that discussion, here are my two cents. While I perfectly understand that other features are more important to implement, I'm a bit surprised by the rather strong opinion voiced on this list against this feature. Personally, I rather see UTF-8 encoded mail headers than HTML-encoded mail bodies. ;). > In other words, email with your "international" sender address will > be undeliverable to vast portions of the Internet. Is that what you > want? Personally, I wouldn't recommend anyone to start creating email addresses with non-ASCII characters in the local part (the domain name part is fine), precisely for the incompatibility reasons you cite. However, on the off-chance that someone else creates such mail addresses, now that it is a IETF proposed standard (as opposed to RFC 5336, which was 'only' experimental), I would hate to see that Postfix, my favorite MTA, would be the one that causes the bounce because it is incapable of handling such address. Regards, Freek
