Message being scanned that shouldn't be.

Julian Field MailScanner at
Thu Aug 13 11:31:26 IST 2009

I have fixed this problem for you, and also an important bug in the code 
that cleans some types of infections out of archives in messages.
Please upgrade to 4.78.9 and these problems should both be fixed.


On 12/08/2009 23:28, Mark Sapiro wrote:
> Mark Sapiro wrote:
>> I think I would have noticed if this had been going on for long. On Aug
>> 5 I upgraded from 4.78.3 to 4.78.7, and before that from 4.78.2 to
>> 4.78.3 on July 31. It happens under both 4.78.7 and 4.78.8 with this
>> one message. At least some other locally originating messages
>> including a test sent in the same way are properly not scanned.
> Actually, I don't know that they aren't virus scanned. I only know that
> they don't get added MailScanner headers.
>> Is it possible that the rearrangement of the virus/spam scanning code
>> in 4.78.3 et. seq. is allowing messages to be virus scanned even if
>> Scan Messages is 'no'?


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