SEM-URIBL & SEM-URIRED tests failing, genuine emails going into junk folder
Problem reported by Arthur G. - June 11 at 2:16 AM
Resolved
All of a sudden SEM-URIBL & SEM-URIRED tests have started failing and majority of genuine emails are now going into junk folder.

Checked spameatingmonkey.net online and everything is ok.

Prior to that antispam settings were solid, no false-positive emails going into junk folder and no issues with deliverability whatsoever.

Is anyone else having the same issue?

9 Replies

Reply to Thread
1
Alex Clarke Replied
I've noticed SEM-URI checks returning false-positives too.

Example spam information from email header:

X-SmarterMail-Spam: SPF [PermError]: 5, Cyren [Unknown]: 0, Message Sniffer [code:0]: 0, DKIM [None]: 5, SEM-URI [count:2]: 10

The domain doesn't appear on any of the SEM lists either.

Here's the same header information from an email sent by ST (support@smartertools.com).

X-SmarterMail-Spam: SPF [Pass]: 0, Cyren [Unknown]: 0, Message Sniffer [code:0]: 0, DKIM [Pass]: 0, SEM-URI [count:2]: 10

2
Steve Norton Replied
Marked As Resolution
It appears to relate to www.w3.org.
I've applied for it to be removed from the SEM database and whitelisted.
1
Alex Clarke Replied
Thanks for this Steve!
1
Steve Norton Replied
I've had a confirmation email, I've checked it and it's not listed now so we should be good from here on in.
0
Arthur G. Replied
Thanks Steve and Alex for your kind help!
0
Ionel Aurelian Rau Replied
@Steve: how is this related to www.w3.org? Can you please elaborate?

And how is this resolved? We`ve seen SEM-URIRED throw false positives a few days ago and disabled it, but now SEM-FRESH and SEM-FRESH10/15/30 have been labeling all incoming mail as SPAM all day long today.
0
Steve Norton Replied
I looked for all http references in the body of the email including raw HTML and looked up the domain and the FQDN via https://spameatingmonkey.com/lookup
www.w3.org was on the lists as described by the OP and I used the removal process under the list status to have it delisted.
0
Ionel Aurelian Rau Replied
Ah, OK, so the www.w3.org link in mail bodies was failing spameatingmonkey`s checks?
Well, since yesterday we`ve had hundreds of emails from very different people, from a wide variety of domains and all are failing spameatingmonkey. No way we`re going to comb through all of these emails in RAW view and check all referenced URLS on spameatingmonkey to find the culprit..
0
Steve Norton Replied
Look in your DNS cache under net.spameatingmonkey.fresh. and you'll see the culprits cached there.

Reply to Thread