Mail Hosting Guide: How to Set Up Corporate Email?

What Is Mail Hosting?

Mail hosting is a service that lets you send and receive email using your own domain, such as @yourcompany.com. Unlike free Gmail or Outlook addresses, a corporate email address belongs to your brand, leaving a professional impression on your business cards, proposals, and contracts.

Technically, email runs on two protocols: SMTP handles sending, while IMAP (or the older POP3) handles receiving. Your domain's MX record determines which server your messages get delivered to. Setting up these three records correctly is the first requirement for your emails to land in the recipient's inbox.

3 Core Options: Hosting Mail, Workspace, Microsoft 365

In practice, there are three main routes to corporate email. The right choice depends on your budget, team size, and the tools you already use.

1. Built-in Hosting Mail (cPanel / Plesk): If you already have a web hosting plan, email accounts usually come included for free. A few clicks in cPanel let you create accounts like info@ or sales@. It's the most economical route, but mailbox size and sending limits are constrained by your plan. See our cPanel guide for details.

2. Google Workspace: Lets you use the Gmail interface with your own domain. It comes bundled with Drive, Docs, Meet, and Calendar. Since the interface is the Gmail everyone already knows, the learning curve is close to zero, and its spam filter is one of the best in the industry.

3. Microsoft 365 (Exchange Online): Outlook plus Word, Excel, PowerPoint, and Teams. Ideal for teams that rely heavily on desktop Office apps and already have an established corporate calendar/meeting routine.

Comparison Table and Pricing

The table below summarizes the key differences between the three options under 2026 Turkish market conditions. Prices are approximate and represent the monthly cost per user.

If you only need 1-2 email accounts and already have a hosting plan, hosting mail is the most sensible starting point. Once your team grows past 5 people and needs a shared calendar or file sharing, switching to Workspace or Microsoft 365 makes things easier. If you're looking for a suitable hosting plan, you can filter by number of email accounts on our hosting comparison page.

Step-by-Step Hosting Mail Setup

Setting up corporate email on a cPanel hosting plan takes just a few minutes:

1. Open cPanel → the Email Accounts section.
2. Click the "Create" button; choose a username (info) and your domain.
3. Set a strong password of at least 14 characters.
4. Set the mailbox size (2-5 GB is enough to start with).
5. Create the account; you can access it right away via Webmail (Roundcube).

Here are the typical settings for adding the mailbox to a client like Outlook or Thunderbird:

Incoming mail (IMAP)
  Server : mail.yourcompany.com
  Port   : 993   (SSL/TLS)
  Username : info@yourcompany.com

Outgoing mail (SMTP)
  Server : mail.yourcompany.com
  Port   : 465   (SSL/TLS)
  Authentication : On (same username/password)

The job isn't done once setup is complete: to keep your emails from landing in spam, you also need to add three verification records on the DNS side. Let's go through them one by one.

What Is an SPF Record and How Do You Set It Up?

SPF (Sender Policy Framework) specifies which servers are authorized to send email on behalf of your domain. It's a TXT record added to your domain's DNS settings. The receiving server checks this record to verify that incoming mail genuinely came from an authorized source.

Add a new TXT record in your domain management panel (DNS Zone Editor):

# Sending only from your own hosting server
Type  : TXT
Name  : @   (i.e., yourcompany.com)
Value : v=spf1 a mx include:_spf.hostingprovider.com -all

# For Google Workspace users
Value : v=spf1 include:_spf.google.com ~all

# For Microsoft 365 users
Value : v=spf1 include:spf.protection.outlook.com -all

Signing Email with DKIM

DKIM (DomainKeys Identified Mail) adds a digital signature to every outgoing email. The receiving server verifies this signature using the public key you publish in your DNS, which proves the message wasn't altered in transit and genuinely came from you.

Your hosting panel (cPanel → Email Authentication) or your Workspace/Microsoft admin console generates the DKIM key for you. You add the value it gives you as a TXT record:

Type  : TXT
Name  : default._domainkey        (the selector is shown in the panel)
Value : v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBg
        QC7x9k8...very-long-public-key...QIDAQAB

The selector name (default above) varies by provider; for Google it's usually google._domainkey. The panel clearly tells you which name and value to enter — copy it exactly and don't split the public key.

Blocking Spoofing with DMARC

DMARC (Domain-based Message Authentication) ties SPF and DKIM together into a policy: it answers the question "what should happen to emails that fail both of these checks?" It also sends you regular reports so you can see who's sending email on your behalf — key to catching brand impersonation (phishing) early.

It's set up with a single TXT record:

# Starting point: monitor only, no blocking
Type  : TXT
Name  : _dmarc
Value : v=DMARC1; p=none; rua=mailto:dmarc@yourcompany.com; pct=100

# Once you trust it: quarantine suspicious mail
Value : v=DMARC1; p=quarantine; rua=mailto:dmarc@yourcompany.com; pct=100

# Full protection: reject anything that fails
Value : v=DMARC1; p=reject; rua=mailto:dmarc@yourcompany.com; pct=100

Tighten the policy in stages: collect reports with p=none for a few weeks, then once you've confirmed everything is passing correctly, move up to p=quarantine and finally p=reject. This removes the risk of losing legitimate emails to a misconfiguration.

Verifying and Testing the Records

DNS changes typically propagate within 15 minutes to a few hours. You can quickly check whether the records are working correctly from the command line:

# Query the SPF record
dig +short TXT yourcompany.com

# Query the DKIM record (selector: default)
dig +short TXT default._domainkey.yourcompany.com

# Query the DMARC record
dig +short TXT _dmarc.yourcompany.com

# Which server does the MX record point to?
dig +short MX yourcompany.com

Windows users can use nslookup -type=TXT yourcompany.com instead of dig. For a practical test, send yourself an email, open it in Gmail, and click "Show original" — you should see SPF: PASS, DKIM: PASS, and DMARC: PASS. Once all three pass, your emails are now considered trustworthy.

Frequently Asked Questions

Do I need separate hosting for corporate email?

No. You can use your existing web hosting plan's built-in mail service, or get corporate email with just a Google Workspace or Microsoft 365 subscription without any hosting at all. Either way, the only thing you truly need is a domain name.

Why do my emails end up in the spam folder?

The most common cause is missing or misconfigured SPF, DKIM, and DMARC records. Once all three records are set up correctly and your server's IP isn't on a blocklist, the spam problem is largely resolved. Using a separate SMTP service for bulk sends also protects your reputation.

Are SPF, DKIM, and DMARC all mandatory?

Technically, no — but without all three in place, modern email providers (Gmail, Outlook) won't trust your messages. Since 2024, this trio has effectively become mandatory for anyone doing bulk sending; for corporate email, be sure to set up all three.

Should I choose Google Workspace or Microsoft 365?

If your team works in the browser and is used to the Gmail interface, Google Workspace will feel more comfortable. Microsoft 365 suits companies that rely heavily on desktop Word/Excel and Teams and already have an established corporate calendar routine. In 2026, their prices are very close to each other (in the ~₺180-300/user range).

Will I lose my emails if I change the MX record?

Changing the MX record only determines which server future incoming mail is delivered to; it doesn't delete the messages already in your old mailbox. When switching providers, you'll need to migrate your old emails to the new account using IMAP.