An update for the list members, following a good remote troubleshooting session last night (which I apologise for taking up the whole meeting with), I think this is where things are with the Email issue.
1. Clive's domain and hosting provider have migrated his mail account to a new server, who's hostname escapes me. He can log into the webmail platform for this server with his credentials. 2. Clive's provider has not updated the MX record for his domain to point to the new server, so the mail still goes to the old server. 3. Clive's provider has turned off authentication on the webmail portal, and for imap access on this old server so Clive cannot view the new messages that are being received. So to reiterate that age old saying, in this case 'It's a DNS problem'... On Sun, 4 Jun 2023 at 15:12, Ralph Corderoy <ra...@inputplus.co.uk> wrote: > Hi Peter, > > Terry wrote: > > > Clive is back from his travels, but thinks that due to his email > > > supplier having upgraded their servers, he cannot access his emails > > > from Thunderbird. I don't think he can get them via webmail either. > ... > > I don't think I've seen this, but his first port of call should be his > > provider. He used to be on Talk Talk > > I think he's paid a company to provide email services for his own domain > for quite a while. His domain's MX record points to a secureserver.net > domain name. > > https://uk.godaddy.com/help/server-and-port-settings-for-workspace-email-6949 > refers to that domain name so perhaps it's something to do with GoDaddy. > > It's unclear where the problem lies. I'd first look for a precise error > message from Thunderbird. If that yields nothing then examine > Thunderbird's configuration and then try to manually make the same > connections. For example, if the connection details were what's on the > above page then each of these can be tried in turn. > > openssl s_client -connect imap.secureserver.net:993 > openssl s_client -connect pop.secureserver.net:995 > openssl s_client -connect smtpout.secureserver.net:465 > > Each should connect and await a command. Entering ‘QUIT’ exits. > > And as Terry said, contact the supplier as they can probably see what's > going wrong in their log files. > > -- > Cheers, Ralph. > > -- > Next meeting: Online, Jitsi, Tuesday, 2023-06-06 20:00 > Check to whom you are replying > Meetings, mailing list, IRC, ... http://dorset.lug.org.uk > New thread, don't hijack: mailto:firstname.lastname@example.org > -- Next meeting: Online, Jitsi, Tuesday, 2023-07-04 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk New thread, don't hijack: mailto:email@example.com