> I just installed Q-S 1.20rc1 in a test environment and played around > with it. What I have seen so far looks great. You have done a > good job. > Thanks.
Just wanted to echo what Alex said above. I've been running this version on our production server for a couple of days now and it is working very well. I just have a few comments and questions. > * "--unzip" disabled by default now. Based on the comments in the code it appears that one of the reasons for this option in the first place was because anti-virus scanners did not include unzip capability (specifically McAfee). I guess that all of them can now do this. Personally, I have this feature enabled, as I want to be able to block particular file types, even inside zip files, using perlscanner. > * Q-S now skips virus-scanning messages that are either text/plain > or non-MIME/uuencoded. This will speed things up a tad. Is it possible for a malicious email to be created that is in for example html format with a content-type of text/plain? If so, would a broken email client (possibly written by Microsoft) render it as html (possibly including VB script)? > * SpamAssassin now sets the spamc "username" field to the > recipient address. This only happens if there is ONE recipient. Is there any disadvantage to this if you are only using site-wide SpamAssassin settings? Currently I have commented out the relevant code. If there is a problem when you only use site-wide settings, it might be worth making this a configuration option. >From the CHANGES file: > Changed defaults so that clamav scanners are listed as the first > scanners. I'm using spamassassin, sophie and clamdscan, and it listed sophie first, even when I specified: --scanners 'clamuko,sophie,verbose_spamassassin' when configuring. Also, it appears the the clamdscan support is an undocumented new feature :). The other minor problem I've found is the email notifications that are sent for messages that are blocked using the new mime features don't include the filename of the email any more. I now get: ---perlscanner results --- problem 'Disallowed characters found in MIME headers' found in message --- when I used to get: ---perlscanner results --- problem 'Illegal MIME chars found in header' found in message /var/spool/qmailscan/mx01.oce.co.uk106125793143818893 --- It's not a major problem, but it makes it easier to check the message manually when you can copy and paste the filename. Thanks, Chris Hine ------------------------------------------------------- This SF.net email is sponsored by: VM Ware With VMware you can run multiple operating systems on a single machine. WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the same time. Free trial click here:http://www.vmware.com/wl/offer/358/0 _______________________________________________ Qmail-scanner-general mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/qmail-scanner-general
