You are setting up email on a new phone, computer, or app, and it asks for things like IMAP server, port, and security type. Guessing these details almost never works. One wrong number and the app refuses to connect, leaving you with a vague error and no mail.
Every email provider publishes exact settings for its service, and finding them is a skill worth learning once. The same approach works for Gmail, Outlook.com, Yahoo, a work account, or email that comes with your website hosting. This guide shows you where to look, what the settings mean, and how to test them.
Quick Answer
Find your provider’s official settings page by searching its help site for IMAP settings, or check the settings inside webmail under Forwarding and POP/IMAP. For most providers the incoming IMAP server uses port 993 with SSL/TLS, and the outgoing SMTP server uses port 587 with STARTTLS or port 465 with SSL/TLS. Always copy the server names exactly as the provider lists them for your account.
What IMAP Server and Port Settings Actually Mean
The IMAP server is the address of the computer that stores your mailbox and delivers it to your apps. It looks like a normal web-style address, for example imap.gmail.com or outlook.office365.com. Your email app connects to this server to read, search, and organise your mail.
The port is the numbered channel the app uses on that server. For IMAP, port 993 is the standard secure port. The older port 143 is still seen sometimes, usually with STARTTLS encryption, but most modern providers prefer 993.
You also need outgoing settings. Sending uses SMTP, a different service with its own server and port. Common SMTP ports are 587, the modern standard with STARTTLS, and 465, used with SSL/TLS. Entering IMAP details correctly but SMTP details wrongly is a frequent reason why people can receive mail but cannot send it.
Finally, the security type tells the app how to encrypt the connection. SSL/TLS and STARTTLS are the two labels you will meet. Match the security type to the port exactly as your provider instructs, because the wrong pairing fails even when the server name is right.
Method 1: Find Settings on Your Provider’s Official Help Pages
This is the most reliable method and should always be your first choice.
- Search the web for your provider’s name plus the words IMAP settings, for example Gmail IMAP settings or Yahoo Mail IMAP settings.
- Open the result from the provider’s own support domain, not a random blog or forum.
- Write down the full details: IMAP server, IMAP port, security type, SMTP server, SMTP port, and whether a full email address is required as the username.
- Check whether the provider requires IMAP to be switched on first, or an app password if you use two-step verification.
Official pages stay updated when servers change. Third-party lists go stale quickly, and an old server name copied from an outdated article is a common cause of setup failure. Microsoft publishes its details on the Microsoft Support page for Outlook.com POP, IMAP, and SMTP settings, and Google does the same for Gmail accounts that use IMAP in other apps.
Method 2: Find Settings Inside Your Webmail
Many providers show the exact settings inside your account, which is ideal because they reflect your specific account type.
- Log in to your email on the provider’s website.
- Open Settings and look for sections named Forwarding and POP/IMAP, Accounts, or Mail settings.
- Confirm IMAP access is enabled. Some services, including Gmail, let you turn IMAP off, and no app will connect while it is disabled.
- Look for a link or panel describing how to set up other email clients. Providers often list the servers and ports there.
For business and website hosting email, log in to your hosting control panel instead. Under email accounts, there is usually a Connect Devices or Configure Mail Client option that displays the exact secure and non-secure settings for your domain, plus an option to download ready-made setup files for some apps.
Method 3: Use Your Email App’s Automatic Lookup
Modern apps try to discover settings for you. When you add an account in Outlook, Thunderbird, Apple Mail, or a phone app, the app checks a database and the provider’s published records, then fills in the servers and ports automatically.
Let automatic setup run first. It succeeds for most major providers. If it fails or fills in a server name you do not recognise, switch to manual setup and enter the official details you found with the first two methods. Thunderbird, for example, shows you the settings it discovered and lets you edit them before finishing, which is a good moment to compare them against the provider’s page.
If you are moving between protocols as well, our overview of how to set up email correctly on a new phone or computer walks through the full account setup process step by step.
Common IMAP and SMTP Settings for Well-Known Providers
The table below gives a quick reference for major free providers. Treat it as a starting point and still verify on the official page, because providers can update their systems.
- Gmail: IMAP server imap.gmail.com, port 993, SSL/TLS. SMTP server smtp.gmail.com, port 587 with STARTTLS or 465 with SSL/TLS. IMAP must be enabled in Gmail settings, and many accounts need an app password or secure sign-in approval.
- Outlook.com: IMAP server outlook.office365.com, port 993, SSL/TLS. SMTP server smtp-mail.outlook.com, port 587 with STARTTLS.
- Yahoo Mail: IMAP server imap.mail.yahoo.com, port 993, SSL/TLS. SMTP server smtp.mail.yahoo.com, port 465 or 587. Yahoo often requires an app password for external apps.
- iCloud Mail: IMAP server imap.mail.me.com, port 993, SSL/TLS. SMTP server smtp.mail.me.com, port 587. An app-specific password is required if you use two-factor authentication.
- Website and hosting email: Often mail.yourdomain.com for both IMAP and SMTP, with IMAP port 993 and SMTP port 465 or 587. Confirm in your hosting panel, because shared hosts vary.
Checking Usernames, Passwords, and App Passwords
Correct servers still fail with the wrong username format. Most providers want your full email address as the username, not just the part before the @ sign. If setup fails with a password error, check this first.
If your account uses two-step verification, your normal password may not work in email apps. Gmail, Yahoo, iCloud, and Microsoft accounts may require an app password — a special password generated in your account security settings for use in one app. Create it on the provider’s website, then use it in the app instead of your usual password. Keep your main password private and never enter it into a site that only looks like your provider.
How to Test and Troubleshoot Your Settings
- Double-check spelling. Server names have no spaces and must match exactly, including dots.
- Match each port with its correct security type: 993 with SSL/TLS for IMAP, 587 with STARTTLS for SMTP in most setups.
- Try receiving before sending. If receiving works and sending fails, the problem is in the SMTP section, including whether outgoing authentication is switched on.
- Make sure outgoing authentication uses the same username and password as incoming mail, unless your provider says otherwise.
- Temporarily check whether a firewall, workplace network, or hotel Wi-Fi blocks mail ports. Try again on your home connection or mobile data.
Error messages help if you read them closely. Authentication failed points to username, password, or app password problems. Connection timed out or server not found points to a wrong server name, wrong port, or a blocked network. Certificate errors suggest the security type does not match.
Common Mistakes to Avoid
- Copying settings from an old forum post: Providers retire servers. Always use the current official page.
- Mixing up IMAP and POP3 details: POP3 uses different ports, commonly 995. Entering POP3 numbers into an IMAP setup will fail.
- Using port 25 for sending: Most home internet providers block port 25. Use 587 or 465 as your provider directs.
- Forgetting to enable IMAP: If IMAP is off in webmail settings, even perfect app settings cannot connect.
- Typing your name instead of your full email address as the username: A very common and easily missed error.
- Ignoring app passwords: Repeatedly retyping your main password will not help if the provider requires an app password.
Conclusion
Finding your email provider’s exact IMAP server and port settings is straightforward once you know the reliable sources: the provider’s official help pages, the settings inside your webmail or hosting panel, and your app’s automatic lookup as a backup. For most services, IMAP on port 993 with SSL/TLS and SMTP on port 587 with STARTTLS will be the pattern, but always confirm the server names in writing from the provider itself. With the exact details, a correct full-address username, and an app password where required, account setup normally takes just a few minutes.
Frequently Asked Questions
What is the standard IMAP port for secure email?
Port 993 with SSL/TLS is the standard secure IMAP port used by almost all major providers today. Port 143 appears in older setups and normally needs STARTTLS to encrypt the connection.
Why can I receive email but not send it?
Receiving uses IMAP and sending uses SMTP, so your IMAP details can be right while SMTP details are wrong. Check the SMTP server, port 587 or 465, security type, and that outgoing authentication is turned on.
Where do I find IMAP settings for email on my own domain?
Open your hosting control panel and go to your email account’s setup or Connect Devices section. It lists the exact mail server for your domain, which is often mail followed by your domain name, along with the correct ports.
Do I need an app password to use IMAP?
Only if your provider requires one, which is common when two-step verification is on. Gmail, iCloud, Yahoo, and Microsoft may all ask you to generate an app password in security settings for use in third-party email apps.
My app found settings automatically. Should I still check them?
Yes, a quick comparison with the provider’s official page is worthwhile, especially for business accounts. Automatic lookup is usually accurate for big providers, but manual confirmation prevents subtle errors in security type or SMTP details.


Leave a Reply