Custom Domain Email Setup Guide: Get Your Own

A custom email address — that is, an email on your own domain in the format name@yourcompany.com — is not a small cosmetic detail; it's the backbone of your digital identity. The perception gap between a freelancer pitching from ahmet1987@gmail.com and one pitching from ahmet@studyom.com.tr often determines the price negotiation itself. And it's not just about prestige: when you own email on your own domain, switching providers becomes a one-click affair, your account doesn't vanish overnight because some platform changed its policy, and your brand communications stay on record.

This guide walks through setting up a custom domain email from scratch: domain selection, the path from hosting's built-in POP/IMAP through cloud suites like Google Workspace and Microsoft 365 to self-hosted solutions like Zimbra/Mailcow — with real DNS examples, real command lines, and real costs. By the end you'll know what to pick for which scenario, how to set up the MX–SPF–DKIM–DMARC triangle, and how to migrate from your old Gmail mailbox to the new address with zero loss.

What Is a Custom Email Address, and How Is It Different From Standard Webmail?

In everyday speech, "custom email" can mean two things: first, an email carrying your own domain name (name@company.com); second, an anonymous/encrypted personal account opened on a privacy-focused provider. The real subject of this guide is the first meaning — that is, setting up domain email. Even so, to fully address the search intent of the pillar keyword, we want to underline the distinction between "email on your own domain" and "personal email," because these two needs are frequently conflated.

Addresses like @gmail.com, @hotmail.com, @yahoo.com are free, convenient, and widely accepted — but on those addresses you're a tenant. If your account is closed under an alleged terms-of-service violation, ten years of correspondence may go with it, and the appeal mechanisms are weak. On top of that, addresses like info.firma1234@gmail.com tend to trip the spam filters of most corporate recipients, creating real friction in B2B proposal acceptance.

Why You Should Get a Custom Email Address: Measurable Benefits

By contrast, a custom email address is provider-independent as long as the domain belongs to you. Today you host on Google Workspace; tomorrow you move to Microsoft 365; next year to your own server or to Zoho — yet name@company.com stays the same, and your business cards, website, and invoices don't change. In our domain guide we cover in more depth why owning your own domain is a critical asset. The question we hear constantly in client meetings — "Gmail already works, why pay an extra 50 lira?" — has five concrete answers, and none of them are romantic prestige arguments. They all translate into hard numbers.

Brand consistency: If your website is company.com, your Instagram is @company, but your mail is @gmail.com, your communication identity breaks. The customer is left wondering: "Are these people serious?"
Deliverability: A corporate domain with SPF/DKIM/DMARC properly configured gains roughly a 15-25% advantage in moving from Gmail's Promotions tab into the primary inbox (in line with M3AAWG reports). For marketing and collections email, that translates directly into revenue.
Data control: When an employee leaves, you take over their account with one click; sales@company.com belongs to a position, not a person. With ahmet.gmail that's impossible.
Redundancy and archiving: Corporate providers offer 5+ years of retention, legal hold, and eDiscovery. Most data-protection laws (GDPR/KVKK) and sector regulations require it.
Portability: If you're unhappy with the provider, copy your mailbox over IMAP, switch the MX record, and you migrate in 24 hours. The address never changes; your customers don't even notice.

Which Domain Extension?.com,.com.tr, or.net?

The most common loss we see in the Turkish SMB market is this: a company that's been running on info.kahveci@gmail.com for 3-4 years moves offices, someone wipes a phone, the recovery SMS never arrives, and the account is permanently closed. Four years of customer correspondence, invoice copies, and contract PDFs vanish. An equivalent data loss is nearly impossible on a corporate account. Before setting up custom email, the central decision is picking the right domain. You don't need a separate domain for mail — whatever your website uses, your mail should use the same one. If you're undecided, the short rule is: if you sell globally, pick .com; if you operate only in the Turkish market and trust signals are critical, pick .com.tr; if you're a digital-first new-generation brand, .io / .co / .app are sensible choices.

A .com email address (i.e., name@company.com) is still the international standard, and more than half of the world's websites use the .com extension. Spam filters have been trained on .com for decades, which gives it a recognition advantage. Still, the new gTLDs (.studio,.agency,.digital) no longer carry an algorithmic disadvantage — they're just less common, and users tend to mistype them.

