IMAP and SMTP Settings by Email Provider: Ports, Encryption, and Authentication Guide
IMAPSMTPwebmailemail setupmail serverstroubleshooting

IMAP and SMTP Settings by Email Provider: Ports, Encryption, and Authentication Guide

WWebmails Live Editorial Team
2026-11-12
7 min read

A practical IMAP and SMTP settings checklist for ports, encryption, authentication, provider setup, and email troubleshooting.

Use this reusable checklist to configure IMAP and SMTP for common email providers, choose the right ports and encryption, understand authentication requirements, and troubleshoot sending or receiving problems without guessing at mail server settings.

Overview

When you add an account to a phone, desktop mail client, ticketing system, or business workflow, you usually need two types of settings. IMAP controls incoming mail synchronization: it lets an application view folders and messages stored on the mail server. SMTP controls outgoing mail: it submits messages for delivery through the provider’s sending server.

The correct configuration depends on the provider, the type of account, the domain owner’s policy, and the application being used. A personal mailbox and a company mailbox using the same domain may have different server names or authentication rules. Treat the values below as a starting reference, then confirm them against the provider’s current documentation or your organization’s administrator instructions.

Provider or account typeIncoming mail (IMAP)Outgoing mail (SMTP)Authentication notes
Gmailimap.gmail.com; commonly port 993 with SSL/TLSsmtp.gmail.com; commonly port 465 with SSL/TLS or 587 with STARTTLSUse the account sign-in method supported by Google. An app password may be required when two-step verification and an app-specific password flow are enabled.
Outlook.com or Microsoft consumer mailimap-mail.outlook.com; commonly port 993 with SSL/TLSsmtp-mail.outlook.com; commonly port 587 with STARTTLSUse the Microsoft account authentication method supported by the client and account.
Yahoo Mailimap.mail.yahoo.com; commonly port 993 with SSL/TLSsmtp.mail.yahoo.com; commonly port 465 with SSL/TLS or 587 with STARTTLSSome clients require a generated app password rather than the normal account password.
iCloud Mailimap.mail.me.com; commonly port 993 with SSL/TLSsmtp.mail.me.com; commonly port 587 with STARTTLSAn app-specific password is commonly used for third-party mail clients when account security settings require it.
Zoho MailUse the IMAP server listed for your Zoho account or organization; commonly port 993 with SSL/TLSUse the SMTP server listed for your account; commonly port 465 with SSL/TLS or 587 with STARTTLSOrganization policies, data-center region, and multi-factor authentication can affect the required credentials.
cPanel or other hosted domain mailOften mail.example.com; commonly port 993 with SSL/TLSOften mail.example.com; commonly port 465 with SSL/TLS or 587 with STARTTLSUse the complete mailbox address as the username unless the hosting provider specifies another format. Confirm the hostname in cPanel or the host’s setup guide.

Port numbers are not interchangeable with encryption choices. Port 993 is generally associated with IMAP over an encrypted connection. SMTP port 465 is commonly used for an encrypted connection established immediately, while port 587 is commonly used with STARTTLS. A client may label these options as “SSL/TLS,” “STARTTLS,” or “TLS,” so read the wording carefully rather than selecting a port at random.

Checklist by scenario

Setting up a new phone or desktop mail client

  1. Record the complete email address and confirm that you can sign in through the provider’s webmail login page.
  2. Choose manual setup when automatic discovery selects the wrong account type or server.
  3. Enter the provider’s IMAP hostname, port 993 where applicable, and the required SSL/TLS option.
  4. Enter the provider’s SMTP hostname and the recommended encrypted port, usually 465 or 587 depending on the connection type.
  5. Enable SMTP authentication and use the same mailbox identity unless the administrator gives you a separate sending account.
  6. Save the settings, then test both directions: receive a new message and send a reply to an address you can check.

Configuring a business or custom-domain mailbox

Do not assume that a custom address uses Gmail, Microsoft, or cPanel servers simply because the mailbox is accessed through a familiar-looking interface. Identify the actual mail host first. Check the hosting control panel, onboarding documentation, DNS records, or the administrator’s approved configuration. Some organizations disable IMAP, require a managed application, or use a separate outbound relay for business email setup.

