*****SPAM***** inserted in Subject

[JohnnyB]

Before I start Thunderbird I open my mail with MW Pro 7.12.188 in Windows 10. Mail that has been detected as SPAM has a *****SPAM***** inserted at the beginning of the Subject line of the email.

I have AVAST running and I turned of the Mail Shield, rebooted and I still have the SPAM in the Subject line.

Anyone have a clue ?
Thank you

[Digerati]

It "sounds" like you might have Cox Communications as your Internet and email provider because that is exactly what happens to email sent to my Cox address they suspect is spam.

And, at least with my experience and Cox's spam filter, that is a good thing!

If not Cox, then a provider that deals with spam in a similar way.

What used to happen years ago when Cox first introduced their spam filter, they would automatically move suspected spam into a spam folder that MailWasher could not reach. Neither could Thunderbird, Outlook, or whatever your PC email handler was.

This meant just to check your spam folder, you had to separately log into your Cox webmail account and check the spam folder. If you had multiple Cox email accounts (I think we are allowed 10 per Internet account), you had to log into each email webmail account separately.

Log in, check the folder, log out. Move to the next email address, log in, check the folder, log out. Move to the next email address... and so on. That was a real PITA - especially because their filter was lousy and had many false positives! That is, they incorrectly tagged many legitimate emails as suspicious (spam) and moved them into spam folders without any notification to us. Not cool! This meant we had no choice but to check each spam folder regularly.

After many Cox customer complaints, they changed how the filter works and added the option to keep the suspected spam in the Cox inbox (where MailWasher, Tbird and Outlook could see it), but then would just append ***SPAM*** to the subject to get our attention. So even if a legitimate email was tagged as spam, it would still get to where MW and we could see it. A good thing.

It looks like that is what is happening to you here.

[JohnnyB]

I use Digitalspace for web and mail.

The last time I had an email with *****SPAM***** inserted, I logged into the Digitalspace portal to look what the email looked like and the Subject didn't have SPAM insert. So it is something between Digitalspace and MW Pro. There must something that happens on AVAST which I find uncomfortable using, but they seem more reliable than the others.

Thanks for responding.

[Digerati]

but they seem more reliable than the others.

I don't know what "more reliable" means, or what "others" means either.

There is nothing to suggest Avast is more (or less) reliable. If you like it, that's great - as long as you keep it (and your OS) current.

I am not familiar with Digitalspace. However, my response does not really change. IMO, it is a good thing the "suspicious" emails are being tagged to get your attention - as opposed to just letting everything through untagged. And it is a good thing "suspicious" emails are still being delivered to your inbox - as opposed to hiding them, without any notice, in a difficult to access spam folder, or worse, automatically deleting them without notice.

[JohnnyB]

MW Pro 7 tags the email with a red tag. I don't need added SPAM notification. With MW I can correct its color and turn off the delete if it is Good and not SPAM. With, I think, AVAST I cannot remove the SPAM in the Subject. As a result I have to be careful to change the header if I reply or forward the email. Also, it is annoying to see it listed in the folder with a great big SPAM.

[Digerati]

MW Pro 7 tags the email with a red tag. I don't need added SPAM notification.

I agree. I'm the same way. But it is not MailWasher putting the *****SPAM***** in the subject.

You keep mentioning Avast, but Avast should have nothing to do with this - unless you have configured Avast to look for spam too. That is unnecessary, IMO.

If you don't have Avast configured that way, then it is your email host adding the *****SPAM***** and not MailWasher.