Maurizio, > now, another question: can be this applied to a single mail account or > domain, or it is sistem wide only?
It can be per-recipient since 2.3.0. See 2.3.0 release notes under NEW FEATURES. (but one should be using 2.3.3 nevertheless) > > $banned_filename_re = new_RE( > > [ qr'^message/multpart$'i => 0 ], # allow > > [ qr'^text/plain$'i => 0 ], # allow > > [ qr'^\.(empty|txt|html)$ => 0 ], > > [ qr'^\.(doc|jpg)$' => 0 ], > > [ qr'^\.(Z|gz|bz2)$ => 0 ], # allow any in Unix-compressed > > qr'^', # block everything else > > ); > > ok, it was just what i was searching for :) I must admit I haven't tried the above, and I expect there might be unexpected interactions between MIME type, file name and short file types, as each node in a MIME tree can have each one of these three attributes, but need not have them. The program does work according to specs, it's just the usability of this approach which needs to be tried out. If it would turn out you need more complex rules, there is always a choice of using the more complex $banned_namepath_re instead of the easier to comprehend but less expressive $banned_filename_re. Mark ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ 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/
