I'm also having the same problems emails being sent to my dsl.pipex.com address are bouncing or not being received. Problem appears to have ben going on for a few days now. The soomner we are moved from the legacy email system to the new talk talk servers the better.
I have had 2 emails bounced this morning from the same sender
Reporting-MTA: dns; know-smtprelay-3-imp [184.108.40.206]
Received-From-MTA: dns; [192.168.0.10] [220.127.116.11]
Arrival-Date: Tue, 14 Jan 2020 09:55:03 +0000
Final-recipient: rfc822; email@example.com
Diagnostic-Code: smtp; 550 5.1.1 rIuei9JJ4QiTy Recipient Undeliverable (TT512)
Last-attempt-Date: Tue, 14 Jan 2020 09:55:06 +0000
The soomner we are moved from the legacy email system to the new talk talk servers the better.
If they were better configured things might improve. They can't even keep the correct time (which is a trivial thing to do).
Hi PeterAA, can you send me some of the emails including:
the timestamp the mail was sent, sender address & recipient address.
Any examples will be passed to the admins for a response and investigation.
And it's started again.
Always seems to be shortly after midnight (for me).
My mail-fetching processes (for 3 different accounts) are now reporting "authorisation failed".
It really shouldn't be happening. It's not as if TalkTalk don't know about it happening, and they should be able to prevent it.
PS: It's smtp.talktalk.net that has the slow clock. mx.talktalk.net appears to be OK.
I have, are the senders still getting bounced mail since the servers were reset today?
E-mail is completely broken today, I've been unable to send anything all day, and incoming mail is massively hindered. Many of the usual 'Connection to the server failed or was dropped.' messages and quite a few '4.1.1 Too many messages' with the occasional '5.7.0. Authentication denied (TT320)' for good measure. Jeez guys get it together!
If I was sending group emails and got the 4.1.1 To many messages bounceback I'd conclude that several of the addresses were incorrect or didn't connect to recipient mailboxes perhaps because of blocking by those mailboxes. A dirty distribution list is something under the sender's control which is why this is a temporary error not a permanent block.
But, in parallel, if I got the 5.7.0. Authentication denied (TT320) that would tell me that I'd exceeded the number of allowed outgoing server authentication attempts in the last hour. That's a hard block but with a time-out so I'd just use the time to check my mail list and with a clean distribution list I'd be able to retry an hour after the last fail.
But, in parallel, if I got the 5.7.0. Authentication denied (TT320) that would tell me that I'd exceeded the number of allowed outgoing server authentication attempts in the last hour.
There's a hard-wired limit on authentication attempts per hour? First I've heard of it.
What is it, and how is it counted?
RFC 3463 - Enhanced Mail System Status Codes - January 2003
This may be useful as a permanent or persistent temporary notification.
These errors will result in the SMTP connection being dropped, and the sending mail server will advise the user that their mail could not be delivered.
5.7.0 Something related to security caused the message to be returned, and the problem cannot be well expressed with any of the other provided detail codes. This status code may also be used when the condition cannot be further described because of security policies in force.
530 Authentication problem