yes, you can. But there's a better way to set things up — and understanding the difference could save you a headache down the line.
Let's break it down.
When you add an email account to a mail client like Outlook, Apple Mail, or Thunderbird, you're asked for incoming and outgoing server details. Most people just type something in, hit connect, and move on. Fair enough — if it works, it works.
But behind the scenes, those hostnames are doing real work. They're telling your mail client exactly which server to talk to, and when it comes to reliability at scale, that detail matters more than you'd think.
For the best experience, here's what to use:
Incoming mail (IMAP): imap.yourdomain.com
Outgoing mail (SMTP): smtp.yourdomain.com
The reason is straightforward. Each service runs on its own dedicated hostname. That setup is intentional — it's built for scale and redundancy. If one service ever needs maintenance or experiences a hiccup, the separation means it doesn't drag everything else down with it.
Using the specific IMAP and SMTP hostnames means your mail client is always talking to the right server, directly — no detours, no ambiguity.
Here's the thing — mail.yourdomain.com does work. We automatically set it up for every package, so it's not like you'll hit a dead end using it.
It exists primarily for two reasons:
Compatibility — Some older mail clients or setups expect a mail. address and don't play nicely with anything else. Rather than leaving those users stuck, we keep mail. available as a fallback.
Easier migrations — If you're moving from another provider, you might already have mail.yourdomain.com baked into your existing client settings. Being able to keep that in place (at least temporarily) means one less thing to change during what's often an already-fiddly process.
So it's a convenience option — useful in specific situations, but not the setup we'd point you to from scratch.
If you're configuring a mail client fresh, use the specific hostnames:
Setting | Hostname |
|---|---|
Incoming (IMAP) |
|
Outgoing (SMTP) |
|
If you're migrating from somewhere else and already have mail.yourdomain.com set up, it'll keep working — but at some point it's worth updating to the dedicated hostnames for the cleanest long-term setup.
If you're ever unsure which settings to use, check the documentation or support pages for your specific hosting package. The exact hostnames can vary slightly depending on your setup, and using the right ones from the start is always easier than troubleshooting connection issues later.
Getting this right once means your mail client just quietly does its job — which is exactly how it should be.
mail.yourdomain.com works, but imap.yourdomain.com and smtp.yourdomain.com are the smarter, more reliable choice for anyone setting things up fresh. When in doubt, go specific.