SMTP error library

Reply codes, enhanced status codes and provider messages with possible causes and what to check.

Content reviewed on 2026-11-03

SMTP error interpreter →

Generic

250Generic

Accepted

The server accepted the command or the message. Acceptance is not delivery to the inbox.

Possible causes
  • Normal reply after RCPT TO or DATA.
What to check
  • Keep the server's queue id from the reply to trace the message later.

Authentication

530 · 5.7.0Authentication

Authentication required

The server will not accept mail on this port without logging in.

Possible causes
  • Sending through a submission port (587/465) without credentials.
  • The client tried to relay before authenticating.
What to check
  • Enable SMTP authentication in the client.
  • Use the username and password of the SMTP account, not the mailbox password of another service.
535 · 5.7.8Authentication

Authentication failed

The credentials were rejected.

Possible causes
  • Wrong username or password.
  • The account requires an application password or a token instead of the normal password.
  • The user is not allowed to use SMTP.
What to check
  • Re-enter the credentials; check for trailing spaces.
  • Confirm the authentication method the provider expects (PLAIN/LOGIN over TLS, XOAUTH2).
  • Check whether the account is locked or SMTP access disabled.
535 · 5.7.8AuthenticationGmail

Gmail: username and password not accepted

Gmail rejected the login; regular passwords are not accepted for SMTP since 2022.

Possible causes
  • Using the Google account password instead of an app password.
  • Two-step verification not enabled, so app passwords cannot be created.
  • Workspace policy blocks less secure apps.
What to check
  • Create an app password and use it as the SMTP password.
  • For applications, prefer OAuth 2.0 or a transactional SMTP relay.
  • Check Google Workspace admin restrictions.
535 · 5.7.139AuthenticationMicrosoft 365 / Outlook

Microsoft 365: authentication unsuccessful

Basic authentication is disabled for SMTP AUTH on this tenant or mailbox.

Possible causes
  • SMTP AUTH disabled at tenant or mailbox level.
  • Security defaults block legacy authentication.
  • Wrong credentials.
What to check
  • Ask the tenant admin to enable SMTP AUTH for the mailbox.
  • Use OAuth 2.0 where the client supports it.
  • Consider a dedicated transactional SMTP service instead of a user mailbox.
504 · 5.7.4Authentication

Authentication mechanism not supported

The client offered an AUTH mechanism the server does not accept.

Possible causes
  • Client configured for a mechanism (for example NTLM or CRAM-MD5) the server lacks.
  • AUTH attempted before STARTTLS, when the server only advertises mechanisms over TLS.
What to check
  • Use PLAIN or LOGIN after STARTTLS.
  • Check the EHLO response for the advertised AUTH mechanisms.

TLS and encryption

530 · 5.7.0TLS and encryption

STARTTLS required

The server requires encryption before accepting commands.

Possible causes
  • Client connected to port 587 without STARTTLS.
  • Encryption disabled in the client configuration.
What to check
  • Enable STARTTLS for port 587 or implicit TLS for port 465.
  • Check the ports and protocols reference.
454 · 4.7.0TLS and encryption

TLS not available or failed

The TLS session could not be established.

Possible causes
  • Certificate problems on the server.
  • Client and server share no cipher suite or TLS version.
  • A proxy or firewall intercepts the connection.
What to check
  • Test with another TLS version or client.
  • Check the server certificate and intermediate chain.
  • Try again later: it can be a temporary server issue.

Relay

550 · 5.7.1Relay

Relay access denied

The server refuses to forward mail to an external domain for this client.

Possible causes
  • Not authenticated, so the server treats the client as an untrusted sender.
  • The recipient domain is not hosted on that server and relaying is restricted.
  • Sending from an IP that is not in the allowed list.
What to check
  • Authenticate before sending.
  • Use the submission port (587/465) rather than port 25.
  • Confirm you are using your provider's SMTP server, not the recipient's MX.
554 · 5.7.1Relay

Relay denied (554)

Same as the 550 variant: forwarding refused for this connection.

Possible causes
  • Trying to deliver through a server that only accepts mail for its own domains.
  • Missing authentication.
What to check
  • Authenticate or use the correct outgoing server.

