552 — Yahoo — Recipient mailbox not found
What response did the server return?
While attempting to send a message to a non-existent address in the yahoo.com domain, the Yahoo server returned:
552 1 Requested mail action aborted, mailbox not found
The following is an anonymised and simplified log excerpt from the actual event. The addresses, queue ID, hostname and IP address have been replaced with example data:
ABC123: to=<[email protected]>,
relay=mta.example.yahoo.net[192.0.2.10]:25,
dsn=5.0.0, status=bounced
(host mta.example.yahoo.net[192.0.2.10] said:
552 1 Requested mail action aborted, mailbox not found
(in reply to end of DATA command))
This page describes a specific response observed while delivering mail to Yahoo. It should not be taken to mean that every SMTP 552 response indicates a non-existent mailbox.
What does this error mean?
The first digit of SMTP reply code 552 indicates a permanent failure. The Yahoo server did not accept responsibility for delivering the message, and the response text states that the recipient mailbox was not found.
The standard meaning of 552 concerns exceeding the available storage allocation. In this case, the complete server response matters more than the three-digit code alone. Classifying this response simply as “mailbox full” would lead to an incorrect diagnosis.
The 1 following 552 is not a complete enhanced status code. Such a code consists of three dot-separated fields, for example 5.1.1. The Yahoo response must therefore not be interpreted as 552 5.1.1.
Postfix assigned the event the generic DSN status:
dsn=5.0.0
This represents a permanent failure without a more specific valid classification supplied by the remote server.
Why was the message rejected after its content was sent?
The fragment:
in reply to end of DATA command
means that Yahoo did not reject the address during RCPT TO. It returned the response only after receiving the message content and the dot that terminates data transfer following the DATA command.
The log alone does not reveal why the server performed the validation at this stage. It does establish that the server did not accept the message.
What did Postfix do?
Because 552 is a permanent rejection, Postfix did not leave the message in the deferred queue for another attempt. In the observed case, it performed the following operations:
- The
smtpprocess received Yahoo’s rejection and recordedstatus=bounced. - The
bounceprocess created a non-delivery notification as a separate message with a new Queue ID and the null envelope sender<>. - The original message was removed from the queue after the permanent failure had been handled.
- The notification was delivered via LMTP to the original sender’s mailbox and was then also removed from the queue.
The bounce was therefore a separate message managed by Postfix, not a modification of the original message.
What can the sender do?
- Check the recipient address for typing errors.
- Ask the recipient to confirm the address through another communication channel.
- If the address came from an old message or address book, make sure it is still current.
- Do not resend to the same address without checking or correcting it first.
Automatic retries will not resolve a permanent failure. Retrying may make sense only after confirming that the mailbox exists or has been reactivated.
When should you contact an administrator?
If the address is correct and should work, the recipient should check the account status or contact Yahoo support. The sending server administrator can confirm the SMTP exchange and the response received, but cannot create or reactivate a mailbox in Yahoo’s system.
For another unknown-recipient case rejected earlier during RCPT TO, see 550 5.1.1 — unknown recipient.
Source documentation
- Yahoo Sender Hub — SMTP Error Codes covers permanent failures, non-existent recipients and the recommendation not to retry delivery to an invalid address.
- RFC 5321, Section 4.2.3 lists the standard meanings of three-digit SMTP replies, including
552. - RFC 3463, Section 2 defines the
class.subject.detailstructure of enhanced status codes.
If you manage business email and need help analysing SMTP responses, bounce messages or Postfix logs, see the business email diagnostics service.
