MailScanner keeps dying on my CentOS 6.2 Server

[Mail Lists]

On 04/24/2012 08:58 AM, Stef Morrell wrote:
> Brian - if you look towards the bottom of MailScanner.conf you will 
> see a couple of settings # Set Debug to "yes" to stop it running as a 
> daemon and just process # one batch of messages and then exit. Debug = 
> no # Do you want to debug SpamAssassin from within MailScanner? Debug 
> SpamAssassin = no Set Debug to yes and you will get a lot of 
> additional output which is useful for diagnostics. It looks like it 
> got through SpamAssassin fine, so I don't think you'll need to debug 
> that as well. Regards Stef 

    Stef,

     Well debug shows no more to me then I already know.. Not much. here 
is the results.

Starting MailScanner daemons:
          incoming postfix:                                 [  OK  ]
          outgoing postfix: Apr 24 10:39:16 poweredge 
postfix/postfix-script[30661]: starting the Postfix mail system
                                                            [  OK  ]
          MailScanner:       Apr 24 10:39:16 poweredge 
postfix/master[30662]: daemon started -- version 2.6.6, configuration 
/etc/postfix
Apr 24 10:39:20 poweredge MailScanner[30680]: MailScanner E-Mail Virus 
Scanner version 4.84.5 starting...
Apr 24 10:39:20 poweredge MailScanner[30680]: Reading configuration file 
/etc/MailScanner/MailScanner.conf
Apr 24 10:39:20 poweredge MailScanner[30680]: Reading configuration file 
/etc/MailScanner/conf.d/README
Apr 24 10:39:20 poweredge MailScanner[30680]: Config: calling custom 
init function SQLBlacklist
Apr 24 10:39:20 poweredge MailScanner[30680]: Starting up SQL Blacklist
Apr 24 10:39:20 poweredge MailScanner[30680]: Read 2 blacklist entries
Apr 24 10:39:20 poweredge MailScanner[30680]: Config: calling custom 
init function MailWatchLogging
Apr 24 10:39:20 poweredge MailScanner[30680]: Started SQL Logging child
Apr 24 10:39:20 poweredge MailScanner[30680]: Config: calling custom 
init function SQLWhitelist
Apr 24 10:39:20 poweredge MailScanner[30680]: Starting up SQL Whitelist
Apr 24 10:39:20 poweredge MailScanner[30680]: Read 3 whitelist entries
Apr 24 10:39:21 poweredge MailScanner[30680]: Using SpamAssassin results 
cache
Apr 24 10:39:21 poweredge MailScanner[30680]: Connected to SpamAssassin 
cache database
Apr 24 10:39:21 poweredge MailScanner[30680]: Enabling SpamAssassin 
auto-whitelist functionality...
Apr 24 10:39:26 poweredge MailScanner[30680]: Connected to Processing 
Attempts Database
Apr 24 10:39:26 poweredge MailScanner[30680]: Found 0 messages in the 
Processing Attempts Database
Apr 24 10:39:26 poweredge MailScanner[30680]: lock.pl sees Config  
LockType =  flock
Apr 24 10:39:26 poweredge MailScanner[30680]: lock.pl sees have_module =  0
Apr 24 10:39:26 poweredge MailScanner[30680]: Using locktype = flock
Apr 24 10:39:26 poweredge MailScanner[30680]: New Batch: Scanning 1 
messages, 1469 bytes
Apr 24 10:39:26 poweredge MailScanner[30680]: Created attachment dirs 
for 1 messages
Apr 24 10:39:26 poweredge MailScanner[30680]: Completed checking by 
/usr/bin/file
Apr 24 10:39:26 poweredge MailScanner[30680]: Virus and Content 
Scanning: Starting
Apr 24 10:39:26 poweredge MailScanner[30680]: Commencing scanning by 
clamd...
Apr 24 10:39:26 poweredge MailScanner[30697]: Debug Mode Is On
Apr 24 10:39:26 poweredge MailScanner[30697]: Use Threads : NO
Apr 24 10:39:26 poweredge MailScanner[30697]: Socket    : /tmp/clamd.socket
Apr 24 10:39:26 poweredge MailScanner[30697]: IP        : Using Sockets
Apr 24 10:39:26 poweredge MailScanner[30697]: Lock File : NOT USED
Apr 24 10:39:26 poweredge MailScanner[30697]: Time Out  : 300
Apr 24 10:39:26 poweredge MailScanner[30697]: Scan Dir  : 
/var/spool/MailScanner/incoming/30680
Apr 24 10:39:26 poweredge MailScanner[30697]: Clamd : Sending PING
Apr 24 10:39:26 poweredge MailScanner[30697]: Clamd : GOT 'PONG'
Apr 24 10:39:26 poweredge MailScanner[30697]: ClamD is running
Apr 24 10:39:26 poweredge MailScanner[30697]: SENT : CONTSCAN 
/var/spool/MailScanner/incoming/30680
Apr 24 10:39:26 poweredge MailScanner[30680]: Completed scanning by clamd
Apr 24 10:39:26 poweredge MailScanner[30680]: Spam Checks: Starting
Apr 24 10:39:26 poweredge MailScanner[30680]: SpamAssassin cache hit for 
message 774E9E09EE.A14B0
Apr 24 10:39:26 poweredge MailScanner[30680]: Message 774E9E09EE.A14B0 
from 201.234.47.187 (aletajose at informaxinc.com) to tatorz.com is spam, 
SpamAssassin (cached, score=27.117, required 4, autolearn=spam, BAYES_50 
0.80, DRUGS_ERECTILE 1.99, DRUG_ED_ONLINE 0.61, RCVD_IN_BL_SPAMCOP_NET 
1.35, RCVD_IN_BRBL_LASTEXT 1.45, RCVD_IN_PBL 3.33, RCVD_IN_PSBL 2.70, 
RCVD_IN_RP_RNBL 1.31, RCVD_IN_XBL 0.38, RDNS_NONE 0.79, 
SERGIO_SUBJECT_VIAGRA01 0.00, URIBL_AB_SURBL 4.50, URIBL_BLACK 1.73, 
URIBL_DBL_SPAM 1.70, URIBL_JP_SURBL 1.25, URIBL_SBL 1.62, URIBL_WS_SURBL 
1.61)
Apr 24 10:39:26 poweredge MailScanner[30680]: Spam Checks: Found 1 spam 
messages
Apr 24 10:39:26 poweredge MailScanner[30680]: Spam Actions: message 
774E9E09EE.A14B0 actions are store
Apr 24 10:39:26 poweredge MailScanner[30680]: writing to 
/var/spool/MailScanner/quarantine/20120424/spam/774E9E09EE.A14B0: 2
                                                            [  OK  ]

Thanks
-- 
Brian ----- Get the latest Fremont, OH Weather 
http://www.Fremont-OH-Weather.com