RE: whitelist v.s. negative values

[Randal, Phil]

Use whitelist_from_rcvd wherever possible instead.  >From the documentation:

 

 

whitelist_from_rcvd [EMAIL PROTECTED] sourceforge.net

Use this to supplement the whitelist_from addresses with a check against the Received headers. The first parameter is the address to whitelist, and the second is a string to match the relay's rDNS.

This string is matched against the reverse DNS lookup used during the handover from the internet to your internal network's mail exchangers. It can either be the full hostname, or the domain component of that hostname. In other words, if the host that connected to your MX had an IP address that mapped to 'sendinghost.spamassassin.org', you should specify sendinghost.spamassassin.org or just spamassassin.org here.

Note that this requires that internal_networks be correct. For simple cases, it will be, but for a complex network, or running with DNS checks off or with -L, you may get better results by setting that parameter.

e.g.

  whitelist_from_rcvd [EMAIL PROTECTED]  example.com
  whitelist_from_rcvd [EMAIL PROTECTED]      sergeant.org

Cheers,

 

Phil

----
Phil Randal
Network Engineer
Herefordshire Council
Hereford, UK

 

---

From: Thomas Deaton [mailto:[EMAIL PROTECTED]
Sent: 31 May 2005 14:27
To: users@spamassassin.apache.org
Subject: whitelist v.s. negative values

We're getting a lot of spam spoofed from people on our whitlists. I was thinking about removing them from the whitelist and putting them in the spam.assassin.prefs.conf  under "From:" with a negative value.

Does this sound like a good idea?

---

E-mail correspondence to and from this address may be subject to the
North Carolina Public Records Law and may be disclosed to third parties by an
authorized county official. If you have received this communication in
error , please do not distribute it. Please notify the sender by E-mail
at the address shown and delete the original message.

Thank you