Subject: The mailing list for listmasters using Sympa
List archive
- From: Adam Bernstein <address@concealed>
- To: address@concealed
- Subject: Re: [sympa-users] AOL sets DMARC p=reject
- Date: Fri, 25 Apr 2014 12:58:32 -0700
On 4/22/2014 3:22 PM, Matt Taggart wrote:
AOL has followed yahoo.com in setting their DMARC policy to reject.
And that did it, we couldn't keep blocking yahoo.com and now add aol.com users too, so we've applied Steve's patch on production and it's working great. Thanks Steve!
But there is one problem: If someone has their list's reply_to_header setting set to "sender" and "forced", Sympa will add its own Reply-To: based on the munged From: line (ie. with the list address), overwriting the fixed-up Reply-To: that was added by the patch. So replies now suddenly are going back to the list, but only on lists where the admin actively tried to be sure they would go only to the sender. And they don't seem to appreciate the irony!
I can see ways to handle that problem with the forced reply setting, but I want to be careful about handling the different edge cases: forced reply_to in sympa, anonymous_sender mode in sympa, explicit Reply-To in the original sender's email settings, etc.
Before I dive in, any thoughts Steve?
adam
--
Electric Embers Cooperative
Handcrafted hosting, powering the fires of change
electricembers.coop
(800) 843-6197
-
[sympa-users] AOL sets DMARC p=reject,
Matt Taggart, 04/22/2014
-
Re: [sympa-users] AOL sets DMARC p=reject,
Adam Bernstein, 04/25/2014
- RE: [sympa-users] AOL sets DMARC p=reject, Steve Shipway, 04/25/2014
-
Re: [sympa-users] AOL sets DMARC p=reject,
Adam Bernstein, 04/25/2014
Archive powered by MHonArc 2.6.19+.