How to Fix Low Email Deliverability on a New Sending Domain
Fix deliverability on a new sending domain by warming it slowly — 50 emails day one, doubling every few days — setting a DMARC policy at p=none first, and never sending marketing mail from the domain that carries your login emails. Reputation takes 4-6 weeks to build and one bad batch to destroy.
The hard truth: most deliverability problems are list quality, not infrastructure. No DNS record fixes a list full of addresses that never opened anything.
What does the DNS setup actually require?
Three records, and only one of them is usually wrong.
| Record | Purpose | Common mistake |
|---|---|---|
| SPF | Authorises sending IPs | Two SPF records (invalid); must be one, with include: appended |
| DKIM | Cryptographic signature | Wrong selector name; check the exact value Loops gives you |
| DMARC | Policy + reporting | Set to p=reject on day one, killing your own mail |
Start DMARC at p=none with a rua= reporting address. After two weeks of clean reports, move to p=quarantine, then p=reject once you have confirmed every legitimate sender is aligned.
p=reject on a domain you have not audited is how companies discover their CRM sends from it too — and now it all bounces.
How should you warm a new domain?
A schedule that works for a small list:
- Day 1: 50 emails to your most engaged contacts (opened in the last 30 days)
- Day 2-3: 100/day, same engaged segment
- Day 4-7: 250/day, expand to 60-day engaged
- Week 2: 500/day
- Week 3-4: 1,000/day, then move to your full list
Send to engaged contacts first, always. A new domain that immediately blasts 10,000 cold addresses gets throttled by Gmail within 48 hours and the damage follows the domain.
If you send more than 5,000/day at steady state, use a dedicated IP — shared IPs are fine below that and a dedicated one you fail to warm is worse than a shared pool.
Why do Gmail and Outlook behave so differently?
Gmail weighs engagement signals heavily: opens, replies, “not spam” clicks, and how often a recipient moves your mail out of Promotions.
Microsoft 365 filters lean harder on authentication and sending infrastructure reputation. A domain that passes everything can still get filtered by Microsoft if your IP has history.
Practical consequence: test with a Gmail consumer account and a Microsoft 365 business account. Those two cover most of the risk. Yahoo and iCloud matter for consumer lists but rarely drive B2B complaints.
How do you read bounce and complaint data in Loops?
Loops shows delivery, bounce, open and complaint stats per campaign and per transactional template.
Hard bounces (unknown mailbox) should be suppressed automatically — Loops does this. Soft bounces (mailbox full, greylisting) are retried and usually resolve.
The number to watch is the complaint rate. Above 0.1% and Gmail starts treating you differently; above 0.3% you are heading for a block. Any single campaign above 0.1% means the list segment was wrong, and the fix is a re-permission email to that segment, not a new subject line.
For transactional mail, the signal to watch is the ratio of sends to deliveries. If password resets start bouncing at 5%, you have a typing-error problem in a form, not a deliverability problem.
What cannot be fixed?
- A purchased list. 30-60% invalid addresses, spam traps, and a reputation hit that takes months to recover. There is no technical workaround.
- A domain used for both login links and newsletters. One bad campaign poisons your password resets. Split them:
mail.yourdomain.comfor transactional,news.yourdomain.comfor marketing, both under the same DMARC parent policy. - Users who marked you spam once. Suppression is permanent and correct.
Sending volume on a small list will not be enough to build reputation quickly. If your list is under 1,000, expect a slower ramp and accept that marketing email will take a quarter, not a week.
Key Takeaways
- Keep exactly one SPF record; append
include:rather than adding a second. - Start DMARC at
p=nonewith reporting, then move to quarantine and reject after two clean weeks. - Warm up: 50 → 100 → 250 → 500 → 1,000 per day, engaged contacts only.
- Use a dedicated IP only above roughly 5,000 sends/day; a cold dedicated IP is worse than shared.
- Keep complaint rate under 0.1%; split transactional and marketing onto separate subdomains.
