SMTP error codes: What they mean and how to fix them

If you’re at risk of impersonation, one of our experts will be in touch to assist.


How SMTP error codes work


Common SMTP error codes (4xx and 5xx)

CodeTypical meaningNext steps
421Service not available, closing transmission channel – The receiving SMTP server is unavailable or busy.Treat this as a temporary issue. If the same error code keeps appearing, contact the recipient’s email administrator.
422Mailbox temporarily unavailable – There is an issue with the license, server, or storage.Retry sending after a short period of time.
450Requested mail action not taken; mailbox unavailable – The mailbox may be full or locked.Try again later. If the issue persists, contact the recipient.
451Requested action aborted, local error in processing – The receiving server may be temporarily overloaded or applying filtering policies.Wait a short time and try sending the email again. If the issue persists, contact the recipient’s email administrator.
452Requested action not taken, insufficient system storage – The recipient’s server is full, busy, or enforcing a policy rule.Try sending the message again after a short delay. If you continue to see the same SMTP error code, raise it with the recipient’s email administrator.
CodeTypical meaningNext steps
501Syntax error in parameters or arguments – This is often due to an invalid recipient address, a malformed SMTP command, or incorrect HELO/EHLO configuration.Verify the recipient address, confirm your SMTP command syntax, and ensure your HELO/EHLO settings are correctly configured.
521Server does not accept mail – The recipient server isn’t configured to accept email, or your sending IP has been blocklisted.Confirm the recipient domain has valid MX records and is active, then check whether your sending IP is on blocklists, fix any issues, and request delisting.
540Recipient address rejected – domain not found – The recipient domain may be inactive, suspended, or blocking your sending domain/IP.Ask the recipient to reactivate the mailbox, then verify SPF/DKIM/DMARC, check IP/domain blocklists, and request allowlisting if needed.
550Requested action not taken: mailbox unavailable – The request was rejected because the address is invalid, authentication checks failed, or your IP/domain reputation is causing blocks.Confirm the address is correct, validate alignment, then check your reputation and blocklists, remediate, then request delisting.
551User not local; please try <forward-path> – The message was rejected because your sending domain is blocklisted, forwarding is misconfigured, or the recipient domain is invalid.Check blocklists, fix the underlying issue, request delisting, then verify the recipient domain via DNS and have the recipient confirm the forwarding address and rules.
552Requested mail action aborted: exceeded storage allocation – The message was rejected because it exceeded size limits, the mailbox is over quota, malware was detected, spam/security filters were triggered, or the recipient address is invalid.Reduce the message/attachment size, confirm the recipient mailbox has space and the address is valid, scan attachments for malware, and adjust content to avoid spam/security filtering.
553Requested action not taken: mailbox name not allowed – The message was rejected due to an invalid address format (RFC), spam filtering, IP blocklisting, or the server denying relay to that destination.Fix the address format, adjust content/authentication to reduce spam filtering, check blocklists and remediate before requesting delisting, and if it’s a relay issue, contact the recipient.
554Transaction has failed – Rejected due to spam/security filtering, poor sender reputation, failed authentication, blocklisting, an invalid recipient, mailbox limits, or malformed headers.Confirm the recipient address, have them free up mailbox space, verify SPF/DKIM/DMARC alignment, check reputation/blocklists and fix issues before delisting, and adjust content/headers.

SMTP error codes FAQs

What is an SMTP error code?

An SMTP error code is a three-digit status code that an SMTP server returns when an email delivery attempt is deferred or fails, explaining why a message wasn’t accepted. SMTP error codes appear in server logs and bounce messages.

SMTP error codes often appear together with enhanced status codes and a short message, which gives you enough information to decide whether to retry or fix something first.

What is the difference between 4xx and 5xx SMTP error codes?

The difference between 4xx and 5xx SMTP error codes is that 4xx codes indicate temporary problems, and 5xx codes indicate permanent failures.

4xx SMTP error codes show persistent transient failures, such as busy servers, full mailboxes, or temporary infrastructure issues. Email systems usually keep trying 4xx responses for a set period.

5xx SMTP error codes show permanent failures, such as invalid addresses or security and policy blocks. You need to correct the address, configuration, or policy issue before sending again.

Where do I find the SMTP code for a bounced email?

The SMTP error code for a bounced email appears in a few common places.

You can find the SMTP error code in:

  • Bounce messages or Non-Delivery Reports (NDRs)
  • SMTP logs, which record the full SMTP conversation