Hi All, I've detected something doubtful situation in mailman because it has released an email with spam flagged. I'm attaching my received email's header which is flagged spam yet released by the mailman. But I've checked this scenario many times later but mailman was rejected them all as it should be. Can someone explain what would be the reason here? Or is it may be a bug? X-Spam_score: 200.3 X-Spam_score_int: 2003 X-Spam_bar: +++++++++++++++++++++++++++++++++++++++++++++++++++ X-Spam_report: Spam detection software, running on the system "", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see @@CONTACT_ADDRESS@@ for details. Content analysis details: (200.3 points, 4.8 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.0 SPF_PASS SPF: sender matches SPF record 50 BLOCK_RULE_TACCDEV BODY: Bad Word 50 BLOCK_RULE_TACC BODY: Bad Word 0.0 NORMAL_HTTP_TO_IP URI: Uses a dotted-decimal IP address in URL 0.0 WEIRD_PORT URI: Uses non-standard port number for HTTP 0.4 MIME_HTML_MOSTLY BODY: Multipart message mostly text/html MIME 0.0 HTML_MESSAGE BODY: HTML included in message 1.0 HTML_FONT_FACE_BAD BODY: HTML font face is not a word -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] 50 BLOCK_RULE2_TACC RAW: Bad Word 50 BLOCK_RULE2_TACCDEV RAW: Bad Word 0.8 RDNS_NONE Delivered to internal network by a host with no rDNS X-Spam-Flag: YES X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: X-SA-Exim-Scanned: No (on ); SAEximRunCond expanded to false --===============4314035725409602216== Content-Type: multipart/alternative; boundary="------------090201060409020801010503" --------------090201060409020801010503 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit Thanks, Rumesh
Re@lබණ්ඩා™ writes:
I've detected something doubtful situation in mailman because it has released an email with spam flagged.
Mailman doesn't know anything about spam or spam flags. Mailman's native filtering uses regular expressions, and takes certain actions based on matches to those regular expressions. In the case of use with SpamAssassin, I would recommend setting Mailman to HOLD or DISCARD when the expression
^X-Spam-Flag:\s*Yes
matches.
There is also an extension, not maintained by this project, which calls SpamAssassin from Mailman, but I don't know how that works. It may reject mail itself, or it may pass on the responsibility to the filters as above.
You need to tell us more about how spam filtering is configured on your system.
Hi Stephen,
Really thanks for the comprehensive answer. In my situation I'm using following reg expression to catch spam.
X\-Spam\-Flag\: Yes.*
Is it wrong?
I have a separate server for spamassasin and not using an extension like you mentioned above.
Thanks, Rumesh
On Tue, Oct 8, 2013 at 8:11 PM, Stephen J. Turnbull stephen@xemacs.orgwrote:
Re@lබණ්ඩා™ writes:
I've detected something doubtful situation in mailman because it has released an email with spam flagged.
Mailman doesn't know anything about spam or spam flags. Mailman's native filtering uses regular expressions, and takes certain actions based on matches to those regular expressions. In the case of use with SpamAssassin, I would recommend setting Mailman to HOLD or DISCARD when the expression
^X-Spam-Flag:\s*Yes
matches.
There is also an extension, not maintained by this project, which calls SpamAssassin from Mailman, but I don't know how that works. It may reject mail itself, or it may pass on the responsibility to the filters as above.
You need to tell us more about how spam filtering is configured on your system.
-- Re@lBanda
Hi Stephen,
Really thanks for the comprehensive answer. In my situation I'm using following reg expression to catch spam.
X\-Spam\-Flag\: Yes.*
Is it wrong?
Maybe. I forget the exact context, but in some places exact matches and regular expressions can both be users. In that case you need to start a regular expression with '^'.
Aside from that, in Python regular expressions, you don't need the backslash on the '-' or the ':'; they only have meaning as operators inside a complex construct ('-' for ranges inside [] character classes, and ':' as part of extension syntax for () groups). Also, there's no need for the ".*" at the end
I believe Mailman automatically makes the match case-insensitive. The only other thing I can think of is that it's legal to use TAB characters (or none at all) between the ':' and the "Yes", so (as I wrote before) I would write the expression as
^X-Spam-Flag:\s*Yes
I have a separate server for spamassasin and not using an extension like you mentioned above.
OK, so the incoming mail should have the X-Spam-Flag in it, and this regular expression should do what you want.
Steve
participants (2)
-
Re@lබණ්ඩා™
-
Stephen J. Turnbull