.com — around $8-15 USD/year; international standard, broadest recognition.
.com.tr — roughly ₺80-150/year (~$3-5 USD); may require a tax ID or trademark certificate; ideal for Turkey-focused corporate trust.
.net — around $12-18 USD/year; an alternative in the tech sector, the second pick when.com isn't available.
.org — around $10-15 USD/year; typically NGOs, associations, foundations — over time, it's acquired a non-profit perception.
.io / .app / .dev — around $30-50 USD/year; modern signaling for software/SaaS brands, but most mail filters still treat them conservatively.

Three Main Paths: Hosting Mail, Cloud Workspace, Self-Hosted

With our domain registration and WHOIS lookup tool, you can check domain availability for free. There are three practical ways to set up email on your own domain, and each one serves a different budget, volume, and control profile. Picking the wrong one of the three creates large migration costs down the road — so make this decision deliberately upfront.

1. Mail bundled with hosting (cPanel/Plesk/DirectAdmin): Email comes as part of your web hosting package. Zero added monthly cost, 10-minute setup. Ideal for low volume (1-5 mailboxes) and hobby use; weak under serious enterprise load.
2. Cloud workspace (Google Workspace / Microsoft 365 / Zoho Mail / Yandex 360): Email plus an office suite sold as SaaS. $3-15 USD per mailbox per month. Half-hour setup, near-zero administration, calendar/drive/video conferencing included. The healthiest path for SMBs and mid-market.
3. Self-hosted (Mailcow, Mail-in-a-Box, Zimbra, iRedMail, Postal): Running your own mail server on your own VPS. Maximum control and privacy, but the maintenance burden, the IP-reputation warmup, and uptime responsibility are all serious. Outside specific industry needs, it's not the right fit for most companies.

Path 1: Setting Up Built-in Email in a Hosting Package (cPanel Example)

The single concrete criterion that determines the choice between paths two and three: is email a core competency for you, or is it infrastructure? For most businesses it's infrastructure — so you keep it in the cloud and leave it to the experts. Nearly every shared hosting package in the $7-25 USD/year range offers between 5 and 50 email accounts; for a low-traffic boutique it's the fastest and cheapest path. You can find every panel detail in our cPanel guide; here we focus only on creating the custom email address.

