¿Nobody has idea? Well, I've done my own search...
Maybe a good option is to stop .EXE recieved files in SMTP level (mime_header_checks if you use Postfix as I do) and permit to send .EXE from your own accounts at filter level (Amavisd-new, using bypass_banned policy). You'll get what I'm looking for: protect your accounts against .EXE files but permit your users to send these kind of executables. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ AMaViS-user mailing list AMaViS-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
