Setting Up a New Email Client: A Step-by-Step Guide

How to set up a new email client step by step depends on one question: does your provider support OAuth login, or will you need to configure IMAP manually? For Gmail and Outlook, OAuth is the faster path — click, approve in a browser tab, and your account is linked in under two minutes. For most other accounts — Fastmail, iCloud, Zoho, or a work mailbox running on a custom domain — you will enter server settings by hand.

Either way, you do not need to export or migrate your email archive first. IMAP leaves your mail on the server; the new client downloads what you ask it to show. This guide covers both connection paths for setting up a new email client, the correct server settings for the most common providers, and what to do when the connection refuses to go through.

Before You Start#

Gathering the right information before you open the add-account screen makes setup take two minutes instead of twenty. What you need depends on the authentication method.

For Gmail and Outlook.com, OAuth is the recommended method. You need nothing except your email address and access to the browser tab the client will open. No server addresses, no port numbers, no password stored inside the client.

For IMAP setup — which covers iCloud, Fastmail, Zoho, and any work or school address on a custom domain — you need four things before you start: your provider's IMAP host name, your SMTP host name, the correct port numbers for each, and either your account password or an app-specific password if two-factor authentication is enabled. Most clients attempt auto-detection when you type your address, but having the details in hand is faster than waiting for detection to time out or fail silently.

One detail that catches many people off guard: if your account uses two-factor authentication, your regular login password will not work in an IMAP client. Google, Microsoft, Apple, and Fastmail all require a separate app-specific password for IMAP access. You generate it once in your account's security settings; the password is longer and randomly generated, and it grants only mail access rather than full account access.

• Your email address and account password, or an app-specific password if 2FA is on
• IMAP host name (for example, imap.gmail.com) and port — usually 993 with TLS
• SMTP host name and port for outgoing mail — usually 587 with STARTTLS, or 465 with TLS
• Your display name — the name that appears in recipients' From fields
• Access to your provider's security settings, in case you need to generate an app password or enable IMAP access for your account

Step-by-Step: How to Set Up a New Email Client#

Follow these steps in order. The exact labels vary by client, but the underlying sequence is the same across all of them.

1. 1

   Open the client and navigate to Add Account

   In most clients, this is under Settings or Preferences, sometimes behind a plus icon in the account sidebar or an Accounts item in the menu bar. On a first launch, the add-account screen usually appears automatically. Look for labels such as Add mailbox, Connect account, or Add email address. If the client shows a welcome screen with provider logos, that is the same flow.

2. 2

   Enter your full email address

   Type your complete address and give the client a few seconds to attempt auto-detection. Clients that recognise common provider domains — gmail.com, outlook.com, icloud.com, fastmail.com, and most major providers — fill in server settings automatically and skip the manual entry steps. If detection fails or returns wrong settings, dismiss the result and proceed to enter the settings by hand using the table in the next section.

3. 3

   Choose your authentication method

   For Gmail and Outlook.com accounts, select Sign in with Google or Sign in with Microsoft when the option appears. A browser tab opens, you complete the normal provider login and grant the client permission to read and send mail on your behalf. No password is stored in the client. For all other providers, or for clients that do not offer OAuth, select IMAP and enter credentials manually in the next step.

4. 4

   Enter your IMAP and SMTP settings

   Fill in the incoming server (IMAP host and port) and the outgoing server (SMTP host and port) using the values for your provider from the table below. For the password field: if your account uses two-factor authentication, do not enter your account login password here — enter the app-specific password you generated from your provider's security settings. The error message you see when you enter the wrong kind of password is usually 'invalid credentials' or 'authentication failed', which looks identical to a mistyped password and sends most people to reset their account password unnecessarily.

5. 5

   Map your folders and set your display name

   The client will ask which server folders to use for Sent, Drafts, Trash, and sometimes Archive. Accept the suggested defaults unless your provider uses non-standard folder names. Set your display name to the name recipients should see in the From line. Add a plain-text signature if you want one — plain text is the safest choice across providers and client combinations, since HTML signatures sometimes render inconsistently.

6. 6

   Wait for the initial sync, then send a test message

   The client downloads recent message headers first, so your inbox appears within seconds of a successful connection even before the full archive arrives. Syncing older messages runs in the background and can take anywhere from a few minutes on a small account to a few hours on a large one. Once the inbox loads, send yourself a test message to confirm the SMTP connection is working. Incoming (IMAP) and outgoing (SMTP) can fail independently — a full inbox does not guarantee that outgoing mail is configured correctly.

IMAP and OAuth Settings by Provider#

The settings below are verified against provider documentation as of July 2026. Server addresses and port numbers change rarely, but if a connection fails with a host-not-found or connection-timed-out error, confirm the current values against your provider's own support page before assuming a configuration mistake.

When the Connection Fails#

Most setup failures fall into three categories: wrong credentials, a blocked port, or a restriction the provider has placed on IMAP access at the account level. The error message tells you which — once you know which category you are in, the fix is straightforward.

Authentication errors — 'invalid credentials', 'login failed', 'username or password incorrect' — almost always mean you are entering your account login password where the client needs an app-specific password. Gmail requires this for IMAP when two-step verification is on. So do Microsoft, Apple, and Fastmail. Go to your account's security settings, generate a new app password, label it with the client name so you can revoke it individually later, and use that string in the password field. Do not attempt to reset your account password; that is not the problem.

Timeout or connection-refused errors usually point to a blocked port. Corporate networks and some residential ISPs block port 143 (unencrypted IMAP) and port 25 (unencrypted SMTP). Make sure you are connecting on port 993 for IMAP over TLS and port 587 or 465 for SMTP. If you are on a VPN, disable it and try again — some VPN exit nodes block outbound mail ports to limit spam from their IP ranges.

Gmail-specific: if the connection is refused with a message about access being disabled rather than invalid credentials, IMAP has not been turned on for your account. In Gmail, open Settings, then See all settings, then the Forwarding and POP/IMAP tab, and enable IMAP access. For Google Workspace accounts, this setting lives in the Admin Console under Apps, Google Workspace, Gmail, Advanced settings — your administrator controls it.

A Faster Way: Managing a Busy Inbox After Setup#

Setting up the client is a one-time task. What follows — deciding which of the messages in your inbox actually need a reply, drafting those replies in your own voice, and keeping the inbox from refilling faster than you can work through it — is the daily work that does not go away once the client is configured.

AI Emaily connects to your existing mailbox the same way you just followed: Gmail OAuth, Outlook OAuth, or IMAP credentials. After connecting, it begins triaging incoming mail by priority and surfacing threads that have stalled. Replies are drafted using your user-set Personal Context brain and per-client profiles — not by training on your past mail. Before any reply sends, Copilot mode presents it for your approval. Nothing moves without your sign-off.

We build AI Emaily. A 7-day free trial is available on Pro and Autopilot plans at app.aiemaily.com. Card required; cancel before day 7 and you owe nothing. Your existing archive stays on the server exactly where it is — no migration, no export.