[Spambayes] Whitelisting with Outlook 2003

Harold Vandeventer Harold.Vandeventer at dpra.com
Wed Apr 14 09:36:07 EDT 2004

I'm not a programmer, just an end-user... but Whitelisting against an
address book, in my own experience, is not worth one second of anyone's

Several of my co-workers names have been spoofed, and the senders of the
junk mail are sending to those same co-workers.  Thus, specifying my
address list or my company's domain doesn't solve the problem.  That
junk mail APPEARS to be from the fellow in the next cube, but in fact is
from a SPAMMER somewhere outside of our system.  But the whitelist
concept would let that mail in, untouched! The message headers clearly
prove my buddy (in my address list) DID NOT send that message.

Harold Vandeventer
Network Administrator
DPRA Incorporated
200 Research Dr
Manhattan, KS 66503
Voice: (785) 539-3565 ext 1026
FAX: (785) 537-0272

-----Original Message-----
From: Cedric Beust [mailto:cbeust at bea.com] 
Sent: Tuesday, April 13, 2004 7:27 PM
Cc: spambayes at python.org
Subject: [Spambayes] Whitelisting with Outlook 2003

There seems to be a way to provide Whitelisting directly from Outlook

I noticed that Outlook 2003 has a rule "When sender is in
<addressbook>".  The idea would be to move any messages matching this
criterion into a folder not monitored by SpamBayes (e.g. "Verified"), so
that SpamBayes doesn't get a chance to treat it (it looks like SpamBayes
kicks in *after* the message has been exposed to all the rules, at least
with Outlook 2003 + Exchange).

The downside is that you end up with four folders (Inbox, Verified, Junk
suspects and Junk).  Not the most convenient set up, but it can be seen
as a "poor man's Whitelisting".

Also, you should be able to Whitelist entire domains (such as any email
coming from someone at your company) using the rule "With specific words
in the sender's address".


Spambayes at python.org
Check the FAQ before asking: http://spambayes.sf.net/faq.html

More information about the Spambayes mailing list