Byteplant Forum

Home » CleanMail Support » CleanMail SpamAssassin Filter » SpamAssassin being ignored?
SpamAssassin being ignored? [message #409] Thu, 21 December 2006 10:00
Mark Haller
Messages: 27
Registered: August 2004
Junior Member

Hi there,

Got a serious problem at the moment ... and not sure what's caused it (probably me!) or how to solve it ... can anyone help?

It appears my mails are not being checked by SpamAssassin on the way in.

I can see only two extra X_ header fields (X_MimeOLE and X_MSMail_Priority) being added and the SPAM scoring, etc, is non-existent.

I've included an extract below. The SpamAssassin command timed out doesn't look right.

I've tested the rulesets using SA-LINT.BAT and apart from two entries with no score, that are ignored, all others are fine.





Dec 21, 2006, 08:51:09 Session 2: Connection from 89.137.16.51 accepted on 66.232.129.149:25
Dec 21, 2006, 08:51:09 Session 2: 220 mail.logicspot.com ESMTP Service (Lotus Domino Build V702_07192006) ready at Thu, 21 Dec 2006 08:51:09 +0000
Dec 21, 2006, 08:51:09 Session 2: EHLO reborn
Dec 21, 2006, 08:51:09 Session 2: 250-mail.logicspot.com Hello reborn ([127.0.0.1]), pleased to meet you
Dec 21, 2006, 08:51:09 Session 2: 250-AUTH LOGIN
Dec 21, 2006, 08:51:09 Session 2: 250-SIZE
Dec 21, 2006, 08:51:09 Session 2: 250 PIPELINING
Dec 21, 2006, 08:51:09 Session 2: MAIL FROM:
Dec 21, 2006, 08:51:09 Session 2: 250 whelpsecondly@accor.com.br... Sender OK
Dec 21, 2006, 08:51:09 Session 2: RCPT TO:
Dec 21, 2006, 08:51:09 Session 2: 250 info@logicspot.com... Recipient OK
Dec 21, 2006, 08:51:09 Session 2: DATA
Dec 21, 2006, 08:51:09 Session 2: 354 Start mail input; end with .
Dec 21, 2006, 08:51:10 Session 2: Received end of data, mail size 3kB
Dec 21, 2006, 08:51:10 Session 2: (Delay Filter) Start delay
Dec 21, 2006, 08:51:31 Session 2: (Delay Filter) Stop delay
Dec 21, 2006, 08:51:31 Session 2: (Delay Filter) Filter result is accept/deliver
Dec 21, 2006, 08:51:31 Session 2: (Attachment Filter) Filter result is accept/deliver
Dec 21, 2006, 08:51:31 Session 2: (SpamAssassin) Executing: sa\spamassassin.exe -x -c "sa\ruleset" -e 255
Dec 21, 2006, 08:52:02 Session 2: (SpamAssassin) Command execution timed out
Dec 21, 2006, 08:52:02 Session 2: (SpamAssassin) Filter result is accept/deliver (unknown result)
Dec 21, 2006, 08:52:02 Session 2: Incoming mail action: accept/deliver (unknown result)
Dec 21, 2006, 08:52:03 Session 2: 250 Message accepted for delivery
Re: SpamAssassin being ignored? [message #410 is a reply to message #409] Thu, 21 December 2006 11:56 Go to previous message
support
Messages: 918
Registered: April 2004
Senior Member
> I can see only two extra X_ header fields (X_MimeOLE and
> X_MSMail_Priority) being added and the SPAM scoring, etc, is
> non-existent.

Look for "X-" headers, not "X_" headers.
>
> Dec 21, 2006, 08:52:02 Session 2: (SpamAssassin) Command
> execution timed out

If SpamAssassin times out, it is probably because automatic expiry did not terminate within the timeout configured for the filter. For this reason we do not set a timeout in the default configuration of the SpamAssassin filter.
If you want to keep the timeout, run expire.bat regularly (you can use the Windows task scheduler for this). You should also set

bayes_auto_expire 0

in the local.cf file.
NoSpamToday! version 3 will do Bayes database expiry itself, but until then the policy lined out here works best.



Customer Support
Byteplant GmbH
Re: SpamAssassin being ignored? [message #411 is a reply to message #409] Fri, 22 December 2006 03:07 Go to previous message
Heidner
Messages: 121
Registered: February 2005
Senior Member

Meanwhile with version 2.xxx you can force the expiration at one of your slower times (mine is 2AM)... by creating a .bat file which contains something like:


cd your_drive_letter:\program files\no spam today!
sa\sa-learn.exe -C sa\ruleset --showdots --force-expire
Re: SpamAssassin being ignored? [message #412 is a reply to message #409] Tue, 10 March 2009 18:40 Go to previous message
Patrick DUMOLEYN
Messages: 1
Registered: March 2009
Junior Member
I've the same trouble, but bayes_auto_expire is already 0. I have now 172.000 words in the SpamAssassin database, its size is 15.424 kbytes.

Mar 10, 2009, 18:21:53 Session 13: Connection from 62.4.16.80 accepted on 194.79.174.227:25
Mar 10, 2009, 18:21:54 Session 13: X-NoSpamToday-MessageID: 49B6A1B2000D0000
Mar 10, 2009, 18:21:54 Session 13: From: algoris@cvm.fr
Mar 10, 2009, 18:21:54 Session 13: To: algoris@cvm.fr
Mar 10, 2009, 18:21:54 Session 13: Subject: Repair your main tool
Mar 10, 2009, 18:21:54 Session 13: (Whitelist) Filter result is accept/deliver
Mar 10, 2009, 18:21:54 Session 13: (Blacklist) Filter result is accept/deliver
Mar 10, 2009, 18:21:54 Session 13: Received end of data, mail size 3kB
Mar 10, 2009, 18:22:12 Session 13: (DNSBL Filter) Filter result is accept/deliver
Mar 10, 2009, 18:22:12 Session 13: (Delay Filter) Start delay
Mar 10, 2009, 18:22:29 Session 13: (Delay Filter) Stop delay
Mar 10, 2009, 18:22:29 Session 13: (Delay Filter) Filter result is accept/deliver
Mar 10, 2009, 18:24:30 Session 13: (SpamAssassin) Command execution timed out
Mar 10, 2009, 18:24:30 Session 13: (SpamAssassin) Filter result is accept/deliver (unknown result)
Mar 10, 2009, 18:24:31 Session 13: (Mail Storage) Message cached in D:\No Spam Today!\Storage\gateway_49B6A1B2000D0000.eml
Mar 10, 2009, 18:24:31 Session 13: Incoming mail action: accept/deliver (unknown result)
Mar 10, 2009, 18:24:33 Session 13: Connection closed by client
Mar 10, 2009, 18:24:33 Session 13: Connection from 62.4.16.80 closed

What to do ?

Thanks for your help.
Re: SpamAssassin being ignored? [message #413 is a reply to message #412] Wed, 11 March 2009 17:19 Go to previous message
support
Messages: 918
Registered: April 2004
Senior Member
Patrick DUMOLEYN wrote:

> Mar 10, 2009, 18:24:30 Session 13: (SpamAssassin) Command
> execution timed out

Give SpamAssassin more time, and disable the timeout (2 minutes may be a too short). Usually the MTA submitting the message has a timeout itself, and if it hasn't there is always NoSpamToday!'s timeout, so there is no chance for SpamAssassin instances staying around forever.

If everything is OK, however, processing should not take more than a few seconds on average. If processing times are always in the range of several minutes, there might be something wrong with your setup. To thoroughly test the SpamAssassin filter, use the setup dialog (advanced options enabled). You can tweak and test the commandline options (try -D for debug output).



Customer Support
Byteplant GmbH
Previous Topic: Spamassassin rules
Next Topic: image plugin
Goto Forum:
  


Current Time: Tue Sep 27 02:10:17 CEST 2016