MailScanner Looping?

Edward Dekkers edward at
Fri Nov 13 03:02:34 GMT 2009

> -----Original Message-----
> From: mailscanner-bounces at [mailto:mailscanner-
> bounces at] On Behalf Of Glenn Steen
> Sent: Thursday, 12 November 2009 9:30 PM
> To: MailScanner discussion
> Subject: Re: MailScanner Looping?
> 2009/11/11 Drew Marshall <drew.marshall at>:
> >
> > On 11 Nov 2009, at 07:01, Edward Dekkers wrote:
> >
> >> Could someone have a quick look at the log and make a suggestion
> before I
> >> enable mailscanner again?
> >
> > I think we will need a bit more than the attached to be able to help.
> Can
> > you run mailscanner --lint and also mailscanner --debug (With some
> messages
> > in the hold directory) and see if there is anything a miss. It may
> well be
> > related to this..
> >
> >> System is Ubuntu 9.10 server (recently upgraded from 9.04)
> >
> > As I would expect there have been Perl updates.
> >
> > Drew
> >
> What this sounds like ... is some message "killing" MailScanner... I'm
> not sure (since I haven't looked), but I don't think the version at
> hand has the processing database thing in place (which is designed
> just to catch this type of situation, so that "malformed" messages
> can't take your system down).
> Without the processing thing, one would have to stop MailScanner (and
> postfix), move all the messages out of hold, to some place
> temporary... then move some into hold, run MailScanner --debug, check
> the logs/what happened ... and repeat until the "bad" message was
> identified.
> Hard to be certain, especially since Ed already did away with the
> "evidence" (the errant queue files:-).

Whoops. Sorry, Glenn. I guess a COPY to the postfix "in" queue would have
been smarter than a move for diagnostic purposes.

I've re-enabled mailscanner now and it seems so be doing it's thing
(although with all my messing around re-installing etc. I get an insecure
warning about the "file -T" command - problem for later).

I'll keep an eye on it and get back to you if it does it again. It IS
processing mail correctly at the moment, which may mean it's not a perl
update, however, this has never happened before so it would seem it COULD be
a perl update problem as well.

As for mailscanner --lint and mailscanner --debug, I'm assuming I just run
them when the problem arises? Do I need to stop (/etc/init.d/mailscanner
stop) mailscanner first or one has nothing to do with the other?


This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

More information about the MailScanner mailing list