Noah writes: > thanks for following up. we just solved the problem.
Good! > it was a misused wildcard in the mailman filter rules. I might > have missed it but it feels like there is not enough verbose output > in the mailman logs files to tell me that a message was filtered > and an entry explaining the corresponding filter rule. I agree, but fixing that will require hacking the main sources. The problem is that currently there is no place to record a reason in the "event" that occurs when a message is discarded. I don't think it is "hard", but it will require one of the core developers. If you can explain what it is you want, then a post to the bug tracker http://sourceforge.net/bugs/?group_id=103 would probably help a lot of people (I think anybody who hasn't lost data to an inappropriate wildcard probably never had any data to lose!), if something can be implemented. Besides the basic "log the rule" request, the important thing I can think of is where you would expect to see the log message. There's a similar existing bug at http://sourceforge.net/tracker/index.php?func=detail&aid=908819&group_id=103&atid=100103 and a related patch http://sourceforge.net/tracker/index.php?func=detail&aid=869394&group_id=103&atid=300103 Neither is quite what you asked for, though. ------------------------------------------------------ Mailman-Users mailing list [email protected] http://mail.python.org/mailman/listinfo/mailman-users 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-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
