Mark Martinec wrote:
Adam,
It would be nice if the score_sender_maps had an entry for an IP or
hostname to limit what sending systems will match the score_sender_map
entry.  This would be very handy as I know where most of the entries
will be sending emails from and could keep spammers from using that
email.  Has this been discussed before?

My plan is to extend the lookup_ip_acl to be able to return information
(like policy bank name) associated with an IP address or CIDR network specs (and not just boolean match/nomatch as now), which will make it possible to associate different policy banks with different client IP addresses - similar to what MYNETS does currently, but more flexible. Other needed mechanisms
are already in place, score_sender_maps can be configured per policy bank.

It is possible to achieve something like this with existing mechanisms,
provided that not too many IP networks need different treatment each:
Postfix can use FILTER to associate content filters on different ports
with client CIDR maps, making it possible for amavisd-new to switch
policy banks based on that.

How do you use policy banks with the sendmail/amavisd-milter setup? Sendmail cannot connect to different amavisd sockets based on originating smtp client IP. It seems like policy banks were really meant for postfix mainly because most comments I see about it are about postfix(even comments in the amavisd.conf file with MYNETS).

The issues I am still trying to find a good solution for are:

- Need a way to bypass all spam checks for mail generated from 127.0.0.1. Automated reports and forwards can sometimes get triggered as spam. I cannot use soft whitelisting for this because mail is sent as the users email address for forwards and other things, etc. I know for a fact that mail generated from 127.0.0.1 will never be spam so it seems more logical to bypass this by IP.

- Need a way to bypass mail from certain hosts that are known to trigger as spam and I never want to check spam from.

It would be nice to be able to bypass spam checking by IP without needing policy banks. Setting up policy banks just to bypass spam checks for some hosts seems like a lot of complexity for what I think is a common need.

Regardless... thanks again for the information.


-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
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/

Reply via email to