Maurizio wrote: > On Wed April 19 2006 18:19, Gary V wrote: >> Maurizio wrote: >> >> > Gary, >> >> > u nicely suggested me to use policy_bank to white list some ips that i >> > trust; >> > i would allow senders fromt that ip to send mail with zip attach closed >> > with >> > password >> >> > i put my ip into white list: >> >> > amavis_client_whitelist: >> > 151.38.3.123 FILTER smtp-amavis:[127.0.0.1]:10026 >> >> > and i issued: postmap /etc/postfix/amavis_client_whitelist >> >> > in postfix main.cf i have: >> >> > smtpd_recipient_restrictions = >> > reject_multi_recipient_bounce >> > permit_mynetworks >> > reject_unauth_destination >> > check_helo_access pcre:/etc/postfix/helo_checks >> > check_policy_service inet:127.0.0.1:60000 >> > check_client_access hash:/etc/postfix/amavis_client_whitelist >> >> >> > coming to amavis conf, >> > in my debian conf i have put into: /etc/amavis/conf.d/50-user >> > Hi Gary, > all your setup you suggested me does work like a charm :) > now, i would add whitelisting for receivers, too; > my /etc/amavis/conf.d/50-user is this: > http://paste.debian.net/10181
> i would add to this file : > @banned_files_lovers_maps => ( [qw( [EMAIL PROTECTED] )]); > what i would get is that no mail with attachment zipped and password > encrypted will ever blocked: > http://paste.debian.net/10182 > i have added the line this way: > # See /usr/share/doc/amavisd-new/ for documentation and examples of > # the directives you can use in this file > # > @banned_files_lovers_maps => ( [qw( [EMAIL PROTECTED] )]); > $inet_socket_port = [10024, 10026]; # change from original setting > [...] > but still mail is blocked; > $interface_policy{'10026'} = 'CLIENTWHITELIST'; > this way 'CLIENTWHITELIST' is applied to $interface_policy{'10026'} > now, how can i apply 'CLIENTWHITELIST' to a mail address or an entire domain? You are talking about two different things here. The CLIENTWHITELIST allows certain clients (machines that are sending mail to you) bypass spam/virus/banned checks. If I'm not mistaken, amavisd-new will allow encrypted zip files to pass. The sample you provided was not delivered because is is INFECTED with a virus, not because it was banned. To allow spam/virus/banned files to a recipient (or domain), you could do something like this: @bypass_virus_checks_maps = ( [qw( [EMAIL PROTECTED] )] ); @virus_lovers_maps = ( [qw( [EMAIL PROTECTED] )] ); @bypass_spam_checks_maps = ( [qw( [EMAIL PROTECTED] )] ); @spam_lovers_maps = ( [qw( [EMAIL PROTECTED] )] ); @bypass_banned_checks_maps = ( [qw( [EMAIL PROTECTED] )] ); @banned_files_lovers_maps = ( [qw( [EMAIL PROTECTED] )] ); @bypass_header_checks_maps = ( [qw( [EMAIL PROTECTED] )] ); @bad_header_lovers_maps = ( [qw( [EMAIL PROTECTED] )] ); but since in this case these are all identical, you could instead set only one of them, and then use that variable to assign all the others: @bad_header_lovers_maps = ( [qw( [EMAIL PROTECTED] )] ); @bypass_virus_checks_maps = @virus_lovers_maps = @bypass_spam_checks_maps = @spam_lovers_maps = @bypass_banned_checks_maps = @banned_files_lovers_maps = @bypass_header_checks_maps = @bad_header_lovers_maps; Gary V ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ 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/
