Andreas wrote:

> Hi

> We would need some help 
> We have to whitelist a whole ip-address
> Not only a mail domain.

> We use postfix-amavis.new-spamassassin 

> Since last week we have to past email coming
> From a mail server with ip xxx.xxx.xxx.xxx sending for
> Multiple domains - very important mailing list to the members of
> Our Executing staff!

> Thanks Andi

This is the type of thing policy banks are good for. Here is an
example of how I would accomplish this particular need:

smtpd_recipient_restrictions =
        permit_mynetworks
        reject_unauth_destination
        check_client_access hash:/etc/postfix/amavis_client_whitelist

contents of /etc/postfix/amavis_client_whitelist
(ip address of the server is listed here):
192.168.1.17 FILTER smtp-amavis:[127.0.0.1]:10026

Then in amavisd.conf:

$inet_socket_port = [10024, 10026]; # change from original setting

$interface_policy{'10026'} = 'CLIENTWHITELIST'; # add this setting

$policy_bank{'CLIENTWHITELIST'} = {  # mail originating from trusted servers
  bypass_spam_checks_maps   => [1],  # don't spam-check
  final_spam_destiny   => D_PASS,    # insure spam passes
};


See more examples in amavisd.conf-sample and
http://www.ijs.si/software/amavisd/amavisd-new-docs.html#pbanks


Gary V



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
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/

Reply via email to