Sender address

550 · 5.1.0Sender address

Sender address rejected

The MAIL FROM address was refused.

Possible causes
  • The sender domain does not exist or has no MX/A record.
  • The address is not allowed for the authenticated user.
  • Sender verification (callback) failed.
What to check
  • Use a sender domain that resolves and accepts mail.
  • Check which From addresses the SMTP account may use.
  • Verify the domain in the sending platform.
450 · 4.1.8Sender address

Sender domain not found (temporary)

The receiver could not resolve the sender domain at that moment.

Possible causes
  • DNS problem on the receiving side.
  • Newly created domain not yet propagated.
  • Typo in the sender domain.
What to check
  • Check the sender domain's MX/A records.
  • Wait and retry; the sender usually retries automatically.

Recipient

550 · 5.1.1Recipient

Recipient does not exist

The receiving server has no mailbox for this address.

Possible causes
  • Typo in the address.
  • The mailbox was deleted or never existed.
  • Alias or distribution list removed.
What to check
  • Stop sending to this address; it is a hard bounce.
  • Confirm the address with the contact through another channel.
  • Validate addresses before adding them to a list.
550 · 5.1.1RecipientGmail

Gmail: account does not exist

Gmail reports that the address is not an active account.

Possible causes
  • Wrong address.
  • Account deleted or renamed.
What to check
  • Remove the address from your lists.
  • Do not retry; the result will not change.
550 · 5.1.10RecipientMicrosoft 365 / Outlook

Microsoft 365: recipient not found

Exchange Online could not find the recipient.

Possible causes
  • Mailbox removed or the address is not assigned.
  • Tenant migrated and the address no longer routes.
What to check
  • Treat as a hard bounce.
  • Ask the contact for a current address.
550 · 5.4.4Recipient

Recipient domain accepts no mail

The recipient domain has no MX, a null MX or no route.

Possible causes
  • Typo in the domain.
  • Domain not configured for email or publishing null MX.
What to check
  • Check the domain with the MX lookup.
  • Treat as a hard bounce if the domain is correct.
550 · 5.7.1Recipient

Recipient refuses by policy

The recipient or their organisation blocks mail from this sender.

Possible causes
  • Sender on the recipient's blocklist.
  • Organisation policy (only internal mail, allowlists).
What to check
  • Contact the recipient through another channel.
  • Do not retry automatically.

Mailbox state

550 · 5.2.1Mailbox state

Mailbox unavailable or disabled

The mailbox exists but cannot receive mail.

Possible causes
  • Account suspended or disabled by the provider.
  • Mailbox locked for inactivity.
What to check
  • Pause sending to this address; retry only if the contact confirms it is active again.
552 · 5.2.2Mailbox state

Mailbox full (permanent)

The recipient's storage quota is exceeded and the server refuses the message.

Possible causes
  • Quota exhausted.
  • Abandoned mailbox.
What to check
  • Treat repeated occurrences as a soft bounce that turns hard.
  • Suppress after several consecutive failures.
452 · 4.2.2Mailbox state

Mailbox full or storage shortage (temporary)

Temporary lack of space; the sending server will retry.

Possible causes
  • Recipient over quota.
  • Receiving server short on disk.
What to check
  • Let the retries run; suppress if it persists for days.

Size and attachments

552 · 5.3.4Size and attachments

Message too large

The message exceeds the receiver's size limit.

Possible causes
  • Large attachments; Base64 adds about 37%.
  • Receiver limit lower than yours (often 10–25 MB).
What to check
  • Compress or link attachments instead of embedding them.
  • Estimate the encoded size with the MIME size calculator.
552 · 5.7.0Size and attachments

Attachment or content blocked

The message was refused because of an attachment type or malware detection.

Possible causes
  • Executable or archive attachments.
  • Antivirus match.
What to check
  • Send a link to the file instead.
  • Scan the file and change the format.

Content and spam filtering

550 · 5.7.1Content and spam filtering

Rejected as spam or by policy

The receiver's filter classified the message as unwanted.

Possible causes
  • Content, links or attachments matched spam rules.
  • Sending IP or domain with poor reputation.
  • Missing authentication (SPF/DKIM/DMARC).
