<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#333333">
<br>
<blockquote
cite="mid:92A6C87E-284E-4491-BEB6-DB306FDE4139@technologytiger.net"
type="cite">
<div>Evening all, been far too long since I have posted (Been
stupidly busy :-( )</div>
<div><br class="webkit-block-placeholder">
</div>
<div>I would suggest you want to check your Delivery method option at
the bottom MailScanner.conf and make sure it is batch and not queue.
Setting it to queue would invoke this behaviour. Changing the queue
runner settings should not be required. The queue running is called by
Postfix when each process finishes to advise the next to run. The 300
second delay is merely to catch anything that 'got left behind'.</div>
<div><br class="webkit-block-placeholder">
</div>
<div>Drew</div>
<br>
</blockquote>
<br>
Hi Drew,<br>
<br>
Bingo !! <br>
<br>
Changing the Delivery Method from queue to Batch solve the problem !!<br>
<br>
I remember reading the FAQ and it advice me to use "Delivery Method =
queue" for High Volume Mail server.<br>
Good thing is .. Someone already went down this path and update the
FAQ: <a class="moz-txt-link-freetext" href="http://www.mailscanner.info/faq.shtml#11">http://www.mailscanner.info/faq.shtml#11</a><br>
<br>
Thank you for all your help !!<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
</body>
</html>