Ok thanks. I've been asked to pass on examples of the issue.
Well, I've already posted examples here of smtp.dsl.pipex.com refusing any incoming SMTP connexion when the sending issue occur. What more can be needed as "an example"?
@OCE_Ady its not easy getting proof of messages that have not been delivered as I am sure you will appreciate. For instance, I have not received some regular, daily, email newsletter this morning.
Also, where do we stand on the missing emails from the outage of the weekend before last? Are the Admins still working on recovering these? Has the Manager you involved been able to get a response?
And, finally, can me please,Please, PLEASE have an update on when migration of Pipex mail to the new email platform will happen
Hi gmlack, please send the latest report you posted.
You can send it to me by personal message include all the full email addresses.
There is no email address involved. This was the SMTP server rejecting any incoming call (and I suspect that the IMAP server was doing the same at the time).
I cannot give you the additional information you requested as only the SENDER of the emails will have this information. I gave you everything that groups.io gave me, which should be sufficient for the admins to find the right place in the system log files.
I suspect the TT email people are trying to give both of us busywork as a distraction here.
They must have system error logs, or can send test emails until it fails, as we have established that email doesn't have to leave the TT network for the problem to occur - and they should have access to non TT email for testing purposes anyway. Customers shouldn't have to do this for them.