Article
What Does 554 5.7.1 Mean? Causes and Fixes for Email Bounces
By Unlimited Verifier Team ·

Summary
A 554 5.7.1 bounce is a permanent policy refusal from the receiving server, meaning it won't accept your message on trust or policy grounds, not because the mailbox is missing. The usual causes are a blocklisted IP or domain, failed SPF, DKIM or DMARC checks, missing reverse DNS, or high complaint levels. Stop retrying, identify the rejecting provider, fix that specific cause, and resume with a small batch of verified contacts.A 554 5.7.1 bounce is a permanent policy refusal from the receiving server. It will not accept your message on trust or policy grounds, not because the mailbox is missing. RFC 3463 defines the 5.7.1 part as "Delivery not authorized, message refused," so the fix lies in your sending setup and reputation, not in the recipient's address.
For every bounce code, start with our pillar guide to email bounce codes.
Quick answer
- Meaning: 554 is the basic SMTP reply for a failed transaction. 5.7.1 is the enhanced code for a policy refusal. It does not mean the mailbox is missing.
- Common causes: a blocklisted sending IP or domain, failed SPF, DKIM or DMARC checks, missing reverse DNS, relay not permitted, or high complaint and spam-trap levels.
- What to do: Don't retry. Save the full bounce text, identify which provider and IP rejected you, fix that specific cause, then restart with a small batch of verified contacts.
- Where your list fits in: Invalid addresses and spam-trap hits inflate bounce and complaint rates, which feed the reputation scoring behind many 5.7.1 blocks. Verify the list before you resume.
What does 554 5.7.1 actually mean?
554 has two parts, and each says something different. The basic reply code says what kind of failure occurred. The enhanced code says why. RFC 5321 defines 554 as a failed transaction in the 5xx range, which means the server treats the failure as permanent.
| Part | Value | Meaning |
|---|---|---|
| Basic SMTP reply | 554 | Transaction failed. Permanent negative reply. |
| Enhanced class | 5 | Permanent failure. |
| Enhanced subject | 7 | Security or policy status. |
| Enhanced detail | .1 | Delivery not authorized, message refused. |
The enhanced code tells you the rejection was a decision about trust or permission. The basic code is a generic wrapper. Many servers use 554 for different refusals, so two bounces with the same code can have different causes. The text after the code carries the diagnosis, but receivers often say little about how they scored your mail. You usually need your own reputation data to confirm the cause.
A 5.7.1 is decided at SMTP time, so the message is not delivered to a spam folder. It is bounced, and the bounce counts against your bounce rate.
Bottom line: 554 5.7.1 is a permanent policy refusal. The surrounding text and your own reputation data point to the cause.
Why does a 554 5.7.1 bounce happen?
A 554 5.7.1 happens when a receiving server runs a trust or policy check and your message fails it. Six causes cover the large majority of cases, and each leaves a recognisable pattern in the bounce text.
| Likely cause | Typical wording (paraphrased) | What it signals | First check |
|---|---|---|---|
| Blocklisted IP or domain | Client host blocked using a named blocklist | A reputation service lists your IP or domain | Look up the IP and domain on Spamhaus |
| Authentication failure | Message fails authentication, or DMARC rejects it | SPF, DKIM or DMARC alignment is broken | Check the Authentication-Results header of a sent message |
| Reverse DNS problem | Sending host does not resolve, or PTR does not match | The IP's PTR record does not match the sending hostname | Confirm the PTR resolves forward to the same host |
| Relay not permitted | Relay access denied | Your server is sending for a domain it is not authorised to relay | Check SMTP authentication and routing |
| Reputation or complaints | Message resembles unsolicited mail | Complaints, spam-trap hits or poor engagement | Check domain and IP reputation in Google Postmaster Tools |
| Shared IP neighbours | Rejection from a shared sending pool | Another tenant on the same IP is generating complaints | Ask your ESP whether the pool has an incident |
Google's sender guidelines ask bulk senders to keep spam rates in Postmaster Tools below 0.10%, and never reach 0.30%. Older guidance and some ESP documentation cite 0.3% as the line. Use 0.10% as your working target, because it leaves room before the hard limit.
The shared-IP cause is the one senders miss. You can have a clean list and still see 5.7.1 errors because someone else on the pool dropped the reputation. Check the pattern in the diagnosis section before you assume the fault is yours.
Bottom line: Six causes explain most 554 5.7.1 bounces. Match the bounce text to one of them before you change anything.
Does a 554 5.7.1 mean you're blacklisted?
Not always. Many 5.7.1 rejections come from a receiver's internal reputation scoring, which does not appear on public blocklists. A clean Spamhaus lookup rules out one cause, but not the others.
If the bounce text names a specific list, treat that as a confirmed listing and follow that list's removal process. If it names no list and your lookups are clean, focus on reputation and authentication.
Bottom line: A blocklist is one cause to rule out, not the default explanation.
How do you find which cause you have?
Find the cause by checking scope: which providers reject you, and whether the rejections cover one recipient domain or all of them. Scope tells you whether this is a reputation problem with one provider or an infrastructure problem affecting everything.
- Copy the full bounce text from your ESP or mail logs, including the rejecting hostname and IP.
- Group bounces by recipient domain. Divide the 5.7.1 count for each provider by the number of addresses you sent to there.
- Look up the sending IP and domain on Spamhaus and any other list the bounce names.
- Check authentication on one sent message. Confirm SPF and DKIM pass and DMARC aligns with your From domain.
- Check reverse DNS. The PTR record should resolve to a hostname that resolves back to the same IP.
- Check reputation data. Google Postmaster Tools reports domain and IP reputation for mail sent to Gmail. For Microsoft's receivers, check the SNDS (Smart Network Data Services) program for your IP.
| Scope of 5.7.1 bounces | Most likely meaning | Where to focus |
|---|---|---|
| One provider only | Reputation or complaint problem with that provider | Complaint rate, spam traps, that provider's postmaster data |
| Several providers at once | Infrastructure or authentication problem | SPF, DKIM, DMARC, PTR, IP blocklists |
| One sending server or app only | Misconfigured sender or relay | Server authentication, relay settings |
| Began after a new IP or platform change | Shared-pool or warm-up problem | ESP's IP status, warm-up schedule |
Bottom line: Group your bounces by provider first. A single-provider pattern and a multi-provider pattern call for different fixes.
Should you retry a 554 5.7.1 bounce?
No. A 5.7.1 is classed as a permanent failure, so a retry to the same server should expect another refusal. Each retry adds a rejection to the same reputation record, which can slow recovery.
Temporary failures are different. A 452 4.2.2 mailbox full error is transient, and 4.7.x codes are temporary security deferrals you can retry after fixing the cause. Our guide to 4xx vs 5xx SMTP errors explains how to tell them apart.
Don't delete a contact because one 5.7.1 came back for that address. The rejection describes your trust as a sender, not the recipient's mailbox. The exception is when verification shows the address itself is invalid, which is a separate finding.
Bottom line: Stop, diagnose and fix. Treat the address as valid until verification says otherwise.
How long does a 554 5.7.1 block last?
No published standard exists. Blocklist removal times vary by list and by the operator's process. Receiver-side reputation blocks ease as clean sending builds a new record, but the timing depends on the cause and on what you change.
Track Postmaster data and your own bounce logs weekly. Measure the trend rather than promising anyone a date.
Bottom line: Duration depends on the cause and your changes. Measure the trend, don't guess a date.
How is 554 5.7.1 different from similar codes?
554 5.7.1 belongs to a family of permanent policy and recipient codes that look alike but need different fixes.
| Code | Meaning | Who is blocked | Fix direction | Read more |
|---|---|---|---|---|
| 554 5.7.1 | Policy refusal | The sender, IP or message | Fix reputation, authentication or relay | This guide |
| 550 5.7.1 | Same policy class, different basic code | Often a block-list rejection from a large provider | Follow the named list and request review | 550 5.7.1 fix guide |
| 550 5.1.1 | User unknown | The recipient address | Verify and remove the address | 550 5.1.1 meaning |
| 550 5.4.1 | Recipient rejected, access denied | The recipient is restricted | Check the address and recipient policy | 550 5.4.1 explained |
| 452 4.2.2 | Mailbox full (temporary) | The recipient, for now | Retry later | 452 4.2.2 mailbox full |
The enhanced code matters more than the basic code. 550 5.7.1 and 554 5.7.1 describe the same kind of decision, so the same fixes apply. 550 5.1.1 is a different problem: the address is bad, so verification is the right tool. For a full lookup, see our enhanced SMTP status codes list. Mixing up 5.7.1 and 5.1.1 is a common reason fixes fail.
Bottom line: 5.7.1 is a sender-trust problem. 5.1.1 is a recipient-address problem. Match the fix to the enhanced code.
Does cleaning your list fix a 554 5.7.1?
Cleaning your list does not change a provider's policy decision directly. It removes the conditions that feed the scoring behind many 5.7.1 blocks. Invalid addresses create hard bounces, and high bounce and complaint rates damage reputation.
Verification helps in three specific ways:
- Invalid addresses cause hard bounces and count against your bounce rate. Suppress them.
- Risky addresses, including catch-all domains and disposable or role-based addresses, are where complaints and spam-trap hits tend to start. Hold them back.
- Valid addresses are the safe base for a restart. Send to the most engaged contacts first.
We recommend keeping total bounces under 2% and aiming for under 1% during recovery. These are our working targets, not a rule set by any provider, and platforms publish different thresholds.
Verification also supports email verification compliance and hygiene, but it does not prove consent. For ongoing hygiene, see our guide to email list maintenance best practices. To keep bad addresses out at the source, add real-time email validation to your forms.
Bottom line: Verification does not lift a block by itself. It removes the failures and complaints that keep the block in place.
How do you fix a 554 5.7.1 bounce? A 7-step framework
Work through these steps in order. Each one is a precondition for the next, and skipping ahead is a common reason blocks return.
- Stop the send and preserve evidence. Copy the full bounce text, timestamps, rejecting host and affected domains. You will need these for any review.
- Identify the scope. Use the scope table to decide whether this is a one-provider or multi-provider problem.
- Fix any listing. Follow each named list's removal process. Don't promise stakeholders a date, since timelines vary.
- Fix authentication and DNS. Confirm SPF passes and stays within the RFC 7208 limit of 10 DNS-querying mechanisms, sign with DKIM, align DMARC, and correct the PTR record.
- Clean the sending list. Suppress invalid addresses, hold risky ones, and remove unsubscribes and complaints.
- Restart with a small, engaged batch. Send to the most recently engaged valid contacts first. Widen over one to three weeks, watching bounces on every send.
- Monitor and document. Track Postmaster data and your complaint rate, and record what you changed and when.
Bottom line: Fix the cause, clean the list, then restart slowly. The restart schedule matters as much as the fix.
How do you clean your list before restarting?
This tutorial covers step 5 of the framework. Unlimited Verifier checks syntax, domain, MX records and the SMTP mailbox, flags catch-all domains, and sorts every address into Valid, Risky or Invalid. Standard verification is unlimited on every plan, including Free.
- Export your send list as a CSV. Include the email column and a last-engaged date if your ESP provides one. Export the bounce log separately to keep your 5.7.1 evidence.
- Create an account. You can sign up for a free account. The Free plan covers 25 lists a month of up to 150 emails each, plus 750 deep verifications a month. Free results are kept for 24 hours, so download them the same day. Pro keeps results for 30 days.
- Upload the file. Use the Upload and verify a list page. CSV and Excel files up to 10MB are accepted, and the email column is detected automatically.
- Run the verification. Each address is checked for syntax, domain, MX records and the SMTP mailbox. Catch-all domains are detected, and disposable and role-based addresses are flagged.
- Sort the three buckets.
- Valid: eligible for your restart batch.
- Invalid: suppress permanently in your ESP.
- Risky: hold back. The Catch-all email verification page explains what a catch-all result does and does not confirm.
- Export the results as CSV, Excel or JSON. Save the summary counts for your records.
- Re-import only Valid contacts as a new segment in your ESP, and add Invalid addresses to its suppression list. Unlimited Verifier has no native ESP, CRM or Zapier integration, so this is a manual CSV export and import.
- Spot-check edge cases. For a single key account that came back Risky, use the free email checker.
If your team needs verification inside its own systems, the email verification API accepts single-email checks and bulk batches of up to 10,000 emails per request. Pro includes API access at 100,000 emails a month. For how automation fits into a workflow, see email verification API and automation. For plan details, see email verification pricing.
Bottom line: Export, verify, suppress the Invalid, hold the Risky, and restart with Valid contacts only.
Worked example: a 12,000-contact newsletter hits 5.7.1 blocks
This scenario is illustrative. The arithmetic is real, and the verification split is hypothetical.
What happened. A SaaS company sent a newsletter to 12,000 contacts from a shared ESP IP. Of those, 5,000 were Gmail addresses. The send produced 1,020 bounces:
- 840 were 554 5.7.1 rejections, all at Gmail.
- 180 were 5.1.1 "user unknown" bounces across other providers.
Diagnosis. The 5.7.1 rate at Gmail was 840 ÷ 5,000 = 16.8%. The overall bounce rate was 1,020 ÷ 12,000 = 8.5%. Because the 5.7.1 rejections clustered at one provider, the pattern points to a Gmail-specific reputation problem rather than a sending-wide authentication fault. Checking authentication on a sample message would confirm that. The 5.1.1 bounces are a separate list-quality issue.
Cleaning. The list is one file, well under the Pro plan's 25,000-email limit per list. Hypothetical results:
| Bucket | Count | Share of 12,000 | Action |
|---|---|---|---|
| Valid | 10,200 | 85% | Restart, most engaged first |
| Risky | 1,100 | 9.2% | Hold back |
| Invalid | 700 | 5.8% | Suppress |
Check: 10,200 + 1,100 + 700 = 12,000.
Plan cost. Pro is $29 for one month, or $25 a month billed annually, which is $300 a year. The Free plan could not cover this list in one month. It would need 12,000 ÷ 150 = 80 lists of 150 emails, but Free allows 25 lists a month, or at most 25 × 150 = 3,750 emails.
Restart plan. Because the block was Gmail-specific, the first send was a small Gmail-only test. The team widened only while Gmail bounces and Postmaster data stayed clean. Volumes below are per send and total 10,200, the Valid count.
| Day | Audience (Valid only) | Volume | Bounce target |
|---|---|---|---|
| 1 | Gmail contacts who opened in the last 30 days | 800 | Zero 5.7.1, under 0.5% |
| 3 | Contacts who opened in the last 30 days, all providers | 1,700 | Under 0.5% |
| 7 | Contacts who opened in the last 90 days | 3,500 | Under 1% |
| 14 | Remaining Valid contacts | 4,200 | Under 1% |
Check: 800 + 1,700 + 3,500 + 4,200 = 10,200. The 1,100 Risky contacts stayed out, and the 700 Invalid were suppressed. Expect the Gmail trend to improve over weeks of clean sending, not overnight.
Bottom line: A single-provider 5.7.1 pattern points to reputation. The fix is a cleaner list and a slow, engaged-first restart.
What are the most common mistakes?
Most failed recoveries come from a small set of avoidable errors.
- Treating 5.7.1 as a bad-address error. The rejection is a sender-trust decision, so deleting contacts won't fix it.
- Retrying the same send. Each retry adds a rejection to the reputation record.
- Fixing the list but not the infrastructure. On a shared IP, the pool can cause the block even when your list is clean.
- Applying a multi-provider fix to a single-provider problem. Scope determines the fix.
- Moving DMARC to
p=rejectbefore SPF and DKIM align. Legitimate mail can be rejected. - Exceeding the SPF lookup limit. RFC 7208 allows 10 DNS-querying mechanisms. Going over breaks SPF.
- Treating "Valid" as proof of consent. A deliverable address is not an address whose owner wants your mail.
- Restarting with Risky and catch-all contacts. They belong at the end of the ramp, if at all.
- Letting evidence expire. Free plan results are kept for 24 hours. Download and save your counts before they go.
Bottom line: Most failed recoveries come from sending too soon or fixing the wrong layer.
How we compared (and limitations)
This guide is based on public documentation: RFC 5321 and RFC 3463 for code definitions, RFC 7208 for SPF, Google's sender guidelines, and Google's Postmaster Tools documentation. We have not tested these codes against any receiver or run controlled experiments. Exact bounce wording varies by server software and changes over time, so treat the examples as patterns.
The 99.5% accuracy figure for deep verification is Unlimited Verifier's own stated number, not an independent benchmark. The worked-example percentages are illustrative. For tool selection, see our guide to how to choose an email verifier and this roundup of best email verification tools.
Bottom line: Treat the codes and thresholds here as a diagnostic guide. Confirm exact wording and current limits with your own provider.
Fix-it steps for a 554 5.7.1 bounce
- Stop sending to the affected provider and do not retry the same message.
- Save the full bounce text and note the rejecting server and IP.
- Check the IP and domain against blocklists such as Spamhaus.
- Verify SPF, DKIM, and DMARC pass on a sent message's Authentication-Results header.
- Confirm the sending IP's reverse DNS (PTR) resolves forward to the same hostname.
- Check complaint and bounce rates and remove invalid or unengaged addresses.
- Resume with a small verified batch, then increase volume gradually while monitoring results.
Frequently asked questions
Is 554 5.7.1 a hard or soft bounce?
554 5.7.1 is treated as a hard, permanent failure. The 5 in the enhanced code means permanent, and the 554 basic reply is a permanent negative response. Retrying the same message usually gets the same refusal, so fix the underlying cause before sending again.
Does 554 5.7.1 mean the email address is invalid?
No. 554 5.7.1 does not mean the mailbox is missing. That would normally appear as a user-unknown code such as 550 5.1.1. A 5.7.1 means the receiving server refused the message on trust or policy grounds.
Can I fix a 554 5.7.1 bounce by retrying?
Usually not. Retrying without changing anything tends to repeat the refusal and can worsen your sending reputation. Save the full bounce text, find the cause, correct it, and then send a small test batch.
How do I find out which blocklist caused the 554 5.7.1?
Read the full bounce text, which often names the blocklist or provider. Then check your sending IP and domain on blocklist lookup tools such as Spamhaus. If you are listed, follow that list's delisting process after fixing the cause.
Why do Gmail or Microsoft return 554 5.7.1?
Major providers use 5.7.1 when a message fails their reputation or authentication policies. Common triggers include failed SPF or DMARC alignment, a poor complaint rate, or sending from a listed IP. Check the provider's postmaster tools and the full bounce text for specifics.
Does a 554 5.7.1 bounce hurt my sender reputation?
Yes. Bounces count toward your bounce rate, and high bounce or complaint rates feed the reputation scoring that often triggers these refusals. Removing invalid addresses and spam-trap hits helps reduce the risk.
What is the difference between 554 5.7.1 and 550 5.7.1?
Both use the 5.7.1 policy detail, but the basic code differs. 550 is a permanent mailbox or action-not-taken refusal, while 554 is a general permanent transaction failure. The text after the code is needed to confirm the specific reason for either.
How long does it take to recover from a 554 5.7.1 block?
It depends on the cause. Authentication fixes can take effect quickly, while blocklist removal or reputation recovery can take days to weeks. Restart with low volume and watch bounce and complaint rates before increasing sending.
Should I remove addresses that bounced with 554 5.7.1?
Generally yes. Suppress addresses that returned permanent failures so you do not keep sending to them. Verify the list before resuming, since invalid addresses and spam traps inflate bounce and complaint rates.
Cut Bounces and Protect Your Sender Reputation With Unlimited Email Verification
Every invalid address you send to hurts your sender reputation and your inbox placement. Verifying your list before each send means fewer bounces, healthier deliverability, and a predictable cost. With Unlimited Verifier, standard verification is unlimited on every plan, with no per-email fees.
Unlimited Verifier checks syntax, domain, MX records and the SMTP mailbox. It also detects catch-all domains and flags disposable and role-based addresses. Export a CSV from your email platform or CRM, upload and verify the list, then re-import the clean results. You can also automate checks with the email verification API.
| Free | Pro | |
|---|---|---|
| Price | $0 | $29/month ($25/month billed annually) |
| Lists | 25 a month, up to 150 emails each | Unlimited, up to 25,000 emails each |
| Deep verifications | 750 a month | 25,000 a month |
| API access | No | Yes (100,000 emails a month) |
| Result retention | 24 hours | 30 days |
Why teams choose Unlimited Verifier
- Unlimited standard verification on all plans, including Free, with no per-email fees.
- Catch-all detection so you know which domains accept every address.
- Clear Valid / Risky / Invalid results, exportable as CSV, Excel or JSON.
- An open-source verification engine you can inspect on GitHub.
Unlimited Verifier states 99.5% accuracy for deep verification.
Create a free account and verify your next list before you hit send.
Want to test a single address first? Try the free email checker.