Opens in a new tab

Gmail 550 5.7.29: the message wasn’t sent over a TLS connection

Gmail requires bulk senders to encrypt the connection with TLS (STARTTLS), and this message arrived over a plain, unencrypted connection.

550 5.7.29 This message was blocked because it wasn't sent over a TLS connection. Gmail requires all bulk email senders to use TLS/SSL for SMTP connections. To set up TLS for email, visit TLS & SSL connections. To learn more about Gmail requirements for bulk email senders, visit Email sender guidelines. - gsmtp
3 other wordings of the same rejection

Temporary:

421 4.7.29 Your email has been rate limited because you're not using a TLS connection. Gmail requires all bulk email senders to use TLS/SSL for SMTP connections. To set up TLS for email, visit TLS & SSL connections. To learn more about Gmail requirements for bulk email senders, visit Email sender guidelines. - gsmtp

The recipient’s domain requires TLS:

421 4.7.0 TLS required for RCPT domain, closing connection. For more information, go to Email encryption in transit. - gsmtp

STARTTLS required before sending:

530 5.7.0 Must issue a STARTTLS command first. For more information, go to About SMTP error messages and review RFC 3207 specifications. - gsmtp
Code550 5.7.29
Sent byGmail
TypePermanent — not retried
CauseTLS

See what receivers see

Send one email to our test address and get back the sending server’s reverse DNS, TLS, authentication and blocklist results — the things this bounce is about.

Run the free email test →

What it means

TLS here is between mail servers, not your website’s certificate. The sending server has to offer STARTTLS when it connects to Gmail and complete the handshake.

The “TLS required for RCPT domain” wording comes from the recipient’s own Workspace policy; 530 5.7.0 means the server tried to send before starting TLS.

Why it happens

  • An old or misconfigured mail server (or a device such as a copier or monitoring box) with TLS switched off.
  • A TLS library too old to agree on a protocol version with Gmail.

How to fix it

  1. Turn on outgoing opportunistic TLS on the sending server (Postfix: smtp_tls_security_level = may; Exchange: TLS on the send connector).
  2. If a device sends directly, relay it through your mail provider’s SMTP server instead, which already uses TLS.
  3. Send a test email to see whether the connection was encrypted.

Sources

Message text and meaning checked on 25 September 2026 against these official sources:

Catch it before the bounces start

Add your domain and we monitor what these bounces are about — SPF, DKIM, DMARC, your sending servers on the blocklists, Gmail’s spam rate — every day, and email you the day something changes. Free for your first domain.

Create a free account