Spam not marked as [-SPAM-]

[#1]

After 20/10/2025 no spam / junk messages have been marked with [-SPAM-] in the email Subject field.

In the Plusnet email management portal our long standing spam settings remain enabled and unchanged,
what has worked very well for years appears to have stopped functioning.

[#2]

All my spam is now appearing in Inbox and not marked as spam. After change of email provider?

[#3]

We have not been notified of a migration to GreenBy for our <names>@<account>.plus.com style of email accounts.

Increasing the spam sensitivity setting in the Plusnet email portal made no difference.

The spam detection & [-SPAM-] flagging process has stopped working.

[#4]

@marshmallow 

Until such time as you receive personal notification your email provider has not changed.  Email routing has changed but everything still comes in via the antivirus / spam filtering platform.

Why its behaviour has apparently changed has been flagged to the business.

[#5]

I have the same issue. In last two weeks the number of phishing emails has increased fourfold. I have reported them as spam but they keep coming.

[#6]

Is someone from Plusnet looking into this? The amount of spam is really annoying

[#7]

@gashouse  / @marshmallow  Is the spam all of a particular 'type'?

[#8]

I get mcafee protection expired, b and q you’re a winner (lots and lots of those with different contents), Argos you’ve won an apple bundle, mediamarkt (all in German) you’ve won a MacBook. Is that what you wanted to know?

[#9]

They all do sound similar in content, (apart from the mcafee one). Do you use an email client or just webmail?

[#10]

I generally use IOS. I have been getting this stuff for a long time but it used to be diverted into Spam

[#11]

As a matter of interest why are you interested in the content? Spam is spam and should be dealt with by plusnet

[#12]

@marshmallow OK. I'll leave this for @Townman  -- he has more of a handle on it than I have.

EDIT

As a matter of interest why are you interested in the content?

Because when you get a lot of spam, it quite often originates fro the same source - knowing where it comes from can  be useful in suggesting ways of alleviating it. 

[#13]

The deluge of spam emails come in from a never ending array of new senders and on a broad range of topics.

If we could have the Plusnet Spam filter working again and marking the vast majority of this stuff as [-SPAM-] that would would bring considerable respite.

Here is a clip of a header from one of these junk messages :-

Authentication-Results: mail.enmail.co;
	dkim=none;
	spf=fail (mail.enmail.co: domain of czsxcxf@aliexpress.com does not designate 27.194.164.10 as permitted sender) smtp.mailfrom=czsxcxf@aliexpress.com;
	dmarc=fail reason="No valid SPF, No valid DKIM" header.from=aliexpress.com (policy=reject)

[#14]

Ah, another one getting 'aliexpress' rubbish - and yes, these are coming from China.

[#15]

 

Here is a clip of a header from one of these junk messages :-

Authentication-Results: mail.enmail.co;
	dkim=none;
	spf=fail (mail.enmail.co: domain of czsxcxf@aliexpress.com does not designate 27.194.164.10 as permitted sender) smtp.mailfrom=czsxcxf@aliexpress.com;
	dmarc=fail reason="No valid SPF, No valid DKIM" header.from=aliexpress.com (policy=reject)

---

@PhilipHeyes 

I took the liberty of analyzing those headers via an automated tool and the result is as follows 

dkim=none No DKIM signature was found in the message headers.

Legitimate AliExpress mail always includes DKIM — so this message was likely spoofed.

spf=fail The sending IP (27.194.164.10) is not authorized to send mail for aliexpress.com. Strong evidence of spam or phishing.

dmarc=fail Since both SPF and DKIM failed, DMARC also fails.

The domain’s DMARC policy says to reject — so your mail server should have rejected this outright.

So technically, the message fails all major authentication checks.

Can you check the full headers to check the presence or absence of spam analysis headers (e.g., X-Spam-Status, X-Spam-Score, etc.).

It's looking like the previous spam filtering is being bypassed somehow. A routing change was mentioned in a previous post and when something that previously worked stops the first question to ask is what's changed?