Plusnet Email servers giving random SMTP 550 errors for inbound emails

[#1]

I got same issue too....
Have changed names at the (AT) symbol so no spam bots pickup on it......
Senders domain exists, 100% !
Cheers
------------------------------

The following organization rejected your message: mx.avasin.plus.net.

 Diagnostic information for administrators:

Generating server: out4d.electric.net

Fix_Plusnet@name.plus.com
mx.avasin.plus.net
Remote Server returned '<mx.avasin.plus.net #5.0.0 smtp; 550 #5.1.8 Domain of sender address <Plz_Fix_Plusnet@amrbs.co.uk> does not exist>'

Original message headers:

Return-Path: <really_plusnet@amrbs.co.uk>

Received: from 1egrDI-0001mm-Ur by out4d.electric.net with emc1-ok (Exim 4.87)

        (envelope-from <Provide_updates@amrbs.co.uk>)

        id 1egrDM-00027z-UA

        for Pnet@me_me_me.plus.com; Wed, 31 Jan 2018 04:10:08 -0800

Received: by emcmailer; Wed, 31 Jan 2018 04:10:08 -0800

Received: from [81.134.199.213] (helo=PER-SVR-EXCH13.tw.local)

        by out4d.electric.net with esmtps (TLSv1.2:ECDHE-RSA-AES256-SHA384:256)

        (Exim 4.87)

        (envelope-from <SLA_plusnet@amrbs.co.uk>)

        id 1egrDI-0001mm-Ur

        for email@reboot.plus.com; Wed, 31 Jan 2018 04:10:04 -0800

Received: from PER-SVR-EXCH13.tw.local (172.18.89.101) by

 PER-SVR-EXCH13.tw.local (172.18.89.101) with Microsoft SMTP Server (TLS) id

 15.0.1210.3; Wed, 31 Jan 2018 12:09:21 +0000

Received: from PER-SVR-EXCH13.tw.local ([fe80::58f2:3b3c:43ae:1e3d]) by

 PER-SVR-EXCH13.tw.local ([fe80::58f2:3b3c:43ae:1e3d%15]) with mapi id

 15.00.1210.000; Wed, 31 Jan 2018 12:09:21 +0000

[#2]

So it's been a month (for me) and the problem is still present 

Plusnet!!!! Any progress on solving this issue????

[#3]

Still happening and still no response or any sign of progress by Plusnet. It seems that they don't care whether their customers can receive their mail or not...

[#4]

Yes, November this issue was first raised and it's now March...

[#5]

@Gandalf wrote:

Thanks for contacting us via Twitter @cerij101

We've raised this with our incident management team to investigate.

EDIT: For internal use, the reference number is: 105238

---

@Gandalf What was the conclusion from that reference to the incident management team?

[#6]

I sent a load more examples over, and it's hopefully been picked up again on this thread:

https://community.plus.net/t5/Email/False-rejection-of-valid-sender-domain/td-p/1492200/page/2

Keith

[#7]

Last I looked, there was some work scheduled to mitigate the issue. Possibly penned in for next week, but I'd need to check.

[#8]

Another month has gone by and still no signs of a fix to this issue which was certainly still occuring last week. Come on Plusnet, give this some priority.

Keith

[#9]

Not sure where we're at with this but it's a peculiar one. Ages ago I set up a Cron job to relay an email from an external domain with a single nameserver, via a third party smtp server, to a plusnet mailbox. This happens every 5 minutes and I've not seen a single failure

[#10]

Given that it is likely to be a DNS lookup failure I suspect you are ensuring that the relevant DNS is kept in cache somewhere by processing mail on a regular basis. We send mail to members with Plusnet addresses on an irregular basis - there might be several days without one and then several in one day, of which some may go through. When the error occurs it is always a domain does not exist error, which has never ever occured with any other recipient domain, but has done with every flavour of Plusnet service (Waitrose, GlobalNet and domains hosted on force9/megamailservers.eu as well as Plusnet addresses). I sent Kelly a selection of examples about 5 weeks ago to aid with nvestigation.

Keith

[#11]

---

@Gandalf wrote in January:

Thanks for contacting us via Twitter @cerij101

We've raised this with our incident management team to investigate.

EDIT: For internal use, the reference number is: 105238

---

Still happening. I've had a rejection from an address on globalnet.co.uk which is now part of Plusnet. Needless to say, the rejection message was correctly received on the domain which did not exist.

[#12]

@bobpullen,

Is the code for the system generating this event accessible to Plusnet?

If yes, how feasible is it to have some code inserted into the bit of code which handles this event to capture diagnostic information on the failure?

If it is a transient DNS issue, there is every possibility that when inspected later .... no issue is going to be found ... so in-event diagnostics are essential to identifying the root cause.

[#13]

FYI guys, this is tracked as IMT-74 on our side.   We've got some DNS work going on at the minute which we hope will resolve it.  I've asked for an ETA on when we should see the impact of that.

[#14]

That's good news, it was still happening this morning if you need a recent example.

Thanks

Keith

[#15]

This problem is now worse for me - 100% failures on e-mails sent to PlusNet users.