Mailscanner (or rather clam AV) tagging some messages as "other infection".

[Scott Silva]

on 8-26-2008 9:40 AM Jan Johansson spake the following:
>> I have a few in my quarantine.. But I see NOTHING which would explain
> it.. 
> 
> Belay that... So, would setting Deliver Unparsable TNEF = yes cure this
> problem (YES I know it is not MY problem, but the customer want these
> mails to go through.
> 
> Aug 26 14:38:48 mx2 check[5521]: Expanding TNEF archive at
> /var/spool/MailScanner/incoming/5521/260931BAC006.67447/winmail.dat
> Aug 26 14:38:48 mx2 check[5521]: Corrupt TNEF winmail.dat that cannot be
> analysed in message 260931BAC006.67447
> Aug 26 14:38:48 mx2 check[5521]: Saved entire message to
> /var/spool/MailScanner/quarantine/20080826/260931BAC006.67447
> Aug 26 14:38:49 mx2 check[5521]: Requeue: 260931BAC006.67447 to
> 2F0741BAC007
> Aug 26 14:38:49 mx2 check[5521]: Logging message 260931BAC006.67447 to
> SQL
> 
It should. Shouldn't take too long to test it, especially if you have a 
quarantined sample.

-- 
MailScanner is like deodorant...
You hope everybody uses it, and
you notice quickly if they don't!!!!

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 250 bytes
Desc: OpenPGP digital signature
Url : http://lists.mailscanner.info/pipermail/mailscanner/attachments/20080826/ef15e812/signature.bin