DNSVerdictAll toolsGuidesHow it works

530 5.7.1 Microsoft bounce: not authenticated

Permanent failure (530 5.7.1): the receiving system will not accept this message as sent, so resending it unchanged will not help. Fix the cause first.

What 530 5.7.1 means

The receiving server does not accept anonymous mail from the Internet, so your sending server must authenticate first.

Message text

530 5.7.1 Client was not authenticated

Common causes of 530 5.7.1

How to fix 530 5.7.1

  1. Use SMTP authentication or your provider's authenticated endpoint.
  2. Run MX lookup on the recipient domain to confirm you are delivering to the intended server.

Check your domain

Check the MX records of the recipient domainRuns in your browser; nothing is uploaded.

Have the full bounce message? Paste it into the bounce code lookup and it will match the code and the provider for you. Open the bounce code lookup.

How to read 530 5.7.1

The first part, 530, is the SMTP reply code. Authentication required: the server wants the client to authenticate first (RFC 4954). Replies that start with 4 are temporary and replies that start with 5 are permanent (RFC 5321 §4.2.1).

The second part, 5.7.1, is an enhanced status code (RFC 3463 §2) written class.subject.detail. Class 5 is a Permanent failure (5xx): the command was rejected and the sender should not repeat it unchanged (RFC 5321 §4.2.1; RFC 3463 §2).. Subject 7 is security or policy: authentication, authorization or policy refused the message. The detail number refines the subject, and providers may define details of their own, which is why one code can read differently at Gmail, Microsoft and Yahoo.

Do not keep resending the same message: a permanent failure repeats until the cause is fixed. Correct the cause, then send a new message.

Official source: learn.microsoft.com. Last verified 2026-10-20.

Related guides

Related codes

FAQ

What does 530 5.7.1 mean?

The receiving server does not accept anonymous mail from the Internet, so your sending server must authenticate first. This is a permanent failure.

How do I fix 530 5.7.1?

Use SMTP authentication or your provider's authenticated endpoint. Run MX lookup on the recipient domain to confirm you are delivering to the intended server.

Is 530 5.7.1 permanent, and should I retry?

530 5.7.1 is a permanent failure, so retrying the same message will fail again. Fix the cause first, then send a new message.

All bounce codes