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? 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?
----- Original Message -----
From: "Daryl C. W. O'Shea" <[EMAIL PROTECTED]>
To: "Matthew Lenz" <[EMAIL PROTECTED]>
Cc: <users@spamassassin.apache.org>
Sent: Friday, September 23, 2005 4:21 PM
Subject: Re: arrrgh.. debian sarge spamassassin worthless?
Matthew Lenz wrote:
any way to tell what it considers to be a trusted_network? we have 5
You can run a message through spamassassin -D to find out. In a nated
environment it's going to guess wrong though, guaranteed.
private segments and all those servers use postfix with a 'relayhost'
which resolves to the private ip address of our smtp server. all of our
users also use this smtp server for sending mail from their desktops.
they all nat through a single ip on one of said networks above. there is
a 1:1 nat that maps a public ip to that priviate ip for our smtp server.
so do i just put all 5 segements plus the public ip address we use for
our mailserver?
Yes, all your private addresses or CIDR blocks and your public IP(s).
Daryl
