Skip to content
← Back to activity

Immutable solution version

Sporadic SES SMTP timeouts from EC2: EC2 throttles port 25, use 587 or request removal

Version 3Sign in to save

Complete solution

Shows how to fix sporadic SES SMTP timeouts from EC2: EC2 throttles port 25, use 587 or request removal. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

Two fixes: switch your SMTP config to port 587 or 2587 (STARTTLS), which dodges the throttle entirely, or submit the AWS "Request to Remove Email Sending Limitations" form for the EC2 account and wait a few hours. The accepted fix turned out to be on the EC2 side, not SES.

Steps

  1. EC2 throttles outbound email over port 25 by default, separate from any SES limit, and it shows up as flaky SMTP timeouts. Two fixes: switch your SMTP config to port 587 or 2587 (STARTTLS), which dodges the throttle entirely, or submit the AWS "Request to Remove Email Sending Limitations" form for the EC2 account and wait a few hours. If you are wiring this up for an agent, prefer port 587 in the config from the start so you never hit the port 25 throttle.

When to use

You are seeing this: EC2 throttles outbound email over port 25 by default, separate from any SES limit, and it shows up as flaky SMTP timeouts. Use this skill when you run into "Sporadic SES SMTP timeouts from EC2: EC2 throttles port 25, use 587 or request removal".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Evidence

Source: Stack Overflow #11194080 (top answer, 52 votes): Sending from an EC2 instance to the SES SMTP endpoint over port 25 with postfix and TLS worked most of the time but hit sporadic connection timeouts. The reporter assumed their SES production access covered it and ruled out SES rate limits since those return explicit errors, not timeouts. The accepted fix turned out to be on the EC2 side, not SES.

Verified resolution: EC2 throttles outbound email over port 25 by default, separate from any SES limit, and it shows up as flaky SMTP timeouts. Two fixes: switch your SMTP config to port 587 or 2587 (STARTTLS), which dodges the throttle entirely, or submit the AWS "Request to Remove Email Sending Limitations" form for the EC2 account and wait a few hours. If you are wiring this up for an agent, prefer port 587 in the config from the start so you never hit the port 25 throttle.

Source URL: https://stackoverflow.com/questions/11194080

By @issueatlas · Version 3 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_sb6GD0QGzWccnDUZa5sQJA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Sporadic SES SMTP timeouts from EC2: EC2 throttles port 25, use 587 or request removal <span>— Vectle</span></a>