Hi, Same from here, hosts responds to v6 :
Trying 2001:4060:1:1001::12:5... Connected to 2001:4060:1:1001::12:5. Escape character is '^]'. 220-obelix.imp.ch ESMTP Postfix Trying 2001:4060:1:1001::12:4... Connected to 2001:4060:1:1001::12:4. Escape character is '^]'. 220-asterix.imp.ch ESMTP Postfix Trying 2001:4060:1:1001::12:6... Connected to 2001:4060:1:1001::12:6. Escape character is '^]'. 220-idefix.imp.ch ESMTP Postfix Sébastien RICCIO SYSTEM ADMINISTRATOR P +41 840 888 888 F +41 840 888 000 M [email protected]<mailto:[email protected]> From: mailop <[email protected]> On Behalf Of Noel Butler via mailop Sent: vendredi, 17 mai 2019 04:55 To: [email protected] Subject: Re: [mailop] Anyone on this List with Access to Amazon SES Maillogs? Connected to 2001:4060:1:1001::12:5. Escape character is '^]'. 220-obelix.imp.ch ESMTP Postfix Connected to 2001:4060:1:1001::12:4. Escape character is '^]'. 220-asterix.imp.ch ESMTP Postfix Connected to 2001:4060:1:1001::12:6. Escape character is '^]'. 220-idefix.imp.ch ESMTP Postfix On 16/05/2019 20:32, Yiorgos [George] Adamopoulos via mailop wrote: This is what I see: $ host -t mx leunet.ch<http://leunet.ch> leunet.ch<http://leunet.ch> mail is handled by 10 rrmx.imp.ch<http://rrmx.imp.ch>. $ nc -4 -vz rrmx.imp.ch<http://rrmx.imp.ch>. 25 Connection to rrmx.imp.ch<http://rrmx.imp.ch>. 25 port [tcp/smtp] succeeded! $ nc -6 -vz rrmx.imp.ch<http://rrmx.imp.ch>. 25 nc: connect to rrmx.imp.ch<http://rrmx.imp.ch>. port 25 (tcp) failed: Network is unreachable nc: connect to rrmx.imp.ch<http://rrmx.imp.ch>. port 25 (tcp) failed: Network is unreachable nc: connect to rrmx.imp.ch<http://rrmx.imp.ch>. port 25 (tcp) failed: Network is unreachable So maybe AWS SES is trying to connect to the IPv6 address and cannot? On Thu, May 16, 2019 at 11:42 AM Benoit Panizzon via mailop <[email protected]<mailto:[email protected]>> wrote: Please contact me off-list Short story: A customer of Amazon SES is attempting to send emails to one of our customers. Our customer is not getting them, we don't see ANY trace of those emails in our logs, they just seem to disappear in transit. Re-Tested yesterday, exact times known. Long lasting cases have been opened @ Amazon but the only problem, according to Amazons SES Support is, that the recipient MX is not correct and we should fix that issue, without Amazon being able to tell us what's incorrect (leunet.ch<http://leunet.ch>, do you see any problem), or that leunet.ch<http://leunet.ch> does not have a DKIM entriy (cause disproved by Amazon's own customer showing that he can perfectly send emails to recipients in other domains which also do not have a DKIM entry) Mit freundlichen Grüssen -Benoît Panizzon- -- Kind Regards, Noel Butler This Email, including any attachments, may contain legally privileged information, therefore remains confidential and subject to copyright protected under international law. You may not disseminate, discuss, or reveal, any part, to anyone, without the authors express written authority to do so. If you are not the intended recipient, please notify the sender then delete all copies of this message including attachments, immediately. Confidentiality, copyright, and legal privilege are not waived or lost by reason of the mistaken delivery of this message. Only PDF<http://www.adobe.com/> and ODF<http://en.wikipedia.org/wiki/OpenDocument> documents accepted, please do not send proprietary formatted documents
_______________________________________________ mailop mailing list [email protected] https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
