Delivery error

554 5.7.1 error: why your email was rejected

554 5.7.1 indicates a permission or policy refusal. It may come from your relay or a server further along the route. Read the full delivery report; if it names SPF, DKIM or DMARC, start with the sender DNS check.

Enter the domain the rejected email was sent from. Free, no sign-up.

  • Free, no sign-up
  • Public DNS records only
  • Result in seconds
4.7/5 · 95 reviewsGoogleGoogleCapterraCapterraTrustpilotTrustpilotG2G2

Want the step-by-step fixes?We email you the full report on SPF, DKIM, DMARC and MX, with the values to copy.

We use your email to send the report and, only if you tick the box, tips and news. Privacy policy.

Done: the report reaches your inbox in a few minutes. If you don’t see it, check spam or Promotions too.

the basics

What 554 5.7.1 means

554 is a permanent rejection, 5.7.1 points to a permission or policy problem. The text after the code gives the reason: for example Relay access denied, Message rejected due to SPF, rejected by DMARC policy or a blocklist reference.

Always read the full text of the bounce message: that’s where the server explains what’s wrong.

Sample rejection554 5.7.1 Message rejected
554Permanent rejection: retrying won’t help until the cause is fixed.
5.7.1A sender permission or security problem.
the text after itIt often says why: SPF, DMARC, a blocklist or relaying not allowed.
common problems

The most common causes and what to do

Relay access denied

Identify the server refusing to relay first. For your configured SMTP server, check authentication and permitted senders; a remote refusal may require its administrator. The code alone does not establish that your password is wrong.

SPF fail

Check the MAIL FROM domain and the actual sending server. Publish one SPF record using the provider instructions and respecting the DNS lookup limit; do not add includes blindly.

DMARC set to reject

With p=reject, the domain requests rejection when DMARC fails: at least SPF or DKIM must pass and align with the From domain. Check received message headers and the sending service configuration.

Blocklist

The IP or domain is listed: check the blocklists and request removal after fixing the cause. Start with the free blacklist check.

locate the rejection first

Where did the 554 response come from? A diagnostic path

  1. Can your application hand the message to its configured SMTP server? If not, check the server, port, authentication and permitted senders. A refusal from your own relay does not establish a recipient-side problem. Follow the provider's setup instructions without disabling TLS or making the relay publicly accessible.
  2. Was the message accepted by your SMTP service but rejected further along the route? Look for the remote server, full response and SMTP stage in the delivery report. A response during RCPT TO concerns that step; rejection after DATA follows transmission of the content. The stage narrows the investigation but does not establish the cause by itself.
  3. Does the response name SPF, DKIM or DMARC? Identify the domain and service actually used for this message, rather than checking only your website domain. Start with published DNS records and, where available, compare message headers. Do not weaken DMARC or add arbitrary records just to remove the error.
  4. Does the refusal name a group, internal rule or recipient restriction? Keep the report and ask the recipient's administrator to inspect that rule. Domain authentication does not override local policy. Blindly switching an address, alias or relay does not explain the refusal.

Repeating an unchanged message is not the fix for a 5xx refusal. After addressing the cause, verify the result with a controlled send to a mailbox you manage. Keep this separate from a temporary 4xx condition: the sending system may already have that message queued, and submitting another copy may create duplicates.

Before asking for help, collect: date and time with time zone, the full response, rejecting server and SMTP stage, plus an identifier to share privately with your provider. Remove addresses, IPs and identifiers from public posts or screenshots. Never include passwords, API keys or account access links.

The email DNS checker reads public records. It cannot inspect credentials, recipient allow lists or every DKIM signature used in a particular send. For the difference between the visible sender and the reply destination, see our From and Reply-To guide.

Technical sources checked October 30, 2026: RFC 5321, SMTP replies; Microsoft's 5.7.1 troubleshooting guide; Google's SMTP error codes. Provider documentation also covers 550 responses; those examples are separate from the 554 log excerpt shown here.

From the error to a controlled test

For a WordPress or WooCommerce rejection, use the official SMTP Senpai plugin guide to check notification generation, transport and the actual received message. If outbound SMTP ports are blocked, consider API mode over HTTPS.

Keep the complete error code and rejection text, removing addresses and identifiers before publishing it. The IANA enhanced status code registry distinguishes permission and policy problems; the fix depends on the rejection detail.

Frequently asked questions

Why does it happen only with some recipients?

Recipients can apply different rules to a domain, group or individual mailbox. Compare complete reports: valid authentication does not rule out a local restriction, and the code alone does not identify the rule involved.

Should I contact the recipient?

It depends on the rejection reason. Fix the sender errors named in the message; if it cites an internal recipient policy, ask their administrator to check that rule.

My hosting sends my website emails and I get 554: what now?

Read the rejection text and check authentication and the sending server. A relay with a verified sender domain can help when the hosting transport causes the problem; it cannot automatically fix a recipient policy or guarantee delivery.

How long until it’s resolved?

There is no fixed resolution time. DNS changes depend on publication and resolver caches; internal rules and blocklists require their operators to review the issue. Address the stated cause and verify the result rather than assuming a few hours will fix it.

Do your website or app emails still leave from the hosting server?

SMTP Senpai is the MailSenpai SMTP relay: it signs your emails with DKIM on your own domain, gives you the DNS records to publish and checks them for you. Servers and data in the EU.

Free · no sign-upCheck