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: Wed, 21 May 2014 14:30:43 -0400
- In-reply-to: <537CEC28.3060704@gmail.com> (richard.pieri@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>
On Wed, 21 May 2014 14:10:48 -0400, Richard Pieri wrote: > Derek Martin wrote: >> If a mailing list--which is already a special case of e-mail >> usage--*ADDS* a reply-to header to an e-mail which matches the from >> header of the message, when none previously existed, the net effect is >> nil: respondants will (assuming they even honor reply-to, which is not > > It most certainly is problematic. The net effect is that it causes good > mail programs to behave inconsistently. When set to the list it breaks > reply to author functions in good mail programs (Elm, Pine and their > derivatives; Thunderbird and Seamonkey, and even the venerable Berkeley > Mail to name a few). When set to the original author it breaks reply to > list and reply to all functions in those same programs. > > 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. > > Thoughtless? Hardly. I've thought about this off and on for far too long. 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. It may be that the list owners want to encourage public rather than private discussion, for example.) -- 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
- From: richard.pieri at gmail.com (Richard Pieri)
- [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
- 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):