"Message attempted to kill MailScanner"

Nigel Kendrick support-lists at petdoctors.co.uk
Wed Jun 3 12:52:56 IST 2009


-----Original Message-----
From: mailscanner-bounces at lists.mailscanner.info
[mailto:mailscanner-bounces at lists.mailscanner.info] On Behalf Of Julian
Field
Sent: Tuesday, June 02, 2009 11:45 AM
To: MailScanner discussion
Subject: Re: "Message attempted to kill MailScanner"

And if you are using Postfix, I would strongly advise you upgrade to 
4.77. Should only take you a couple of minutes, upgrade_MailScanner_conf 
will do the heavy lifting for you.





Thanks to Julian and martin for the replies.

I have upgraded to the latest 4.77, but no inbound mail is being processed.
I have deleted all the queued messages and sent through a test one that just
has my sig and the time in it, but it never leaves the HOLD queue.

Log shows:

Jun  3 12:41:25 gospond postfix/smtpd[19864]: connect from
c2beaomr06.btconnect.com[213.123.26.184]
Jun  3 12:41:25 gospond postfix/smtpd[19864]: 40BC11B98058:
client=c2beaomr06.btconnect.com[213.123.26.184]
Jun  3 12:41:25 gospond postfix/cleanup[19867]: 40BC11B98058: hold: header
Received: from c2beaomr06.btconnect.com (c2beaomr06.btconnect.com
[213.123.26.184])??by gospond.home.local (Postfix) with ESMTP id
40BC11B98058??for <nigel.kendrick at xxxxxxxxxx>; Wed,  3 Jun 2009 12 from
c2beaomr06.btconnect.com[213.123.26.184]; from=<nigel.kendrick at yyyyyyyyyy>
to=<nigel.kendrick at xxxxxxxxxx> proto=ESMTP helo=<c2beaomr06.btconnect.com>
Jun  3 12:41:25 gospond postfix/cleanup[19867]: 40BC11B98058:
message-id=<465FFE92CCE848E0A7032D39BC67AD6B at SUPPORT01V>
Jun  3 12:41:27 gospond MailScanner[19828]: New Batch: Scanning 1 messages,
5869 bytes 
Jun  3 12:41:28 gospond MailScanner[19868]: MailScanner E-Mail Virus Scanner
version 4.77.9 starting... 
Jun  3 12:41:28 gospond MailScanner[19868]: Read 857 hostnames from the
phishing whitelist 
Jun  3 12:41:28 gospond MailScanner[19868]: Read 10610 hostnames from the
phishing blacklists 
Jun  3 12:41:28 gospond MailScanner[19868]: Using SpamAssassin results cache

Jun  3 12:41:28 gospond MailScanner[19868]: Connected to SpamAssassin cache
database 
Jun  3 12:41:28 gospond MailScanner[19868]: Enabling SpamAssassin
auto-whitelist functionality... 
Jun  3 12:41:36 gospond MailScanner[19868]: Connected to Processing Attempts
Database 
Jun  3 12:41:36 gospond MailScanner[19868]: Found 3 messages in the
Processing Attempts Database 
Jun  3 12:41:36 gospond MailScanner[19868]: Using locktype = flock
Jun  3 12:42:14 gospond dovecot: IMAP(nkendrick): Disconnected: Logged out
Jun  3 12:42:14 gospond dovecot: imap-login: Login: user=<nkendrick>,
method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured
Jun  3 12:46:06 gospond MailScanner[19868]: Making attempt 2 at processing
message 40BC11B98058.AB9BA 
Jun  3 12:46:06 gospond MailScanner[19868]: New Batch: Scanning 1 messages,
5869 bytes 
Jun  3 12:46:07 gospond MailScanner[19923]: MailScanner E-Mail Virus Scanner
version 4.77.9 starting... 
Jun  3 12:46:07 gospond MailScanner[19923]: Read 857 hostnames from the
phishing whitelist 
Jun  3 12:46:07 gospond MailScanner[19923]: Read 10610 hostnames from the
phishing blacklists 
Jun  3 12:46:08 gospond MailScanner[19923]: Using SpamAssassin results cache

Jun  3 12:46:08 gospond MailScanner[19923]: Connected to SpamAssassin cache
database 
Jun  3 12:46:08 gospond MailScanner[19923]: Enabling SpamAssassin
auto-whitelist functionality... 
Jun  3 12:46:15 gospond MailScanner[19923]: Connected to Processing Attempts
Database 
Jun  3 12:46:15 gospond MailScanner[19923]: Found 3 messages in the
Processing Attempts Database 
Jun  3 12:46:15 gospond MailScanner[19923]: Using locktype = flock  

That's it and everything's gone quiet.

MailScanner --lint runs through OK.

Hay-elp!

Nigel



More information about the MailScanner mailing list