MailScanner no longer scanning mail

[Julian Field]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



Jody Cleveland wrote:
> Hello,
>
>   
>> Default answer... : change to debug mode and see what it outputs.
>>     
>
> Ok, I switched to debug mode, and this is what I get:
>
> [root at destiny MailScanner]# service MailScanner start
> Starting MailScanner daemons:
>          incoming postfix:                                 [  OK  ]
>          outgoing postfix:                                 [  OK  ]
>          MailScanner:       In Debugging mode, not forking...
>
>
> And it just sits there. I sent a few messages to it, but after 10 minutes it
> still just sat there. So, I ctrl-z'd to get out of it and looked at the
> maillog. This is what it said:
>
> May  3 07:09:17 destiny postfix/postfix-script: starting the Postfix mail
> system
> May  3 07:09:17 destiny postfix/master[5525]: daemon started -- version
> 2.3.3, configuration /etc/postfix
> May  3 07:09:17 destiny postfix/qmgr[5535]: warning: bounce_queue_lifetime
> is larger than maximal_queue_lifetime - adjusting bounce_queue_lifetime
> May  3 07:09:19 destiny MailScanner[5543]: MailScanner E-Mail Virus Scanner
> version 4.59.4 starting...
> May  3 07:09:19 destiny MailScanner[5543]: Read 778 hostnames from the
> phishing whitelist 
> May  3 07:09:19 destiny MailScanner[5543]: Config: calling custom init
> function SQLBlacklist
> May  3 07:09:19 destiny MailScanner[5543]: Starting up SQL Blacklist
> May  3 07:09:19 destiny MailScanner[5543]: Read 29 blacklist entries
> May  3 07:09:19 destiny MailScanner[5543]: Config: calling custom init
> function MailWatchLogging
> May  3 07:09:19 destiny MailScanner[5543]: Started SQL Logging child
> May  3 07:09:19 destiny MailScanner[5543]: Config: calling custom init
> function SQLWhitelist
> May  3 07:09:19 destiny MailScanner[5543]: Starting up SQL Whitelist
> May  3 07:09:19 destiny MailScanner[5543]: Read 59 whitelist entries
> May  3 07:09:19 destiny MailScanner[5543]: Using SpamAssassin results cache
> May  3 07:09:19 destiny MailScanner[5543]: Connected to SpamAssassin cache
> database 
> May  3 07:09:19 destiny MailScanner[5543]: Enabling SpamAssassin
> auto-whitelist functionality...
> May  3 07:09:22 destiny MailScanner[5543]: lock.pl sees Config  LockType =
> flock 
> May  3 07:09:22 destiny MailScanner[5543]: lock.pl sees have_module =  0
> May  3 07:09:22 destiny MailScanner[5543]: Using locktype = flock
> May  3 07:09:22 destiny MailScanner[5543]: New Batch: Found 1420 messages
> waiting 
> May  3 07:09:22 destiny MailScanner[5543]: New Batch: Scanning 30 messages,
> 151181 bytes 
> May  3 07:09:22 destiny MailScanner[5543]: Created attachment dirs for 30
> messages 
> May  3 07:09:43 destiny MailScanner[5543]: RBL Checks: returned 0
> May  3 07:09:43 destiny MailScanner[5543]: SpamAssassin cache hit for
> message D20223E425E.0C4FB
> May  3 07:09:48 destiny postfix/smtpd[5556]: connect from
> unknown[203.188.225.208]
> May  3 07:09:50 destiny postfix/smtpd[5556]: 435F83E4380:
> client=unknown[203.188.225.208]
> May  3 07:09:50 destiny postfix/smtpd[5554]: connect from
> static-66-16-148-219.dsl.cavtel.net[66.16.148.219]
> May  3 07:09:50 destiny postfix/smtpd[5554]: E7C293E4382:
> client=static-66-16-148-219.dsl.cavtel.net[66.16.148.219]
> May  3 07:09:51 destiny postfix/cleanup[5571]: E7C293E4382: hold: header
> Received: from static-66-16-148-219.dsl.cavtel.net
> (static-66-16-148-219.dsl.cavtel.net [66.16.148.219])??by
> destiny.winnefox.org (Postfix) with SMTP id E7C293E4382??for
> <jackisch at oshkoshpubliclibrary from
> static-66-16-148-219.dsl.cavtel.net[66.16.148.219];
> from=<cservice.refS89652695WO.cm at bbt.com>
> to=<jackisch at oshkoshpubliclibrary.org> proto=SMTP
> helo=<static-66-16-148-219.dsl.cavtel.net>
> May  3 07:09:51 destiny postfix/cleanup[5571]: E7C293E4382:
> message-id=<20070503120950.E7C293E4382 at destiny.winnefox.org>
> May  3 07:09:51 destiny postfix/smtpd[5554]: disconnect from
> static-66-16-148-219.dsl.cavtel.net[66.16.148.219]
>
> Is that helpful at all?
>   
Do
    service MailScanner stop
then wait a few seconds, then
    service MailScaner startin
and that should start incoming mail going into the queue that feeds 
MailScanner, without starting MailScanner itself at all. So then do
    MailScanner -debug
and see what it says. It will sit and wait until it has at least 1 
message to process, then it will process them completely, then 
gracefully die of old age.

Post the entire output of that command.

Then
    service MailScanner stop
again so the incoming queue doesn't keep building up.

Jules

- -- 
Julian Field MEng CITP
www.MailScanner.info
Buy the MailScanner book at www.MailScanner.info/store

MailScanner customisation, or any advanced system administration help?
Contact me at Jules at Jules.FM

PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
For all your IT requirements visit www.transtec.co.uk



-----BEGIN PGP SIGNATURE-----
Version: PGP Desktop 9.6.1 (Build 1012)
Charset: ISO-8859-1

wj8DBQFGOfuIEfZZRxQVtlQRAiCpAKDXOPT7WwMDyKHwAvnNyAEMsS/DdwCg0z/L
Zgkbp+dB9G++9uqTfaqLQ+8=
=IDs4
-----END PGP SIGNATURE-----

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
For all your IT requirements visit www.transtec.co.uk