What to check
  • Check SPF, DKIM and DMARC alignment.
  • Review links, images and wording; remove URL shorteners.
  • Look up the exact text in the receiver's postmaster documentation.
554 · 5.7.1Content and spam filtering

Message refused (554)

The server rejected the transaction, usually for policy or spam reasons.

Possible causes
  • Blocklisted IP.
  • Policy rejection of the sender or content.
What to check
  • Read the full server text; it often includes a URL with details.
  • Check the sending IP on the receiver's postmaster tools.
550 · 5.7.1Content and spam filteringGmail

Gmail: message likely unsolicited

Gmail's filters rejected the message at SMTP time.

Possible causes
  • Unauthenticated mail (no SPF or DKIM).
  • Low domain or IP reputation.
  • Content patterns associated with spam.
What to check
  • Authenticate with SPF and DKIM aligned to the From domain.
  • Set up DMARC and review Google Postmaster Tools.
  • Reduce volume to the affected domain while reputation recovers.

Rate limits and greylisting

421 · 4.7.0Rate limits and greylisting

Rate limited or too many connections

The receiver is throttling your sending; retry later.

Possible causes
  • Too many messages or connections in a short time.
  • New IP without reputation.
What to check
  • Slow down and spread the sending.
  • Reduce parallel connections per destination.
  • Use the rate limit converter to size your throughput.
450 · 4.7.1Rate limits and greylisting

Temporarily deferred (greylisting or rate)

The receiver asks the sender to try again later.

Possible causes
  • Greylisting of an unknown sending IP.
  • Per-sender rate limits.
What to check
  • Allow the sending server to retry; most deliveries succeed on the second attempt.
  • Keep a consistent IP and HELO name.
421 · 4.7.28Rate limits and greylistingGmail

Gmail: unusual rate of unsolicited mail

Gmail temporarily limits mail from your IP.

Possible causes
  • Sudden volume increase.
  • High spam complaint rate.
What to check
  • Reduce volume to Gmail recipients immediately.
  • Check complaint and spam rates in Google Postmaster Tools.
  • Warm up gradually.
421 · 4.7.0Rate limits and greylistingYahoo / AOL

Yahoo/AOL: temporarily deferred

Yahoo defers mail from your IP because of volume or reputation.

Possible causes
  • Unexpected volume from the IP.
  • Reputation signals.
What to check
  • Throttle sending to Yahoo and AOL domains.
  • Check Yahoo's sender hub for the TS code shown.

IP and domain reputation

550 · 5.7.1IP and domain reputation

Sending IP blocked or listed

The receiver refuses mail from your IP, often referencing a blocklist.

Possible causes
  • IP present in a DNSBL (Spamhaus and others).
  • Shared IP with a bad neighbour.
  • Compromised account sending spam.
What to check
  • Check the IP on the blocklist named in the reply and follow its removal process.
  • Stop any compromised sending source first.
  • Consider a dedicated IP or a reputable relay.
554 · 5.7.1IP and domain reputation

Access rejected for this IP (554)

The server refuses the connection or transaction from your IP.

Possible causes
  • Blocklist hit.
  • Receiver policy against the IP range.
What to check
  • Identify the list from the reply text and request delisting.
  • Check reverse DNS of the sending IP.
550 · 5.7.1IP and domain reputationMicrosoft 365 / Outlook

Microsoft: IP blocked

Outlook.com or Microsoft 365 refuses mail from the IP (S3150 and similar codes).

Possible causes
  • IP on Microsoft's internal blocklist.
  • Low reputation in SNDS.
What to check
  • Use the Microsoft sender support form to request mitigation.
  • Register the IP in SNDS and the Junk Mail Reporting Program.
  • Fix authentication and complaint sources before asking.

SPF, DKIM, DMARC and reverse DNS

550 · 5.7.26SPF, DKIM, DMARC and reverse DNS

Rejected by DMARC policy

The From domain publishes a DMARC reject policy and the message did not pass aligned SPF or DKIM.

Possible causes
  • Sending through a platform without DKIM signing for your domain.
  • Return-Path on another domain and no aligned DKIM.
  • Forwarding broke SPF and DKIM.
