
The From was not being munged, it was showing up as
From: Jane User <user@yahoo.com>
However, I noticed some other problems so I rebooted the host just to make sure every change had fully taken hold .. and things are working now. So it is strange, while I had previously restarted mailman, something was still not working right until a reboot. Maybe a problem in my init scripts.
thx
glen
On 06/13/2014 09:02 PM, Mark Sapiro wrote:
On 06/13/2014 08:07 PM, glen martin wrote:
I'm having a similar problem, also using 2.1.18-1. Posts from a Yahoo user are bouncing on redelivery to him.
Jun 13 18:55:00 host postfix/smtp[15681]: 912BD520AB: to=<user@yahoo.com>, relay=mta5.am0.yahoodns.net[98.138.112.33]:25, delay=1.2, delays=0.05/0/0.25/0.92, dsn=5.7.9, status=bounced (host mta5.am0.yahoodns.net[98.138.112.33] said: 554 5.7.9 Message not accepted for policy reasons. See http://postmaster.yahoo.com/errors/postmaster-28.html (in reply to end of DATA command))
... General Options
from_is_list is Munge From anonymous_list is No
Privacy Options --> Sender Filters
dmarc_moderation_action is Munge From dmarc_quarantine_moderation_action is Yes
with the above, your list should be munging the From: on all outgoing messages because from_is_list is Munge From. The dmarc_moderation_action of Munge From is redundant in this case. It would serve to munge the From only on messages originally from domains with DMARC p=reject or quarantine if from_is_list were No.
So the first question is what does the From: look like on messages from the list. Is it
From: Jane User <user@yahoo.com>
(which is not what it should be - something is wrong) or is it
From: Jane User via LISTNAME list <listname@mailman.host>
which is what it should be. If it is the latter, and your mailman.host does not publish a DMARC policy, then Yahoo is not rejecting the mail for DMARC, but for some other unknown to me reason, but Mailman is doing what it can.
If the From: is not munged, then there is a Mailman issue we can investigate. So which is it?