Re: [AMaViS-user] whitelist_client_maps for amavisd-new 2.5.2

This is a discussion on Re: [AMaViS-user] whitelist_client_maps for amavisd-new 2.5.2 within the Amavis User forums, part of the Anti-Spam and Anti-Virus Related Forums category; On 10/25/07, Eddy Beliveau wrote: > Hi! > > We are utilizing amavisd-new 2.5.2 with ...


Go Back   Usenet Forums > Anti-Spam and Anti-Virus Related Forums > Amavis User

FAQ Members List Calendar Search Today's Posts Mark Forums Read
  #1 (permalink)  
Old 10-26-2007
Gary V
 
Posts: n/a
Default Re: [AMaViS-user] whitelist_client_maps for amavisd-new 2.5.2

On 10/25/07, Eddy Beliveau wrote:
> Hi!
>
> We are utilizing amavisd-new 2.5.2 with great success. Thanks :-)
>
> Currently, I'm using @whitelist_SENDER_maps manually to bypass some sender email addresses or domains.
> This work correctly.
>
> I noticed that I have a lot of request to add/remove domain names from the same client.
>
> My wishe would be to have a map like @whitelist_CLIENT_maps
> which will contains the ip address of their smtp server
> and to considered that any emails from those ip address to be whitelisted.
>
> Ideally, I would like to use the fqdn instead of the ip address
>
> I was going to add them to @mynetworks but doesn't like it.


If you are using xforward (as shown in the following example) in the
amavis transport, then I think it should work (depending on what you
have the MYNETS policy bank doing)..

smtp-amavis unix - - - - 2 smtp
-o smtp_data_done_timeout=1200
-o smtp_send_xforward_command=yes
-o disable_dns_lookups=yes

> I prefer to consider @mynetworks as being the list of my own internal servers.


Probably a good idea.

>
> Can it be done ?
> Other solution ?
>
> Thanks,
> Eddy


This is where another policy bank may be used. Assuming you are using Postfix:

smtpd_client_restrictions =
check_client_access hash:/etc/postfix/amavis_whitelist

example contents of /etc/postfix/amavis_whitelist:
192.168.1.41 FILTER smtp-amavis:[127.0.0.1]:10026

Create a policy bank in amavisd.conf that listens on port 10026:
# change this from the original setting
$inet_socket_port = [10024, 10026];

# add these
$interface_policy{'10026'} = 'WHITELIST';

$policy_bank{'WHITELIST'} = { # those configured to send mail to port 10026
bypass_spam_checks_maps => [1], # don't spam-check this mail
};

http://www.ijs.si/software/amavisd/a...html#pbanks-ex
http://www200.pair.com/mecham/spam/bypassing.html

--
Gary V

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
AMaViS-user mailing list
AMaViS-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/...fo/amavis-user
AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/howto/
Reply With Quote
Reply
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are Off
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On




All times are GMT +1. The time now is 05:07 AM.


Powered by vBulletin® Version 3.7.3
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO 3.0.0