Message Delivery Failure - Anyone else having problems?

[davidneill]

Very interesting. My domain provider is 123.Reg.

I have raised it with them but so far they have not responded.

[IanMK13]

As the OP, I can say that it's now over 24hours since I received a failure notification so the issue appears to have now been fixed.

I have also added SPF records to my domains hosted by 123-reg.  Their help pages very helpfully detail how to add an SPF record  through their control panel and the precise content of the record (as detailed earlier in this thread). Whether or not this prevents the occasional incoming email going into my BT junk filter (as suggested earlier in this thread) remains to be seen.

Thanks for everyone's contributions and the moderators' escalation.

[MrDiddins]

Still receiving failure notices. Quite random as to whether it happens or not.

[Roger1945]

Have you added the SPF record as suggested earlier in this thread?
So far it seems to work for me - no more 'lost' messages in the last 18 hours. Previously there would have been half a dozen or more.

[Dan_B1]

I feel like it’s getting better but still not fixed. Just did a bit of online shopping and no order confirmation emails have arrived! It worries me what emails I might be missing! So frustrating!

[timyarby]

I added the SPF thingy to 123-reg and so far so good.

[TimSGX]

@IanMK13

It’s nice to know there’s an answer but what is it that’s changed that requires this  additional step?  Any idea?

[licquorice]

It's not an additional step, it's always been good practice. Guess BT have tightened up the requirement for it to be implemented.

[sbadger]

Not had any failures since Friday morning (of an email from Thursday).

So far so good..  🤞

[jingars]

My last of the "In a queue too long" errors was received on Friday afternoon.

However, on Saturday I received a new variant (to coin a current phrase) of error.

Reporting-MTA: dns; p3plwbeout02-05.prod.phx3.secureserver.net [72.167.218.100]
Received-From-MTA: dns; mailex.mailcore.me [94.136.40.144]
Arrival-Date: Sat, 24 Apr 2021 04:15:55 -0700


Final-recipient: rfc822; my wife's email address@btinternet.com
Diagnostic-Code: smtp; 554 Message rejected on 2021/04/24 12:18:42 BST, policy (3.2.1.1) ID (603DC20809C13002) - Your message looks like SPAM or has been reported as SPAM

Last-attempt-Date: Sat, 24 Apr 2021 04:18:43 -0700

The email in question as a flyer from a UK-based sewing provisions website.

The Guv'nor is going to be upset if she thinks I am deliberately inhibiting her ability to hoard even more fabric than she already has, so could this rejection be down to a setting in my shiny new IPS tag?