Cached Timeout MailScanner

Joey Casas Joey.Casas at nexusmgmt.com
Wed May 27 13:56:02 IST 2009


In recent experience on my systems, this was due to an increase in the size of some spam. I also believe it was related to an increase in the number of rules I have enabled recently. I checked the size of the emails that were involved in the timeouts and they were generally larger than 50kbytes. There are many potential causes however and anything that can cause SA to run longer than the timeout in MailScanner.conf can generate these. Ultimately I increased my timeout value.

SpamAssassin Timeout =

I believe the "failure x of 20" is saying that soon (if the count reaches 20) MailScanner will disable SA checks and pass emails unscanned. This is to prevent SA failures from causing a full mail stoppage.

Joey Casas
-------------------------------------------
Linux Engineering Team
n|m Nexus Management
4 Industrial Parkway
Suite 101
Brunswick, Maine 04011
 
Tel (US)	: 1 207 319 1105
Tel (UK)	: 0207 100 4968 x421
Cell (US)	: 1 207 607 1047
Fax		: 1 207 725 8552
SIP: 0421 at pbx.nexusmgmt.com
Nexus Management, Inc.│ Registered Office:  4 Industrial Parkway, Suite 101, Brunswick, Maine.  04011│Company No. 19891257D, Registered in Maine│ A member of the Nexus Management Plc group of companies


-----Original Message-----
From: mailscanner-bounces at lists.mailscanner.info [mailto:mailscanner-bounces at lists.mailscanner.info] On Behalf Of shyam hirurkar
Sent: Wednesday, May 27, 2009 8:37 AM
To: MailScanner discussion
Subject: Re: Cached Timeout MailScanner

One more error I am getting like below

SpamAssassin timed out (with no network checks) and was killed, failure 15 of 20

I am not able to understand the where i went wrong..

Thanks,
Shyam


On Wed, May 27, 2009 at 5:37 PM, shyam hirurkar <shyamph at gmail.com> wrote:


	Hi All,
	
	
	Even I observe the mailq was 50 and RAM was being utilized  60% and swap not at all used. Still I am getting the same error in maillog.... any other reason...as spams are passing...
	
	
	Thanks and Regards,
	Shyam


	On Wed, May 27, 2009 at 3:58 PM, Martin Hepworth <maxsec at gmail.com> wrote:
	

		Depends on the amount of of traffic and size of the emails, but that should be good enough for a a few 100k of emails per day.


		2009/5/27 shyam hirurkar <shyamph at gmail.com>
		

			Hi ,
			
			Thanks for the link,
			
			
			My server is running dual core,4GB ram and RAID 5 of 160GB, Hope this is good enough to run MailScanner. Is there any else i need to look at..
			
			Thanks,
			Shyam


			On Wed, May 27, 2009 at 3:14 PM, Martin Hepworth <maxsec at gmail.com> wrote:
			

				Ah that's spamassassin timing out not the cache.

				see

				http://wiki.mailscanner.info/doku.php?id=maq:index#getting_the_best_out_of_spamassassin
				http://wiki.mailscanner.info/doku.php?id=maq:index#optimization_tips

				and 

				http://wiki.mailscanner.info/doku.php?id=documentation:test_troubleshoot:performance&s=performance


				2009/5/27 shyam hirurkar <shyamph at gmail.com>


					Hi All,
					
					This is the error i am getting in the log
					
					May 27 15:03:47 mx1 MailScanner[31435]: SpamAssassin timed out and was killed, failure 3 of 10
					May 27 15:03:48 mx1 MailScanner[31435]: Message A76B125A8047.9FN8C from xxx.xxx.xxx.xxx (username at yahoo.co.in) to domain.com is not spam, SpamAssassin (not cached, timed out)
					
					Regards,
					Shyam


					On Wed, May 27, 2009 at 3:04 PM, shyam hirurkar <shyamph at gmail.com> wrote:
					

						Hi ,
						
						I have removed the cache dba nd restarted the mailscanner but still i am able to see cached not timed out error in the log.
						
						Any thing else i needs to be done ??
						
						Thanks and Regards,
						Shyam
						
						
						On Thu, May 21, 2009 at 9:18 PM, Scott Silva <ssilva at sgvwater.com> wrote:
						

							on 5-21-2009 3:17 AM shyam hirurkar spake the following:
							
							> Hi ,
							>
							> Thanks for the input but small question how often i need to do is there
							> any automation for this.
							>
							
							You only need to do this if the cache becomes corrupt. It could be days or
							years, you never know when a db can get corrupted. I'm not sure if you could
							automate this. I guess if there is a utility in sqlite that can check for
							corruption and exit with an errorlevel, you could automate this in a startup
							script.
							
							
							
							--
							MailScanner mailing list
							mailscanner at lists.mailscanner.info
							http://lists.mailscanner.info/mailman/listinfo/mailscanner
							
							Before posting, read 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
					
					Support MailScanner development - buy the book off the website!
					
					




				-- 
				Martin Hepworth
				Oxford, UK
				

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




		-- 
		Martin Hepworth
		Oxford, UK
		

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





More information about the MailScanner mailing list