How inbox placement is decided
Mailbox providers decide where a message lands from three kinds of signal: whether the sender can be authenticated, the reputation of the sending domain and IP address, and how recipients react (replies, deletes without reading, spam reports).
That makes deliverability mostly a discipline, not a trick. Authenticate your domain properly, send to people who want the mail, grow volume slowly and stop when the numbers turn bad.
Use dedicated sending domains
Cold outreach has a higher chance of complaints than the mail your team sends to customers. Send it from separate domains, often close variants of your brand name, so that a problem never touches the domain your invoices and support replies come from.
- Keep your primary domain for one-to-one mail only
- Use a separate domain, or separate sender, for opt-in marketing
- Use dedicated cold domains for outreach, and replace one that is blacklisted rather than trying to rescue it
SPF: who may send for the domain
SPF is a DNS TXT record listing the servers allowed to send mail for your domain. Receivers compare the connecting server with that list.
v=spf1 include:_spf.google.com ~all
- Publish exactly one SPF record per domain. Two records make SPF fail.
- SPF evaluation is limited to 10 DNS lookups. Every include counts, so keep the record lean.
- ~all (soft fail) is the common choice while you are setting up; -all is stricter.
DKIM: proving the message was not altered
DKIM adds a cryptographic signature to each message. The public key lives in DNS under a selector, and receivers use it to verify that the message came from your domain and was not changed in transit.
- Use 2048-bit keys where your provider supports them (MailStream checks for this)
- Publish the record at selector._domainkey.yourdomain
- Some providers need you to switch DKIM on in their admin console before they start signing
DMARC: what to do when checks fail
DMARC tells receivers what to do with mail that fails SPF and DKIM alignment, and where to send reports. Alignment means the domain in the visible From address matches the domain that SPF or DKIM authenticated.
v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com; pct=100
- Start at p=none to collect reports without affecting delivery
- After two to four clean weeks, move to p=quarantine, and later to p=reject if you want the strictest policy
- Read the aggregate reports: they reveal services sending as your domain that you forgot about
MX, reverse DNS and TLS
A domain that sends mail should also be able to receive it: publish MX records that point to a working mail host. Sending servers should have matching forward and reverse DNS and use TLS.
If you send through Google Workspace, Microsoft 365 or another hosted provider, they run the servers and handle this. If you run your own server, it is your job.
Warm up before you send cold
A brand-new domain has no reputation. Providers are wary of a new sender that suddenly mails strangers. Warm-up builds a history of normal behaviour first: real conversations, replies and a steady, modest volume.
MailStream's warm-up plan depends on the domain. A brand-new domain gets three weeks of warm-up before cold sends. A domain older than 30 days that has never sent gets a compressed plan of about two weeks. A domain that is blacklisted or scores below 40 is better replaced.
In the warm-up network, mailboxes exchange mail with each other, rescue messages that land in spam and reply, and the dashboard charts inbox versus spam per day.
Ramp volume slowly
After warm-up, increase volume gradually. MailStream starts cold sending at 5 emails a day per mailbox and adds one a day, up to that mailbox's daily limit. Daily volume is slightly randomized so that a mailbox does not send an identical number every day.
Spread volume across several mailboxes rather than pushing one to its limit. Microsoft filters are stricter, so MailStream limits recipients on Microsoft to at most 60% of a mailbox's daily volume.
Gmail and Yahoo bulk-sender rules
Since 2024, Gmail and Yahoo require more from senders who send in volume. Gmail's bulk threshold is about 5,000 messages a day to Gmail addresses, but authentication is expected of everyone.
- Authenticate with SPF and DKIM, and publish a DMARC policy (at least p=none) for bulk senders
- Make the From domain align with SPF or DKIM
- Support one-click unsubscribe with the List-Unsubscribe and List-Unsubscribe-Post headers (RFC 8058), and honour requests within two days
- Keep the spam complaint rate below 0.10% as reported in Google Postmaster Tools, and never let it reach 0.30%
- Use TLS, valid forward and reverse DNS, and keep message formatting standards-compliant
MailStream adds unsubscribe headers and a hosted unsubscribe page, keeps a suppression list that every send checks, and pauses a mailbox whose complaint rate passes 0.1%. You still have to make sure the people you mail have a reason to expect your message.
List quality
Bounces and complaints come mostly from the list. Verify addresses before sending, treat role addresses (info@, sales@) with care, remove unsubscribes and bounces permanently and prefer people with a real reason to hear from you.
MailStream pauses a mailbox automatically when its bounce rate passes 2% over at least 20 sends, a limit chosen so that a bad list is stopped early.
Write like one person writing to another
- Short plain text, one clear ask, no stacked images
- Few links, and no link shorteners
- Avoid claims and phrases that trigger filters and readers alike, such as guarantees and urgency
- Personalize with facts you can prove about the recipient, not fake familiarity
MailStream lints each step for these patterns and fact-checks AI drafts against the lead data they were written from.
Monitor, then react
- Blacklists: check sending domains and IPs, and act when one is listed
- Inbox placement: watch warm-up inbox versus spam, and run seed-list tests if you use them
- Google Postmaster Tools: domain and IP reputation for Gmail
- Your own numbers: bounce rate, complaint rate, reply rate per mailbox
If a mailbox's warm-up inbox health falls below 80%, MailStream holds its cold sends until it recovers. Take the hint: pause, find the cause, fix it, then resume.
What no tool can promise
Nobody controls what Gmail, Outlook or any other receiver does with a message, and rules change. A good tool gives you authentication checks, sensible limits and honest data. It cannot guarantee placement. Treat any product that does as a warning sign.