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: invalid at pizzashack.org (Derek Martin)
- Date: Wed, 21 May 2014 14:06:33 -0500
- In-reply-to: <201405211830.s4LIUh4C004497@dsl092-065-009.bos1.dsl.speakeasy.net>
- 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> <201405211830.s4LIUh4C004497@dsl092-065-009.bos1.dsl.speakeasy.net>
On Wed, May 21, 2014 at 02:30:43PM -0400, Robert Krawitz wrote: > > Lists setting or rewriting Reply-To headers punishes users of > > good, open source mail programs and rewards users of broken, > > proprietary mail programs like Outlook. On this, Richard and I agree. > OK. So if the list has a policy that all replies should be directed > to the list rather than the author, what should the list do to > "encourage" members to honor that policy? > > (Don't simply say that it's a bad policy... But it IS a bad policy. It is not the place of the list or the list manager to decide that my tangential response to a poster I know, on an off-topic subject, and content which is not fit for "polite company" belongs on the list. And it should not make it hard for me to provide such responses, or make it easy for such responses to accidentally end up posted to the list contrary to my expectations. Reply-to munging[1] is a bad practice, period. The poster knows best where his response should go, and should be afforded full control over that. > "Linux doesn't dictate how I work, I dictate how Linux works." Isn't that exactly the same sentiment? --- [1] ...which I define as "adding, or replacing an existing, reply-to header with a value *having no direct relation to the sender of the message*." The case we are discussing in relation to DMARC *does not* do that. -- Derek D. Martin http://www.pizzashack.org/ GPG Key ID: 0xDFBEAD02 -=-=-=-=- This message is posted from an invalid address. Replying to it will result in undeliverable mail due to spam prevention. Sorry for the inconvenience.
- Follow-Ups:
- [Discuss] DMARC issue, Yahoo and beyond
- From: rlk at alum.mit.edu (Robert Krawitz)
- [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: rlk at alum.mit.edu (Robert Krawitz)
- [Discuss] DMARC issue, Yahoo and beyond
- Prev by Date: [Discuss] DMARC issue, Yahoo and beyond
- Next by Date: [Discuss] DMARC issue, Yahoo and beyond
- Previous by thread: [Discuss] DMARC issue, Yahoo and beyond
- Next by thread: [Discuss] DMARC issue, Yahoo and beyond
- Index(es):