Can't open port 25 (URGENT)

Question

Hey my team and I are building an email verification tool, and we need to open port 25 to be able to do SMTP checks, I already read this article: https://repost.aws/knowledge-center/ec2-port-25-throttle

I submitted an application at least 12 times using this form: https://support.console.aws.amazon.com/support/contacts#/rdns-limits

And bottom line I just received templated messages explaining why I'm not a fit, I requested an account manager to appeal the decision, but unfortunately, nobody reached out.

All of the people I see online with the same problem as me haven't found a solution.

We need this to deploy it in our software. Thanks in advance!

Sivaraman Selvam · Answer

Hello,

You could still use port 465 or 587 to connect to SMTP using Amazon SES: https://repost.aws/knowledge-center/ses-set-up-connect-smtp

Leo K · Answer

The advice offered by others is accurate, but I'd like to add that the best way to send emails in AWS is with SES (as also others suggested) and specifically, using the SES API instead of SMTP: https://docs.aws.amazon.com/ses/latest/dg/send-email-api.html

If you're sending emails from your own, custom code, I would recommend switching from SMTP to the Amazon SES API. The SMTP interface only supports authenticating with a username and password that are derived from static access keys associated with an IAM user (https://docs.aws.amazon.com/ses/latest/dg/send-email-concepts-credentials.html), meaning that it doesn't support temporary credentials. The Amazon SES API and SES API v2 interfaces support temporary credentials issued for an IAM role, such as an EC2 instance role or Lambda execution role, and don't require setting up long-term static credentials at all, making creating a secure setup much more straightforward.

David · Answer

I've seen these denied in the past if you don't offer an *explanation* on how you will ensure the setup will not result in spam messages.

Can't open port 25 (URGENT)

Relevant content