I'm setting up a new Mailman server to replace an elderly MajorDomo
that isn't DMARC-compatible.
I set up the list to use the list's address as the From address and to
put the sender's address in Reply-To:. I started playing around with a
test list - in no time at all, AOL began bouncing all my
On 10/17/2014 10:33 PM, Ed Ravin wrote:
I set up the list to use the list's address as the From address and to
put the sender's address in Reply-To:. I started playing around with a
test list - in no time at all, AOL began bouncing all my mail.
After researching AOL's error messages, it
I have a somewhat different issue. I am using dmarc_moderation_action =
Munge From, and when an AOL user posts to the list, the list message
sent back to the user bounces with 521 5.2.1 : AOL will not accept
delivery of this message. (in reply to end of DATA command)). The same
messages sent to
On 10/18/2014 11:26 AM, John Levine wrote:
I have a somewhat different issue. I am using dmarc_moderation_action =
Munge From, and when an AOL user posts to the list, the list message
sent back to the user bounces with 521 5.2.1 : AOL will not accept
delivery of this message. (in reply to end
John Levine writes:
I would be surprised if AOL were doing DMARC checks on Reply-To,
and agree that it's not a problem worth solving.
I wouldn't. As you know, John, we (dm...@ietf.org) are all expecting
the spammers to emulate these DMARC mitigation various tricks. If
they have any
Mark Sapiro writes:
If and when there is an accepted standard governing this behavior, I'll
consider it. In the mean time, I'm not interested in accommodating
non-compliant behavior by one rogue ESP.
I'm in complete sympathy, but unfortunately that rogue provider is
still the MTA for tens
On Sat, Oct 18, 2014 at 11:03:11AM -0700, Mark Sapiro wrote:
...
I have a somewhat different issue. I am using dmarc_moderation_action =
Munge From, and when an AOL user posts to the list, the list message
sent back to the user bounces with 521 5.2.1 : AOL will not accept
delivery of this
