From: NFN Smith [mailto:[EMAIL PROTECTED]
>
> Following up on my own post. I'm still thrashing, and not
> getting any
> difference in results.
>
> NFN Smith wrote:
> >
> > OK, I've expanded my settings, but I'm still not making any
> > progress.
> >
> >
> >> trusted_networks 64.65.180.91
> >> trusted_networks 10.10.10.141
> >> trusted_networks 68.99.120.79
> >> trusted_networks 24.249.175.230
> >
> >
> >> internal_networks 64.65.180.91
> >> internal_networks 10.10.10.141
> >
> >
> >> whitelist_from_rcvd [EMAIL PROTECTED] pulsar.lfa.com
> >> whitelist_from_rcvd [EMAIL PROTECTED] lakecmmtao05.coxmail.com
> >> whitelist_from_rcvd [EMAIL PROTECTED]
wsip-24-249-175-230.ph.ph.cox.net
> >
> >
> > - pulsar.lfa.com has a public address of 64.65.180.141, and its
> > internal IP address is 10.10.10.91
> >
> > - lacecmmtao05.coxmail.com is 68.99.120.79
> >
> > - 24.249.175.230 (wsip-24-249-175-230.ph.ph.cox.net) is the
> > network that the message is originating from
> >
> > What else am I missing?
>
> Any chance that I'm missing something different, such as DNS checks
> not running, or some sort of blockage (i.e., firewall)?
Oops. I was going to reply to you this morning and things just got a
bit busy...
Now that you've made those changes, post the headers from another
example email so we can see if anything changed.
Also, you may want to save your email into a file and manually run it
through SA to see what happens. Just add '-t -D' to the option list
to get debugging output and force a spam report to be added. This
should let you know if there are any problems running the network
checks. This will generate quite a bit of output, just scan through
it for anything that looks like an error.
The command line would look like this:
spamassassin -t -D < message.txt
Bowie
