Note there is also a patch for the SA 3.1 SPF plugin to quench it when a message is coming from a trusted (but not internal) host:
http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4661 The patch is in response to my problem report from 2005-11-04: > According to SA docs on trusted/internal_networks, the > MSA is to be included in the trusted_networks list, and not in > internal_networks. > > Now the question. A mail submitted to MSA from an external > authenticated client (which also happens to be DUL-listed) uses > a sender address of our domain (as it should be, according to SPF docs). > The SPF check (as done by SA) submits this foreign IP address to SPF, > which naturally claims it is a forgery. This is clearly wrong, the IP > address submitted to SPF should be that of MSA, or SPF check > should be skipped altogether. Mark ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ 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/
