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 16:07:21 -0400
- In-reply-to: <537CFD95.7060306@gmail.com>
- 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>
Richard Pieri wrote: > You are incorrect. When the Reply-To field is set then all replies use > the Reply-To field contents for the new To field. This is unexpected > when reply to list would otherwise use the list's address. This is > unexpected when reply to all would otherwise use all addresses in the > original From and To fields. NB: I know that Gnus can be made to act the way Derek describes because I wrote a custom Reply-To handler to deal with lists that munged Reply-To fields. It or something like it may be in the main line Gnus code. Seamonkey is inconsistent: if there is a Reply-To field of any sort then reply to all ignores it in favor of the list headers (I think) but if there is none then reply to all fills in To and Cc fields with the From and To fields of the original. And in the case of the Reply-To being the same as the From it leaves the To field empty (at least in the tests I just did; YMMV). I don't know about any of you but I don't see how these inconsistent behaviors can be even remotely described in terms like "absolutely no effect". Also, apologies for what I did with my previous message: I set the Reply-To to my own mailbox to demonstrate some of these inconsistencies. -- Rich P.
- Follow-Ups:
- [Discuss] DMARC issue, Yahoo and beyond
- From: warlord at MIT.EDU (Derek Atkins)
- [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
- 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):