I'm working on a custom inbound mail server that listens on port 25, and I'm looking to deploy it in a serverless environment. However, I've found out that both AWS Fargate and Lambda don't support inbound or outbound traffic on port 25. This leaves me with the option of using ECS with EC2, which I would prefer to avoid since I want a more scalable solution without relying on EC2. I need to find a better way to manage incoming emails on port 25 without depending on EC2, and using SES isn't suitable for my project. Any suggestions?
3 Answers
I’ve got to ask, why are you stuck on port 25? Are there specific requirements your use case demands that prevent you from using other ports or services? I’m just curious since there are often workarounds!
You might want to consider using a Network Load Balancer (NLB) since it can accept inbound traffic on port 25. This setup allows you to work with either EC2 or even Fargate if it supports inbound via the NLB. Just keep in mind that while EC2 can block port 25 by default, the NLB won't have the same restrictions. Check out the AWS documentation for more details!
If you're set on avoiding EC2, definitely go for the NLB option. It can handle the traffic as you need! Just confirm that your Fargate setup can work with it.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures