Post 21 on this thread has a moderator writing; "We have received word back from our email team and this should be fixed now." No details forthcoming on what revisions have been made.
Today I received a direct message advising me that no changes were made to my email account, which may be correct but I suspect is not the full story.
Post 32 raises the topic of SPF records for the first time.
Post 33 is me asking for info to correctly populate the SPF record with BT server details.
Post 37 has BT declining to assist with SPF config info, telling me to contact 123 Reg.
I don't want to go off the deep end and rail against BT; I have received two direct messages as a result of this thread and (as best as I can tell) I have not an email issue for 6 days now, but a bit more openness about the revisions made /not made on 21st April, along with some advice on what BT elements need to be included in a SPF entry to cover the outbound mail, would be welcome.
Currently I don't know whether I have an issue or not.
Hi
I am still getting bouncing emails. Luckily I am on a group who mail every day. The group advises of bouncers which is handy. Got three today. Never received one email from them.
At this point it may be good to see SPF text from somebody which works.
For info for fellow sufferers:
As a result of my post #87, a BT mod asked me by PM to send the delivery failure details, which I did.
I have now had a PM reply saying the info I sent would be added to the investigation, and they'd get back to me.
No indication of timescale.
My most recent delivery failure notification was at 13.09 today for an email sent at 12.16 yesterday, so this issue persists.
It looks like the spam settings filter on the 123reg Control Panel are reversed. Strong = Weak and Weak = Strong. I've just changed and it works a lot better now. Is it all fixed? Who knows but I now have an SPF in place which Dmarc seems to think might be alright. I used template from Bob at yorkley -thank you Bob.
As a follow-up to last email. Direct forwarding to Btinternet still no good. Roundabout via GMAIL works though.
Are you forwarding your 123-reg email to Gmail and then forwarding that to BT?
Another question - are you forwarding a domain email or is it an actual 123-reg email you are forwarding?
Bob
Are you forwarding your 123-reg email to Gmail and then forwarding that to BT?
Another question - are you forwarding a domain email or is it an actual 123-reg email you are forwarding?
1 Forwarding from 123reg to a Gmail account then forwarding to a Btinternet address.
2. Forwarding my domain email as the 123reg email system cost.
Basically, the idea was to have the ability to change my ISP without having to change my email.
What puzzles me is that a lot of emails are arriving without any delay or problem (including the notifications of posts to this thread!), but the occasional one each day gets delayed.
Sigh!!
@graywallis wrote:
1 Forwarding from 123reg to a Gmail account then forwarding to a Btinternet address.
2. Forwarding my domain email as the 123reg email system cost.
Basically, the idea was to have the ability to change my ISP without having to change my email.
Why bother to forward it to a BTinternet address at all, just forward it to the Gmail address and collect it from there. If you regularly change ISP, why bother with an ISP address from any provider.
Graywallis
Thanks for that info. Same as me then and the same reason.
I also have a gmail account but only because I have a tablet. Never use it normally but may try the forward.
Somebody sent me a fialure message:-
From: mailer-daemon@secureserver.net
Date: 28 April 2021 at 10:34:42 BST
To: srs0=dq/bjvghwg=jy=cyaptygehtrwwsme@britishtelephones.com
Subject: Message Delivery Failure
This is an automatically generated Delivery Status Notification.
Delivery to the following recipients failed permanently:
* xxxxxxxx@btinternet.com
Reason: There was an error while attempting to deliver your message with [Subject: "Re: Footpath at crossing cottage"] to xxxxxxx@btinternet.com. It has been in queue too long, and will not attempt delivery again.