Bounce errors / 553 5.1.2 and 5.1.3 Gmail and any provider
What do errors 553 5.1.2 and 5.1.3 mean for an email address?
The address itself is written wrongly: either the domain after the @ cannot be found (5.1.2), or the whole address is not valid (5.1.3). Correct the spelling or the stray characters and write a new message, or drop the address.
- Hard bounce
- Who fixes it: You
- Try again: No
553-5.1.2 We weren't able to find the recipient domain. Please check for any 553-5.1.2 spelling errors, and make sure you didn't enter any spaces, periods, 553 5.1.2 or other punctuation after the recipient's email address. - gsmtp
You see this when an address has a typo, a stray space or symbol, or a domain that does not exist.
Here is how to read that message.
Each colour marks one part of the message, and the numbers match the notes underneath.
- 1The reply code553 means the mailbox name is not allowed. It starts with a 5, so it is permanent.
- 2The status code5.1.2 is a bad destination system address: RFC 3463 says the domain, the part after the @, does not exist or cannot accept mail. 5.1.3 means the address was not written in a valid form.
- 3The plain wordsGmail could not find the domain you wrote. It asks you to check the spelling and any characters after the address.
- 4The servergsmtp is Google's tag. Other providers give the same codes with different words.
There is another version of this message.
The words after the code are what separate one cause from another. Find yours.
The 5.1.3 version, when the whole address is not valid
553-5.1.3 The recipient address <jane..doe@example.com> is not a valid 553-5.1.3 RFC-5321 address. Learn more at 553 5.1.3 https://support.google.com/mail/answer/6596 - gsmtp
Here is what the message means in plain words.
These two codes are about the address as typed, before any mailbox is looked up. RFC 3463 defines 5.1.2 as bad destination system address, where the domain does not exist or cannot accept mail, and 5.1.3 as bad destination mailbox address syntax, where the address was syntactically invalid in any part.
That makes them the easiest bounces to fix, and the easiest to prevent: a checker finds a bad address before a server ever sees it.
These are the usual reasons for it.
- A typo in the domain ending, such as .cmo or .con.
- A space, comma, semicolon or period stuck to the end of the address when it was pasted.
- Two dots in a row, two @ signs, or a missing @ or dot.
- An empty merge field in a campaign, which leaves an address like jane.@example.com.
- A domain that never existed, has expired, or has no mail servers.
Who has to fix it?
The blue card is the one that fixes it. A dashed card helps in some cases, and a grey card has nothing to do.
553 5.1.2 and 5.1.3You, the sender
Fixes itYou fix it. The error is about how the address was written.
The person you emailed
Not involvedNothing to do. They never see the message.
Their email admin
Not involvedNothing to do. The address never got as far as their server.
Follow these steps to fix it.
- Read the address in the bounce.Look at it one character at a time. Check the domain ending, then the part before the @.
- Remove anything that is not part of the address.Take off spaces, trailing periods and commas, angle brackets, and anything copied along with the address, such as the word mailto.
- Check that the domain exists.Open the domain in a browser or run it through an MX lookup. A domain with no mail servers cannot receive email.
- Check your merge fields.If the addresses in a campaign are built from names, make sure no name field is empty and that accents, spaces and apostrophes are cleaned out.
- Run the corrected list through a syntax check.A syntax checker flags every address that is not written correctly, so you fix the rest in one pass.
- Drop what you cannot correct.If the address stays invalid, remove it and do not resend.
Here is how to stop it from happening again.
Bad syntax is the one bounce that needs no mail server to catch. Check the list before it goes into a campaign and these never leave your outbox.
The mailbox exists and accepts email. Keep it and send.
The domain accepts every address. Send these in a smaller, separate batch.
The mailbox can't receive email. Remove it before it bounces.
The mail server did not answer in time. Check it again in a little while.
These errors look similar, and here is how they differ.
| Error | Where you see it | What it means | Try again? |
|---|---|---|---|
| 553 5.1.2 and 5.1.3 | Gmail and any provider | This page. The address is written wrongly | No |
| 550 5.1.1 | Gmail | The address is well formed, but the account does not exist. | No |
| 550 5.1.1 | Microsoft 365 and Outlook | Recipient not found. | No |
| 5.1.7 | Any provider | Bad sender's mailbox address syntax. Your own From address is not valid. | No |
| 554 delivery error | Yahoo and AOL | The account does not exist. | No |
These are the questions people ask about this error.
What is the difference between 5.1.2 and 5.1.3?
5.1.2 is about the domain, the part after the @, which does not exist or cannot accept mail. 5.1.3 is about the whole address being written in an invalid form.
Can a valid-looking address cause 5.1.3?
Yes. Two dots in a row, a trailing period or a stray symbol can look fine to a person and still not be a valid address.
Why would a domain not be found?
It was typed wrongly, it expired, or it never had mail servers. A name that looks right can still have no MX record.
Will a corrected address work?
Yes, once the address is written correctly and the account exists. Write a new message to the corrected address.
How do I find these before I send?
Run the list through the email syntax checker and the bulk email verifier. Both flag addresses that are written wrongly.
Other bounce errors you may run into.
These are the sources behind this page.
The message wording and the fixes come from the providers' own documentation and from the RFC that defines the codes.
Catch bad addresses before they go out.
Emailchaser finds email addresses, checks them and sends your cold emails from your own mailboxes.