I am still getting "It has been in queue too long, and will not attempt delivery again." delivery failure messages. I have had 2 today...
Date: Sat, 24 Apr 2021 13:04:55 +0000 (UTC)
Date: Sat, 24 Apr 2021 13:25:57 +0000 (UTC)
I have had the most recent version of the SPF update in my DNS settings for over 48 hours now.
What am I doing wrong? 😞
I am having this problem over the last few days, exactly as described.
I have read the 'solution' in post 32, and the instructions on the 123 reg website.
I am not understanding any of the instructions, and am not at all comfortable to 'fiddle'. How is someone in my position going to solve this?
You all seem to know what you are doing 🙂
Will 123 reg do it for me if I ask them - or will I get caught in crossfire with them & BT?
Interesting. So far I haven't had another failure (AFAIK). Just adding the SPF record to my 123.com domain as advised earlier in this thread seems to have fixed it for my several redirected 123.com addresses (so far) .
The curious thing about this fault is that BT would advise me that an email couldn't be delivered because it had been in the queue too long - but the 'missing' email was then included below the fault message so nothing was actually missing. If BT managed to retrieve such messages from 123.com (without the SPF record) why did they report it as a fault at all? If it was a 'subtle' reminder to fix the SPF record it would have been far more customer-friendly to advise us of the solution rather than flagging it as a serious (undelivered email) problem when it never was!
Has there been a good technical description of why this all started about a week ago and why it was handled so poorly by BT?
Exactly what I’ve been thinking. 👍
See message 58
Yes, I have the same problem. I have submitted a 'Ticket' to 123Reg. Any other ideas?
@Roger1945 From my understanding, it's not BT that is managing to retrieve the message, it's 123-reg relay servers. The reason you get the failure and the msg as an attachment is that the 123-reg server sends the failure report to the email address in the X-SECURESERVER-ACCT header. This is usually pretty random looking but importantly will be your 123-reg domain. If you have a catch all email forwarder on the 123-reg you will get the failure report (assuming it doesn't get stuck in a queue).
Also, If I'm honest I'm not sure the SPF is what's fixed it here. I think it was what the BT admins did, but I expect it's more of an 'made it much less likely' than a permanent fix. If it was indeed the max concurrent connections they changed.
The permanent fix, of course, is not to forward the mail to the BT mail system in the first place and collect it direct from 123 Reg.
Email hosting is, I think, an additional cost service from 123 Reg.
I am reluctant to pay to resolve a technical issue which has been introduced by BT to a service which has hitherto been working without issue for some considerable time; years, in my case.