Bryan Fullerton wrote:

Yay, upgraded. :)

Is the bug you mentioned below filed on SF?

No.

                                            Just wondering what the
issue is, and specifically if this will fix a problem I've seen with
SpamAssassin-tagged mail leaking through to my mailman@ list despite a
header_filter_rule that really should be blocking it...  but haven't
had time to double-check everything is setup properly here before
reporting it as a bug.

Sorry for the inconvenience. The shame is on me. While applying my patch, by hand, to collect subpart headers, I might have something out of mind and an intermediate version has gone out. I am going to give some seminar on the security of mailman this weekend in Tokyo and while preparing my presentation I wanted to check the new feature. Then, the bug is there!
You can check what was wrong using diff in CVS.
http://cvs.sourceforge.net/viewcvs.py/mailman/mailman/Mailman/Handlers/SpamDetect.py?r1=2.3.2.2&r2=2.3.2.3



-- Tokio Kikuchi tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/

_______________________________________________
Mailman-Developers mailing list
[email protected]
http://mail.python.org/mailman/listinfo/mailman-developers
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org

Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

Reply via email to