What to check
  • Check alignment with the DMARC alignment simulator.
  • Sign with DKIM using your own domain.
  • Review DMARC reports for unexpected sources.
550 · 5.7.23SPF, DKIM, DMARC and reverse DNS

SPF failure

The sending IP is not authorised by the sender domain's SPF record.

Possible causes
  • New sending service not added to SPF.
  • Too many lookups make the record permerror.
  • Wrong Return-Path domain.
What to check
  • Run the SPF checker on the Return-Path domain.
  • Add the provider's include or IP range.
  • Keep the record under 10 lookups.
550 · 5.7.20SPF, DKIM, DMARC and reverse DNS

DKIM failure

The signature could not be verified.

Possible causes
  • Message modified in transit (footer, forwarding).
  • Selector not published or key rotated.
  • Body hash mismatch due to line-ending changes.
What to check
  • Look up the selector with the DKIM key lookup.
  • Check that the signing platform's DNS record is published.
  • Use relaxed canonicalisation.
550 · 5.7.25SPF, DKIM, DMARC and reverse DNS

No or mismatched reverse DNS

The receiver requires a PTR record that resolves back to the sending IP.

Possible causes
  • No PTR for the sending IP.
  • PTR points to a generic hosting name.
  • Forward lookup of the PTR name does not match the IP.
What to check
  • Ask the hosting provider to set a PTR matching your mail host name.
  • Verify with the PTR tool.
  • Make the HELO name match the PTR.

Protocol and syntax

504 · 5.5.2Protocol and syntax

HELO/EHLO rejected

The greeting host name is invalid or not fully qualified.

Possible causes
  • Client sends a bare host name or localhost.
  • HELO name does not resolve.
What to check
  • Configure the mail client or server with a fully qualified host name that resolves.
500 · 5.5.2Protocol and syntax

Syntax error or command unrecognised

The server did not understand the command.

Possible causes
  • Client bug or protocol mismatch.
  • Line longer than the server allows (often a long header).
  • Sending ESMTP commands to a server that only speaks SMTP.
What to check
  • Capture the SMTP conversation to see the offending line.
  • Fold long headers.
503 · 5.5.1Protocol and syntax

Bad sequence of commands

A command arrived out of order.

Possible causes
  • RCPT before MAIL FROM.
  • DATA before any RCPT accepted.
  • AUTH after MAIL FROM.
What to check
  • Follow the order EHLO, STARTTLS, EHLO, AUTH, MAIL FROM, RCPT TO, DATA.

Server availability

421 · 4.3.2Server availability

Service not available

The server is closing the connection; try later.

Possible causes
  • Server overload or maintenance.
  • Connection limit reached.
  • Idle timeout.
What to check
  • Retry with backoff.
  • If persistent, contact the receiving postmaster.
451 · 4.3.0Server availability

Local error in processing

A temporary problem on the receiving server.

Possible causes
  • Filter or storage error on their side.
  • Backend timeout.
What to check
  • Let the sender retry; if it lasts, contact the receiver.

DNS

451 · 4.4.4DNS

Temporary DNS failure

The receiver could not resolve a name needed to accept the message.

Possible causes
  • Sender domain DNS unreachable.
  • Receiver resolver issue.
What to check
  • Check your domain's name servers respond.
  • Retry later.

Network and connection

— · 4.4.1Network and connection

Connection refused

No service answered on that host and port.

Possible causes
  • Wrong port (25 vs 587 vs 465).
  • Firewall or ISP blocking outbound port 25.
  • Service down.
What to check
  • Confirm host and port with the provider.
  • Try 587 with STARTTLS or 465 with TLS.
  • Check outbound firewall rules.
— · 4.4.2Network and connection

Connection timed out or lost

The connection could not be established or dropped mid-session.

Possible causes
  • Network path blocked (port 25 filtering).
  • Server overloaded.
  • Large message on a slow link.
What to check
  • Test connectivity to the host and port.
  • Reduce message size or parallelism.
  • Retry later.
Mailiqo

Follow every message without opening headers

In Mailiqo every message has its own history of statuses and events: deliveries, bounces and errors with their reason, all from the panel.

See what Mailiqo includes