How to Relay gmail smtp

Published October 16, 2024 · Updated July 18, 2026 · SMTP & Deliverability

Relaying your app or website email through Gmail SMTP is a common quick fix — but it is worth knowing when it is the right move and when it will hold you back. Here is a straight decision guide on relaying through Gmail.

When relaying through Gmail makes sense

Low volume — a contact form, a personal project, a handful of notifications a day.
You already have a Gmail or Workspace account and want the fastest setup.
You are testing before committing to real infrastructure.

When it will let you down

You send more than a few hundred a day — Gmail's caps stop you cold.
You need a dedicated IP and full control over deliverability.
You are running marketing campaigns — Gmail is not built for them, and heavy use risks your account.

How to relay through Gmail (quickly)

Point your app at smtp.gmail.com, port 587 (STARTTLS), and authenticate with your address and an app password. That is all it takes for low-volume sending.

The line to watch: the moment your sending outgrows a few hundred a day or starts driving revenue, relaying through Gmail costs you more in caps and deliverability than a dedicated SMTP would.

Related reading: Freeware smtp relay · Gmail as smtp · test your email deliverability

Outgrown Gmail relay?

Relay through a dedicated SMTP instead

Dedicated IP, no caps, and authentication done for you — the upgrade from Gmail relay when your sending gets serious. From $39.99/mo.

See unlimited SMTP plans →See all plans

Frequently asked questions

Can I relay email through Gmail SMTP?

Yes, for low volume — point your app at smtp.gmail.com on port 587 with an app password. For higher volume, use a dedicated SMTP.

What are the downsides of relaying through Gmail?

Daily caps, a shared IP you do not control, and account risk if you push volume — all of which a dedicated SMTP avoids.