
SMTP ports decide how your mail software connects to a mail server, and choosing the wrong one is behind many "can't connect" and "authentication failed" errors. Port 25 is for server-to-server delivery, port 587 is the standard submission port using STARTTLS, port 465 is submission over implicit TLS, and 2525 is a non-standard alternative some providers offer. This guide explains each, what the standards recommend, why many clouds block port 25, the correct settings for Google Workspace and Microsoft 365, and what cold emailers actually need to configure.
SMTP Ports: The Short Answer
Port | Use | Encryption | Use it for |
|---|---|---|---|
25 | Server-to-server relay (MX delivery) | Opportunistic STARTTLS | Mail servers talking to each other |
587 | Message submission | STARTTLS (upgrade after connect) | Apps and clients sending mail |
465 | Message submission | Implicit TLS (encrypted from connect) | Apps and clients sending mail |
2525 | Non-standard alternative | Provider-dependent | When 587/465 are blocked and your provider supports it |
💡 Key Takeaways
Apps and sequencers submit mail on 587 or 465 with authentication. Port 25 is for servers relaying to other servers, and is often blocked on cloud and residential networks.
465 vs 587: Which Should You Use?
RFC 8314 recommends connecting to submission servers using implicit TLS in preference to connecting on a cleartext port and upgrading with STARTTLS, and it registered port 465 for implicit-TLS submission. Port 587 with STARTTLS remains widely supported. In practice: use whichever your provider documents; if both are offered, 465 (implicit TLS) is the more modern default, and 587 is a safe fallback.
Port 25 and Why It's Often Blocked
Port 25 carries mail between servers. Because it's heavily abused for spam, many networks block outbound connections on it. Google Cloud, for example, documents that connections to destination port 25 outside your VPC are blocked, including SMTP relay with Google Workspace, and suggests using other ports or third-party services (Google Cloud: sending mail). Residential ISPs commonly block it too. If you're self-hosting, this matters — see self-host email server.
Port 2525
2525 isn't an official SMTP port, but some email services offer it as an alternative submission port for networks that block standard ones. Google Cloud's documentation uses 2525 as an example of a custom port you can open with a firewall rule. Only use it if your provider supports it.
Settings for Google Workspace and Microsoft 365
Service | Server | Ports | Notes |
|---|---|---|---|
Gmail / Google Workspace SMTP | smtp.gmail.com | 465 (SSL) or 587 (TLS) | OAuth or app passwords; less secure apps no longer supported |
Google Workspace SMTP relay | smtp-relay.gmail.com | 25, 465 or 587 | For devices and apps; IP or SMTP auth (Google relay setup) |
Microsoft 365 SMTP AUTH | smtp.office365.com | 587 (STARTTLS) | Basic auth being retired; use OAuth (Microsoft timeline) |
For cold email, connect Google Workspace and Microsoft 365 inboxes to your sequencer by OAuth where possible, so you don't manage SMTP ports or passwords at all (Google Workspace + Smartlead, Microsoft 365 + Smartlead).
Troubleshooting Port Problems
Symptom | Likely cause | Fix |
|---|---|---|
Connection timed out | Port blocked by network or firewall | Try 465/587; check firewall |
TLS handshake error | Wrong encryption for the port | 465 = SSL/TLS; 587 = STARTTLS |
Authentication failed | Basic auth disabled or wrong credentials | Use OAuth or app password |
Relay access denied | Not authenticated to relay | Authenticate (550 5.7.1) |
Works locally, not in cloud | Cloud blocks outbound 25 | Use 465/587 or provider relay |
What Cold Emailers Actually Need
Using Google Workspace or Microsoft 365 with OAuth → no port configuration.
Using SMTP credentials in a sequencer → 465 or 587 with the provider's host.
Running your own server → 25 for outbound delivery to other servers, 587/465 for your apps (SMTP server setup).
Using a relay → follow the relay's documented ports (SMTP relay vs SMTP server).
Ports Connect You — Reputation Delivers
Once connected, deliverability depends on:
🔐Authenticate every domain
SPF, DKIM and DMARC aligned (authentication guide, Google Workspace setup, Microsoft 365 setup).
🌐Use secondary sending domains
Keep your main domain out of cold outreach (domain setup, domain risks).
🔥Warm or start pre-warmed
Ramp gradually (warm-up guide) or use pre-warmed inboxes (pre-warmed vs fresh).
📉Keep per-inbox volume low
Scale with inboxes, not volume (safe sending limits, inbox sizing).
✅Verify every list
Bounces damage reputation fast (verification tools, list cleaning).
📊Monitor weekly
Spam rate, bounces and blocklists (Postmaster setup, blacklist tools).
Skip Port Configuration Entirely
LiteMail | OAuth-connected inboxes
Fresh from $2.50/inbox
Official Google Workspace and Microsoft 365 inboxes for outreach
LiteMail provisions official Google Workspace and Microsoft 365 inboxes on secondary domains, configures SPF, DKIM and DMARC automatically and lists dedicated US and EU IPs. Inboxes export in bulk by OAuth to Instantly, Smartlead, Lemlist and Pipl.ai, so there's no port or password setup per inbox.
Strengths | Keep in mind |
|
|
Explore pricing, the inbox calculator, infrastructure, bulk inboxes and setups for agencies, SaaS and recruiters. Comparing providers? See Google Workspace vs Microsoft 365.
Connect by OAuth and forget about ports. Get Pre-Warmed Inboxes →
Frequently Asked Questions
Which SMTP port should I use?
Use 465 (implicit TLS) or 587 (STARTTLS) for sending from apps and clients; use whichever your provider documents.
Is port 465 deprecated?
No. RFC 8314 registered 465 for submission over implicit TLS and prefers implicit TLS.
What is port 25 used for?
Server-to-server mail delivery.
Why is port 25 blocked?
It's heavily abused for spam, so many cloud providers and ISPs block outbound connections on it.
What is port 2525?
A non-standard alternative submission port some providers offer.
What are Gmail's SMTP settings?
smtp.gmail.com on 465 (SSL) or 587 (TLS), with OAuth or an app password.
What are Microsoft 365's SMTP settings?
smtp.office365.com on port 587 with STARTTLS; Microsoft is retiring Basic auth for SMTP AUTH in favour of OAuth.
Do I need SMTP ports for cold email?
Not if you connect Google Workspace or Microsoft 365 inboxes to your sequencer by OAuth.
Connected in Minutes, No Ports Required
Official Google Workspace and Microsoft 365 inboxes with automated SPF, DKIM and DMARC on dedicated US and EU IPs.
Automated DNS · Pre-warmed options · OAuth export
About LiteMail — LiteMail provides fresh and pre-warmed Google Workspace and Microsoft 365 inboxes for cold email outreach, with automated SPF, DKIM and DMARC setup, dedicated US and EU IPs, separate client workspaces and one-click OAuth export to Instantly, Smartlead, Lemlist and other sending tools. View pre-warmed inbox plans →
Related reading: Google Workspace + Smartlead · Microsoft 365 + Smartlead · Smartlead Setup · Microsoft 365 Cold Email Setup · Google Workspace Setup for Lead Gen · Bulk Email Inboxes


