Yoonadev

Sending or connection rate limited

Sending volume or concurrent connections have reached a limit.

What to do now

  1. Wait for the interval requested by the server, then check the sending result.
  2. If you operate the mail server, inspect and reduce the sending rate and concurrent connections.

Representative reply

421 Too many concurrent SMTP connections

Retry decision

Reduce sending rate and observe the requested waiting period.

Why it happens

Concurrent connections or sending volume may exceed a receiver limit.

Typical stage

CONNECT

  1. CONNECT
  2. EHLO
  3. MAIL FROM
  4. RCPT TO
  5. DATA
  6. DELIVERY

Stages vary by server. Confirm the actual stage from the complete reply and session logs.

What is SMTP Reply Code?Open only the explanations you need

Three-digit server reply: 4xx is transient, 5xx permanent. Read the complete text to investigate the cause.

What is Enhanced Status Code?Open only the explanations you need

An extended status such as 5.1.1. Server wording and usage may vary.

Check directly

  1. Wait for the interval requested by the server, then check the sending result.
  2. If you operate the mail server, inspect and reduce the sending rate and concurrent connections.

If you operate or diagnose the mail server, the tools below can help with these checks.

Cautions

Observed DSNs do not map one-to-one to causes. The stage shown is typical; confirm it with the full reply and actual logs.

Similar reply wording and observed status codes
  • too many concurrent smtp
  • too many connection
  • you sent too many messages
  • mail too quickly
  • rate limited

Observed DSNs: 4.2.1, 4.7.26, 4.7.28

Related errors

Analyze another SMTP error →

Back to SMTP Error Dictionary

Find a tool

↑ ↓ to select · Enter to open · Esc to close