Thijs Koetsier wrote:
> I'm running spamassassin 3.0.4 on Debian-exim.
>
> In my /etc/spamassassin/whitelist.cf I've this line:
>
> whitelist_to [EMAIL PROTECTED]
OK; inbound mail sent to this *EXACT* address will be whitelisted.
Note that you're probably better off just not passing mail for this
account through SA.
> Today, this user recieved an e-mail marked as spam with the following
> header:
[snip]
> Envelope-to: [EMAIL PROTECTED]
Not the same as your whitelist_to...
[snip]
> Received: from Debian-exim by my.mailserver.nl with spam-scanned
> (Exim 4.52)
> id 1Ebavm-0006E7-9j
> for [EMAIL PROTECTED]; Mon, 14 Nov 2005 10:47:18 +0100
^^^^^^^^^^^^^^^^^^^^^
Not the same as your whitelist_to...
[snip]
> Does anyone know why this message wasn't whitelisted, which it should
> have?
I don't see any other record of the destination address in those
headers, other than the two instances I pointed out. (Most messages
have a To: header; was it really missing in the example?)
The SA whitelist_* and blacklist_* configuration options don't require a
perfect match to work as designed, but your usage *does* require an
exact match to avoid whitelisting *all* inbound mail. You've
whitelisted [EMAIL PROTECTED], but your server is processing mail for
[EMAIL PROTECTED] - not even (apparently) the same domain!
You should probably look at whitelisting the sender, rather than the
recipient; and if you *really* want the recipient to receive
everything, "just" stop passing their mail through SA.
-kgd
--
Get your mouse off of there! You don't know where that email has been!
