Hey, I have tried submitting a request [57875736200] as stated in https://repost.aws/knowledge-center/ec2-port-25-throttle to get port 25 outbound traffic unblocked from my EC2 instance and VPC.
This is my use case:
Running a personal email server for myself currently and perhaps up to 10 people in the foreseeable future. Rarely sending email myself but still need to be allowed to send at all. My email server has a throttle set so it should never send mass-emails in short amount of time.
Unfortunately, I have received a copy-pasted response, like in https://repost.aws/questions/QUhOiYfU2ESzyjHNFLdih5lQ/smtp-port-25-outgoing-connections-blocked .
This account, or those linked to it, have been identified as having at least one of the following:
- A history of violations of the AWS Acceptable Use Policy
- A history of being not consistently in good standing with billing
- Not provided a valid/clear use case to warrant sending mail from EC2
Unfortunately, we are unable to process your request at this time, please consider looking into the Simple Email Service. https://aws.amazon.com/ses/
The first 2 possible reasons are simply just not true, so that leaves the third one. I have submitted a reply to elaborate, but it is unlikely that they will lift it. In that case, I'll just pack my bags and do business somewhere else since getting SES, as someone who will never do email marketing and have only myself as the user, defeats the entire purpose of a private mail server.
Now, seeing that running a personal mail server is probably not considered a valid use case, can we be given "valid" use cases to be allowed to send emails?
Cheers.
PS: I guess, even providing a succinct and well-written use case won't get you approved either. Don't use AWS EC2 at all if you plan to ever have a private email server. https://repost.aws/questions/QUmfBJQl3jTgWJP8Bt6mMiTw/guess-we-are-leaving-the-cloud-outbound-email-ports-blocked-aws-refuses-to-unblock
AWS OFFICIALUpdated 10 months ago
