Next: RBL Settings
Up: Mail Filters
Previous: Outbound Spam Protection
  Contents
Whitelists and Blacklists control which messages will
be exempt from being scanned for spam and which messages will always
be marked as spam on a sender and recipient basis, as opposed to a
domain basis as in the Outbound Spam Protection section mentioned
earlier.
- Sender Whitelist
- These patterns define From: addresses that
will be exempt from spam scanning. All messages from a sender address
listed here will not be spam scanned.
- Sender Blacklist
- These patterns define From: addresses that
will always be tagged as spam.
- Recipient Whitelist
- These patterns define To: addresses
that will be exempt from spam scanning.
- Spam Trap List
- These patterns define To: addresses that
will always be tagged as spam. This is usually a spam trap
email address set up to attract spam messages only. Spam trap
email addresses are normally set up to create a database of spam messages
(spam corpus), which can be used to teach Bayes manually.
Whitelisting mailing lists requires entries in both the Sender
Whitelist and the Recipient Whitelist in order to work correctly.
You can create an entry simultaneously in both of these access lists
by clicking the Clicking Here link.
For specifying domains, use *domain.com. This pattern will
match the subdomains also. For just the domain, use *@domain.com.
For particular users, use user@domain.com
- [Note:]Remember that the whitelisting and blacklisting
is based on information in the e-mail header, which can be easily
forged. For example, If a spam sender gains knowledge of a whitelisted
sender address, he can forge the From: field
in the header and send mail bypassing spam scanning. It is recommended
that contents of the whitelists be considered sensitive.
Next: RBL Settings
Up: Mail Filters
Previous: Outbound Spam Protection
  Contents
docs@guardiandigital.com
2004-07-09