Charchy Senddocs

Deliverability basics

How to keep your emails in the inbox — authentication and DMARC, warming up a new domain, and handling bounces and complaints.

Mail providers decide between inbox, spam and nowhere from who you are (authentication), how you behave (volume and history), and how people react (bounces and complaints).

1. Authenticate your domain

  • DKIM — every email is signed with your domain's key, set up once with three DNS records (Domains and DNS).
  • DMARC — Gmail and Yahoo require one from anyone sending at volume. Start with p=none, read the reports for a few weeks, then move to p=quarantine and finally p=reject. A strict policy stops others from sending as your domain.
_dmarc.daringaming.com   TXT   "v=DMARC1; p=none; rua=mailto:dmarc@daringaming.com"
  • Send from the same one or two addresses (no-reply@, orders@), so readers and filters learn to trust them.
  • Consider a subdomain (mail.daringaming.com) for app mail, to keep its reputation apart from your staff's everyday email.

2. Warm up a new domain

Providers distrust a domain that suddenly sends thousands of emails, so a workspace is capped at 500 emails a day for its first 7 days (daily caps).

  • Start with your most-wanted mail: sign-in codes, receipts.
  • Moving from another provider? Move a slice of your traffic first, then the rest over a week or two.

3. Handle bounces and complaints

  • A hard bounce (the address doesn't exist) is suppressed and skipped from then on. Use the email.bounced webhook to ask the user to fix their address.
  • A complaint (the reader pressed "spam") suppresses the address for both the API and Campaigns, and fires email.complained.
  • Providers start filtering above about 0.1% complaints; we pause sending at 4% bounces or 0.08% complaints (why).
  • Only send to addresses your users gave you — never bought, scraped or guessed lists.
  • Confirm addresses at sign-up (a verification code does it), so typos never reach your bounce rate.

4. Write emails that look expected

  • A from name your users recognise, and a subject that says what the email is: "Your sign-in code: 482910", not "Important!".
  • Send a text part too, or let us make it from your html.
  • Keep html small — Gmail clips emails over about 102 KB — and use hosted images with alt text.
  • Link to your own domain, not public link shorteners (spammers use them).
  • For Kurdish and Arabic, set dir="rtl" on your HTML's container.

Watch the numbers

The dashboard's Overview shows delivered, bounce and complaint rates for today and the last 30 days, next to the limits that would pause sending.

On this page