<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1170" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV>Julian,</DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>What would be the process roadmap that occurs when
both virus and spam checking is enabled and we start to get build up of email in
the mqueue.in dir.</FONT></DIV>
<DIV><FONT face=Arial size=2>When we turn off the spam checking the mqueue.in
starts to clear out. Turn Spam checking back on system runs normal until
something causes it to return to a buildup in mqueue.in once again. Could
be days before we see this or hours still looking for something in the log files
to indicate reason but have yet to see anything or any patterns.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Normal operation 100-200 messages in dir
+or- 30%</FONT></DIV>
<DIV><FONT face=Arial size=2>When mqueue.in starts to build up I notice this
from log</FONT></DIV>
<DIV>May 12 16:03:45 postman MailScanner[8224]: New Batch: Found 500 messages
waiting <BR>May 12 16:03:45 postman MailScanner[8224]: New Batch: Scanning 44
messages, 341312 bytes <BR>May 12 16:03:45 postman MailScanner[8224]: Spam
Checks: Starting <BR></DIV>
<DIV><FONT face=Arial size=2>New Batch will continue to increase scanning can
jump around on messages maybe 9 or as above 44 no pattern</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial><FONT size=2>Using Sophos for virus protection using
SpamAssassin with<STRONG> </STRONG>spam list ORDB-RBL Infinite-Monkeys #
MAPS-RBL+ costs money Sendmail calls this directly as we pay for this service
and is picked up on a secondary machine that gets updates from
MAPS-RBL+</FONT></FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Any ideas or is more information required, Julian
you have already reviewed our system and told us it was large enough to handle
the email we have coming through the system. The temp disk suggestion that
you gave me, did not work as I currently do not have the ability to do that with
the current kernel. I will have to try that but in the mean time I'm at a
stand still on what is causing this issue.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Thanks in advance</FONT></DIV>
<DIV><FONT face=Arial size=2>Steve</FONT></DIV></BODY></HTML>