1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
0
Hi, did you try to send individual emails to those addresses (or similar test ones that you created) to really validate that the issue is not on recipient mail server side ? You would then probably get other info re. NDRs
Similarly, to get more details about such problems, setting SNS notifications providing more details is very useful. See https://docs.aws.amazon.com/ses/latest/dg/notification-contents.html
Hope it helps! Didier
Contenuto pertinente
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata 9 mesi fa
- AWS UFFICIALEAggiornata 2 anni fa
Thanks for your feedback. Yes, we had tried sending individual emails. So email to same recipient from someone@yahoo.com works however, from someone2@hotmail.com never arrives and results in an NDR. I was wondering if there were any logs we could see on SES on the SES Side. Most SES Stats seems to be delivery (sending) related. The sender gets NDR with as below. The IP (52.5.58.6 mentioned in NDR seems to be Amazon one)
email@mydomain.com 7/13/2023 11:03:39 AM - Server at LO0P123MB6939.GBRP123.PROD.OUTLOOK.COM returned '550 5.4.316 Message expired, connection refused(Socket error code 10061)' 7/13/2023 10:53:12 AM - Server at mydomain.com (52.5.58.6) returned '450 4.4.316 Connection refused [Message=Socket error code 10061] [LastAttemptedServerName=mydomain.com] [LastAttemptedIP=52.5.58.6:25] [SmtpSecurity=-2;-2] [CWLGBR01FT030.eop-gbr01.prod.protection.outlook.com 2023-07-13T10:53:39.401Z 08DB82ED0BE846D1](Socket error code 10061)'