250GenericAccepted
The server accepted the command or the message. Acceptance is not delivery to the inbox.
- Normal reply after RCPT TO or DATA.
- Keep the server's queue id from the reply to trace the message later.
Reply codes, enhanced status codes and provider messages with possible causes and what to check.
Content reviewed on 2026-11-03
250GenericThe server accepted the command or the message. Acceptance is not delivery to the inbox.
530 · 5.7.0AuthenticationThe server will not accept mail on this port without logging in.
535 · 5.7.8AuthenticationThe credentials were rejected.
535 · 5.7.8AuthenticationGmailGmail rejected the login; regular passwords are not accepted for SMTP since 2022.
535 · 5.7.139AuthenticationMicrosoft 365 / OutlookBasic authentication is disabled for SMTP AUTH on this tenant or mailbox.
504 · 5.7.4AuthenticationThe client offered an AUTH mechanism the server does not accept.
530 · 5.7.0TLS and encryptionThe server requires encryption before accepting commands.
454 · 4.7.0TLS and encryptionThe TLS session could not be established.
550 · 5.7.1RelayThe server refuses to forward mail to an external domain for this client.
554 · 5.7.1RelaySame as the 550 variant: forwarding refused for this connection.
550 · 5.1.0Sender addressThe MAIL FROM address was refused.
450 · 4.1.8Sender addressThe receiver could not resolve the sender domain at that moment.
550 · 5.1.1RecipientThe receiving server has no mailbox for this address.
550 · 5.1.1RecipientGmailGmail reports that the address is not an active account.
550 · 5.1.10RecipientMicrosoft 365 / OutlookExchange Online could not find the recipient.
550 · 5.4.4RecipientThe recipient domain has no MX, a null MX or no route.
550 · 5.7.1RecipientThe recipient or their organisation blocks mail from this sender.
550 · 5.2.1Mailbox stateThe mailbox exists but cannot receive mail.
552 · 5.2.2Mailbox stateThe recipient's storage quota is exceeded and the server refuses the message.
452 · 4.2.2Mailbox stateTemporary lack of space; the sending server will retry.
552 · 5.3.4Size and attachmentsThe message exceeds the receiver's size limit.
552 · 5.7.0Size and attachmentsThe message was refused because of an attachment type or malware detection.
550 · 5.7.1Content and spam filteringThe receiver's filter classified the message as unwanted.
554 · 5.7.1Content and spam filteringThe server rejected the transaction, usually for policy or spam reasons.
550 · 5.7.1Content and spam filteringGmailGmail's filters rejected the message at SMTP time.
421 · 4.7.0Rate limits and greylistingThe receiver is throttling your sending; retry later.
450 · 4.7.1Rate limits and greylistingThe receiver asks the sender to try again later.
421 · 4.7.28Rate limits and greylistingGmailGmail temporarily limits mail from your IP.
421 · 4.7.0Rate limits and greylistingYahoo / AOLYahoo defers mail from your IP because of volume or reputation.
550 · 5.7.1IP and domain reputationThe receiver refuses mail from your IP, often referencing a blocklist.
554 · 5.7.1IP and domain reputationThe server refuses the connection or transaction from your IP.
550 · 5.7.1IP and domain reputationMicrosoft 365 / OutlookOutlook.com or Microsoft 365 refuses mail from the IP (S3150 and similar codes).
550 · 5.7.26SPF, DKIM, DMARC and reverse DNSThe From domain publishes a DMARC reject policy and the message did not pass aligned SPF or DKIM.
550 · 5.7.23SPF, DKIM, DMARC and reverse DNSThe sending IP is not authorised by the sender domain's SPF record.
550 · 5.7.20SPF, DKIM, DMARC and reverse DNSThe signature could not be verified.
550 · 5.7.25SPF, DKIM, DMARC and reverse DNSThe receiver requires a PTR record that resolves back to the sending IP.
504 · 5.5.2Protocol and syntaxThe greeting host name is invalid or not fully qualified.
500 · 5.5.2Protocol and syntaxThe server did not understand the command.
503 · 5.5.1Protocol and syntaxA command arrived out of order.
421 · 4.3.2Server availabilityThe server is closing the connection; try later.
451 · 4.3.0Server availabilityA temporary problem on the receiving server.
451 · 4.4.4DNSThe receiver could not resolve a name needed to accept the message.
— · 4.4.1Network and connectionNo service answered on that host and port.
— · 4.4.2Network and connectionThe connection could not be established or dropped mid-session.
In Mailiqo every message has its own history of statuses and events: deliveries, bounces and errors with their reason, all from the panel.