Moving a company to branded email is not just creating mailboxes. Authentication and monitoring decide whether messages land in the inbox — or the spam folder your customers never open.

This checklist is for founders and ops leads anywhere who switched to @company.com and still hear “I never got your email.” Softlinks sets up AzAd Workspace and MailTry around these realities for international teams.

Why mail still lands in spam

  • No SPF — receivers cannot tell who is allowed to send as you
  • No DKIM — messages are not cryptographically tied to your domain
  • No DMARC — spoofed or misaligned mail has no policy
  • Shared hosting IPs with a poor reputation
  • Mixing newsletters and password resets on the same stream
  • Sudden volume spikes from a cold domain

Minimum viable setup

  • SPF for authorized senders
  • DKIM signatures on outbound mail
  • DMARC policy that you actually monitor (start with reporting, then enforce)
  • Separate transactional vs marketing streams when volume grows
  • Aligned From domains — do not send as your brand from a random relay forever
  • Inventory every system that sends as your domain (app, CRM, billing, marketing)
  • Fix DNS authentication before chasing content tweaks
  • Warm up new domains gradually
  • Watch DMARC reports weekly for the first month
  • Only then tighten policy toward reject

AzAd Workspace and MailTry are built for branded business mail. Softlinks can migrate domains, harden authentication, and keep deliverability in scope during a mail engagement. See the mail & workspace service page or start a project if you need a domain review.

FAQ

We created @company.com mailboxes. Why is mail still in spam?
Mailbox creation is not authentication. Receivers look for SPF, DKIM, and a DMARC policy you actually monitor — plus a clean sending reputation.
What is the minimum viable setup?
SPF for authorized senders, DKIM signatures on outbound mail, a DMARC policy you monitor, and separate transactional vs marketing streams as volume grows.