Setting up email hosting
Create mailboxes, connect a client, and get the MX and authentication records right.
Create a mailbox
In /panel/domains → Email, add a mailbox on a domain you host. You set the local part (you@), a strong password, and a quota. Then send yourself a test message.
Point the domain's mail at us
Add or update the MX record:
example.com. MX 10 mail.example.com.Before switching MX away from another provider, export your existing mail — MX changes only affect new delivery, not what is already in the old mailboxes.
Client settings
| Protocol | Port | Security |
|---|---|---|
| IMAP | 993 | SSL/TLS |
| IMAP | 143 | STARTTLS |
| SMTP submission | 465 | SSL/TLS |
| SMTP submission | 587 | STARTTLS |
Use the full email address as the username. Prefer 993/465 (implicit TLS) where offered. Never use port 25 for submission — it is for server-to-server delivery and most networks block it.
Do not forget authentication
Configure SPF, DKIM and DMARC before you start sending volume. Without them, a large fraction of your mail is treated as suspicious.
Also set reverse DNS (PTR) for your sending IP to match your mail hostname. Many receivers require this.
Autodiscover / autoconfig
Publish autoconfig/autodiscover records (or the standard well-known files) so mail clients configure themselves. It saves every user a support call.
What "email hosting" does and does not include
Includes: mailboxes, IMAP/SMTP access, spam filtering, authentication records, quotas.
Does not include: guaranteed inbox placement. Deliverability is a shared responsibility — reputation, authentication, list hygiene and content all matter. See Email deliverability troubleshooting.
Related reading