R: Spamassassin Timeout issue.

Marcello Anderlini m.anderlini at database.it
Wed Sep 10 15:59:25 IST 2008


I beg your pardon but I have the same problem and I looking for a solution
since many month.
 
On my system is installed a dns server resolving also our domain.

Very often during the day, unexpectedly without change nothing spamassassin
starts to run very slowly.
I have followed all the tips founded but without success. Could be a dns
problem ?
This is my extract from my dns configuration. Is it enough to set it also as
a cache dns ?

Thanks and sorry for my worst english.




======================
options {
# file di boot per named
        directory "/var/named";
        forwarders { 83.216.172.1;83.216.172.2;213.234.128.211; };
        query-source address * port 53;
};
 
logging {
  channel local_log {
   /*
    * Use a file channnel. The file is
    * /var/log/named.log. [Why the ".log"
    * suffix?] Keep 2 versions of the file
    * and don't let it get bigger than 1 Mb.
    */
#   file "/var/log/named.log"
   file "/var/log/named/named.log"
   versions 2 size 1M;
   print-time yes;
  };
  category default {
   /*
    * Send every log category to the
    * local_log channel defined above.
    */
   local_log;
  };
};
======================

 
Dr. Marcello Anderlini
m.anderlini at database.it
---------------------------------------------
Database Informatica S.r.l.
Microsoft Certified Partner
Tel.  +39059775070
Fax. +39059779545
http://www.database.it <http://www.database.it/> 
--------------------------------------------- 
 

________________________________

Da: mailscanner-bounces at lists.mailscanner.info
[mailto:mailscanner-bounces at lists.mailscanner.info] Per conto di Alex Neuman
van der Hans
Inviato: mercoledì 10 settembre 2008 16.22
A: MailScanner discussion
Cc: MailScanner discussion
Oggetto: Re: Spamassassin Timeout issue.


When spamassassin times out, it usually is because of a DNS issue.
Restarting works in your case probably because people trying to connect to
your server "back off" when you restart it because to them it looks like
your server died. They take pity and don't bother it for a while. When they
see it back online, the load and backlog rises. 

Sent from my iPhone

On Sep 10, 2008, at 9:05 AM, "Swati Meghanand" <swati.meghanand at gmail.com>
wrote:



	hi,

	I am not running any name server on the same machine, actually I am
having a fail-over cluster of 3 machine having same configuration/setting I
facing this prob in 2 machines the another thts 3rd is running smoothly...
	

	When I restart machine it works well for atleast 12-15 Hrs.(But
restarting Mailscanner didn't helped me)

	Did u mean this could be a DNS related issue....

	Regards,

	Swati Meghanand


	2008/9/10 Alex Neuman van der Hans < <mailto:alex at rtpty.com>
alex at rtpty.com>
	

		It's actually quite clearly indicating the opposite. You are
not reading the logs right. If spamassassin is timing out, you need to take
care of that. What caching nameserver are you running on that box?
		
		Sent from my iPhone 


		On Sep 10, 2008, at 3:54 AM, "Swati Meghanand" <
<mailto:swati.meghanand at gmail.com> swati.meghanand at gmail.com> wrote:
		
		

			Hi,
			
			I'm using mailscanner on a busy mail gateways from
serveral months, which was working fine so far.From last few days I noticed
incresed no of spam mails as well log Filtering queues (ofcourse slow
processing of mailscanner).In log file of mailscanner I found following
lines,
			
			Sep 10 04:47:29 localhost MailScanner[11027]: Virus
and Content Scanning: Starting
			Sep 10 04:47:37 localhost MailScanner[8400]:
SpamAssassin timed out and was killed, failure 8 of 20
			Sep 10 04:47:37 localhost MailScanner[8680]:
SpamAssassin timed out and was killed, failure 14 of 20
			Sep 10 04:47:38 localhost MailScanner[8680]: Message
1KdL6x-0005q5-L3 from xx.xx.xx.xx (xxx at xxx.x) to xxx.xx is not spam,
SpamAssassin (not cached, timed out)
			Sep 10 04:47:38 localhost MailScanner[8400]: Message
1KdLDG-0006se-Ox from xx.xx.xx.xx (xxx at xx.xxx) to xxx.xx is not spam,
SpamAssassin (not cached, timed out)
			
			it clealy indicates mailscanner is not (able to)
scanning messages.
			
			Any idea about this issue.
			
			Thanks in advance :-)
			
			Regards
			
			Swati Meghanand
			
			
			
			
			-- 
			MailScanner mailing list
			<mailto:mailscanner at lists.mailscanner.info>
mailscanner at lists.mailscanner.info
	
<http://lists.mailscanner.info/mailman/listinfo/mailscanner>
http://lists.mailscanner.info/mailman/listinfo/mailscanner
			
			Before posting, read
<http://wiki.mailscanner.info/posting> http://wiki.mailscanner.info/posting
			
			Support MailScanner development - buy the book off
the website!
			

		-- 
		MailScanner mailing list
		<mailto:mailscanner at lists.mailscanner.info>
mailscanner at lists.mailscanner.info
		<http://lists.mailscanner.info/mailman/listinfo/mailscanner>
http://lists.mailscanner.info/mailman/listinfo/mailscanner
		
		Before posting, read <http://wiki.mailscanner.info/posting>
http://wiki.mailscanner.info/posting
		
		Support MailScanner development - buy the book off the
website!
		


	-- 
	MailScanner mailing list
	mailscanner at lists.mailscanner.info
	http://lists.mailscanner.info/mailman/listinfo/mailscanner
	
	Before posting, read <http://wiki.mailscanner.info/posting>
http://wiki.mailscanner.info/posting
	
	Support MailScanner development - buy the book off the website! 
	


-- 
Messaggio verificato dal servizio antivirus di Database Informatica
<http://www.database.it/> . 


-- 
Messaggio verificato dal servizio antivirus di Database Informatica



More information about the MailScanner mailing list