<div dir="ltr"><div><div>local caching DNS server<br></div>only run a couple of RBL's (no need to run lots)<br></div>drop unknown recipients on the incoming MTA<br></div><div class="gmail_extra"><br clear="all"><div>-- <br>
Martin Hepworth, CISSP<br>Oxford, UK</div>
<br><br><div class="gmail_quote">On 1 May 2013 15:31, Arjan Melein <span dir="ltr"><<a href="mailto:Amelein@dantumadiel.eu" target="_blank">Amelein@dantumadiel.eu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
We're currently getting flooded by spam and every so often our mailscanner is having trouble seems to have trouble keeping up causing our inbound queue to hit 3000+ messages and I am trying to figure out where the processing time is going.<br>
I am getting the impression *something* is causing a delay, I am unsure as to what but I'm thinking in the way of RBL's or DNS...<br>
<br>
The server is a quadcore with 20 MS threads and it can churn through 10-30 average mails per second depending on their size so either e-mails are being delivered faster then they can be scanned or there is indeed a delay somewhere.<br>
<br>
Its a 'new' install (few months old) on FC18. I've seen it clear the 3000 message queue in 5 - 10 minutes after manually stopping and starting mailscanner.<br>
<br>
Any ideas anyone ?<br>
<br>
-<br>
Arjan<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
MailScanner mailing list<br>
<a href="mailto:mailscanner@lists.mailscanner.info">mailscanner@lists.mailscanner.info</a><br>
<a href="http://lists.mailscanner.info/mailman/listinfo/mailscanner" target="_blank">http://lists.mailscanner.info/mailman/listinfo/mailscanner</a><br>
<br>
Before posting, read <a href="http://wiki.mailscanner.info/posting" target="_blank">http://wiki.mailscanner.info/posting</a><br>
<br>
Support MailScanner development - buy the book off the website!<br>
</font></span></blockquote></div><br></div>