Problem Messages

Julian Field MailScanner at
Tue Jun 16 11:55:25 IST 2009

On 16/06/2009 11:15, Remco Barendse wrote:
> On Mon, 15 Jun 2009, Julian Field wrote:
>> On 15/06/2009 11:17, Remco Barendse wrote:
>>>  On Mon, 15 Jun 2009, Julian Field wrote:
>>> >  That's quite normal, it processed the message successfully (apart 
>>> from >  you needing to update your copy of ClamAV). So whatever was 
>>> causing your >  message to kill MailScanner has gone away and isn't 
>>> doing it now.
>>>  Strange, another problem meBssage appeared over the weekend, i ran it
>>>  through MailScanner in the same way and also this message processed 
>>> well.
>>>  I'm a bit puzzled why these "Problem Messages"  messages keep 
>>> appearing
>>>  but at the same time the message gets quarantined and moved to the
>>>  quarantine properly. Is there maybe some bug in the thingy that 
>>> controls
>>>  Processing.db ? I get a new mail message reporting the same problem 
>>> every
>>>  hour or so, until i nuke Processing.db
>>>  Is there any way to increase the log level of "Problem Messages" to 
>>> get
>>>  some more info from that?  (If these messages come up very rarely 
>>> anyways,
>>>  why not be more verbose)
>> What more info would you like? As all I know is that the message 
>> caused MailScanner to crash somehow, there's almost no information to 
>> give you, sorry.
> OK, i hoped it was possible to include some information on 
> specifically what caused the crash.
> Strange, i have never seen this behaviour on any server running 
> MailScanner, just the server that was newly installed. Maybe i did 
> something wrong or some of the perl packages did not compile properly.
>> I should add some code to remove the problem message from the 
>> Processing.db when it gets quarantined though.
> Would be neat :)
I've just tested it, and it's actually working just how I originally 
intended. When a message gets quarantined for being tried too many 
times, it moves it into the "archive" table, which is what "MailScanner 
--processing" reports (in addition to the main table of current messages).

Would you rather I scrapped the "archive" table altogether? It's just 
that it is a good way to show you how many messages are being 
quarantined for crashing MailScanner, rather than you having to look in 
the logs.

What would you all like me to do with this problem?


Julian Field MEng CITP CEng
Buy the MailScanner book at

Need help customising MailScanner?
Contact me!
Need help fixing or optimising your systems?
Contact me!
Need help getting you started solving new requirements from your boss?
Contact me!

PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
Follow me at and

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