Sigh, answering myself again, but this seems relevant and
others here
may find this as useful as I did. This can not only prevent
spam relayed
through mail lists from having a negative score applied, but
actually
help identify it as spam if it is sent to the mail relay
server from a
known spam source.
--Greg
-------- Forwarded Message --------
> From: Matthias Leisi <matthias leisi.net>
> To: woodsucar.edu
> Subject: Re: [Maia-users] RCVD_IN_DNSWL_MED rule
> Date: Mon, 24 Sep 2007 17:43:01 +0200 (CEST)
>
> Hi Greg,
>
> I'm responsible for the dnswl.org project, and I've
been alerted to your
> mail on Maia-users through my Google Alert on
"dnswl". Since I'm not
> subscribed to the Maia-users list, you may want to
forward this
> information:
>
> The effect you are seeing is not limited to the
dnswl.org-rule in
> SpamAssassin. SpamAssassin applies the dnswl.org and
other DNSxL rules
> differently depending on the Received: header where an
IP address shows
> up: on the first trusted, last untrusted, first
external etc. header.
>
> If you want to make sure that these rules are applied
to mail that is
> forwarded eg through moderators.isc.org, you should add
the IP address of
> such a forwarder to the trusted_networks configuration
in SpamAssassin.
> This will ensure that DNSxLs are not applied to the
forwarder itself, but
> to the "hop" before.
>
> The "trusted" in trusted_networks means:
trusted not to be directly
> operated by a spammer, and therefore it is safe to
believe the Received:
> header added by this hop.
>
> -- Matthias
>
_______________________________________________
Maia-users mailing list
Maia-usersrenaissoft.com
http://www.renaissoft.com/mailman/listinfo/maia-users
|
