7 Common Pitfalls with Business Email Setup

Most issues with business email arise during migration and handover, not daily use. The common thread across all seven pitfalls is incorrect sequencing, disorga…

Insights:7 Common Pitfalls with Business Email Setup

Pitfall 1: Switching MX Before Creating Accounts

Symptom: The domain DNS is switched to a new provider, but accounts haven't been created yet, so all emails are bounced.

Fix:

  1. Create accounts and aliases first.
  2. Then configure SPF/DKIM/DMARC.
  3. Only switch MX after successful testing.
  4. Keep the old service active for a period.

Pitfall 2: Failing to Remove the Old MX Record

Symptom: Both old and new MX records exist simultaneously, causing random mail delivery and intermittent failures.

Fix:

  • Keep only the new provider's MX record during the switch.
  • Verify with a DNS lookup tool.
  • Screenshot old records for archive and easy rollback.
  • Monitor for 24–48 hours.

Pitfall 3: Multiple SPF Records

Symptom: Multiple TXT records contain v=spf1, leaving receiving servers unable to determine validity and resulting in authentication failure.

Fix:

  • Retain only one SPF record per domain.
  • Merge all sending sources into a single record.
  • Check whether subdomains and email platforms each have their own record.
  • Validate using an authentication testing tool.

Pitfall 4: Configuring Only SPF Without DKIM/DMARC

Symptom: Emails can be sent but frequently land in spam folders; impersonation goes undetected.

Fix:

  • Set up DKIM signing.
  • Start DMARC with p=none for monitoring.
  • Collect aggregate reports.
  • Gradually tighten policies once stable.

Pitfall 5: Treating Aliases as Independent Accounts

Symptom: Assuming sales@ is a standalone account when it's merely a forwarding alias; mail stops flowing after the employee leaves.

Fix:

  • Clearly distinguish between accounts, aliases, and mailing lists.
  • Assign responsible owners to critical role-based addresses.
  • Reassign ownership before deactivating accounts upon departure.
  • Audit the address list regularly.

Pitfall 6: Skipping Migration and Backup

Symptoms: Old emails are lost after switching, or cannot be exported; accidentally deleted messages cannot be recovered.

Solution:

  • Synchronize historical emails before switching.
  • Verify for missing and duplicate emails.
  • Keep old accounts in read-only mode for a period.
  • Enable backup and recycle bin.
  • Conduct regular recovery drills.

Pitfall 7: No Handover on Resignation, No Permission Revocation

Symptoms: Clients keep emailing resigned employees; former employees can still log in.

Solution:

  • Include mailbox handover in the offboarding process.
  • Transfer aliases to successors.
  • Freeze or delete accounts.
  • Revoke admin privileges.
  • Retain necessary archives.

Comparison Table of Seven Pitfalls

Pitfall DIRECT CONSEQUENCE PREVENTION
Cutting MX first Email bounces Create accounts first, then switch
Residual old MX records Unstable delivery Only keep new MX records
Multiple SPF records Authentication failure Merge into one
Missing DKIM / DMARC Emails land in spam Configure all three together
Using aliases as accounts Client loses contact Clarify ownership
No migration, no backup Data loss Migrate + back up
No handover on departure Security and client risks Standardized handover process

Five Questions Before Go-Live

  1. Are all accounts created?
  2. Is there only one correct set of DNS records?
  3. Has authentication testing been completed?
  4. Can old emails be recovered?
  5. Who handles the handover for departing staff?

If all five questions have answers, then switch traffic.

Related readings: