How to create a mailbox in Mozilla Thunderbird and Microsoft Outlook
Mozilla Thunderbird and Microsoft Outlook are two of the most widely used desktop email clients for working with a professional mailbox (for example, info@your-domain.com) outside of webmail. When configured correctly, they give you reliable synchronization, offline access, fast search, and better day-to-day productivity. In this guide you’ll learn how to add the same mailbox in both clients, how to choose IMAP vs POP3, how to set up secure SMTP sending, and what to check when something fails.
Before you start, confirm that the mailbox already exists on the server (for example in cPanel, VestaCP, ISPmanager, or another control panel) and that you have the correct connection details: full email address as the username, mailbox password, incoming server hostname (IMAP/POP3), outgoing server hostname (SMTP), ports, and encryption methods. If you are still choosing where to host your website and email, a common starting point is Hosting. For secure TLS connections and avoiding certificate warnings, proper certificates matter; you can use SSL Certificates. For teams that need shared calendars, contacts, and collaboration features in addition to email, consider Zimbra Collaboration Suite.
In most modern business scenarios, IMAP is the recommended choice. IMAP keeps messages on the server and synchronizes folders, read/unread state, and message moves across devices. POP3 is usually used for a single-device workflow or for “download and archive” use cases; depending on settings it may remove mail from the server, which can create confusion when you later open webmail or another device.
1) The settings you need (IMAP/POP3 and SMTP)
You will configure two things: incoming mail and outgoing mail. For incoming mail, use IMAP over SSL/TLS (commonly port 993) or POP3 over SSL/TLS (commonly port 995). For outgoing mail, use authenticated SMTP: either SMTPS (port 465) or Submission with STARTTLS (port 587). In both cases, SMTP must require authentication, and the username is typically your full email address.
The server hostname is often mail.your-domain.com. If your provider has given you a specific host (for example, srv123.cloudhosting.lv), use that value. Avoid using an IP address in client settings because the TLS certificate usually does not match the IP, which triggers warnings. Use the hostname that is covered by the certificate whenever possible.
Also keep in mind that “client settings” and “mail delivery” are different layers. Even if Outlook/Thunderbird connects successfully, your domain still needs correct MX records for mail to arrive. If you can log in but you are not receiving messages, MX records and DNS propagation are a more likely culprit than your desktop client configuration.
2) Mozilla Thunderbird: adding the mailbox (IMAP recommended)
Open Thunderbird and choose “Set up an account” → “Email” (or go to Account Settings and add a new account). Enter your display name, email address, and password. Thunderbird will try to discover settings automatically. If it succeeds, verify that it selected IMAP (not POP3 unless you specifically want POP3) and that the connection security is SSL/TLS.
If automatic discovery is incorrect or incomplete, click “Manual config” and enter values manually: Incoming — IMAP, server mail.your-domain.com, port 993, SSL/TLS; Authentication — Normal password; Username — full email address. Outgoing — SMTP, server mail.your-domain.com, port 465 with SSL/TLS or port 587 with STARTTLS. Save the configuration, then send a test email to an external address and reply back to yourself to validate both sending and receiving.
Thunderbird also lets you control folder behavior. If you notice that sent messages don’t appear where you expect, open “Copies & Folders” and set which folder should store Sent, Drafts, and Trash on the server. Another practical step is “Subscribe” to folders (especially for shared folders). Small folder mismatches are a common reason users think email “disappeared”, when it actually landed in a different server folder.
3) Microsoft Outlook: adding the account and Advanced setup
In Outlook (Microsoft 365 or Outlook 2019/2021), go to “File” → “Add Account” and enter the email address. Outlook may auto-detect the server settings. If it fails or selects the wrong type, choose “Advanced options” → “Let me set up my account manually” and select IMAP.
Use these typical values: Incoming mail server — mail.your-domain.com, port 993, encryption — SSL/TLS. Outgoing mail server (SMTP) — mail.your-domain.com, port 587 with STARTTLS or port 465 with SSL/TLS. Crucially, enable “My outgoing server (SMTP) requires authentication” and select “Use same settings as my incoming mail server”. If you skip this, sending often fails even though receiving works.
Outlook can cache credentials aggressively. If you changed the mailbox password on the server but Outlook keeps prompting or failing, open Windows Credential Manager, remove stored credentials related to that mailbox, and try again. This quick reset solves many “it worked yesterday” cases.
4) TLS, certificates, and avoiding security warnings
Certificate warnings typically happen for three reasons: you used a hostname that is not listed on the certificate, the certificate is expired or the chain is incomplete, or you selected an encryption mode that doesn’t match the port. The most reliable fix is to use the exact hostname your provider recommends (often mail.your-domain.com) and ensure the server uses a valid TLS certificate that covers mail/webmail hostnames.
Avoid blindly “accept permanently” when you do not understand the warning. Permanent exceptions can hide real man-in-the-middle risks. If you see a warning, check the certificate name, validity dates, and issuer. Once the server certificate is correct, clients usually stop warning immediately.
5) Troubleshooting: what to check when email doesn’t work
If login fails, start with the basics: correct password (no extra spaces), correct username (full email address), correct ports, and correct encryption. “Authentication failed” usually means wrong credentials or a locked mailbox. “Cannot connect” usually means a network/firewall problem or the wrong server hostname.
If you can receive mail but cannot send, focus on SMTP: authentication enabled, correct port (465 or 587), and correct encryption. Client-side sending should not use port 25. Some networks block port 25 entirely; submission ports are designed for client sending and are more reliable. If mail sends but lands in spam, that is typically not a client issue—check SPF/DKIM/DMARC and the sending IP reputation.
For a quick deliverability sanity check, send a message to Gmail and open the message headers (“Show original”). You can see whether TLS was used, whether DKIM passed, and what SPF result was returned. Even though this article is about configuring clients, the header view quickly tells you whether the problem is on the client, server, or DNS layer.
Quick checklist and practical recommendations
After setup, run three tests: (1) send an email to an external address, (2) receive a reply, (3) confirm synchronization on a second device. With IMAP, folders and read/unread state should match across devices. Also confirm your Sent/Trash folder mapping to avoid duplicates or “missing” sent mail across clients.
For business usage, keep things tidy: use unique strong passwords, enable two-factor authentication if your email solution supports it, and avoid sharing one mailbox password with multiple people. If several people must work from one address, consider shared mailbox workflows or collaboration suites with calendars and contacts instead of credential sharing. Finally, keep your software updated—Thunderbird and Outlook updates often include security fixes that directly affect email authentication and encryption.