Skip to main content
When connecting your mailbox in a third-party email client (Outlook, Apple Mail, Thunderbird, etc.) or a custom app, you typically need IMAP (incoming) and SMTP (outgoing) server details, plus an app password or authorization code—not your web login password.
Most major email providers require two-factor authentication (2FA) before you can generate an app password. Enable 2FA in your account security settings first, then follow the guide for your provider.

​
Key concepts

​
Browse by provider

Gmail / Google

App passwords and IMAP/SMTP settings

Outlook / Microsoft

Microsoft app passwords and server settings

Yahoo Mail

Yahoo app passwords and IMAP/SMTP

iCloud Mail

Apple app-specific password setup

AOL Mail

AOL app passwords and server settings

Zoho Mail

Zoho app passwords and IMAP/SMTP

QQ Mail

Authorization codes and server settings

NetEase 163 / 126

Authorization codes and IMAP/SMTP

Proton Mail

Bridge and paid IMAP options

​
Quick reference

​
FAQ

Confirm you are using an app password or authorization code, not your web login password. For Gmail, verify IMAP is enabled in the web settings. For QQ/163, regenerate the authorization code if it expired or after re-enabling the service.
Check that the SMTP port matches the encryption method (465 for SSL, 587 for STARTTLS). Some networks block ports 465/587—try switching ports or networks.
You must enable two-step verification first. Google Workspace admins may disable this feature. Some account types that sign in only through Google do not support app passwords.
Enterprise Microsoft 365 may disable basic authentication. Use an OAuth-capable client, or ask your IT admin to enable SMTP AUTH if policy allows.
After setup, test both incoming (IMAP) and outgoing (SMTP) once in your client before using the account in production or automation.