
Moved from mailman-users.
Mark Sapiro writes:
I've long thought that this is a design bug.
This is one nice thing about SpamAssassin: it tells you which rules were triggered.
Is this already improved in 3.0? Would better logging be something to target in 2.2?

On Wed, Feb 13, 2008 at 05:35:21AM +0900, Stephen J. Turnbull wrote:
This is one nice thing about SpamAssassin: it tells you which rules were triggered.
This reminds me of Mailman's most annoying reason for holding a message, the 'suspicious header' error/warning. It doesn't say what the header is, or what's suspicious about it; some regular posters to lists I admin often get caught by this message, but I have no easy way of telling why.
--amk

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Feb 13, 2008, at 8:48 AM, A.M. Kuchling wrote:
Agreed! I really want to get rid of this for MM3. Instead, I've
implemented a fairly generic header matching rule which can be used to
accept, hold, reject, or discard the message based on the match.
These rules will be storable in the database or on file and the plan
is to include exactly the match in any hold or rejection message. The
rule stuff is implemented and in the tree, the notification message
stuff is not yet.
- -Barry
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin)
iD8DBQFHsvt82YZpQepbvXERAvf3AKCR5rov3kxffNGi0QLoz7WXSOCTLwCbBo08 x+aJ/d2i21ONNxlEqtHlINI= =HcwJ -----END PGP SIGNATURE-----
participants (3)
-
A.M. Kuchling
-
Barry Warsaw
-
Stephen J. Turnbull