Matthias Leisi schrieb am 17.10.2007 09:46:
Correct. But by setting (in your local.cf or equivalent)
| trusted_networks 204.9.177.18
you are telling SpamAssassin that this relay is not operated by a
spammer and that it should apply all black-/whitelist rules etc. to the
IP address one more hop away. Then, in the context of SpamAssassin, you
regain full control of connection-oriented rules.
That's not fully equivalent to having the actual "spamming connection"
to deal with, but as close as it gets -- if you need it "closer", you
should not use forwarding services.
Good point. I think I start to understand what trusted_network is for
and how it works. Currently, I have a provider whose MX receives mail
for me and forwards it to my local mail server. Spam detection improved
much when I added its IP address to trusted_networks some time ago.
Now, I occasionly get spam to my users.sourceforge.net account, just
like Dan Mahoney is getting spam to his Livejournal account. Sourceforge
is also listed with LOW at dnswl and acts as a forwarder to my own mail
server.
Since I never get spam from users.sourceforge.net accounts directly but
only spam sent to my users.sourceforge.net account from random
addresses, I suppose the Sourceforge mail server is trusted in that way
that spam doesn't originate from it, and that's the purpose of
trusted_network. Just like my Provider forwarding mail to me sent from
random originators, but never produces spam itself.
Tschau
Alex
