Re: Update to RFC 5322 to allow "group" syntax in the "from" header

I intensely dislike what EAI has done to email interoperability, and I 
don't think that IETF should have ever standardized email addresses that 
wouldn't work with legacy mail processing software.

Having said that, there's been a longstanding need for a non-replyable 
originator address in a wide variety of situations.   I'm not 
particularly enamored with the idea of using group syntax to represent 
such an address, but it might be better than some of the alternatives.

Keith

On 08/08/2012 05:30 PM, John Levine wrote:
>> In other words, I think the "Sender" should be required
>> when a "From" header field specifies a group with an empty
>> list of mailboxes.
> This is a reasonable suggestion, except that the primary motivation
> for this change is EAI messages downgraded by POP or IMAP delivery
> agents.  If the addresses on the From: or Reply-To: line are
> non-ASCII, there is no way for an ASCII MUA to display or reply to
> them, so the idea is that the header will be rewritten to something
> like this:
>
>    From: an international address :;
>
> So either there's an existing Sender header, which might itself need
> to be downgraded, or there isn't, but either way there's no promise
> that there is a non-ASCII address that could be put in the Sender.
> So it's not gonna happen.
>
> R's,
> John
>
> PS: EAI went around for years trying to come up with a general way to
> allow non-ASCII mail software to read and reply to EAI messages, and
> finally gave up.  See the experimental RFCs and the mailing list for
> details.
>

_______________________________________________
ietf-822 mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/ietf-822