For a shared mailbox, help desk, or automated workflow, clarify whether the account is permitted to authenticate through SMTP. Document the sender address, relay hostname, port, encryption mode, authentication identity, and any sending restrictions. Keep credentials out of scripts, screenshots, and shared notes.

Replacing an expired password or app password

First test the normal webmail login. If webmail works but the mail client fails, the client may contain an old password, a revoked app password, or an authentication method the provider no longer accepts. Generate a replacement credential only through the provider’s account-security area, update every approved device, and remove the old credential from the client. If the account uses multi-factor authentication, do not disable it merely to make an older mail application work.

Troubleshooting sending or receiving

Separate the problem into incoming and outgoing tests. If messages are not arriving, inspect the IMAP hostname, port, encryption, folder synchronization, mailbox storage, and server-side filters. If messages remain in the outbox, inspect the SMTP hostname, port, authentication checkbox, sender address, and network restrictions. A successful webmail login proves that the account is active, but it does not prove that third-party IMAP or SMTP access is enabled.

What to double-check

  • Username format: The username is often the full email address, not only the text before the at sign. Hosted mail systems can vary.
  • Encryption mode: Match SSL/TLS or STARTTLS to the provider’s instructions. Avoid unencrypted connections unless an administrator explicitly requires one on a trusted internal network.
  • SMTP authentication: Receiving mail successfully does not automatically authenticate outgoing mail. Look for a separate “Outgoing server requires authentication” setting.
  • Provider policy: Modern accounts may require OAuth, an app password, or an administrator-approved application. A normal password may be rejected even when it is correct.
  • Account type: Confirm whether the address is a personal mailbox, an organization-managed account, an alias, a forwarding address, or a shared mailbox. These may not support identical sign-in behavior.
  • Certificate and hostname matching: Use the exact server hostname supplied by the provider. Substituting an IP address or an unrelated domain can produce certificate warnings and connection failures.
  • Network access: A workplace firewall, VPN, mobile carrier, or security product may block or inspect mail connections. Test from an approved network before changing server settings.

For related account protection work, review the webmail two-factor authentication and passkeys checklist. If the issue is broader than mail-client configuration, use the email troubleshooting checklist for login, sending, receiving, and sync diagnostics.

Common mistakes

A frequent error is entering the webmail address as both the incoming and outgoing server. Some providers do use a shared hostname, but many do not. Another is choosing port 465 with STARTTLS or port 587 with an “SSL on connect” option when the client expects different encryption behavior. Read the client’s labels and provider instructions together.

Users also commonly test only incoming mail. SMTP can fail independently because of a disabled authentication option, a sender address mismatch, a blocked port, or an expired app password. Always send a test message after receiving one.

Do not copy settings from an old device without checking them. Providers change authentication requirements, and old clients may retain credentials that should no longer be used. Avoid repeatedly guessing passwords: multiple failed attempts can trigger account security controls, and storing credentials in plain text creates a separate security risk.

When to revisit

Return to this checklist whenever you configure a new device, migrate a mailbox, change a domain host, replace an app password, enable stronger account security, or move from personal to organization-managed email. Recheck the provider’s official settings when a client update changes its setup screens, when webmail works but synchronization fails, or when sending and receiving stop at the same time.

For administrators, review documented mail server settings before seasonal planning cycles, onboarding periods, and device refreshes. Keep a dated internal record of approved hostnames, ports, encryption modes, and authentication methods, but do not store active passwords in that record. If a provider changes its documentation or authentication policy, update the record and retest a clean account configuration.

Before closing an incident, complete this final sequence: verify webmail access, confirm IMAP synchronization, send an authenticated SMTP test, receive the reply on the configured device, check the spam folder, and record the exact error if any step fails. This creates a useful handoff for support and avoids changing several settings at once.

For account-security reviews, see the webmail security audit and incident response checklist. When you need provider access or password-reset guidance rather than mail-client settings, use the webmail login help center.

Related Topics

#IMAP#SMTP#webmail#email setup#mail servers#troubleshooting
W

Webmails Live Editorial Team

Technology Editors

Senior editor and content strategist. Writing about technology, design, and the future of digital media. Follow along for deep dives into the industry's moving parts.