Bounce code · Gmail

550 5.7.29: This message was blocked because it wasn't sent over a TLS connection

Gmail returns 550 5.7.29 when not sent over TLS. The sending system is misconfigured: relaying through the wrong server, no TLS, no authentication to the outbound server.

Published Updated 4 min read
550 5.7.29, at a glanceChecked
Code
550 5.7.29
Provider
Gmail
Message
This message was blocked because it wasn't sent over a TLS connection.
Cause
Configuration
Bounce type
Hard (permanent for that message)
Does warming help
No: the cause is not reputation
Immediate action
The sending server delivered without TLS. Enable STARTTLS on the outbound server; every major provider offers it.

What 550 5.7.29 means

The message Gmail attaches to this code is This message was blocked because it wasn't sent over a TLS connection., as written on its reference page. The first digit says how final it is: a 5xx reply is permanent for that message, so the sending server gives up and returns a bounce. The enhanced status 5.7.29 says what class of problem it is: configuration. The sending system is misconfigured: relaying through the wrong server, no TLS, no authentication to the outbound server.

Why it happens

The sending system is set up wrong: relaying through a server that will not carry the mail, no authentication to the outbound server, encryption refused, or sending straight to the recipient's server when the provider expects its own. The message never gets far enough for reputation or content to matter.

What to do first: The sending server delivered without TLS. Enable STARTTLS on the outbound server; every major provider offers it.

Why warming does not fix this

Warming builds sender reputation. 550 5.7.29 in this form is a configuration problem, and no amount of engagement history changes it. Fix the cause and the bounce stops; warming is for what comes after, when the mail is accepted and the question becomes which folder it lands in. See how warming works for that part.

How to fix it, in order

  • Fix the outbound server: authenticate to it, relay through the right host, enable STARTTLS
  • Send through the provider's SMTP rather than direct-to-MX where the error says so

More on Gmail

Questions about 550 5.7.29

What does 550 5.7.29 mean?

Gmail returns 550 5.7.29 with the message "This message was blocked because it wasn't sent over a TLS connection.": not sent over TLS. The sending system is misconfigured: relaying through the wrong server, no TLS, no authentication to the outbound server.

Is 550 5.7.29 a hard bounce or a soft bounce?

A hard bounce for that message: the 550 reply is permanent, and the message is not retried. Whether the address should be removed depends on the cause: here the fix is on the sending side, not the list.

How do I fix 550 5.7.29?

The sending server delivered without TLS. Enable STARTTLS on the outbound server; every major provider offers it. Gmail's own reference for the code is linked on this page.

Does email warmup fix 550 5.7.29?

No. 550 5.7.29 in this form is a configuration problem, and warming builds reputation, which is not what is failing here. Fix the cause and the bounce stops.

What this page was checked against

The message text on this page was matched verbatim against Gmail's own reference on . If Gmail has changed the wording since, tell us and we will correct it.

All 37 verified codes, decoder and search.