[spambayes-bugs] [ spambayes-Feature Requests-975933 ] Spambayes needs a White List

[SourceForge.net]

Feature Requests item #975933, was opened at 2004-06-20 06:19
Message generated for change (Comment added) made by anadelonbrin
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=498106&aid=975933&group_id=61702

Category: Outlook
Group: None
>Status: Closed
Priority: 5
Submitted By: Brian C (briancu)
Assigned to: Mark Hammond (mhammond)
Summary: Spambayes needs a White List

Initial Comment:
We recently rolled out SpamBayes to approx 100 of our 
users. The program works great, however it needs a 
whitelist. Users spend too much time checking their Junk 
E-Mail and Junk Suspects folders for "good" e-mail.

We have also rolled out a program called "Spam Bully" to 
approx 25 users. This program also uses bayesian 
filtering. The users like this program better only because 
it has a whitelist. I have also switched over to this 
program because of the whitelist. Unfortunately, the 
program costs $25 per user.

The other problem that occurs frequently with 
Spambayes is that users accidently delete the junk e-
mail folder or the junk suspects folder. This freaks out 
the spambayes program. We have upgraded users to 
Outlook 2003 (users cannot delete the junk e-mail folder 
in Outlook 2003) and have routed all e-mail to this 
folder. I don't know if there is anything you can do 
about this.

The bottom line is that the product is great but is not 
viable without a whitelist. One false positive is too many 
for our managers - we never hear the end of it when it 
happens.

Thanks for your product and keep up the good work. 
Brian.

  

----------------------------------------------------------------------

>Comment By: Tony Meyer (anadelonbrin)
Date: 2004-06-24 11:44

Message:
Logged In: YES 
user_id=552329

Please read FAQ 6.6:

<http://spambayes.org/faq.html#why-don-t-you-add-whitelisting-blacklisting-to-spambayes>

Regarding the deleting the unsure/spam folder - we're aware
of this problem and have solutions in mind.  The changes are
too large to go in pre 1.0, however, so will appear some
time in the future.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=498106&aid=975933&group_id=61702