- Newest
- Most votes
- Most comments
Updating with what turned out to be the problem. I doubt it will be useful to anyone.
No, AWS was not blocking my IP.
It looks like I had a broken iptables configuration. There was a custom script that configured the firewall on the server, but it was crashing before it could permit established/related traffic inbound on IPv4 (IPv6 was working fine). Because SES's SMTP endpoints are all IPv4, traffic to it was not working. Every other service on this host was working fine because they were all inbound, not outbound.
In this specific case, I was able to verify the problem was coming from iptables by running a tcpdump on all ICMP traffic on the affected interface, and pinging the SMTP server. I could see the ICMP replies come in, but the ping could not receive them.
Troubleshooting info here: https://docs.aws.amazon.com/ses/latest/dg/troubleshoot-smtp.html
Sounds like you have done some pretty good validation. I would recommend opening a support case to make specific query about the service. re:Post is a community forum so there is a limit to the specific knowledge of any service changes that may occur.
Hope this helps.
Relevant content
- asked 4 years ago
- asked 2 years ago
- AWS OFFICIALUpdated 17 days ago