Whitelist being ignored by Spam Assassin?

R

Rokatesh

Perch
I've put an email address on the white list - yet the system still tags it as spam. What do I need to do to REALLY put it on the white list?



==============================
"Spam detection software, running on the system "mail3.m****here.biz", 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 analysis details: (6.8 points, 4.0 required)

pts rule name description
---- ---------------------- --------------------------------------------------
1.3 FROM_STARTS_WITH_NUMS From: starts with many numbers
0.6 HTML_90_100 BODY: Message is 90% to 100% HTML
0.9 HTML_IMAGE_RATIO_04 BODY: HTML has a low ratio of text to image area
1.4 HTML_IMAGE_ONLY_28 BODY: HTML: images with 2400-2800 bytes of words
0.0 HTML_MESSAGE BODY: HTML included in message
0.4 MPART_ALT_DIFF BODY: HTML and text parts are different
0.4 MIME_HTML_ONLY BODY: Message only has text/html MIME parts
1.7 MISSING_SUBJECT Missing Subject: header

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.
 
What I've ended up doing is reducing the aggressiveness of the spam assassin - but this is not my preferred method for receiving emails that I send to myself...
 
Not sure if either of you are using "catch-all', but that's the only time I ever had a problem with the white/black lists and the reason was because I didn't have an alias created for my catch-all that I used.

catch-all = [email protected]

Used [email protected] for registering and emails to that address got marked as spam. I white-listed Amazon's email address and it still was marked as spam.

I added the alias of "amazon" to my catch-all address and white-list started working.

This was my situation and might not be relevant to yours, but thought I'd share just in case.

Cliff
 
Please submit a ticket regarding this issue, a tech needs to look into this on a case by case basis to check why its not working..
 
I've not recently seen a whitelist not working.
Mostly it is client not checking the return-path header that is actually used to whitelist a sender.
 
You must log in or register to reply here.
Back
Top