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: abreauj at gmail.com (John Abreau)
- Date: Tue, 27 May 2014 13:52:00 -0400
- In-reply-to: <4a5422ed9ef74e44b230526c29aac557@CO2PR04MB684.namprd04.prod.outlook.com>
- References: <537A7274.7080705@gmail.com> <20140521172852.GG3797@dragontoe.org> <537CEC28.3060704@gmail.com> <20140521185146.GH3797@dragontoe.org> <537CFD95.7060306@gmail.com> <20140521205815.GA5683@dragontoe.org> <537D2ED1.7070109@gmail.com> <20140522170512.GB5683@dragontoe.org> <20140522172630.GB8020@dragontoe.org> <sjmlhtsa7v7.fsf@mocana.ihtfp.org> <20140523202011.GC13777@dragontoe.org> <CA+h9Qs67ZuRpd5YxkEc-ZnKCjhA+g8dCvHDVMY0_oXKya5iZ_w@mail.gmail.com> <sjmwqd78itc.fsf@mocana.ihtfp.org> <4a5422ed9ef74e44b230526c29aac557@CO2PR04MB684.namprd04.prod.outlook.com>
On May 27, 2014, at 10:50 AM, "Edward Ned Harvey (blu)" <blu at nedharvey.com> wrote: > I'm not really sure where this thread got to - I got lost in things that sounded like people philosophizing on the way things should be, without tying it back to the real world. I've mostly avoided commenting on this, because the reply-to flame war is one of those recurring disputes that flares up periodically and accomplishes nothing. When I first set up the lists, almost 20 years ago, I set the reply-to to the list address, which was the common practice at the time. The first time this argument came up, I was persuaded by the paper "Reply-To Considered Harmful", and I changed the list config based on that. The next time the argument flared up, I came to realize that both sides had compelling arguments, the people who seemed to care about the issue were a very small fraction of the community, and the numbers of such people on each side of the argument seemed to be about the same. Somebody suggested voting on the issue, and it was clear that if we did this, we'd be voting on it every time the argument recurred, with the result that the list's behavior would be arbitrarily changed periodically. I decided that changing the list behavior back and forth arbitrarily would be far more disruptive than the consequences of either setting. That was probably about 10-15 years ago.
- Follow-Ups:
- [Discuss] DMARC issue, Yahoo and beyond
- From: blu at nedharvey.com (Edward Ned Harvey (blu))
- [Discuss] DMARC issue, Yahoo and beyond
- References:
- [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
- From: invalid at pizzashack.org (Derek Martin)
- [Discuss] DMARC issue, Yahoo and beyond
- From: invalid at pizzashack.org (Derek Martin)
- [Discuss] DMARC issue, Yahoo and beyond
- From: warlord at MIT.EDU (Derek Atkins)
- [Discuss] DMARC issue, Yahoo and beyond
- From: invalid at pizzashack.org (Derek Martin)
- [Discuss] DMARC issue, Yahoo and beyond
- From: jabr at blu.org (John Abreau)
- [Discuss] DMARC issue, Yahoo and beyond
- From: warlord at MIT.EDU (Derek Atkins)
- [Discuss] DMARC issue, Yahoo and beyond
- From: blu at nedharvey.com (Edward Ned Harvey (blu))
- [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):