Armin, > > 08:50:26 mx4 ~ # file ALL-IN-ONE_en.fmx > > ALL-IN-ONE_en.fmx: MS-DOS executable (EXE), OS/2 or MS Windows
> > i tried to whitelist the sending email address (mine) > > but afaik are these whitelist options in amavisd only for whitelisting > > spamassasin or viruscanners. Whitelisting only affects spam checks. From Justin B. Alcorn: > If you want to allow filemaker files globally, add it to > $banned_filename_re as an exception. Make sure it's in the rule EARLY: > > $banned_filename_re = new_RE( > [ qr'^\.(fmx)$'=> 0 ], # Allow Filemaker files > qr'\.[^./]*[A-Za-z][^./]*\.(exe|vbs|pif|scr|bat|cmd|com|cpl|dll)\.?$'i, > > Or, make yourself a banned_file_lover so you'll get banned files. Almost, but as Armin said, the file(1) does not recognize the file contents as .fmx, so you can't add an allow rule to $banned_filename_re based on the short file type, but you can only do it based on the name of a file, e.g.: [ qr'\.fmx$'=> 0 ], # Allow Filemaker files with names ending in .fmx ( note the absence of anchoring ^ ) Note that the use of 'allow' rules in $banned_filename_re requires a recent version of amavisd-new. Old versions used a different evaluation order which made such rules mostly useless. Mark ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ AMaViS-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
