You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by bu...@bugzilla.spamassassin.org on 2007/03/05 21:03:47 UTC
[Bug 5326] Whitelist triggers on "To", not "From"
http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5326
spamassassin@dostech.ca changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |INVALID
------- Additional Comments From spamassassin@dostech.ca 2007-03-05 12:03 -------
Return-Path: <te...@testdomain.com>
As documented, your whitelist entry is applied to the Return-Path address (see
last line quoted below). I'd suggest that you heed the suggestion in the
documentation and not use whitelist_from for your own domain.
whitelist_from add@ress.com
Used to specify addresses which send mail that is often tagged
(incorrectly) as spam. If you want to whitelist your own domain, be
aware that spammers will often impersonate the domain of the recip-
ient. The recommended solution is to instead use
"whitelist_from_rcvd" as explained below.
Whitelist and blacklist addresses are now file-glob-style patterns,
so "friend@somewhere.com", "*@isp.com", or "*.domain.net" will all
work. Specifically, "*" and "?" are allowed, but all other
metacharacters are not. Regular expressions are not used for secu-
rity reasons.
Multiple addresses per line, separated by spaces, is OK. Multiple
"whitelist_from" lines is also OK.
The headers checked for whitelist addresses are as follows: if
"Resent-From" is set, use that; otherwise check all addresses taken
from the following set of headers:
Envelope-Sender
Resent-Sender
X-Envelope-From
From
In addition, the "envelope sender" data, taken from the SMTP enve-
lope data where this is available, is looked up.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.