[prev in list] [next in list] [prev in thread] [next in thread] 

List:       cobaltfacts
Subject:    Re: [cobaltfacts] Mailscanner and Spamassin problem
From:       "George K C" <gkc () flashmail ! com>
Date:       2005-08-22 8:58:38
Message-ID: 20050822082823.D37FD4FBD3 () sbtho-trivandrum ! com
[Download RAW message or body]

>Hi,
>I've put mailscanner and spamassassin on a raq350 today and run into a
>little problem
>
>Mailscanner can deliver mail fine on its own with spamassassin disabled but
>when I enable spamassassin no mail is processed the output from
>"/etc/rc.d/init.d/sendmail restart; tail -f /var/log/maillog" is:
>Aug 21 17:17:30 muck MailScanner[29291]: MailScanner E-Mail Virus Scanner
>version 4.23-7 starting...
>Aug 21 17:17:33 muck MailScanner[29291]: Enabling SpamAssassin
>auto-whitelist functionality...
>Aug 21 17:17:40 muck MailScanner[29307]: MailScanner E-Mail Virus Scanner
>version 4.23-7 starting...
>Aug 21 17:17:43 muck MailScanner[29307]: Enabling SpamAssassin
>auto-whitelist functionality...
>Aug 21 17:17:46 muck MailScanner[29307]: Using locktype = flock
>Aug 21 17:17:46 muck MailScanner[29307]: New Batch: Scanning 1 messages, 933
>bytes
>Aug 21 17:17:46 muck MailScanner[29307]: TCP Checks: Starting
>Aug 21 17:17:50 muck MailScanner[29309]: MailScanner E-Mail Virus Scanner
>version 4.23-7 starting...
>Aug 21 17:17:53 muck MailScanner[29309]: Enabling SpamAssassin
>auto-whitelist functionality...
>Aug 21 17:17:56 muck MailScanner[29291]: Using locktype = flock
>Aug 21 17:17:56 muck MailScanner[29291]: New Batch: Scanning 1 messages, 933
>bytes
>Aug 21 17:17:56 muck MailScanner[29291]: TCP Checks: Starting
>Aug 21 17:17:57 muck MailScanner[29309]: Using locktype = flock
>Aug 21 17:17:57 muck MailScanner[29309]: New Batch: Scanning 1 messages, 933
>bytes
>Aug 21 17:17:57 muck MailScanner[29309]: TCP Checks: Starting
>
>This showing that mailscanner just seems to stop after a few seconds. I have
>looked at the mailing lists and found a few threads that are of this nature
>but I cannot find a solution. Anybody know where I need to look next to find
>where its going wrong? Is it possible to test spamassassin on its own to
>check its installed properly??
>
>Thanks
>Jason

Try the following to diagnose.
1. Disable spamassassin from MailScanner.conf.
2. Reduce the Max Children to 1
3. Increase Queue Scan Interval to 20

Open two windows. Run
tail -f /var/log/maillog	 in one window
Stop sendmail if it is running. Kill all pids by killall sendmail.
Restart MailScanner from the other window. Verify whether any socket error is there. 
MailScanner may spawn in multiple initially. This is natural.
Revert with Results.

George K Cyriac
Trivandrum, India




_______________________________________________
Cobaltfacts site list
Cobaltfacts@list.cobaltfacts.com
http://list.cobaltfacts.com/mailman/listinfo.cgi/cobaltfacts
[prev in list] [next in list] [prev in thread] [next in thread]