Warm up a new email domain by authenticating it first, sending wanted transactional mail to people who just took an action, adding real staff replies on the same domain, then raising volume only while bounce quality and Gmail user-reported spam stay clean. A 2–4 week ramp is a starting frame, not a guarantee. Fake reply networks and day-one blasts to strangers are the wrong template for receipts and password resets.
The 5 p.m. authentication, 9 a.m. blast problem
A founder finishes ArawaMail onboarding at 5 p.m.: Cloudflare zone active, receiving on, sending on, SPF, DKIM, custom MAIL FROM, and DMARC published. The launch calendar still says 20,000 announcement emails at 9 a.m.
Mailbox providers treat that domain as unknown. Passing SPF, DKIM, and DMARC proves who you are. It does not prove you are wanted. Inbox placement is earned by the mix of recipients, content, and complaint behavior over the next days—not by a checkbox on a DNS page. That is why the domain is the product.
What domain warmup actually means in 2026
Email domain warmup is the controlled first use of a newly authenticated sending domain so mailbox providers can observe wanted mail before they see volume. For an ArawaMail customer that usually means:
- Product mail people requested in the last session (resets, receipts, invites, OTPs).
- Human mailbox traffic on the same domain: staff send and reply.
- A pause rule when authentication fails, bounce quality collapses, or Gmail spam rate climbs toward 0.10%.
It does not mean renting a “warmup network” that fabricates opens and replies. Those products train a pattern that looks nothing like a SaaS receipt stream. It also does not mean buying a dedicated IP on day one. Clean the domain first; see don’t buy a dedicated IP until the domain is clean and domain reputation vs IP reputation.
How we analyzed this
This plan is constrained by public mailbox-provider rules and by what ArawaMail actually documents:
- Gmail asks senders to keep user-reported spam below 0.10% and to treat 0.30% or higher as a hard problem. Above 0.30%, delivery support or mitigation is typically unavailable until the rate recovers (often seven consecutive days below 0.30%).
- Gmail Postmaster Tools v2 no longer shows High / Medium / Low domain or IP reputation badges. Watch Compliance status, spam rate, authentication, delivery errors, and any Deliverability analysis verdict. Do not wait for a “High” badge that no longer exists.
- Bulk-sender rules still apply near 5,000+ messages per day to personal Gmail: SPF + DKIM + DMARC (at least
p=none), plus one-click unsubscribe on marketing or subscribed mail. Transactional streams should stay promotion-free. See Gmail and Yahoo bulk-sender requirements. - ArawaMail documented order is add domain → active Cloudflare zone → Activate receiving → Enable sending → create mailboxes → create API keys. Sending requires receiving first.
- The Send API requires a
fromdomain that belongs to the API key’s company and is sending-active. Retrieve Emaillast_event(examplesent) is acceptance/processing visibility, not inbox placement, bounce, or complaint telemetry. - ArawaMail does not document a warmup product, seed-test product, dedicated-IP product, or complaint dashboard. Plan volume inside published monthly send caps (Free 3,000 / Pro 50,000 / Business 100,000).
No schedule guarantees inbox placement. Postmaster data can be missing at low Gmail volume.
Do you need a warmup service?
Usually no—if the first weeks are ordinary transactional mail plus staff mailboxes, and every recipient just asked for the message. You need a written ramp and stop rules, not a third-party inbox farm.
You do need extra caution if the first use of the domain is a purchased list, scraped addresses, or a marketing blast that people did not request. That is a list problem, not a missing warmup widget. Fix hygiene first: email list hygiene in 2026.
Transactional warmup vs marketing warmup
Keep the two streams conceptually separate even when they share a company.
- Transactional warmup is password resets, receipts, booking confirmations, and invites tied to an action in the last minutes or hours. Recipients expect the message. Complaints should be rare if content matches the action.
- Marketing warmup is newsletters, launches, and promotions. Recipients forget they opted in. Complaint rates are higher. One-click unsubscribe is mandatory once you approach bulk thresholds. Do not put this traffic on a brand-new domain on day one.
If you will send both at scale, put marketing on a subdomain later. The rationale lives in why marketing and transactional email should use separate subdomains. During week one, the new apex or product domain should look like a product, not a blast list.
A 2–4 week ramp you can copy
Treat the daily numbers as a shape for a typical SaaS domain, not a law. A two-person studio sending 40 receipts a day does not need to invent volume. A marketplace expecting thousands of OTPs does need to climb. Stay inside your ArawaMail plan cap.
Days 0–2 — prove the domain
- Cloudflare zone active. Follow connect a Cloudflare domain and the ArawaMail DNS record reference.
- Activate receiving, then enable sending. Create the mailboxes humans will actually use.
- Confirm SPF, DKIM, custom MAIL FROM, and a DMARC record (start at
p=noneif you are still collecting reports). - Send a handful of tests to team-controlled inboxes at Gmail, Microsoft, and Yahoo if those are real audience providers. Read the raw message: authentication results, From, Return-Path. See From, Reply-To, and Return-Path.
- Enroll the domain in Gmail Postmaster Tools so Compliance and spam-rate charts exist when volume appears.
Do not schedule the 20,000-message launch in this window.
Days 1–7 — known recipients only
Turn on the product events that already have consent baked in: password reset, email verification, receipt, “you were invited.” Staff use the same domain for real work and reply when customers reply. Keep From addresses stable by category (receipts@, security@, a person’s mailbox)—see receipts should come from an address people can reply to and stop sending from noreply@.
Hard rules for week one:
- No purchased lists.
- No sudden marketing blast.
- No AI agent blasting from a new From address. Give agents a mailbox and a budget; see don’t let an AI agent burn your domain.
Days 8–14 — widen only if clean
Increase transactional volume gradually as real product usage grows. Watch:
- Bounce quality (invalid addresses vs temporary deferrals).
- Gmail Postmaster spam rate once volume is high enough to plot.
- Authentication failures and unusual 4xx deferrals.
last_event=sent in ArawaMail means the platform accepted and processed the message. It is not inbox placement. For how to test before a major send without treating seed inboxes as truth, use how to test inbox placement.
Days 15–28 — ramp toward expected production
Add less-engaged but opted-in recipients only after complaints stay low. If you must announce a launch, send it as a smaller, clearly subscribed message after the transactional stream already looks ordinary—or put it on a marketing subdomain that you warm the same way, later.
Pause the ramp if you see authentication failures, blocklist hits, unusual deferrals, or a spam-rate climb toward 0.10%. At or above 0.30% on Gmail, stop experimenting and request human review; mailbox providers will not treat more volume as the fix.
Metrics that matter now that reputation badges are gone
| Signal | Why it matters | Stop if… |
|---|---|---|
| SPF / DKIM / DMARC alignment | Identity is table stakes | Any production failure after go-live |
| Gmail user-reported spam | The threshold that still has teeth | Trend toward 0.10%; emergency at 0.30%+ |
| Compliance / Deliverability analysis in Postmaster v2 | Replaces the old High/Medium/Low badges | Verdicts degrade while you are still ramping |
| Hard bounces to never-valid addresses | Looks like a bad list, not a new domain | Rate jumps after you widen recipients |
| Human replies on the same domain | Shows the domain is a real organization | Staff never send from it |
ArawaMail last_event | Confirms acceptance only | You treat sent as “in inbox” |
If mail still lands in spam after a clean ramp, diagnose content and list quality with why your emails go to spam. Use the free email tools hub for DNS and authentication checks.
When to stop and get a human involved
- Authentication that passed in staging fails in production.
- Spam rate approaches 0.10% while you are still adding volume.
- A blocklist or sudden wave of deferrals appears after a content or list change.
- Someone scheduled marketing from the same new From address that just started sending OTPs.
More volume on a hurting domain is how Q4 turns a dirty domain into a quarter of missed receipts. That story belongs to the next piece in this series; this article only owns the first weeks.
FAQ
Is a 14-day warmup enough?
Sometimes. Low-volume transactional mail to known users can look normal in a week. High-volume or mixed marketing streams often need closer to four weeks. The calendar is a frame; the spam rate and bounce quality are the decision.
Can I warm up only with seed inboxes?
No. Seeds do not complain like customers and do not represent Gmail’s personal-inbox population. Use them as a canary, not as the warmup.
Does passing DMARC mean I can send 20,000 messages tomorrow?
No. DMARC is identity. Warmup is behavior.
Should marketing and transactional share the new domain on day one?
No. Start with wanted product mail and staff replies. Add subscribed marketing later, preferably on a subdomain.
Does ArawaMail run warmup or seed tests for me?
No. ArawaMail hosts the domain, mailboxes, and sending API. The ramp is an operating plan you run with real product events.