On Sat, 13 Jan 2018, Don Hollander wrote:
2) I’ve added a section identifying which fields need to be considered when doing EAI retrofitting. Can someone provide such a list? Are there also tasks/functions that we need to apply?
For sending, all you have to do is to handle UTF-8 text in addresses in From:, To:, Cc:, Sender:, Reply-To:, and Resent-*:. But RFC 6532 also says that you can use UTF-8 nearly everywhere that used to require ASCII, so the display names, Subject: line, and message body can also be UTF-8, so you better be prepared to handle that on incoming mail even if you don't send it. Also, when doing attachments, if your mail program can attach one message to another, e.g., forward as an attachment, it needs to check if the message being forwarded is EAI and if so attach is as message/global rather than message/rfc822. It's probably also worth mentioning a few things not to change. Don't change the Date: header, since it's in a rigid format intended to be parsed and redisplayed by MUAs. (Mine displays dates in the local timezone, adjusting appropriately.) Don't change Message-IDs, they're for computers, not people.
3) Should we identify UASG Good Practices where they are not addressed one way or another within the RFCs? Eg Aliasing vs ‘downgrading’ on the fly.
Aliasing is the only thing that comes to mind. Regards, John Levine, johnl@iecc.com, Primary Perpetrator of "The Internet for Dummies", Please consider the environment before reading this e-mail. https://jl.ly