How to Set Up Mailboxes on Your Domain

Published on July 29, 2026

A new domain email address should take minutes, not a late-night investigation into DNS records and forgotten passwords. Yet mail is one of those services where a small missing setting can stop messages from arriving, send them to spam, or leave a team unable to reply when it matters.

This practical guide explains how to set up mailboxes for a domain, from choosing the right addresses to verifying delivery. The exact screen labels vary between hosting platforms, but the sequence stays the same: create the mailbox, point your domain to the mail service, secure sending, and connect the devices your team actually uses.

Before You Set Up Mailboxes, Make Three Decisions

Start with the mailbox plan, not the control panel. Decide which addresses need their own inboxes and which ones should simply forward messages to someone else.

A real mailbox has its own login, storage, and inbox. Addresses such as `jane@yourdomain.com`, `support@yourdomain.com`, and `billing@yourdomain.com` often need this because more than one person may use them, or because messages need to remain available after a staff change.

An alias or forwarder receives mail at one address and sends it to another inbox. For example, `hello@yourdomain.com` can forward to `jane@yourdomain.com`. This is useful for a small business that needs a public-facing address without maintaining another inbox. Be careful with forwarding, though: it can complicate spam filtering and makes shared access harder to manage as the business grows.

Also decide where your email will be hosted. You can use the mail service included with your server control panel, a dedicated business email provider, or a hosted service from your web host. There is no universal winner. Hosting mail on the same server can simplify management and keep services in one place. A separate provider may be a better fit for larger teams, strict compliance needs, or organizations that need advanced collaboration tools.

1. Create the Mailbox and Set a Strong Password

In your hosting or server panel, select the domain and open the Mail section. Choose the option to add a mailbox, then enter the mailbox name, such as `sales`, and create a password.

Use a long, unique password generated by a password manager. Email accounts are high-value targets because password reset links, invoices, client conversations, and access requests all tend to pass through them. A familiar password with an extra exclamation point is not a security plan.

Set a storage quota if your platform supports it. For a single user, a few gigabytes may be enough. Shared mailboxes and accounts that receive attachments may need more room. The right number depends on your retention habits, but unlimited storage is rarely a reason to stop thinking about cleanup and backups.

If you are creating addresses for a team, avoid sharing one password across several people. Give each user an individual mailbox whenever possible. For a shared function such as support, use delegated access, a shared mailbox feature, or a ticketing system if available. That preserves accountability and makes offboarding much less dramatic.

2. Configure the DNS Records That Route Email

Creating a mailbox does not automatically tell the internet where to deliver email. That job belongs to DNS. If your domain’s DNS is managed outside the mail host, you will need to add the records there.

MX records

MX, or Mail Exchange, records tell sending servers which mail server accepts email for your domain. Your mail provider will give you a hostname and priority value. Enter them exactly as provided.

Remove old MX records that point to a previous mail service unless your provider specifically instructs you to keep them. Conflicting MX records are a common reason messages land in the wrong place or disappear into an inbox nobody checks.

SPF, DKIM, and DMARC records

MX records handle incoming mail. SPF, DKIM, and DMARC help prove that outgoing mail is legitimate. They are not optional extras for a business domain anymore. Without them, messages are more likely to be filtered, rejected, or treated with suspicion.

SPF is a TXT record that lists the services allowed to send mail for your domain. It must include every legitimate sender, which may include your mail host, website forms, CRM, invoicing platform, and marketing tool. You should have one SPF record per domain. Adding multiple SPF TXT records is a surprisingly effective way to create a problem.

DKIM adds a cryptographic signature to outgoing email. Your provider generates the record, usually as a selector and a long public key. Add it to DNS, then enable DKIM in the mail service if that is a separate step.

DMARC tells receiving servers what to do when SPF or DKIM checks fail. Start with a monitoring policy, such as `p=none`, while you confirm that all valid sending services are aligned. Once reports show that legitimate mail is passing correctly, move toward a stricter policy. A rushed `p=reject` setting can block your own invoice emails just as efficiently as it blocks spoofing.

DNS changes may apply quickly, but full propagation can take several hours and occasionally up to 24 to 48 hours. Plan for that delay when moving email from another provider. Do not cancel the old service until you have tested delivery at the new one.

3. Connect Webmail and Email Apps

Once the mailbox exists and MX records point to the correct service, sign in through webmail first. Send a test message to a personal address and reply back. This confirms that the account works before you introduce a phone, desktop app, and another layer of settings.

To use Outlook, Apple Mail, Thunderbird, or a mobile email app, you will need the incoming and outgoing server names, port numbers, encryption type, and your full email address as the username. Most modern setups use IMAP for incoming mail and SMTP for outgoing mail with SSL/TLS encryption.

Choose IMAP rather than POP unless you have a specific archival workflow. IMAP keeps email synchronized across webmail, laptops, and phones. POP downloads messages to one device and can create confusion when a user expects a message to appear everywhere.

For outgoing mail, enable SMTP authentication. This means the app must log in before sending. It reduces abuse and prevents a server from becoming an open relay, which is the kind of configuration mistake that gets a mail server blacklisted very quickly.

If the app offers automatic configuration, use it first. If it fails, enter the provider’s settings manually rather than guessing. One incorrect server name or security setting is enough to make an otherwise healthy mailbox look broken.

4. Test Delivery Before You Hand It to the Team

A mailbox is not ready because the creation screen said “success.” Test the full route.

Send messages from the new address to Gmail, Outlook.com, and another external provider if possible. Then send mail back to the new address. Check the inbox, spam folder, and any quarantine area in the mail panel. Test an attachment and a reply from each device your team plans to use.

Review the message headers or your mail provider’s delivery logs if anything fails. A rejected message often contains the real reason: an MX record still points elsewhere, SPF does not authorize the sending server, DKIM is missing, or the recipient rejects the connection. Reading the error is faster than trying random settings until something changes.

If you are moving from an existing email provider, keep the old mailbox active during the transition. Copy historical email if needed, update DNS, test both directions, and only then retire the previous service. Email migrations reward patience. A few hours of overlap costs less than a missed customer request.

Everyday Practices That Keep Mailboxes Healthy

Mailbox setup is the first part. Keeping email dependable takes a small amount of routine care. Review accounts when employees or contractors leave, remove old forwarders, and rotate passwords if you suspect an account has been exposed. Enable two-factor authentication where your mail platform supports it.

Watch storage use, delivery errors, and spam complaints. A sudden wave of bounced messages can indicate a DNS change, a compromised mailbox, or an application sending from an address it was never authorized to use.

For server-based email, monitoring also matters. Low disk space, expired SSL certificates, and blocked outbound ports can all affect mail delivery. A panel such as FASTPANEL gives you a clearer place to manage domains, mailboxes, and server health without turning every routine check into a command-line expedition.

The goal is not to make email complicated. It is to give your business an address people trust, an inbox your team can use from anywhere, and a setup you can still understand six months from now when someone asks, very reasonably, why mail is not arriving.