Denis.Beauchemin at USherbrooke.ca
Tue Feb 14 13:56:33 GMT 2006
Jonas Lilja wrote:
>Hi, my problem is that if I have to send an exe-file, I usually (in an earlier version of MailScanner) rename the file to txt and it will pass through the MailScanner filter. But - after the upgrade - if I first compress the exe-file to zip and then rename the zip to txt it will be blocked by MailScanner (I can still rename pure exe-files to txt and send them). I have already comment out "Block executables" in my conf but leaved the default block rule for exe, com and other dangerous attachements. How can I solve this?
>/Jonas Lilja, Sweden.
>PS- I´m running MailScanner 18.104.22.168 on a RedHat ES4.
It is probably caught by filetype.rules.conf that checks the first bytes
of each attachment to determine their true nature.
Personnally, I turned it off...
°v° Denis Beauchemin, analyste
/(_)\ Université de Sherbrooke, S.T.I.
^ ^ T: 819.821.8000x2252 F: 819.821.8045
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 3226 bytes
Desc: S/MIME Cryptographic Signature
Url : http://lists.mailscanner.info/pipermail/mailscanner/attachments/20060214/edc0d1b1/smime.bin
More information about the MailScanner