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: Thu, 22 May 2014 12:37:55 -0500
- In-reply-to: <201405221220.s4MCK7No011705@dsl092-065-009.bos1.dsl.speakeasy.net>
- References: <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> <20140521190633.GI3797@dragontoe.org> <201405221220.s4MCK7No011705@dsl092-065-009.bos1.dsl.speakeasy.net>
On Thu, May 22, 2014 at 08:20:07AM -0400, Robert Krawitz wrote: > On Wed, 21 May 2014 14:06:33 -0500, Derek Martin wrote: > > On Wed, May 21, 2014 at 02:30:43PM -0400, Robert Krawitz wrote: > >> (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. > > Here's the use case: a support mailing list for a FOSS project where > users post questions and issues. [...] I'm familiar with the use case. There are two solutions: 1. The developer in question can set his sender address to the list address, if that is his biggest concern (and I agree it's a valid concern). If you do this, you should (IMO) include a footer in your messages that says that you have, to at least give the poster a chance to decide that replying to the list is not what is wanted. 2. Suck it up. See above. Users generally have an expectation that replying to a person will send a response to that person's address, and reply-to is a rarely used feature that breaks this expectation. I'd venture a guess that more than 50% of all e-mail users don't even know about it... Using it should be avoided, except when it's really necessary. -- 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: richard.pieri at gmail.com (Richard Pieri)
- [Discuss] DMARC issue, Yahoo and beyond
- References:
- [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
- From: invalid at pizzashack.org (Derek Martin)
- [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):