Error 552 when sending emails

[#1]

Hello

I am receiving a bounceback  "552 Spam Message Rejected" error when I send an email which contains the domain name "theomnicollective.com" to a PLUSNET email address

Even if I send a simple email with no attachments and it just contains the single line "theomnicollective.com" and nothing else that is sufficient  to trigger the bounceback error.

It doesn't happen sending to other email providers just when sending to PLUSNET

Unfortunately it is my daughters wedding caterers domain and she is pulling her hair out.

Help!

[#2]

I can confirm that this happens if this domain name is used as the email subject - following bounce back from @outlook.com sending to one of my PN mailboxes

DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outlook.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=AJD6s2lVUzCugujOR1/QqX/gqN0LrBCtRq4YCcJpkPU=;

b=ZBAPnI4Cw4j82Am6D7wRqkoRCVY00tx99ezFS2ZB4ot0GO+4MuT2jBD93NA4VQakw0aqWQqjEh7fUvDaUUKVXQx089DWB6dKezZXvrDOErC/dMeQmsxM2P9uG628yhI9VjYhxeiItCCvht7h8Iak3CYd2bI5O5MZ+xg8r9FMN5qgO/nLPgGinzJfz5WfoimLH+kyHGlNgJ0fJhvKv/9RrZdQ9GwjkaCypWzWE8ePIw2au/cF7JLM66kksyli2nRthcWPUMR//uadRS8TD44Xn3RQTzo8omgfhX+Zi7uBXMBNKBnZh/jaDNk6CsiwRGFm54e42kfJ3HZITi6ka1Y+AA==

Received: from HE1EUR01FT059.eop-EUR01.prod.protection.outlook.com (10.152.0.54) by HE1EUR01HT208.eop-EUR01.prod.protection.outlook.com (10.152.1.139) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.527.22; Tue, 13 Mar 2018 17:17:52 +0000

Received: from HE1PR02MB1372.eurprd02.prod.outlook.com (10.152.0.52) by HE1EUR01FT059.mail.protection.outlook.com (10.152.0.241) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.527.22 via Frontend Transport; Tue, 13 Mar 2018 17:17:52 +0000

Received: from HE1PR02MB1372.eurprd02.prod.outlook.com ([fe80::78c7:1396:b23d:2baf]) by HE1PR02MB1372.eurprd02.prod.outlook.com ([fe80::78c7:1396:b23d:2baf%14]) with mapi id 15.20.0588.013; Tue, 13 Mar 2018 17:17:51 +0000

From: XXmeXX <XXmeXX@outlook.com>

To: "XXmeXX@mydomain.me.uk" <XXmeXX@mydomain.me.uk>

Subject: theomnicollective.com

Thread-Topic: theomnicollective.com

Thread-Index: AdO67zTxoGkq6qSWQB6V/89zJSOCEA==

Date: Tue, 13 Mar 2018 17:17:51 +0000Message-ID: <HE1PR02MB1372D1D3E022021AD2331FC5EDD20@HE1PR02MB1372.eurprd02.prod.outlook.com>

Accept-Language: en-GB, en-US

Content-Language: en-US

X-MS-Has-Attach:

X-MS-TNEF-Correlator:

x-incomingtopheadermarker: OriginalChecksum:2A5B1088E87E492127A1802515C8D38D5BA85FA819C021555081540E1CFC1E33;UpperCasedChecksum:CF269303BC54FE525753CA7654C862B1E2C3DECD0FB52447EC7E886172F00859;SizeAsReceived:6787;Count:43

x-tmn: [HE/H120+nBwzRkmDGH1bEvqiKIZ7gEml]

x-ms-publictraffictype: Email

x-microsoft-exchange-diagnostics: 1;HE1EUR01HT208;7:KRjRrbCfKF1vI52i/dzqOGTr/vfEOcnwAqHC5BaaiEvMAkfb0eZnEKTDiL08/qdfmL3z9RLC0j+TGGXBsmxRsoFtTvWlqpcGO/9wkWIqXkly62zE4V0ab8gRZ7FSMvRkAnNX5QgoxEwugY5l8pnl5gBhqvpJeef/OZLeDuLu2jlB4HiiGMpUZoxdmfJy13duJqd0U1JWvesaB/2JinQX2AYsD0OJt7LbPP3eO7V9bo2R6fVFt465N38jhn492m9E

x-incomingheadercount: 43

x-eopattributedmessage: 0

x-microsoft-antispam:

UriScan:;BCL:0;PCL:0;RULEID:(7020095)(201702061078)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322404)(1601125374)(1603101448)(1701031045);SRVR:HE1EUR01HT208;

x-ms-traffictypediagnostic: HE1EUR01HT208:

x-ms-office365-filtering-correlation-id: 2533dbee-f93f-4e2e-0dfa-08d589065a40

x-exchange-antispam-report-cfa-test:

BCL:0;PCL:0;RULEID:(444000031);SRVR:HE1EUR01HT208;BCL:0;PCL:0;RULEID:;SRVR:HE1EUR01HT208;

x-forefront-prvs: 0610D16BBE

x-forefront-antispam-report:

SFV:NSPM;SFS:(7070007)(98901004);DIR:OUT;SFP:1901;SCL:1;SRVR:HE1EUR01HT208;H:HE1PR02MB1372.eurprd02.prod.outlook.com;FPR:;SPF:None;LANG:;

x-microsoft-antispam-message-info: 9GK/fgkeQ12Z3/PDoLJ5e0Cn9X1z4CfMc9H4geHUqp9hRnxl5m0GC0zmu9z9KAJG98TZH9nFtOR7ZVuXGa7mFUqsbV2uB//NvRN/sF5JxwQ70VnRNOu7sYDboArhPJbNWFhp5FurIRBTHcKFSeD4gbVgiRiCIacqSonFC1MasJ2IowETAsQwhZIVaW1oZRi0

spamdiagnosticoutput: 1:99

spamdiagnosticmetadata: NSPM

Content-Type: multipart/alternative;        boundary="_000_HE1PR02MB1372D1D3E022021AD2331FC5EDD20HE1PR02MB1372eurp_"

MIME-Version: 1.0

X-OriginatorOrg: outlook.com

X-MS-Exchange-CrossTenant-Network-Message-Id: 2533dbee-f93f-4e2e-0dfa-08d589065a40

X-MS-Exchange-CrossTenant-originalarrivaltime: 13 Mar 2018 17:17:51.9437 (UTC)

X-MS-Exchange-CrossTenant-fromentityheader: Internet

X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa

X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1EUR01HT208

@Kelly / @bobpullen - is there any insight as to why this and other domain names have been black-balled?  There seems to be a spate of them of recent times.

Would white listing this domain in the PN email spam filter help any?

[#3]

... answer to my own question - well in part ...

If these emails are coming from @theomnicollective.com the putting that domain name in the white sender's list will cause the spam filter to allow the email "in" see here - https://www.plus.net/my.html?action=myemail&s=1&redirected=yes > Manage My Mail > Spam > White list near the bottom.

However replying fails...

Your message did not reach some or all of the intended recipients.

     Subject:     RE: theomnicollective.com

      Sent:  13/03/18 17:42

The following recipient(s) cannot be reached:

     'XXmeXX' on 13/03/18 17:42

            552 vnwBePhVNIlWkvnwCeKxw3 message rejected due to spam or virus. If you believe this is in error please login to your portal or contact your ISP support team.

I guess that the bit in red is generic text, as it is of little help to Plusnet users.

[#4]

Thanks for investigating but unfortunately they aren't always coming (in fact most of the time) from that domain - sometimes they are forwarded by my daughters boyfriend (he happens to be using a gmail account but I've also tried using other email providers)

[#5]

You can fix your daughter receiving those emails by putting the domain name or specific email address into the sender's white list - this will exclude ANYTHING sent by the whitelisted entity from SPAM filtering.

As I said, not a fix but something to help with part of the issue until a PN staffer picks this up.

[#6]

Thank you for suggesting that temporary fix for emails sent directly from that domain

[#7]

Is this still happening? Just checked the offending domain name and it's coming back clear.

[#8]

Hi Bob,

I just ran the test I did yesterday and it is not being rejected. Is there any insight as to why we are seeing so many similar issues with innocuous domain names please?

[#9]

It's born from our anti-spam vendor. They're good guys really, and there's always a legitimate reason for such false positives, but sometimes the nice guys get on the naughty guys' list. Typically from others reporting messages as spam, or messages hitting global spam traps.

[#10]

I wonder if it is because the domain is with GoDaddy?

[#11]

That shouldn't be a problem. The initial block might have been association through their IP addresses with other domains sharing the server. Later refinement could have provided more focused blocking releasing this domain (and others) from the block.

Unfortunately spam control is not an exact science.