Matthew Lenz wrote:
ok. i think i got it. what parts of the headers does spamassassin look
at for trusted_networks? my guess is that if there are any untrusted
ip's mentioned in the received: headers it marks it as untrusted?
Yeah, it trusts each received header starting from the top until it
finds an IP that's not in the list of trusted_networks.
what
about my pop-before-smtp users? they'll be relaying through the public
ip sending emails to one another on that same machine. how does it know
that isn't a direct MX spam?
Some questions first...
1. do you control the IPs that your dial-up users are connecting from
2. does the smtp smarthost that the dial-up users use have the same IP
as the smtp server that is passing the mail to SA or is it different?
3. can you obtain enough pain medication to get them all to convert to
auth'd SMTP connections?
Daryl