Mysterious delivery failure reason
|
Dave, ? ?MX lookup returned: lookup on : server misbehaving For a usual rejection case That text (and the three-digit code that should have preceded it) would have been issued by the member's email service during the connection from Groups.io. So most likely that service would have to be asked what it means. But in particular, port 53 in that IP address suggests that the receiving service mistook Groups.io as its DNS service provider, and attempted to look up that domain there. That's one seriously confused receiver. Also, I can't find any link between the user's domain name and the IP address Yes, Linode is a commercial service hosting Groups.io's web and mail servers. (I have sent substantially the same message to <[email protected]>. But maybe ? Good. Groups.io will want to make sure that its servers have the correct DNS entries in place. Or that there wasn't a glitch in the transaction with the receiver's service. But most likely this is not a Groups.io problem. It sounds like the recipient's server is rather confused about how to authenticate the message. Shal -- Help: /static/help More Help: /g/GroupManagersForum/wiki Even More Help: Search button at the top of Messages list |
|
On Fri, Oct 5, 2018 at 05:43 PM, SBL webmaster wrote:
"Misbehaving" is not very descriptive. Does anyone know what this is reallyLooks to my as if a nameserver somewhere along the line could not resolve the provided domain into an IP address. Google cannot find it either. I'm surprised that this tld is still being used. Try tomsk.ru instead. Hope this helps, Bruce? -- The system Help is your friend.??/static/help |
|
Yes, that does look odd and it could be a misbehaving dns server.? Be nice if you would post the resolution from support on this.
The MS lookup is:
The IP address of the mail server is:
So the lookup works on google dns servers at the present time. Toby |
MX lookup returned: lookup mpeks.tomsk.su on 173.230.155.5:53: server misbehavingThe :53 means that the error was during a NS lookup. The domain mpeks.tomsk.su currently has no NS records: ~ $ dig mpeks.tomsk.su ns ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 7063 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1 The "ANSWER: 0" means zero NS records. It's not normal, it confuses groups.io software. Consider email addresses @ mpeks.tomsk.su currently invalid, misconfigured. A NS check tool finds multiple errors: Coincidentally, the mail admin with an address @ mpeks.tomsk.su yesterday posted to the Russian-language mailing list for users of mail server software "Exim" I participate in: I'll notify him. |
Shal Farley
Bruce Bowman
Toby Kraft
Lena