Chris Hastie wrote: > > It looks like you've answered your own question. If ClamAV can find them > at this point then the fault does not seem to lie with ClamAV. Whatever > automated process you are using to scan incoming mail, it is either not > presenting the mail to ClamAV, not doing so in a format that ClamAV can > cope with, not correctly interpreting ClamAV's response, not acting on > that response as you would like or exhibiting some other problem that > I've missed (don't you just love caveats?!). > > I'm not familiar with Exim or Exiscan so I can't really be more help > than that. I use Postfix and Amavisd with Clamd and seem to trap pretty > much all the malware that comes my way. But I rely on Amavisd to > deconstruct MIME messages, decode UUEncode and uncompress archives, not > Clamd.
Yes this is the problem we also observe on our testmachines - exiscan relies on the ripmime-library for mimedecoding and imho this library still has some problems with malformed messages(sadly viruses tend to generate such messages :- ) ). There has just been a new maintenance release of exiscan(4.10-17) with should help with some of these issues (by incorporating an updated ripmime-library) Stefan -- Stefan Kaltenbrunner mastermind at madness dot at --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