1. Log into cPanel: Sign in via the panel URL provided by your host (e.g., https://server.company.com:2083).
2. Go to Email Accounts: From the left menu, click Email → Email Accounts → Create.
3. Fill in the address: Enter info in the Username field, company.com in the Domain field, and generate a strong password (at least 14 random characters).
4. Set a quota: 5 GB per mailbox is a reasonable starting point. The Unlimited option lets the host suspend the package when the disk fills up — be careful.
5. First webmail login: Test through Roundcube/Horde at https://company.com/webmail.

At this point your custom email is technically working, but the messages you send will most likely land in Gmail/Outlook spam. That's because SPF, DKIM, and DMARC records haven't been set up yet — we cover those steps in detail below. Beyond webmail, you also need to enter IMAP/SMTP settings for desktop clients (Outlook/Thunderbird/Apple Mail) and mobile clients (iPhone Mail/Gmail App).

Path 2: Professional Mail with a Cloud Workspace (the Most Common Choice)

In Outlook, "automatic configuration" usually works when you add the account; if it doesn't, choose "manual setup → IMAP" and enter the values above. If Apple Mail throws a certificate warning, that's because the host is using a self-signed certificate; you can permanently silence it by adding free SSL via Let's Encrypt. For SMBs and mid-market companies, the path we recommend most often is a cloud workspace. In around 30 minutes you get a professional office suite — calendar, shared drive, mobile sync, anti-spam, anti-phishing, and conferencing — all included. Below we compare the four major options at real 2026 price ranges (approximate; varies by provider; 2026 data).

Google Workspace Business Starter: ~$7 USD/mailbox/month; 30 GB storage; custom domain mail; Meet, Drive, Docs included.
Google Workspace Business Standard: ~$14 USD/month; 2 TB storage; meeting recording, additional security features.
Microsoft 365 Business Basic: ~$6 USD/month; 50 GB mailbox + 1 TB OneDrive; web Office, Teams.
Microsoft 365 Business Standard: ~$12.5 USD/month; desktop Office + 50 GB mail + 1 TB OneDrive.
Zoho Mail Lite: ~$1 USD/month; 5 GB mailbox; minimalist and cost-effective for small teams.
Zoho Workplace Standard: ~$3 USD/month; 30 GB mail + WorkDrive + Cliq.
Yandex 360 for Business: ~$3-5 USD/month; particularly low latency in Turkey/CIS regions.
ProtonMail Business: ~$7-10 USD/month; end-to-end encrypted; for sectors where privacy is critical.

Setting Up Custom Email with Google Workspace, Step by Step

For most Turkish SMBs, the two most common picks on the price/feature curve are Microsoft 365 Business Standard and Google Workspace Business Starter. If you handle a lot of Office documents, the Microsoft side is more frictionless; if your workflow is browser-first, Google sets up faster.

On the Google Workspace side, setup has three main phases: creation, verification, and MX redirection. 1. Start at workspace.google.com with Business Starter; enter your team size, domain, and admin details. 2. Google gives you a TXT record (google-site-verification=...); add it in your DNS manager and wait for propagation. 3. In Admin Console, under the Users tab, create accounts like info@company.com, sales@company.com, and so on. 4. Open your domain registrar panel, delete the existing MX records, and add Google's. 5. Add SPF, DKIM, DMARC (detailed below). 6. Import old mail from the legacy IMAP into Workspace via the Data Migration Service or GMMM.

MX changes can take 1-48 hours due to DNS propagation; in practice they typically propagate within 30 minutes. With our DNS lookup tool you can verify in real time that the right records have propagated. During propagation, expect some messages to land on the old server and others on the new one — monitor both inboxes through the cutover window.

Setting Up Custom Email with Microsoft 365

On the Microsoft side the flow is similar; Microsoft Admin Center → Setup → Add domain. For verification, Microsoft issues a TXT in the format MS=ms########. Then you add a single MX record. Once the Autodiscover CNAME is correctly set, Outlook desktop or the iOS/Android Outlook client connects with zero manual configuration.

The DNS Triangle: SPF, DKIM, DMARC — the Non-Negotiable Setup

This is the most-skipped step in mail setup, and the one that bills you the highest. If the SPF, DKIM, DMARC trio isn't set up correctly, every message you send — invoices, quotes, info mail included — either lands in Gmail/Outlook spam or doesn't get delivered at all. Together, these three records are the standard way of telling the receiving server, "I really did send this message; it's not a forgery."

SPF: Sending Server Authorization (RFC 7208)

Sender Policy Framework lists which servers are authorized to send mail on behalf of your domain. It's done with a single DNS TXT record. There can't be more than one SPF record for the same domain; combine them into a single line. The trailing -all means hard fail (reject); ~all means soft fail. For new domains, the safe strategy is to start with ~all and switch to -all after 2-4 weeks of monitoring DMARC reports. SPF records can't exceed 10 DNS lookups; if you stack too many includes, you get a "too many lookups" error.

DKIM: Cryptographic Signing (RFC 6376)

DomainKeys Identified Mail adds an RSA/Ed25519 signature to the headers of every message you send; the recipient verifies that signature against the public key you've published in your domain's DNS. SPF guarantees the sending IP; DKIM guarantees that the content wasn't tampered with in transit. You get the DKIM key from the provider and write it into DNS as a TXT record at selector._domainkey.company.com. The modern recommendation is a 2048-bit RSA or Ed25519 signature.

DMARC: Policy and Reporting (RFC 7489)

DMARC — Domain-based Message Authentication, Reporting and Conformance — tells the recipient what to do when SPF/DKIM fail, and sends you daily reports. Starting in 2024, Gmail and Yahoo phased in a DMARC requirement for bulk senders. p=none means do nothing; p=quarantine means treat as spam; p=reject means reject outright. Don't start a new domain straight at p=reject — it will drop your legitimate mail too.

Daily XML reports land at the rua address; to read them, use dmarcian, Postmark DMARC, or open-source parsedmarc. On top of the DMARC trio, modern domains also add MTA-STS (RFC 8461) and TLS Reporting (RFC 8460) records to require enforced TLS encryption between sender and recipient. Without those, you stay exposed to downgrade attacks.

Path 3: Self-Hosted Mail Server (Mailcow Example)

If you want full control, if data must stay within Turkey/EU borders for KVKK/GDPR reasons, or if industry regulations forbid foreign clouds, running your own mail server is a legitimate path. But this path is much more expensive than most SMBs assume: the biggest hidden cost is the "earning IP reputation" process. A new VPS IP delivers nothing close to a high deliverability rate to Gmail/Outlook for the first 4-12 weeks; a gradual warmup is required.

The most pragmatic tool for self-hosting is Mailcow: dockerized. All the components (Postfix, Dovecot, Rspamd, SOGo, Z-Push, Roundcube) ship in Docker containers; one docker compose up brings it up. Alternatives: Mail-in-a-Box (simpler, suitable for small domains), iRedMail, Zimbra.

At the end of this setup your mail server is running, but to send mail to the outside world you need five additional steps: (a) ports 25/465/587/993 open in the firewall, (b) a reverse DNS (PTR) record pointing to mail.company.com (request this from your VPS provider), (c) SPF/DKIM/DMARC records in place, (d) automatic Let's Encrypt certificate renewal, (e) a planned IP warmup period.

AWS EC2, Azure, and many large cloud providers block outbound port 25 traffic by default. To send mail you'll either open a support ticket and request "unblock" or move to a mail-friendly provider like Hetzner, OVH, or Contabo. A new mail server IP is a stranger to Gmail and Outlook; the IP warmup strategy is gradual: 50 messages on day one, 100 on day two, 200 on day three, 5,000 in week three — slowly ramping up to signal recipients that this IP is well-behaved. Rspamd, integrated with Mailcow, can manage the throttling automatically.

Email Address Naming: <code>info@</code>, <code>contact@</code>, or <code>first.last@</code>?

The naming format of a custom email address looks like a small detail, but it directly affects conversion rates. Five practical rules:

Function-based addresses for general mailboxes: info@, contact@, sales@, support@, billing@, careers@. Even if a position changes, the address stays.
first.last for personal addresses: ahmet.yilmaz@company.com. Don't use Turkish characters (cagri, not çağrı); they cause issues with spam filters and international recipients.
Be generous with aliases: The same mailbox can receive on info@, hello@, contact@ all at once. There's no extra cost, and customers reach you no matter which one they try.
Use catch-all carefully: *@company.com accepts everything; it's a spam magnet. Don't use it — set up aliases instead.
Don't use noreply@: It works technically but hurts user experience; redirect replies to a support@ address instead.

Migrating an Old Gmail/Hotmail Account to the New Address

If you've worked with company.coffeeshop@gmail.com for years, you'll want to move the past 10 years of correspondence into the new info@company.com mailbox. The method: confirm that both source and destination support IMAP (every modern provider does), then pick one of four tools — imapsync (open source, CLI, optimized for millions of messages), Google Workspace Data Migration Service (built into the Workspace admin panel), Microsoft 365 IMAP migration (Exchange Online admin → Migration → IMAP), or manual via Thunderbird (for small mailboxes).

The most critical point during migration: run imapsync before changing the MX records, so you also capture the new mail still landing in the old account. On cutover day, switch the MX, then run imapsync one more time for the last 24-hour delta. With this method, you lose zero mail.

Email Format: HTML, Plain Text, and Mobile Compatibility

After setting up custom email, the first mistake teams make is taking the PSD they got from the design studio and converting it as-is into HTML mail. Email HTML is a constrained world stuck 20 years behind web HTML: Outlook 2016 still uses the Microsoft Word render engine, flexbox doesn't work, and position: absolute breaks in most clients.

Table-based layout: The <table> element, exiled on the modern web, is still standard in email.
Inline CSS: <style> blocks are stripped by most clients; write every style as an attribute.
Maximum 600px width: Outlook reading pane, mobile portrait, and web preview are all narrow.
Optimize images: Images over 100 KB get clipped automatically by Gmail. Always include alt text.
Plain text alternative: With multipart/alternative, attach a text/plain version to every HTML message — critical for DMARC and spam scoring.
Pre-header text: The short greyed-out blurb after the subject line; well-written, it lifts open rates by 15%.

Email Security: BEC, Phishing, and Employee Training

Switching to a custom email address doesn't, on its own, make you secure; if anything, the corporate look creates an open target for spear-phishing attacks. BEC (Business Email Compromise) fraud globally crossed $50 billion annually between 2024-2026. The typical scenario: the attacker registers a domain that closely resembles the CEO's address (company-com.com, cornpany.com, company.co), sends the CFO an "urgent wire transfer" email, and millions are lost.

2FA / MFA mandatory: For every user on Google Workspace, Microsoft 365, and Zoho; FIDO2 hardware keys when possible.
Register lookalike domains: Picking up cornpany.com, company-com.com, company.com.tr defensively at $100-300 USD/year is cheaper than an insurance premium.
Banking-change protocol: Never reply by email to messages that say "the IBAN has changed" — require verbal confirmation through a known phone number.
Employee awareness training: Run simulated phishing every six months with KnowBe4 or similar.
Anti-phishing policy: Defender for Office 365 in Microsoft 365, Advanced Phishing Protection in Google Workspace — keep both enabled.
External tag: Automatically prepending [EXTERNAL] to the subject line of inbound messages from outside the org dramatically increases employee vigilance.

GDPR/KVKK and Data Residency: Which Provider in Turkey?

For a broader security perspective, our OWASP Top 10 2026 and DDoS Protection Guide articles are foundational references.

Turkey's KVKK Law No. 6698 imposes strict conditions on transferring personal data abroad. Since email correspondence almost always contains customer personal data, the data-center location of your provider matters. Google Workspace and Microsoft 365 offer EU data-center options; for some sectors (healthcare, financial services) that may not be sufficient. Local Turkish providers offer the advantage of in-country data centers, with corporate POP/IMAP packages running ₺200-2000/year (~$8-80 USD). For self-hosted options, Hetzner Helsinki/Nuremberg, Contabo Germany, and Vultr Istanbul all sit in countries on KVKK's "adequate protection" list, so no extra contracts are required. Google and Microsoft sign their standard DPAs through their portals; under KVKK Article 9, retaining those records is mandatory.

Separating Mailing List, Transactional Mail, and Marketing Mail

As of 2026, sending both invoices and newsletters from a single info@company.com address is no longer the recommended architecture. You need to split mail traffic into three streams:

Corporate mail: Person-to-person correspondence between employees. The main company.com domain. Low volume, high reputation.
Transactional mail: Order confirmations, password resets, invoice PDFs. A separate subdomain or a separate provider: mail.company.com + Postmark/SendGrid/Mailgun. High deliverability is critical.
Marketing mail: Newsletters, campaigns, promotions. A completely separate subdomain: news.company.com + Mailchimp/SendGrid Marketing/Brevo. Isolated so that bounce rates don't pollute corporate-stream reputation.

Webmail, Desktop Client, or Mobile?

If you don't separate these three streams, a single bad campaign mail list can wreck the reputation of the whole domain — and even your invoice mail starts landing in spam. Subdomain separation means that if one stream gets contaminated, the others are protected.

The actual user experience of a custom email address is shaped by the client. The combination we most often recommend: the provider's webmail (Gmail/Outlook Web) for daily work, Thunderbird for archive and bulk operations, and Outlook Mobile or the native Mail app on mobile. All clients sync over IMAP; a message you read on one device shows as read on the others.

Backup: Mail Can Disappear Even From the Cloud

The infrastructure behind Google and Microsoft doesn't go down, but your account can. An employee being deleted on the way out, an admin policy mistake, an account suspension — every year, hundreds of thousands of SMBs face losses like these. Using the cloud doesn't relieve you of backup responsibility; if anything, the small print of the contract usually leaves it squarely on you.

Third-party cloud backup: Synology Active Backup for M365/Workspace, Veeam, AvePoint. They periodically copy mailboxes.
Local IMAP archive: Use Thunderbird at year-end to download every mailbox to a local .eml folder; zero added cost.
Google Takeout / Microsoft eDiscovery: Periodic exports for individual accounts; sufficient for small teams.
3-2-1 rule: 3 copies, 2 different media, 1 offsite. Applies to email too.

Email Signature Standards and Legal Disclaimer Text

The same general principles we use for database backup apply equally to email; we cover 3-2-1 and PITR in detail in our Backup Strategies guide. The detail that doubles the corporate impact of a custom email address is a consistent email signature. In Turkey, certain legal disclaimers are mandatory in some sectors (e.g., insurance); even outside your sector, linking to a privacy/KVKK notice is good professional practice.

You can enforce the signature template across the whole domain — using "Append footer" in Google Workspace or a transport rule in Microsoft 365 — so employees don't have to set their own signatures and brand consistency is guaranteed.

Two Common Mistakes and How to Recover From Them

Mistake 1: MX changed, but mail still ended up on the old host. When migrating to Google Workspace, you change MX in your DNS panel — but the old hosting panel may still be accepting mail. Some legacy packages ignore the MX and deliver locally anyway ("local delivery"). The result: some messages land in the new Workspace, others in the old hosting mailbox; the customer says, "I sent you mail and got no reply." Fix: in cPanel, go to Email Accounts → MX Entry and switch to "Remote Mail Exchanger"; this delegates MX authority to the external server and disables local delivery.

Mistake 2: SPF doesn't combine all senders into a single record. After adding the Workspace SPF, when Mailchimp is added for marketing, the existing SPF isn't deleted; instead a new one is written as a separate record. Per RFC 7208, a domain may have only one SPF record; on seeing two, the receiving server returns "PermError" and rejects the mail.

Sending Limits and Measurement: Was the Mail Actually Delivered?

The daily send limit on your custom email varies by provider; for campaign sending, these numbers are decisive.

Google Workspace: 2,000 external recipients/day (500 on new accounts). For more, use Google Marketing Platform or a third-party SMTP relay.
Microsoft 365: 10,000 external recipients/day; 30 messages/hour to the same recipient.
Zoho Mail Standard: 1,000 external messages/day.
cPanel mail (shared hosting): 100-500 messages/hour; the package can be suspended on spikes.
Mailcow self-hosted: Bound by hardware/IP reputation, no theoretical limit, but warmup is mandatory.
SendGrid Pro: 100K messages/second; the industry standard for transactional mail.

If you're sending 5,000+ marketing messages per week, send them from a separate transactional provider (SendGrid, Postmark, Mailgun, Amazon SES), not your corporate mailbox. Don't assume setup is finished after a single test message; the mail may have left the server fine but landed in spam. Three tools are mandatory for verification: mail-tester.com (a score out of 10), mxtoolbox.com (DNS/blacklist), Google Postmaster Tools (Gmail deliverability, domain reputation), and Microsoft SNDS (the Outlook side).

Cost Table: Teams of 1, 5, 25, and 100 Users

Making the decision requires hard numbers. The table below shows annual total mail cost at 2026 average prices for four team sizes (approximate, varies by provider, USD ex-VAT).

1 user (solo): Mail in the hosting package (~$30 USD/year, part of web hosting) → Zoho Mail Lite (~$12 USD/year) → Google Workspace Starter (~$84 USD/year).
5 users (small team): Hosting mail (~$50 USD/year) → Zoho Workplace (~$180 USD/year) → Microsoft 365 Basic (~$360 USD/year) → Google Workspace Starter (~$420 USD/year).
25 users (SMB): Microsoft 365 Basic (~$1,800 USD/year) → Google Workspace Starter (~$2,100 USD/year) → Self-hosted Mailcow + 4 vCPU VPS (~$600 USD/year + 8-15 sysadmin hours/month).
100 users (mid-market): Microsoft 365 Standard (~$15,000 USD/year) → Google Workspace Standard (~$16,800 USD/year) → Self-hosted enterprise Zimbra (~$3,000 USD license/year + a full-time admin).

In the 5-25 user band, $6-7 USD/user/month for email alone may look expensive; but since a single BEC fraud attempt can carry a $50,000 USD loss, the threshold at which the risk pays for itself is low. The real cost of self-hosting isn't software — it's 10-20 sysadmin hours per month; price that time alone and the cloud is usually cheaper.

Frequently Asked Questions

Can I convert an existing Gmail account into a domain account? There's no direct conversion; but you can open a new name@company.com in Google Workspace and use the Data Migration Service to import the old Gmail, effectively "moving" it. The old Gmail address still exists; if you want, you can forward it to the new address.

Is there a free custom email address? Yes, with limits. Zoho Mail's Forever Free Plan offers 1 domain and 5 users with a 5 GB mailbox. Cloudflare Email Routing lets you take info@company.com and forward it with one click to your existing Gmail — receive only, no sending. Hosting packages are technically "paid," but they don't charge extra for mail.

Can I buy the domain in one place and the mail in another? Absolutely; it's a common practice. DNS management lives at the registrar; you point the MX records at whichever mail provider you like. In fact, this is the recommended architecture — putting domain and mail in the same vendor lock-in makes future migrations harder.

Can I use Turkish characters (çağrı@company.com)? Technically possible via SMTPUTF8 (RFC 6531), but in practice we don't recommend it. Many older mail clients reject these addresses, and your B2B recipients may not be able to deliver to you. Prefer cagri@company.com. Can the same domain run both hosting mail and Workspace? No, MX can only point at one provider. You can split by subdomain — main domain on Workspace, support.company.com on hosting — but managing two mailboxes for a single user rarely makes sense. What happens if I don't renew the domain my mail depends on? When the domain expires, you can recover it during the 30-45 day redemption period; mail won't flow during that time. After redemption, the domain hits the open market; if someone else buys it, you effectively lose your email address. Keep auto-renew on at all times, and keep credit card details current.

Checklist: Have You Finished Setting Up Your Custom Email?

Domain purchased and registrar panel access verified.
Mail provider chosen (hosting / Workspace / self-hosted) and an account opened.
Domain ownership verified via the TXT record requested by the provider.
MX records repointed at the new provider; old MX records deleted.
SPF record contains every sending provider on a single line.
DKIM key obtained from the provider, added to DNS, and validated.
DMARC record started at p=none, with a reporting address defined.
MTA-STS and TLS-RPT (for modern domains) added.
User accounts created, with 2FA made mandatory.
IMAP/SMTP settings entered on desktop and mobile devices.
Old mail migrated via imapsync or the Migration Service.
Corporate email signature template prepared and rolled out to staff.
Backup provider (Veeam/Synology/Takeout) configured.
Score of 9/10 or above on mail-tester.com.
Google Postmaster Tools and Microsoft SNDS accounts added.
Banking-change protocol against BEC announced to the team.
Defensive lookalike (typosquatting) domain registrations done.
DPA signed; KVKK/privacy records updated.

Decision Matrix: Which Path for Which Scenario?

A setup that ticks all 18 items above is what we'd call a "grown-up" mail infrastructure at SMB scale. Every missing item carries a hidden cost — sooner or later it shows up as a spam-folder problem, a BEC incident, or an issue at a compliance audit.

Solo freelancer / 1-2 people: Hosting's built-in mail + SPF/DKIM/DMARC. $0 USD additional per month.
3-15-person SMB, mostly business correspondence: Microsoft 365 Business Basic or Google Workspace Starter.
15-50 people, office suite required: Microsoft 365 Business Standard.
E-commerce, transactional-heavy: Workspace + a separate SendGrid/Postmark subdomain.
Public sector / regulated industry / KVKK-critical: EU sovereign cloud or self-hosted Mailcow + a Turkey/EU data center.
Developer / DevOps team, control-oriented: Self-hosted Mailcow + 2 vCPU VPS, with a sysadmin on the team.
Temporary project / short term: Cloudflare Email Routing + an existing Gmail (if no sending needed).

References

Get professional help setting up your custom email

For domain selection, MX/SPF/DKIM/DMARC configuration, Workspace/M365 migration, Mailcow self-hosting, and KVKK/GDPR compliance, get in touch. contact us

Readers of this article also read these

mail 27 min

Türkticaret Webmail Guide: Login, IMAP/SMTP Setup and Mail Management (2026)

Comprehensive 2026 guide to Türkticaret webmail login, IMAP/POP3/SMTP configuration, mobile and desktop setup, signatures, domain-bound mail management, SPF/DKIM/DMARC, and troubleshooting.

mail 28 min

Buying a Gmail Account: Account Marketplaces, Risks, and Legitimate Alternatives

What sits behind the 'buy Gmail account' query? A vendor-neutral engineering deep dive into how the ready-made account market works, the real risks (ToS, KVKK/GDPR, fraud), how to set up custom-domain Gmail with Google Workspace, and how to create free Gmail accounts the right way.