Critical ErrorSMTP Error · Permanent (5.x.x)
550 5.7.29

Gmail: message not sent over TLS

A 550 5.7.29 from Gmail means the message was blocked because the connection did not use TLS. Gmail says: "This message was blocked because it wasn't sent over a TLS connection." The temporary form is 421 4.7.29.

Updated June 13, 2026

SMTP Exchange / Mail Log
> MAIL FROM:<you@yourdomain.com>> RCPT TO:<recipient@example.com>✕ 550 5.7.29 Gmail: message not sent over TLS
All guides

Is your domain affected?

Run a free check — we'll show you exactly what's misconfigured.

550 5.7.29 is a permanent SMTP reply meaning gmail: message not sent over tls. Gmail requires bulk senders to use TLS when they deliver mail. Your server connected and sent the message in plain text.

What 550 5.7.29 means

Gmail requires bulk senders to use TLS when they deliver mail. Your server connected and sent the message in plain text.

⚠️
This is a 5.x.x permanent failure — the message will keep bouncing until you fix the cause. Retrying the same message unchanged won't help.

Common causes

📨
#1

STARTTLS is turned off on your server

Most common

Postfix, Exim or another MTA is not set to use TLS for outbound mail.

🔁
#2

The TLS setup fails and the server falls back

Common

An old TLS version, an expired certificate or a bad cipher list makes the handshake fail.

⚙️
#3

A device or app sends directly to Gmail

Less common

Printers, scanners and old apps often cannot use TLS.

How to fix 550 5.7.29

  1. 1

    Turn on opportunistic TLS for outbound mail

    In Postfix, set smtp_tls_security_level = may (or encrypt). Other MTAs have the same setting.

  2. 2

    Use TLS 1.2 or newer

    Remove old protocol versions and make sure the server certificate is valid and not expired.

  3. 3

    Route old devices through a relay

    Send device mail through Google Workspace SMTP relay or your ESP, which use TLS.

Confirm your domain is set up correctly

Most delivery failures — permanent or temporary — trace back to authentication or reputation. Run a free EmailHealth check to confirm SPF, DKIM, DMARC, blacklist status, and TLS are all healthy for your sending domain. If you send in volume, free daily monitoring will alert you before a small issue becomes a flood of bounces.

Stop this error from coming back

Most delivery problems start when a DNS record changes, a key is removed or a domain lands on a blocklist. EmailHealth checks your sending domains every day and sends one alert, by email, Slack or webhook, with the exact fix.

1 domain free. Sending from many domains (cold email, agencies, MSPs)? Early access covers 10.

Frequently asked questions

Check your domain for free

SPF, DKIM, DMARC, MX, blocklists and TLS in about 2 seconds. No account needed.

Run the check