If you need to whitelist mail (make sure that it passes all the spam tests),
you can do so, based on the IP address, the return address, or text that appears
within the E-mail.
WARNING: White listing is a last
resort to accept mail from poorly administered mail servers, and will often
allow spam through if you are not careful.
Example
WHITELIST FROM
@hotmail.com
Will allow a LOT of spam through as this is often
forged.
WHITELIST FROM mail.com
Would whitelist mail from mail.com and hotmail.com
WHITELIST FROM your_domain.com
Should never be used (since many spammers will use a made-up return
address on your domain). If you do not understand these warnings, you should not
use whitelists.
Whitelist an IP address add a line to your
global.cfg (replacing 127.0.0.1 with the IP you wish to
whitelist).
WHITELIST IP 127.0.0.1
Whitelist a range
of IP addresses such as 127.0.0.0 through 127.0.0.255, you can do so by
adding a line:
WHITELIST IP 1 27.0.0.
(which will whitelist
any E-mails from mail servers with an IP address that contains
127.0.0.).
You can also use a CIDR range (see
www.DNSstuff.com site's CIDR
tool for assistance), such as:
WHITELIST IP 127.0.0.0/8 or
WHITELIST IP 192.0.2.0/24
Whitelist an E-mail address, add a line to your global.cfg
(replacing user@example.com with the address you wish to
whitelist):
WHITELIST FROM user@example.com
Whitelist an domain, add a line to your global.cfg (replacing
@example.com with the domain you wish to whitelist):
WHITELIST FROM @example.com
Whitelist a sub-domain add a line to your global.cfg (replacing
subdomain and example.com with the subdomain and domain you wish to
whitelist):
WHITELIST FROM @subdomain.example.com
Whitelist all sub-domains add a line to your global.cfg
(replacing example.com with the domain you wish to whitelist):
WHITELIST
FROM .example.com
NOTE: that WHITELIST FROM will whitelist a
return address (like
Imail does in the Kill List), which may be
different from the From: or Reply-To: addresses. You need to look at the
X-Declude-Sender: header (if you use the XSENDER ON option)
or the MAIL FROM: line in the
MAILSERVER SMTP log file to find the return
address.
Whitelist text You can whitelist text that appears anywhere in
the headers or body of the E-mail, add a line to your global.cfg (replacing
"text" with the text you wish to use for whitelisting).
WHITELIST
ANYWHERE text
Example
WHITELIST ANYWHERE
The secret code is 12345
Any E-mail containing "The secret code is
12345" would be whitelisted.
Whitelist mail TO a certain
domain add a line to your global.cfg (replacing example.com with the
domain you wish to whitelist TO):
WHITELIST TODOMAIN
@example.com
Whitelist mail TO a certain user add a line to
your global.cfg (replacing user@example.com with the user address you wish to
whitelist TO):
WHITELIST TO user@example.com
You do not
need to enter domain aliases if do not want to.
Example
WHITELIST TODOMAIN
@example.com
(If you have the domain name as "example.com" with
"mail.example.com" as an alias, both iwll be
whitelisted).
Whitelist Habeas
Habeas headers will
appear in legitimate E-mail from sources that are approved to use the headers.
Any spammers that get whitelisted due to the Habeas headers can be reported to
www.habeas.com, and legal action will
likely be taken against them. This is a good way to help prevent false positives
-- people whose E-mail gets caught as spam can just go to the URL shown to find
out how to add the Habeas headers to their E-mail.
Whitelist E-mail with
the
Habeas Headers by adding
a line the following line to your global.cfg
WHITELIST
HABEAS
Whitelist Limit
You can have up to 200 of the
WHITELIST entries in the global.cfg file. They only work in the global.cfg file.
Also, they work on a "partial match", so you should not remove the "@" from
E-mail addresses (or domains) that you whitelist, without thinking of the
consequences.
If you need to have unlimited whitelist entries, or if you need per-user or
per-domain whitelisting, you may find the WHITELISTFILE option helpful.
To use this option, you need to add a line to the appropriate
$default$.junkmail configuration file or the per-user/per-domain configuration
file you wish to use the whitelists with:
WHITELISTFILE C:\{MAILSERVER}\Declude\mywhitelist.txt
The mywhitelist.txt file would then contain either:
#E-mail
address
user@example.com
#Domain
@example.com
#Subdomain
.example.com
One entry per line per line. The whitelist files can have unlimited entries
in them.
NOTE: the file you use with the WHITELISTFILE option does NOT use the
same format as the WHITELIST entries in the global.cfg file. and that the
WHITELISTFILE option does not work in the global.cfg file.
Automatic Whitelisting (Not Currently Supported by Imail
2006)
You can automatically whitelist E-mail addresses that are
listed in the recipient's address book. To do this, you just need to add a line
to your global.cfg
AUTOWHITELIST ON
To turn this feature
off:
AUTOWHITELIST OFF
With this feature enabled, when an E-mail is received, Declude JunkMail will
check to see if the sender is listed in the recipient's web messaging address
book. If so, the E-mail will automatically be whitelisted. This feature can help
reduce false positives.
Whitelisting Authenticated Users
To
automatically whitelist your own users that authenticate. This is useful to help
ensure that the E-mail your users send does not get caught, especially if they
are using a mail client such as Outlook that may fail several anti-spam tests.
To do this, you just need to add a line to your
global.cfg
WHITELIST
AUTH
NOTE:Versions of IMail proir to 8 do not
support this directive.
Quick Reference
|
Feature
|
Sample
Filename
|
Sample
Format
|
How matches
work
|
Comments
Allowed?
|
|
Whitelist - 'Anywhere'
|
global.cfg
|
WHITELIST ANYWHERE some text
|
Partial match (matches any E-mail with 'some text' in
it)
|
No
|
|
Whitelist - Habeas Headers
|
global.cfg
|
WHITELIST HABEAS
|
n/a - whitelists all E-mail with Habeas headers
|
No
|
|
Whitelist - HELO/EHLO
|
global.cfg
|
WHITELIST HELO example.com
|
Partial match (matches any HELO/EHLO data 'example.com' in
it)
|
No
|
|
Whitelist - IP
|
global.cfg
|
WHITELIST IP 192.168.100.1
|
Partial match (matches 192.168.100.1 and
192.168.100.10)
|
No
|
|
Whitelist - IP Range
|
global.cfg
|
WHITELIST IP 192.168.100.0/24
|
Matches a CIDR range
|
No
|
|
Whitelist - Recipient
|
global.cfg
|
WHITELIST TO user@example.com
|
Exact match (matches if any recipient is
'user@example.com')
|
No
|
|
Whitelist - Recipient Domain
|
global.cfg
|
WHITELIST TODOMAIN @example.com
|
Partial match (matches any recipient address with '@example.com'
in it)
|
No
|
|
Whitelist - Reverse DNS
|
global.cfg
|
WHITELIST REVDNS .example.com
|
Partial match (matches any return address with '.example.com' in
it)
|
No
|
|
Whitelist - Sender
|
global.cfg
|
WHITELIST FROM user@example.com
|
Partial match (matches any return address with
'user@example.com' in it)
|
No
|
|
Whitelist - Sender Domain
|
global.cfg
|
WHITELIST FROM @example.com
|
Partial match (matches any return address with '@example.com' in
it)
|
No
|
|
Whitelist - Sender Subdomain
|
global.cfg
|
WHITELIST FROM .example.com
|
Partial match (matches any return address with '.example.com' in
it)
|
No
|
|
Whitelist - Subject
|
global.cfg
|
WHITELIST SUBJECT Make Money Fast
|
Partial match (matches any subject with "Make Money Fast" in
it)
|
No
|
Note that other formats will not work; for example, using a "*" or "-" in an
IP address will not work.