Bounces and errors

What Does 530 5.7.0 Mean, and How Do I Fix It?

Outreach2dayPublished 4 min read
On this page

Short answer

530 5.7.0 means the SMTP server refused to take mail because the session lacked something it requires: a login (Authentication required) or an encrypted connection (Must issue a STARTTLS command first). No email was sent, and reputation plays no part. Fix the connection settings in your sending tool: the submission host, the port and encryption your provider documents, and authentication with the full address and password.

A missing login or missing TLS

A submission server answers 530 when your tool tries to send before the session meets the server's policy. RFC 4954 defines 530 5.7.0 Authentication required for the case where "server policy requires authentication in order to perform the requested action and authentication is not currently in force." RFC 6409 has submission servers answer MAIL with 530 until the session is authenticated.

The second meaning comes from RFC 3207. A server that requires TLS first should answer "530 Must issue a STARTTLS command first" to every command other than NOOP, EHLO, STARTTLS or QUIT, with 5.7.0 as the enhanced code. RFC 3463 calls 5.7.0 "Other or undefined security status", which is why one code covers both cases.

Either way the session stopped before any message data moved. The text after the code tells you which part is missing.

The texts by provider

Provider

Text in the error

What the session lacked

Gmail

"530 5.7.0 Authentication required."

A login

Gmail

"530 5.7.0 Must issue a STARTTLS command first."

TLS on a connection that started in plain text

Microsoft 365

"5.7.57 Client not authenticated to send mail"

A login to smtp.office365.com

Microsoft 365

"Client was not authenticated to send anonymous mail during MAIL FROM"

A login, or a device sending with no account at all

Both Gmail texts are in Google's SMTP error list (updated November 10, 2026), next to a related one: "554 5.7.0 Too many unauthenticated commands." Microsoft 365 uses its own code, 5.7.57. Its NDR article titles it 550 5.7.57 and says that smtp.office365.com needs "the credentials of a user who has an Exchange Online mailbox." The code also appears as 530 5.7.57, for example in this Microsoft Q&A thread from an Exchange hybrid setup.

The settings behind it

Port

What the server expects

Typical mismatch

587

Plain text, then STARTTLS, then a login

Encryption "None": "Must issue a STARTTLS command first"

465

TLS from the first byte

STARTTLS or "None": the handshake fails before any 530

25

Relay between servers; submission hosts still want a login

No login: "Authentication required"

Per Google's IMAP, POP and SMTP page, if your client "begins with plain text before issuing the STARTTLS command," use smtp.gmail.com:587; port 465 requires implicit SSL/TLS. RFC 8314 describes the same split for submission.

Microsoft's device setup page asks for smtp.office365.com, port 587 (recommended) or 25, and TLS 1.2 or 1.3. It adds that an app which "recommends or defaults to TCP port 465" does not support the TLS versions Microsoft requires.

An empty password field leads to the same missing login. Microsoft's printer and app troubleshooting article notes that a device which never asked for a password "is trying to send email without logging on."

How to fix it

  1. Copy the full error with the host and port the tool used.

  2. Check the host. Use your mailbox provider's submission host: smtp.gmail.com for Gmail and Google Workspace, smtp.office365.com for Microsoft 365, or the SMTP host your provider gives you.

  3. Match port and encryption. Port 587 goes with STARTTLS, which many tools label TLS. Port 465 goes with SSL/TLS. Microsoft 365 documents 587 or 25.

  4. Turn authentication on. Enter the full email address as the username and fill in the password.

  5. Update old software. Microsoft 365 needs TLS 1.2 or later, so an outdated plugin or library fails there.

  6. Test again and read the new code. A 535 means TLS works and the login itself was refused: a password, app password or admin setting. For Microsoft 365, the troubleshooting article adds an admin check: SMTP AUTH enabled on the mailbox.

Free guide19 min read

Send 100,000 cold emails a month

Domains and mailboxes you need, DNS, warmup, lists, copy and follow-ups, with a launch checklist, sent to your inbox.

Unsubscribe in one click.

When a 530 comes back in a bounce

Sometimes the 530 comes from a recipient's server. Microsoft's NDR guide shows a bounce with "530 5.7.1 Client was not authenticated" from a server that "is configured not to accept anonymous email from the Internet," and puts the fix with that domain's administrators. RFC 3207 points the same way for TLS: a server listed in a domain's MX "MUST NOT require use of the STARTTLS extension in order to deliver mail locally."

For a cold email list that is one domain's problem. See where the domain's mail goes with MX lookup and pause sends to it.

Questions

Does 530 5.7.0 mean my password is wrong?

Usually the server never checked a password: the tool sent mail commands before logging in or before starting TLS. A refused login comes back as 535; RFC 4954 defines 535 5.7.8 as "Authentication credentials invalid." For 5.7.57, Microsoft still lists checking the credentials first, next to TLS.

Is 530 5.7.0 a block on my domain or IP?

No. The server stopped the session over a missing login or TLS, before it saw a message. Gmail's reputation refusals carry other codes and say so in the text; see 421 4.7.0 and 550 5.7.1.

What we recommend at Outreach2day

Outreach2day mailboxes are standard SMTP/IMAP on our own infrastructure, and their logins work in any tool that accepts SMTP/IMAP; we don't sell Google Workspace or Microsoft 365 mailboxes. For Instantly and Smartlead you connect an API key and we add the mailboxes to the tool ourselves, with no SMTP settings to type.

Sources

Deliverability call

Talk to our deliverability team

Book a call with the people who run our mailbox infrastructure. We look at your current setup and tell you what to change.

  • Review your domains, DNS records and current inbox placement
  • Size the setup: domains, mailboxes per domain and daily volume per mailbox
  • Plan warmup and the move from your current provider or sequencer

Free call

See open times in your time zone and book on this page.

Or open the booking page

See deliverability issues before they kill performance

Check each mailbox's daily inbox, spam and bounce rate, replace the weak ones early, and keep warmup, protection, and sending in one place.