White list- what's the point?

WebFire

WebFire

Perch
Received an email today marked spam even though it's in the whitelist. The interesting thing is this little message in the DSPAM message:

Content preview: This is in the white list but still picked up as spam

So then what is the point? I thought the whitelist sent everything through regardless of spam score.
 
I echo WebFire's sentiment. I have *.school.nz in my whitelist, but still many come through labelled as Spam (eg sendername(at)pnbhs.school.nz)
 
Please submit a ticket on this issue, we will look into it. They do work, and if they are not working in your case there must be a specific issue/bug with your filter setup.
 
Actually, I've turned off the anti-spam on all of my client's accounts due to false positives from within the respective domains, inability to recognize white list entries, marking of government email as spam and myriad other issues.

Really, any anti-spam system which flags emails with a single user on the to line from within the domain as spam is simply not worth having. I'll just continue to recommend that folks install spambayes on their client machines and be done with it. Far, far less hassle.


*edit: ooooooh, I'm a whitetip now!
 
Spam detection software, running on the system localhost, has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details.

Content preview: This is in the white list but still picked up as spam

Content analysis details: (6.7 points, 5.0 required)

pts rule name description
---- ---------------------- --------------------------------------------------
3.6 FB_GET_MEDS BODY: Looks like trying to sell meds
3.1 TVD_FUZZY_SYMBOL BODY: TVD_FUZZY_SYMBOL

The original message was not completely plain text, and may be unsafe to open with some email clients; in particular, it may contain a virus, or confirm that your address can receive spam. If you wish to view it, it may be safer to save it to a file and open it with an editor.
 
WebFire and nzkiwi, please create a ticket with message headers of this bounce message as well as the attachment "Original message before spamassassin.txt" file.
Hafa, a good news here is that in coming updates we will be able to whitelist our entire network. So no more spamassasin problems with emails sent from websites. For whitelisting issues you had I really would like to know a ticket number with details of where it failed.
And for false positives, we train dspam on weekends, you all are invited to post false postives via ticket.
Ofcourse it won't match SpamBayes in accuracy right away, On the other hand creating a server side service like spambayes will be equivalent to some enterprise email hosting in pricing. I can assure you it will be just better, but again costs will be there.
With dspam that covers all our domains, accuracy has been 99.9% recently.
 
Ahh! Now I Understand. It's the Return-Path address that is checked against the whitelist, not the From address as I assumed :redface:
 
You must log in or register to reply here.
Back
Top