BLU Discuss list archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Discuss] DMARC issue, Yahoo and beyond
- Subject: [Discuss] DMARC issue, Yahoo and beyond
- From: richard.pieri at gmail.com (Richard Pieri)
- Date: Wed, 21 May 2014 18:55:13 -0400
- In-reply-to: <20140521205815.GA5683@dragontoe.org>
- References: <49ef9e53017b42958b2c16e83c5668dc@CO2PR04MB684.namprd04.prod.outlook.com> <CADdM39wcBj3xQvT5fzN5jMgYKmsENca9KVqzNDoeZybR91=m+g@mail.gmail.com> <df75e797b6294fe3bf6a75f4ec73a9d4@CO2PR04MB684.namprd04.prod.outlook.com> <53754F74.4000703@gmail.com> <20140519195327.GE3797@dragontoe.org> <537A7274.7080705@gmail.com> <20140521172852.GG3797@dragontoe.org> <537CEC28.3060704@gmail.com> <20140521185146.GH3797@dragontoe.org> <537CFD95.7060306@gmail.com> <20140521205815.GA5683@dragontoe.org>
Derek Martin wrote: > in any fashion. Mutt properly ignored your reply-to header and did > what I asked it to do. It had *absolutely no effect* as I said. With the caveat that I did not list Mutt by name but that's quibbling. Point is, as you've experienced yourself, Mutt's behavior is not consistent when improperly-set Reply-To fields are in play. The reason is simple: the program is trying to deal with two conflicting directives. The only ways for a MUA to reconcile these conflicts is to ignore one of the two users: the original sender or the author of the reply. Ignore the original sender and you break RFCs 822 and 2822. Ignore the author of the reply and you annoy that user. Pick one. Or you can pick the third option: don't insert or alter Reply-To fields. If there is no Reply-To field then there is no conflict. If there is no conflict then any given MUA will behave consistently for its user. -- Rich P.
- Follow-Ups:
- [Discuss] DMARC issue, Yahoo and beyond
- From: invalid at pizzashack.org (Derek Martin)
- [Discuss] DMARC issue, Yahoo and beyond
- References:
- [Discuss] DMARC issue, Yahoo and beyond
- From: blu at nedharvey.com (Edward Ned Harvey (blu))
- [Discuss] DMARC issue, Yahoo and beyond
- From: drew.vanzandt at gmail.com (Drew Van Zandt)
- [Discuss] DMARC issue, Yahoo and beyond
- From: blu at nedharvey.com (Edward Ned Harvey (blu))
- [Discuss] DMARC issue, Yahoo and beyond
- From: richard.pieri at gmail.com (Richard Pieri)
- [Discuss] DMARC issue, Yahoo and beyond
- From: invalid at pizzashack.org (Derek Martin)
- [Discuss] DMARC issue, Yahoo and beyond
- From: richard.pieri at gmail.com (Richard Pieri)
- [Discuss] DMARC issue, Yahoo and beyond
- From: invalid at pizzashack.org (Derek Martin)
- [Discuss] DMARC issue, Yahoo and beyond
- From: richard.pieri at gmail.com (Richard Pieri)
- [Discuss] DMARC issue, Yahoo and beyond
- From: invalid at pizzashack.org (Derek Martin)
- [Discuss] DMARC issue, Yahoo and beyond
- From: richard.pieri at gmail.com (Richard Pieri)
- [Discuss] DMARC issue, Yahoo and beyond
- From: invalid at pizzashack.org (Derek Martin)
- [Discuss] DMARC issue, Yahoo and beyond
- Prev by Date: [Discuss] DMARC issue, Yahoo and beyond
- Next by Date: [Discuss] [OT] Android development books
- Previous by thread: [Discuss] DMARC issue, Yahoo and beyond
- Next by thread: [Discuss] DMARC issue, Yahoo and beyond
- Index(es):