Thunderbird Won't Connect to Server
1. Read the exact error message
Thunderbird's error dialogs are usually pretty specific once you actually read them — "Connection timed out," "Login failed," and "Certificate error" each point somewhere different below.
2. "Login failed" — check your password and app password
If your provider has two-factor authentication on, Thunderbird needs an app password, not your normal login one. Generate it from your provider's security settings and use that instead — this is the fix I reach for first, honestly.
Connecting to an Outlook.com or Microsoft 365 account specifically? Microsoft has been requiring OAuth2 authentication for these rather than a plain saved password, and older Thunderbird setups using the outdated imap-mail.outlook.com server address don't support it. Two things to check: the incoming/outgoing server address should be outlook.office365.com (not the old one), and the authentication method in Server Settings should be set to OAuth2 rather than "Normal password." Once both match, Thunderbird will prompt you to sign in and grant access, and it should hold from there.
3. "Connection timed out" — verify server settings
- Account Settings → Server Settings (incoming) and Outgoing Server (SMTP).
- Confirm the address, port, and connection security match your provider's current documentation. Common combinations:
- IMAP: port 993, SSL/TLS
- SMTP: port 465 (SSL/TLS) or 587 (STARTTLS)
4. "Certificate error"
- Double-check the server hostname is typed exactly right — a typo here is the most common cause I've seen.
- On a work or school network, a firewall or antivirus might be intercepting the connection. Try a different network to confirm.
5. Re-run the account setup wizard
- Account Settings → Account Actions → Add Mail Account, or remove and re-add the existing one.
- Let Thunderbird auto-detect settings where it can, rather than entering everything manually.
6. Check for a provider-side outage
If the same account works fine in a browser but not Thunderbird, it's almost always the server settings, not an actual outage.