header_filter_rules should have precedence

Bug #266103 reported by M-a
2
Affects Status Importance Assigned to Milestone
GNU Mailman
Invalid
Medium
Mark Sapiro

Bug Description

Hi,

I am trying to discard spam (tagged via a header by
amavis-new), but Mailman apparently gives precedence to
the fact that the post's originator is a non-member and
holds the post rather than discarding it.

Please give priority to the header_filter_rules before
checking membership.

Thanks.

[http://sourceforge.net/tracker/index.php?func=detail&aid=992201&group_id=103&atid=100103]

Revision history for this message
M-a (m-a) wrote :

Mailing list reference to Eric D. Christensen's earlier post
that went unanswered on the list:
http://mail.python.org/pipermail/mailman-users/2004-January/033952.html

Revision history for this message
Mark Sapiro (msapiro) wrote :

Since their introduction in Mailman 2.1.4, header_filter_rules have always been processed before any other tests except the legacy spam filters in mm_cfg.py KNOWN_SPAMMERS.

Perhaps you are confusing header_filter_rules with the legacy bounce_matching_headers which are not tested until after membership and moderation.

Changed in mailman:
assignee: nobody → msapiro
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.