Free IMAP & SMTP Settings Lookup

Settings result

Connect from code: Gmail

Generated from the settings above. Credentials are read from environment variables; never hard-code passwords or commit them. Use the credential this provider requires: sign in with google (oauth), or an app password.

import imaplib
import os
import smtplib
import ssl
from email.message import EmailMessage

# Gmail: credentials come from environment variables, never hard-code them.
user = os.environ["MAIL_USER"]  # Your full Gmail address
secret = os.environ["MAIL_PASSWORD"]  # app password, or use OAuth 2.0 (XOAUTH2) instead
context = ssl.create_default_context()

# IMAP: imap.gmail.com:993 (SSL/TLS)
with imaplib.IMAP4_SSL("imap.gmail.com", 993, ssl_context=context) as imap:
    imap.login(user, secret)
    imap.select("INBOX", readonly=True)
    status, data = imap.search(None, "UNSEEN")
    print(status, data)

# SMTP: smtp.gmail.com:465 (SSL/TLS)
msg = EmailMessage()
msg["From"] = user
msg["To"] = user
msg["Subject"] = "Test"
msg.set_content("Sent with Python.")

with smtplib.SMTP_SSL("smtp.gmail.com", 465, context=context) as smtp:
    smtp.login(user, secret)
    smtp.send_message(msg)

import nodemailer from "nodemailer";

// Gmail: read credentials from the environment, never commit them.
const transporter = nodemailer.createTransport({
  host: "smtp.gmail.com",
  port: 465,
  secure: true, // implicit TLS from the first byte
  auth: {
    user: process.env.MAIL_USER, // Your full Gmail address
    pass: process.env.MAIL_PASSWORD, // app password, or use OAuth 2.0 (XOAUTH2) instead
  },
});

await transporter.verify();
await transporter.sendMail({
  from: process.env.MAIL_USER,
  to: process.env.MAIL_USER,
  subject: "Test",
  text: "Sent with Nodemailer.",
});

Add the account to your mail app

Menu names change between app versions, so these steps stay general. Prefer the app's built-in sign-in for Google, Microsoft, Yahoo, AOL and iCloud: it uses OAuth and sets the servers for you.

Ports 465, 587, 993 and 25 explained

Source: RFC 8314: Use of TLS for Email Submission and Access. Port 25 blocking: Xfinity and Microsoft help pages linked in the reference table.

Troubleshooting: why isn't my IMAP or SMTP working?

• The port and encryption type don't match

  Ports 993 (IMAP), 995 (POP) and 465 (SMTP) expect SSL/TLS from the first byte. Port 587 (and IMAP 143) expect STARTTLS. Picking SSL on 587 or STARTTLS on 465 usually ends in a timeout or a TLS error. (RFC 8314)

• Gmail says "Username and password not accepted"

  Gmail no longer accepts apps that only ask for your Google password. Remove the account, add it again and choose Sign in with Google. If the app has no Google sign-in and you use 2-Step Verification, create an app password. (Gmail Help)

• Outlook.com or Microsoft 365 keeps asking for your password

  Outlook.com requires Modern Auth (OAuth2), and Exchange Online has disabled Basic authentication for POP and IMAP. Update your mail app or switch to one that signs in with Microsoft's own sign-in page. (Microsoft Learn)

• IMAP or POP access is turned off

  Outlook.com and GMX turn POP/IMAP off by default, Zoho needs IMAP Access enabled, Google Workspace and Microsoft 365 admins can switch it off (security defaults do in Microsoft 365), and Gmail needs POP turned on before POP works. The card above lists what your provider needs.

• Your provider requires an app password or a paid plan

  Yahoo, iCloud and Fastmail require app passwords, AT&T uses a secure mail key, and Proton Mail needs the Bridge password. Fastmail Basic plans, newer free Zoho accounts and free Proton plans don't include IMAP/SMTP access.

• Sending fails on port 25

  Port 25 is for server-to-server relay. Many ISPs and networks block it for customers (Xfinity doesn't support it for sending, and Microsoft notes ISPs often block it). Use 587 or 465 as your provider documents. (Microsoft Learn)

• A firewall, VPN or antivirus blocks the connection

  Corporate networks, hotel Wi-Fi, VPNs and some antivirus "mail shields" block or intercept ports 465, 587 and 993. Try another network or turn off mail scanning briefly to see whether it's the cause. This is general advice, not specific to any provider.

• Too many simultaneous connections

  Gmail allows up to 15 email clients at a time per account. Close or sign out of apps you no longer use. (Gmail Help)

Still stuck? Test the outgoing server with the SMTP Tester and check where the domain's mail goes with the MX Record Lookup.

IMAP, POP3 and SMTP settings for every provider

Every value comes from the provider's own help page (GoDaddy: its own autodiscover service), checked November 1, 2026. Providers change their settings, so follow the source link if something doesn't connect.

Custom domains are matched by MX record: smtp.google.com, aspmx.l.google.com and other legacy aspmx hosts (Google Workspace); *.mail.protection.outlook.com (Microsoft 365 / Exchange Online); mx.zoho.*, mx2.zoho.*, mx3.zoho.* (Zoho Mail (paid organization)); *.messagingengine.com (Fastmail); *.privateemail.com (Namecheap Private Email); mx1.hostinger.com, mx2.hostinger.com (Hostinger Email); *.secureserver.net (GoDaddy Professional Email); *.yahoodns.net (Yahoo Mail). Not covered: Bluehost (its help site blocked our checks).

How to find and use your IMAP and SMTP settings

1. 1

   Enter your email or pick a provider

   Type your email address or domain and select Find settings, or choose your provider from the list. Well-known providers resolve instantly; for a custom domain the tool looks up its MX records.

2. 2

   Copy the IMAP, POP and SMTP settings

   Copy each host and port, or copy all settings at once. Check the username format, password type and anything you must turn on first.

3. 3

   Add them to your mail app

   In Outlook, Apple Mail, the Gmail app or Thunderbird, add the account and enter the settings manually if the app can't detect them.

4. 4

   Test the connection

   If sending fails, check the server, port and encryption with the free SMTP Tester before changing anything else.

Frequently asked questions

Sources: Google for Developers: IMAP, POP, and SMTP, Microsoft Support: POP, IMAP, and SMTP settings for Outlook.com, Microsoft Learn: POP3 and IMAP4 in Exchange Online, RFC 8314: Use of TLS for Email Submission and Access. Checked November 1, 2026.

Related tools

Browse all free email tools