Blog · · 6 min read
How to read an email bounce: what 550 5.1.1 and 5.7.1 mean
By Y Naga Vamsi, creator of Mailtruss.
On this page
When an email bounces, the receiving server explains why in a line of text that looks like noise: 550 5.1.1 The email account that you tried to reach does not exist. It is actually structured, and once you can read it you can tell in seconds whether to retry, fix the address, or fix your domain.
Two codes, then a sentence
The line has three parts. 550 is the SMTP reply code (RFC 5321): the first digit says how the server answered, and 4 means "try again later" while 5 means "no". 5.1.1 is the enhanced status code (RFC 3463), which says why. Then comes free text, written by whoever configured the receiving server.
The free text is the most specific part, and the least standard. Always read it. Many receivers put the real reason there, such as which policy blocked you or which authentication check failed.
Reading 5.1.1
The enhanced code has three numbers, class.subject.detail.
- Class.
2is success,4is a persistent transient failure (try again later),5is a permanent failure (do not retry as it is). - Subject. What the failure is about:
1addressing,2the mailbox,3the mail system,4network and routing,5the delivery protocol,6message content,7security or policy. - Detail. The specific case, defined in the IANA registry of enhanced status codes.
5.1.1is "bad destination mailbox address",5.2.2is "mailbox full",5.7.1is "delivery not authorized, message refused".
The codes you will see most
5.1.1: the mailbox does not exist. Fix the typo or remove the address. Do not retry.5.1.2: the recipient's domain could not be found. Usually a typo in the domain part.5.1.10: the recipient's domain publishes a null MX and accepts no mail (RFC 7505).5.2.2or4.2.2: the mailbox is full. A 4 is temporary, a 5 is permanent.5.3.4: the message is too big for the receiving system. Shrink or remove attachments.5.7.1: refused by policy: a blocklist, spam filtering, or the recipient's own rules. The address may be fine.5.7.20to5.7.26: authentication results.5.7.20to5.7.22are DKIM,5.7.23and5.7.24are SPF,5.7.25is reverse DNS,5.7.26is "multiple authentication checks failed".5.7.27: the sender address has a null MX. Different from the others: it is about the domain in your From address accepting no mail.4.x.x: temporary. A busy server, a greylist, a rate limit. Mail servers retry these on their own.
Retry or not
The first digit decides. A 4 can be retried later, and the sending service usually already did before it reported the failure. A 5 should not be retried until the cause is fixed: sending the same message to a mailbox that does not exist just bounces again, and repeated hard bounces damage your sender reputation. After a permanent bounce, stop sending to that address.
Two cases need judgement. A 5.7.1 can be permanent for this message but not for the address, if the cause was your content or your reputation and you have fixed it. And a 5.2.2 that keeps coming back usually means an abandoned mailbox.
Paste it instead
If you would rather not decode it by hand, paste the line into the bounce explainer. It runs in your browser, applies the same rules Mailtruss uses on every bounce it records, and tells you the reason, what to do, and whether a retry is safe. If no rule matches, it says so rather than guessing. The full list of classes, with causes and fixes, is under delivery errors.
Keep reading
- 5 min readWhy email open rates mislead, and what to measure insteadOpen tracking counts image loads, not reading. Apple Mail Privacy Protection, Gmail's image proxy, blocked images and security scanners all distort it. What is worth measuring.
- 6 min readSPF's ten-lookup limit, and how to stay under itWhy an SPF record that looks fine can fail: RFC 7208 allows ten DNS lookups. What counts, what does not, how to count yours, and the safe ways to get under the limit.