- Newest
- Most votes
- Most comments
Hello,
This is Rajat from AWS Premium Support team.
I understand that you were denied the access to port 25 from EC2 and hence, you are not able to host mail services into the same. I would like to share with you that the decision to keep or remove port 25 restriction is based upon multiple security checks that AWS Trust & Safety performs and not to upsell AWS services to the customers. These checks are done to protect our IP reputation as well as different parameters of shared infrastructure, keeping secure interest of multiple AWS customers that will be using this infrastructure provided by AWS.
You can use SES to send out mails and can also setup incoming mails in SES but it cannot provide you POP3. In order to use a complete mailbox like service, you can use Amazon Workmail, which is a managed email and calendaring service with strong security controls and support for existing desktop and mobile email clients. You can configure your applications in a manner that high mail sending can be done through Amazon SES whereas you can have few mail addresses setup in Amazon Workmail to receive the mails.
[+] Email receiving with Amazon SES - https://docs.aws.amazon.com/ses/latest/dg/receiving-email.html
[+] What is Amazon Workmail - https://docs.aws.amazon.com/workmail/latest/userguide/what_is.html
Please note that if you wish yo send mails to unverified identities using SES, you need to gain access to production mode. In addition to that, the mail sending is monitored for Bounce, complaints & spam content. All of this is done by our Trust & Safety team. Therefore, all the actions taken are to safeguard the shared services offered by AWS.
[+] Moving out of SES Sandbox - https://docs.aws.amazon.com/ses/latest/dg/request-production-access.html
Lastly, I would like to request you to please open a case with our Trust & Safety team and request a senior review for your use case as a review might require access to internal information related to your account, which is not advisable on a public platform i.e. aws re:Post
well, sorry but it does not look like anyone senior want to look into this or reply. Such a shame, i was looking forward to moving my services to AWS, but having websites that are not allowed to send nor receive emails, when AWS competitors will, means i will have to start the migrations again to another (more sensible) VPS provider....
Thanks Jon
Relevant content
- asked 10 months ago
- asked 3 months ago
- asked 6 months ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 7 months ago
Thank you so much for taking the time to reply to me & i do understand AWS's need to keep spammers out of you servers. The problem is now resolved, the trust and safety team (via business support and with their help), have now opened port 25 for me, so all is good and no need to use SES (although i may still use SES in future, as it does sound like it has some advantages to me) It did take 4 requests to open the port, but on my 4th request (i am migrating servers to AWS). I provided them with my "current/now previous servers" rDNS and other details, so that they could maybe check my 20 years of "good standing" + i explained some of my lack of knowledge on how i did not fully understand the questions they were asking of me. in under an hour, i got approved, and (now as i was migrating servers), i just need to setup on AWS the rDNS and email this to the T&S team. Thank you again for your attention, but i hope all will now be OK. The migration should be completed today. i just need to read up on how to set up the rDNS :-)