{"id":164,"date":"2026-05-27T15:06:06","date_gmt":"2026-05-27T15:06:06","guid":{"rendered":"https:\/\/blog.offshorekaka.in\/?p=164"},"modified":"2026-08-27T05:43:56","modified_gmt":"2026-08-27T05:43:56","slug":"setup-business-email-on-offshore-hosting","status":"publish","type":"post","link":"https:\/\/offshorekaka.in\/blog\/setup-business-email-on-offshore-hosting\/","title":{"rendered":"How to Set Up Business Email on Offshore Hosting"},"content":{"rendered":"
\n

Tutorial<\/span><\/p>\n

The mailbox is the easy part<\/h2>\n

Creating you@yourdomain.com<\/code> takes about thirty seconds in any hosting panel. Getting that mail to land in someone’s inbox rather than their spam folder is the actual job, and it comes down to three DNS records.<\/p>\n

Without SPF, DKIM and DMARC, Gmail and Outlook treat your mail as unverified, and unverified mail from a new IP goes to spam. This guide covers setting the mailbox up on offshore hosting<\/a> and then getting those records right.<\/p>\n

\n
Time<\/strong>20 minutes plus DNS caching.<\/span><\/div>\n
The hard part<\/strong>Deliverability, not setup.<\/span><\/div>\n
Needed<\/strong>MX, SPF, DKIM. DMARC is worth adding too.<\/span><\/div>\n<\/div>\n<\/div>\n
On this page<\/strong>Where should mail live<\/a>Create the mailbox<\/a>The three records<\/a>Verifying them<\/a>Connecting your mail app<\/a>If mail goes to spam<\/a>FAQ<\/a><\/div>\n

Where should mail live?<\/h2>\n

Worth deciding before you start, because moving later means changing MX records and migrating mailboxes.<\/p>\n

On your hosting<\/strong> is free, included, and fine for a few addresses that mostly receive. The catch is that your server’s IP has no sending reputation, and a shared IP inherits whatever reputation the other sites on it have earned.<\/p>\n

With a mail provider<\/strong> like Zoho, Google Workspace or Microsoft 365 costs a little but gives you IPs that are already trusted, better spam filtering, and mail that keeps working when the web server is being rebuilt.<\/p>\n

There is also a privacy angle. If you use Cloudflare to hide your origin IP, a mail record pointing straight at the same server gives it away, since MX records cannot be proxied. Mail elsewhere closes that gap. Our Cloudflare guide<\/a> covers the proxying side.<\/p>\n

Create the mailbox<\/h2>\n

In cPanel, go to Email Accounts, click Create, choose the address and set a password. In aaPanel the Mail Server plugin does the same thing.<\/p>\n

Use a real password, not a memorable one. A compromised mailbox on your own domain gets used to send spam within hours, and then your domain is the one on the blocklist.<\/p>\n

The three records<\/h2>\n

MX<\/strong> says which server receives mail for your domain:<\/p>\n

Type: MX   Host: @   Value: mail.yourdomain.com   Priority: 10<\/code><\/pre>\n
The priority number is which server to try first, lowest wins. Multiple MX records are for failover, not for load balancing.<\/p>\n
SPF<\/strong> lists who is allowed to send as you:<\/p>\n
Type: TXT   Host: @   Value: v=spf1 a mx ~all<\/code><\/pre>\n
Two rules that catch people out. You may only have one<\/strong> SPF record per domain, so if you use both your host and a newsletter service, combine them into one line rather than adding a second record. And end with ~all<\/code> or -all<\/code>, never +all<\/code>, which tells the world anyone may send as you and defeats the whole point.<\/p>\n
DKIM<\/strong> signs each message cryptographically. Your panel generates the key, usually in the Email Deliverability section in cPanel. Copy the whole value, which is long, and paste it as a TXT record on the selector host the panel gives you, typically default._domainkey<\/code>.<\/p>\n
Then add DMARC<\/strong>, which tells receivers what to do when SPF or DKIM fail, and asks them to report back:<\/p>\n
Type: TXT   Host: _dmarc   Value: v=DMARC1; p=none; rua=mailto:you@yourdomain.com<\/code><\/pre>\n
Start with p=none<\/code>, which changes nothing and just collects reports. Move to p=quarantine<\/code> once the reports show your legitimate mail is passing. Going straight to p=reject<\/code> is how people accidentally block their own invoices.<\/p>\n
Verifying them<\/h2>\n
dig +short MX yourdomain.com\ndig +short TXT yourdomain.com\ndig +short TXT default._domainkey.yourdomain.com<\/code><\/pre>\n
\"Terminal
MX with priorities, and one SPF line. Two SPF lines would be a problem.<\/figcaption><\/figure>\n
Read the SPF output carefully. If two lines starting with v=spf1<\/code> come back, that is a broken configuration and receivers will treat SPF as failing entirely.<\/p>\n
The most reliable end to end test is to send a message to a Gmail address you own, open it, and use Show Original. That page shows PASS or FAIL for SPF, DKIM and DMARC on the actual message, which is worth more than any checker.<\/p>\n
Connecting your mail app<\/h2>\n
Use IMAP, not POP3. IMAP keeps mail on the server so your phone and laptop stay in sync; POP3 downloads and usually deletes, which is why mail read on a laptop vanishes from a phone.<\/p>\n