You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Rejaine Monteiro <re...@bhz.jamef.com.br> on 2006/11/01 14:24:38 UTC

How to not delivery messages when spamc gives imeout

Hi,


My qmail-scanner+spamassasin  works extremely well.

The only problem is when the spam processing server ever die mail 
continues to be processed without spamassassin. 

My spamc options on qmail-scanner-pl olny have "-c " option  (my 
$spamc_options=' -c ';)
So, the default timeout  is used (600 seconds)

Here is an example of the log file when this is happening:

Nov  1 09:49:11 serv spamc[11540]: connect(AF_INET) to spamd at 
127.0.0.1 failed, retrying (#1 of 3): Connection refused
Nov  1 09:49:12 serv spamc[11540]: connect(AF_INET) to spamd at 
127.0.0.1 failed, retrying (#2 of 3): Connection refused
Nov  1 09:49:13 serv spamc[11540]: connect(AF_INET) to spamd at 
127.0.0.1 failed, retrying (#3 of 3): Connection refused
Nov  1 09:49:14 serv spamc[11540]: connection attempt to spamd aborted 
after 3 retries
Nov  1 09:49:14 srv qmail-scanner[10390]: 
Clear:RC:0(82.135.252.97):SA:0(?/?): 102.8215 1114 
cecilia@engleepl.com.sg malu@domain.com.br best_products_the_industry 
<11...@srv> orig-srv116238524754010390:1114 
1162385248.10399-0.srv:520

In that case above, spamd deamon is running, but 783 port not respoding...

I'm  using MONIT to restart spamd daemon if  783 port is not respoding 
or daemon is not running.
Monit execute a spamd service recovery very quickly,  and all becomes to 
work , but all spam received (hundreds) before recovery are delivery to 
user...

Does anyone have any idea how to NOT delivery messages in case of any 
problems with  spamassassin (like requeue or other idea)?
And why spamd/spamc dies or timeout sometimes?