If an email you sent bounced back with a 550 5.1.0 error, the receiving mail server refused it because of a problem with an email address. Most often that's the sender's address: yours. This article explains what the error means, how to check your domain in a few minutes, and how to fix the most common causes.
What the error looks like
The bounce message will contain a line similar to one of these:
550 5.1.0 <you@yourdomain.com>: Sender address rejected 550 5.1.0 Address rejected 550 5.1.0 Message rejected due to sender authentication failure
(These are examples. Your bounce may word it differently.)
| Part | What it means |
|---|---|
| 550 | A permanent rejection. The receiving server won't accept the message, and it won't be retried. |
| 5.1.0 | The problem is with an email address, either the sender's or the recipient's. |
| The text after it | The receiving server's reason. This is the most important part, so always read it. |
Tip: strict organizations, such as banks, financial institutions and government agencies, are the most likely to send this error, because they check carefully that emails really come from the domain they claim to be from.
Step 1: Check which address is the problem
Read the full bounce message:
- If it mentions your address (for example "Sender address rejected," or "sender authentication failure"), go to Step 2.
- If it mentions the recipient's address, check it for typos and confirm it's correct with the recipient. A wrong or closed recipient address can also cause a 5.1.0 error.
Step 2: Check your domain right now (2 minutes)
Receiving servers use three DNS records to confirm your emails are genuine:
| Record | What it does | Needed? |
|---|---|---|
| SPF | Lists the servers allowed to send email for your domain | Required |
| DMARC | Tells receivers what to do when checks fail | Required by many banks and large email providers |
| DKIM | Adds a digital signature to prove your emails weren't changed | Recommended |
You can check them yourself with these free tools. Just enter your domain name, for example yourdomain.com:
| Check | Free tool | What you want to see |
|---|---|---|
| SPF | https://easydmarc.com/tools/spf-lookup | One valid SPF record that includes your email provider, 10 lookups or fewer, and no duplicate entries |
| DMARC | https://easydmarc.com/tools/dmarc-lookup | A DMARC record found for your domain |
| DKIM (optional) | https://easydmarc.com/tools/dkim-lookup | A valid DKIM record. You'll need the selector from your email provider. |
Keep the results. Take a copy, or save the page. They tell you, your email provider, and our support team exactly what needs fixing.
If your email is with us
-
Cloud Email: DKIM signing is handled automatically by our email platform, so you don't need to add a DKIM record. Because the signature is applied by our platform rather than your own domain, receiving servers rely on your SPF record to pass DMARC. So make sure your SPF record includes our Cloud Email servers. It does by default if your domain uses our DNS, and you just need a DMARC record in place.
-
Web hosting (Plesk): DKIM is enabled for email sent from your hosting. If your domain uses our DNS, the DKIM record is published automatically. If your DNS is with another provider, copy the DKIM record (
default._domainkey) from your hosting control panel to your DNS provider.
Step 3: Fix what the check found
| What the check found | How to fix it |
|---|---|
| No DMARC record | Add one. Many banks and large email providers now reject email from domains without DMARC. See the example below. |
| No SPF record, or more than one | Your domain must have exactly one SPF record. If you have two, combine them into one. |
| Your email provider isn't in your SPF record | Add your provider's SPF entry, which they can give you. |
| Duplicate entries, or more than 10 lookups | Remove duplicates and any services you no longer use. |
| No DKIM record (optional) | Not required, but recommended. Turn on DKIM with your email provider and add the record they give you. (Cloud Email customers can skip this. See above.) |
Example of a basic DMARC record:
Host: _dmarc Type: TXT Value: v=DMARC1; p=none; rua=mailto:you@yourdomain.com
Replace you@yourdomain.com with an address you check. p=none only monitors, so it won't block your own email.
Step 4: Make the change where your DNS is managed
These records live in your domain's DNS, so they must be changed wherever your nameservers point:
-
If your domain uses our nameservers, you can add or edit these records in your account under your domain's DNS settings, or contact our support team for help.
- If your domain uses another provider's nameservers, contact that provider. You can find your nameservers with a WHOIS lookup. Send them the bounce message and your lookup results, and ask them to fix your SPF and DMARC records (and DKIM, if needed).
Step 5: Wait, then resend
DNS changes usually take effect within a few hours. Once they have:
- Run the checks in Step 2 again to confirm the problem is fixed.
- Resend the email. The original bounced message won't be delivered on its own.
Still bouncing? Here's what to send us
To help us investigate right away, without needing to ask you for more information, please contact our support team with:
-
The full bounce message, in its original form:
- As an .EML file (Gmail: ⋮ → Download message; Outlook: File → Save As; Apple Mail: File → Save As → Raw Message Source), or
- Forwarded as an attachment, or
- Copied and pasted in full, including the technical details at the bottom.
Please don't send a screenshot. We need the exact text.
- Your lookup results from Step 2: SPF, DMARC and, if you have it, DKIM.
- When you sent the email, including the time zone, and who you sent it to.
Frequently asked questions
Why does this only happen with certain recipients, like my bank?
Banks and other strict organizations check email authentication much more closely than most. An email that reaches everyone else can still be rejected by them if SPF or DMARC is missing or incorrect.
Will adding DMARC with p=none block my email?
No. p=none only tells receivers to report results, not to block anything. It's the safest way to start.
Do I need DKIM?
It isn't required to fix most 550 5.1.0 errors, but it's recommended because it adds an extra layer of trust. Cloud Email customers don't need to set it up, since our platform signs emails automatically.
Is the problem on the recipient's side?
Usually not. A 550 5.1.0 about your sender address means the receiving server didn't trust your domain's setup. Fixing your authentication records is the solution.
My SPF check passed. Why is my email still rejected?
Check that you also have a DMARC record. Many strict receivers now require it, even when SPF passes.
If you have any questions, please contact our support team.
Comments
0 comments
Please sign in to leave a comment.