optimisation hints required & broken links on wiki

Randal, Phil prandal at herefordshire.gov.uk
Tue Oct 9 12:24:29 IST 2007


I think you'll find that the ordb rbl is long dead.

Remove it and see if that helps.

Phil

--
Phil Randal
Network Engineer
Herefordshire Council
Hereford, UK  

> -----Original Message-----
> From: mailscanner-bounces at lists.mailscanner.info 
> [mailto:mailscanner-bounces at lists.mailscanner.info] On Behalf 
> Of Sandro Dentella
> Sent: 09 October 2007 11:14
> To: mailscanner at lists.mailscanner.info
> Cc: Giulio Patisso
> Subject: optimisation hints required & broken links on wiki
> 
> Hi,
> 
>   I 'inherited' in these days a mailserver in which there are 
> huge delays. I
>   need to optimize but reading the wiki I discovered some 
> relevant links are
>   broken, namely:
> 
>   How to run a DCC:
>        http://www.mailscanner.info/serve/cache/312.html
> 
>   Bayes growing out of control
>        http://www.mailscanner.info/serve/cache/317.html
>   
>   How to manually train SpamAssassin:
>       http://www.sng.ecs.soton.ac.uk/mailscanner/serve/cache/98.html
> 
>   I'd appreciate any hint on how to get to those pages.
> 
> 
>   In the meanwhile I'like to better understand where I should 
> concentrate to
>   get a more responsive server.  Main problem is that often 
> the queue goes
>   higher that 5000 messages and some messages are delivered 
> after 1 hour and
>   even more.
> 
>   My hardware setup should be quite fast:
> 
>   * dual xeon 3GB server - 4GB RAM around 50.000 mail/day 
> concentrated in
>   * working time postfix on debian sarge - mailscanner 4.57.6 
> DNS is local
>   * (named from bind9) load average is normally low (1-4) cpu 
> around 4%
>   
> 
>   Max Unscanned Messages Per Scan = 10
>   Max Unsafe Messages Per Scan = 10
>   Spam List = ORDB-RBL
> 
>   in this moment average time is high:
> 
>      Batch (10 messages) processed in 51.55 seconds 
>      Batch (12 messages) processed in 57.42 seconds 
>      Batch (13 messages) processed in 46.37 seconds 
>      Batch (14 messages) processed in 52.74 seconds 
>      Batch (11 messages) processed in 46.81 seconds 
>      Batch (12 messages) processed in 48.57 seconds 
>      Batch (10 messages) processed in 29.24 seconds 
>      Batch (12 messages) processed in 42.29 seconds 
>      Batch (14 messages) processed in 36.74 seconds 
>      Batch (10 messages) processed in 35.31 seconds 
>      Batch (12 messages) processed in 41.79 seconds 
>      Batch (10 messages) processed in 42.96 seconds 
> 
>      and later:
> 
>       Batch (12 messages) processed in 119.03 seconds 
>       Batch (12 messages) processed in 113.34 seconds 
>       Batch (12 messages) processed in 144.11 seconds 
>       Batch (10 messages) processed in 142.57 seconds 
>       Batch (10 messages) processed in 148.63 seconds 
>       Batch (13 messages) processed in 120.17 seconds 
>       Batch (13 messages) processed in 109.28 seconds 
>       Batch (11 messages) processed in 152.12 seconds 
>       Batch (10 messages) processed in 226.92 seconds
> 
>   compared with what stated in the wiki (below 3 seconds)
>   Is there a way to understand how is time spent?
> 
> 
>   According to ps ax, MailScanner is mainly busy with 
>   SpamAssassin
> 
>  9030 ?        S      0:08 MailScanner: checking with SpamAssassin
> 
>   I'd really appreciate any hint / document to read. This situation is
>   becoming more and more important to me...
>   
>   Tanks a lot in advance
>   sandro
>   *:-)
> -- 
> 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