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: rlk at alum.mit.edu (Robert Krawitz)
- Date: Thu, 22 May 2014 08:20:07 -0400
- In-reply-to: <20140521190633.GI3797@dragontoe.org> (invalid@pizzashack.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> <201405211830.s4LIUh4C004497@dsl092-065-009.bos1.dsl.speakeasy.net> <20140521190633.GI3797@dragontoe.org>
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: >> > 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. Here's the use case: a support mailing list for a FOSS project where users post questions and issues. All too often one of the developers replies (copying the list) and the user simply replies to sender, either because s/he prefers the discussion to be with one point person or because the default "reply" is just to sender...but we want the replies to all go to the list in addition to the sender, so that others may chime in. -- Robert Krawitz <rlk at alum.mit.edu> MIT VI-3 1987 - Congrats MIT Engineers 6 straight men's hoops tourney Tall Clubs International -- http://www.tall.org/ or 1-888-IM-TALL-2 Member of the League for Programming Freedom -- http://ProgFree.org Project lead for Gutenprint -- http://gimp-print.sourceforge.net "Linux doesn't dictate how I work, I dictate how Linux works." --Eric Crampton
- 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: 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
- Prev by Date: [Discuss] [OT] Android development books
- 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):