Please don't top post.Your missing the case where the mail is not coming from a private network or a nated server.
I experience this problem (as mentioned in the bug report) from roaming users who are connecting through authenticated SMTP to their mail server, and relaying to me. I'd have to trust all the IP pools of every dynamic user - or the network of every SMTP server of every trusted network.
This would potentially be hundreds of networks...
None of these servers are nated - the IP causing the problem is the IP of the original message submitter - not the relaying server, but even if trusting the IP of the relaying server works I'd still have to track all of them down - yes?
Or am I missing something?
m/
No, you're not missing anything. This is a known bug in SA 2.6X. People saying to add your IP to trusted_networks are not getting it. It's a bug, it's been proven, the only way around it is to disable or severly lower the test score at this time. 2.7X is supposed to fix the problem. I also experience this problem on a non-natted machine. Adding the machines IP to trusted networks has absolutely no bearing on this test triggering. It hits on the first received header, and unless there is only 1 received header, that is NOT supposed to happen. Hopefully 2.7X is close to being finished.
Chris
------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
