It looks like your mail was run through as a forward from inside
your network.
I always strip all markups off and leave the message as SpamAssassin
would see it fresh out of procmail (amavisd in your case). That way
nothing thinks it came from an internal address.
I test "eml" with "spamc <eml". You'd want to use "spamassassin <eml"
or even "spamassassin -t <eml" to give you the recap at the end. The
-D option can go in there, too, for the spamassassin version. It's
unfortunate spamc does not understand a -D.
{^_^}
----- Original Message -----
From: "M.Lewis" <[EMAIL PROTECTED]>
Thanks jdow & Jon. I was unaware of the 'clear_trusted_networks'. I have
added it now (and restarted mail):
# Trusted
clear_trusted_networks
trusted_networks 127.0.0.1 192.168.1.0/16 64.125.72.2
I took a spam from earlier today and run it through spamassassin -D <
spam. Here's something I saw in the output that makes me think I still
have a problem somewhere.
debug: received-header: relay 192.168.123.205 trusted? yes internal? yes
jdow wrote:
From: "M.Lewis" <[EMAIL PROTECTED]>
I've seen quite a few messages regarding trusted_networks lately. I
have played around with my setup and still don't think I have it set
correctly.
What I have is this:
# Trusted
trusted_networks 127.0.0.1 192.168.1.0/16
My setup is my mail is dragged down via fetchmail from my provider,
runs through Postfix, then Amavisd, then Spamassassin. Yes, I am
NAT'd. I do not have a public IP.
Is my setup of trusted_networks correct? If so, why do I see the
following in I think in every spam message.
-3.3 ALL_TRUSTED Did not pass through any untrusted hosts
Your ISP's mail server is the trusteded server you should use. For me
it's Earthlink's servers:
trusted_networks 192.168.0/24 127/8 207.217.121/24
{^_^}
