I won't call this a bug but I think it's an issue :-)
This is with 2.1.18-1 which my provider updated to a few weeks ago.
I have (via the GUI sender filters) dmarc_moderation_action set to 'munge
from' and yet a post from aol.com went through unmunged (and caused 100+
subscribers to be disabled).
I think (but may be wrong) the problem is that I also have(had) a spam
filter set to catch all posts from ISPs with a bad spam/hacking/leaking
history. This holds everything that matches:
^from:.*(aol|yahoo|hotmail|btinternet|btopenworld).*
So, it appears to me that being held by this spam filter and then released
by a moderator results in the message escaping the DMARC munging :-(
My guess is that this is a natural consequence of the ordering of
processing actions in the pipeline rather than a bug but it would be good
to have confirmation from those who know the code.
Thanks in advance, Malcolm.
--
Malcolm Austen <[email protected]>
GENUKI trustee <[email protected]>
Oxfordshire FHS webmaster <[email protected]>
PUG chairman <[email protected]>
FFHS Communications Officer <[email protected]>
------------------------------------------------------
Mailman-Users mailing list [email protected]
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
