> Hey guys, > > Is there any way to block outgoing but allow incoming extensions with > amavis? I tried to create policies but found out that sending e-mails > with extensions to both and internal and external address triggers the > policy that allows the extensions to go through, not blocking the > outgoing e-mail. A postfix limitation actually. Anyone has done it > before? I could really use some help here. >
Inbound and outbound can use a different policy. In that policy (MYNETS?) you can set up different rules. For inbound (allow anything?) Something like this in amavisd.conf $banned_filename_re = new_RE(qr'.' =>0); $banned_namepath_re = undef; # new-style For outbound: (in mynets policy bank): banned_namepath_re => undef, banned_filename_maps => ['MYNETS-DEFAULT'], Grep in amavisd (notes?) for MYNETS-DEFAULT for ideas. -- Michael Scheidell, CTO >|SECNAP Network Security Finalist 2009 Network Products Guide Hot Companies FreeBSD SpamAssassin Ports maintainer _________________________________________________________________________ This email has been scanned and certified safe by SpammerTrap(r). For Information please see http://www.secnap.com/products/spammertrap/ _________________________________________________________________________ ------------------------------------------------------------------------------ The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-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/
