Problem with this fix is it only fixes things for my users locally - when my users send mail to someone else, they would have to set the same networks as trusted.
This is untrue..
What ALL affected admins must do is set trusted_networks to is _their own_ server.. not having anything to do with the source.
Of course, you can't fix other people's broken servers, but they do NOT need to enter your IP to fix the dynablock mislisting bug.
ie: at my work xanadu.evi-inc.com was tripping dynablock on messages from my comcast account.. xanadu is a NAT'ed server. I had to add the following line to xanadu's local.cf to stop the misfire. (note here is 192.168.xx.xx is the IP address of xanadu's ethernet interface, which static maps to a public IP as it goes through a NAT router).
trusted_networks 192.168.xx.xx/32
That's got nothing to do with trusting any of comcast's IPs.. and applying that one line fixed _all_ the mis-checked dynablocks.
------------------------------------------------------- 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
