Hi, > $r->banned_filename_re = new Amavis::Lookup::RE(qr/.\.($re)\$/i);
There is no banned_filename_re within PerRecip, so that's not gonna work. > What is the right way to implement banned rules for domains (using > Amavis::Custom)? Could you please describe what you exactly need. If you want to ban different filetypes based on the recipient, you can do this without Amavis::Custom: Have a look at @banned_filename_maps and %banned_rules. When you ban with Amavis::Custom you have to do the complete banning decision yourself. If you want to block something in Amavis::Custom::checks, you have at least to put the correct contents category (CC_BANNED) in the PerRecip contents_category and in the msginfo contents_category. Kind regards, Gerd -- Address (better: trap) for people I really don't want to get mail from: jo...@cactusamerica.com ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ 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/
