on 28-10-2018 06:02 PM
It looks like the certificate on the Pipex SMTP server has expired overnight, I have the SMTP server setting set to smtp.dsl.pipex.com (using Windows Mail on Windows 7), although this may just be an alias at the TalkTalk end that goes to some other server.
@SiHancox has also reported the same issue in another thread : https://community.talktalk.co.uk/t5/Email-Webmail/Problem-with-Pipex-POP-server/m-p/2268900
Attempts to send emails using Pipex SMTP are failing for me with the below error :
@SiHancox has provided more detailed screenshots in the other thread mentioned above.
Please could this be looked into, and the certificate renewed if this is indeed just an expired certificate causing the issue.
on 01-11-2018 01:56 PM
Thanks, I’m still searching the web at the moment, lots of stuff regarding on how to “trust” an expired certificate, not much about the process of updating one, other than deleting your account and then adding back, apparently that process may trigger a new certificate download.
Reluctant to do that at the moment without confirmation that the method actually works, and especially since no one yet has informed on the new certificate availability.
on 01-11-2018 01:00 PM
Strangely I couldn’t find much online regarding macOS Mail and the certificate update process, must be a “black art”, at odds with the supposedly “keep it simple” mantra, ah well, that’s progress.
I’ll keep looking, but in the mean time I’ve posted the question on the Apple forum, someone I’m sure will have knowledge of this process and may therefore enlighten me.
Just out of curiosity, will Windows Mail (or whatever manages keys/certificates) allow you to see certificate details, if so has the date changed, or is that sort of thing locked off from the user?
on 01-11-2018 12:42 PM
on 31-10-2018 11:43 PM
I've just looked at the certificate under Keychains on macOS and it remains unchanged so far as the date is concerned, that might be due to the fact I've recently marked it "Trusted" (so I could keep sending mail) or that the "system" takes a little while to refrest outdated ones even when the new are made available, will keep a watch out.
on 31-10-2018 01:30 PM
Another poor response from TT and not really unexpected.
This is also affecting people recieving e-mails from us, quote from one of my contacts:
"You definitely have gremlins, your email come with a warning that TalkTalk had not encrypted it, and another one saying Gmail could not verify that this email was from"
E-mails sent to iCloud address are just being returned to me as undeliverable:
"Delivery to the following recipients was aborted after 13.9 hour(s):
Reason: The following message to firstname.lastname@example.org was undeliverable.
The reason for the problem: Maximum Retry Queue Age Reached
Reporting-MTA: dns; cmout2mk [xxx.xx.xxx.xx]
Received-From-MTA: dns; [xxx.xxx.x.xx] [xx.xx.xx.xx]
Arrival-Date: Tue, 30 Oct 2018 09:32:28 +0000"
Jolly poor show Talk Talk and no response, that I know about. from moderators here...
on 29-10-2018 05:15 PM
29-10-2018 01:25 PM - edited 29-10-2018 01:27 PM
I am having a similar issues and have sorted by clicking ok on my laptop but dont appear to have the option on my iphone 😞
I had the option on my iPad Mini 2 to “Accept” or “Continue”, can’t remember which, but on the iPhone X it just gave me “View” or “Cancel”. After a quick search the only way around it that I found was to delete the Pipex Mail Account and then Add it back again, the reason this works is during the last part of setup when it’s checking the details and connections, you are prompted to “accept” what it can’t automatically confirm (I believe it’s the outdated certificate), once done you should be back up and running again.
on 28-10-2018 06:57 PM
Thanks for explaining how the certificate update process will likely go and that seems to mirror what has happened previously. I had a similar Mail issue several years back and recall having to trust the outdated certificate then, didn’t really give it much attention after that but can remember noticing the certificate date had changed automatically somewhere along the line. So it appears when new ones get pushed out they either update or replace the old, in Apple Keychains anyhow, I’ll keep watching this discussion and my Keychains to see what happens.
on 28-10-2018 06:21 PM
on 28-10-2018 06:16 PM
I’ve replied in the other discussion, but having seen your security warning do you not just select “Yes”, my Apple devices were basically asking the same and once done I’ve not been asked again.
I didn’t see any harm in agreeing to an outdated certificate because the server info was still relevant plus I assume TalkTalk will issue an updated one in due course, and it better than reverting to non-ssl mode!