With 31.0, McAfee Internet Security marks ALL email as spam. What's the fix?
No matter the level of anti-spam filtering I choose, every single incoming email is tagged as spam in my inbox. (Also, FWIW, all messages go to the inbox even if I try to opt to have them sent to the McAfee anti-spam folder.) I have three PCs with the same McAfee program and Thunderbird. After the problem arose on one PC I checked the others, which had not yet been updated to 31.0. No problem until I updated T'bird. Then: BOOM! Everything is marked as spam on both of those as well.
Hard to believe that McAfee hasn't heard from other T'bird users on this. Doesn't it seem that there must be an innate conflict between McAfee IS and T'bird 31.0?
McAfee techs want to take remote access of my computer to play around with the registry, presumably looking for a corruption of some sort. I have declined, because I can't see that happening simultaneously in all three of my computers, nor do I wish to have the McAfee techs learning on my equipment. Let them solve the problem in-house.
But meantime, just in case, does anyone have a solid suggestion? Thanks!
Alle antwoorden (4)
The use of the word 'Spam' means that it is not Thunderbird, which only uses the word 'Junk'.
There has been many reports of issues with McAfee.
Some info here: https://wiki.mozilla.org/Thunderbird:Testing:Antivirus_Related_Performance_Issues#McAfee
It is recommended that you inform McAfee of your issue.
Yes, I understand. I've informed McAfee (as I wrote above but your boilerplate reply doesn't recognize) and am trying to push the problem to their Tier 3 level for resolution. I was hoping someone here has seen this issue and come up with a temporary workaround until a fix is created.
re: but your boilerplate reply doesn't recognize This facetious remark is uncalled for and not polite to people trying to offer assistance.
McAfee needs to keep up to date if it intends to offer what it claims without causing aggrivation and issues to the user, but obviously informing them helps and this you are doing, which is good.
You ask for a workaround: The link offers some advise from a Thunderbird perspective.
I've also done some internet searching on your behalf and located that this issue seems to occur regardless of email client. On this McAfee forum, there is a similar question albeit a year old, with some advise on what to try. Try this:
Bewerkt door Toad-Hall op
McAfee's Tier2 has just proposed that I do a system restore to go back to the Thunderbird version before 31.0, where the problem started. I declined. It seems to me it's up to McAfee to work out the conflict. They say they'll have their research team get in touch with Thunderbird on this issue, but they aren't having enough complaints to give it much urgency.
It looks as though the previous thread's suggestion of uninstalling and reinstalling the McAfee software may or may not work. I'll probably give McAfee a little time to come up with a patch. If not soon, then when I have the time to try that approach I will, so thanks very much for this.