This is what I see: $ host -t mx leunet.ch leunet.ch mail is handled by 10 rrmx.imp.ch. $ nc -4 -vz rrmx.imp.ch. 25 Connection to rrmx.imp.ch. 25 port [tcp/smtp] succeeded! $ nc -6 -vz rrmx.imp.ch. 25 nc: connect to rrmx.imp.ch. port 25 (tcp) failed: Network is unreachable nc: connect to rrmx.imp.ch. port 25 (tcp) failed: Network is unreachable nc: connect to 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 < mailop@mailop.org> 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, do you see any problem), or that > 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- > -- > I m p r o W a r e A G - Leiter Commerce Kunden > ______________________________________________________ > > Zurlindenstrasse 29 Tel +41 61 826 93 00 > CH-4133 Pratteln Fax +41 61 826 93 01 > Schweiz Web http://www.imp.ch > ______________________________________________________ > > _______________________________________________ > mailop mailing list > mailop@mailop.org > https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop > -- keep raising the bar
_______________________________________________ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
