Why does Amazon EC2 limit port 25? [closed]

Answer 1

To be clear on SES sending limits, you have to understand there are two types of limits: Maximum Send Rate and Sending Quota

Apart from these limits, port 25 sending rate is throttled by default - but that throttle can be removed.

Maximum Send Rate

The maximum number of emails that Amazon SES can accept from your account per second.

Sending Quotas

The maximum number of emails that you can send in a 24-hour period. All new SES accounts are setup in a sandbox, and have a default Sending quota of 200 emails per 24-hour period. You can request this limit be raised, based on your needs and actual usage patterns.

To answer your questions directly:

Why doesn't it throttle ports 465 and 587?

Default rate limits are enforced on port 25, as this is the common sending port. This leads to a lot of spam being sent on this port. To prevent this, AWS EC2 throttles port 25 by default. Ports 465 and 587 are less well known, and are not as subject to as much spam abuse.

Why doesn't everyone use these ports instead of 25 and avoid the throttling issue altogether?

They can/should if their software allows use of those ports. Some legacy applications can only used port 25. In those cases, you can request the throttle be removed.

In summary regarding SES sending limits:

• Ports TCP/465 and TCP/587 are not throttled
• Port 25 is throttled by default, but it can be removed by request.
• The Per Day Sending Quotas limits of your SES account always apply
• The Per Second Maximum Send Rate limits of your SES account always apply

Answer 2

This is an anti-spam measure.

Without this restriction you could create a new Amazon account, fire up an EC2 machine and send a few million spam messages before anything could be done. By throttling the connection, it makes that scenario unavailable to new user accounts.

465/587 are authenticated ports, and it specifically mentions Amazon Simple Email Service (SES) Which is specifically designed for bulk sending email and is tuned to detect use by spammers.

Edited to add SES information

When you first sign up for SES you are placed in a sandbox. This will place the following restrictions upon your account.

• You can only send mail to the Amazon SES mailbox simulator and to verified email addresses and domains
• You can only send mail from verified email addresses and domains.
• You can send a maximum of 200 messages per 24-hour period.
• Amazon SES can accept a maximum of one message from your account per second.

Which basically means that if you want to use SES in a production scenario because you can only send to / from accounts that you have explicitly verified. You need to request a sending limit raise. Which you can either do from the console or by raising a support ticket.

You will then have a new sending limit applied and a daily quota. For instance on my dev account I have a 50,000 per day daily quota and 14/second sending limit.

If I were to attempt to send more than 14 messages per second, over SMTP (regardless of port) you will get this SMTP error message 454 Throttling failure: Maximum sending rate exceeded if I tried to send more than 50,000 messages I would receive 454 Throttling failure: Daily message quota exceeded

In order to understand how throttling works, you need to think about the process that is occurring.

When you connect to SES over SMTP (on any port) you pass your credentials, AWS will check the limits on your account and start counting against your limits. At that point you are an authenticated user coming over an authenticated endpoint (you cannot send via SES anonymously - You can receive email in SES, but there are no incoming email limits applied, apart from message size) In that context you can see that throttling a particular port would be entirely pointless.

The only AWS service to have default throttling on port 25 is EC2.

the ONLY time that SES will throttle your messages is when you exceed your allowed limits.

Those limits can never be removed, they can only be increased (albeit increased to reasonably insane numbers)

Those limits will grow over time, if you are diligent in your use of SES and your handling of blocked / bounced messages your numbers will increase.

So, in summary.

• SES Does not throttle port 25, port 465 or port 587.
• SES will only rate limit messages based on your quotas.
• SES Rate limits apply entirely independently to TCP port numbers.