Duis mollis, est non commodo luctus, nisi erat porttitor ligula, eget lacinia odio sem nec elit. Sed posuere consectetur est at lobortis. Vestibulum id ligula porta felis euismod semper. Donec ullamcorper nulla non metus auctor fringilla. Aenean lacinia bibendum nulla sed consectetur. Cras justo odio, dapibus ac facilisis in, egestas eget quam. Cras mattis consectetur purus sit amet fermentum. Morbi leo risus, porta ac consectetur ac, vestibulum at eros. Sed posuere consectetur est at lobortis. Etiam porta sem malesuada magna mollis euismod. Cum sociis natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus. Duis mollis, est non commodo luctus, nisi erat porttitor ligula, eget lacinia odio sem nec elit. Cras justo odio, dapibus ac facilisis in, egestas eget quam. Aenean eu leo quam. Pellentesque ornare sem lacinia quam venenatis vestibulum. Curabitur blandit tempus porttitor. Sed posuere consectetur est at lobortis.
I believe that is the correct behavior.
I had the same type of issue when someone who was on my white list sent me a message with a subject line that could well have been interpreted as spam.
Purely conjecture, but since email addresses can be spoofed, the Norton anti-spam engine may be designed to protect against known spam keywords and then override the white list. You could look at it two ways: a false positive or a double layer of protection. I prefer the latter.
For me it was no big deal to mark the message as "This is not spam".
Correct.
Ant spam sees white list stronger than the blacklist
Thanks for answers.
Marking message as "this is not spam" only moves message to inbox folder and does not affect any future messages from that person.
When receiving about 100 spam messages a day it's hard to track if there are messages important for you.
Please help me understand what is white list for in that case?
Qba
Qba,
In my case when I mark a message as "This is not spam" it is then placed in the white list and those email senders are not marked as spam going forward, unless of course something in the subject line or perhaps even the header triggers the antispam engine.
Is there anything you notice about your "problem messages" that could trigger the spam alert?
Phil_D wrote:Qba,
In my case when I mark a message as "This is not spam" it is then placed in the white list and those email senders are not marked as spam going forward, unless of course something in the subject line or perhaps even the header triggers the antispam engine.
Is there anything you notice about your "problem messages" that could trigger the spam alert?
It is the way it really works. There must be something else.
Of course there are words that can trigger spam alert.
Maybe I explain not clear.
Let's say I set keyword "green" in spam filter and messages with word "green" should be placed in spam folder.
And let's take 2 people - user1@domain.com and user2@domain.com . And let's user1@domain.com add to white list.
And now both sends message to me with word "green"...
What's difference ? According to you both messages should be placed in spam folder?
So what's advantage of placing user1 at white list?
Hi Qba,
The advantage is that if user1@ dom sends a message one time which triggers the spam filter, that user is not relegated to the spam list forever; you have the option to add that person to the white list.
As long as future messages from user1@ dom do not contain spam triggers, then user1@ dom will always come though in the normal fashion.
Phil_D
Thank you for explanation, now I understand how it works.
Hi bradylaw,
Do you know how "[Norton AntiSpam]" is getting into the subject line of your message? As near as I can tell, the error you are seeing is the recipient's ISP's (Secureserver.net) mail server rejecting your message. Usually this happens because your email address or IP address is on a blacklist of known spam sources. I am not sure what the explanation - the message "matches a profile the Internet community may consider spam," - is actually referring to, but it seems to indicate that something about the message itself is causing the server to refuse to accept or deliver it.