Understand the system before you buy it.
Short answer: cold email works when the sending infrastructure is authenticated and separate, the data is verified, the message is relevant, and replies are handled quickly. Everything below explains why.
Email infrastructure in plain language
No jargon, no vendor language. These are the terms that decide whether your campaign reaches anybody.
- DNS
- The public instruction system for a domain. It tells internet services where the website and email services are located, and which services may act for the domain.
- MX record
- Tells other mail servers where incoming email for a domain should be delivered. It affects receiving mail. It does not prove an outgoing sender is genuine.
- SPF
- A DNS text record listing the services allowed to send email for a domain, like an approved sender list. SPF alone is not enough: it checks the envelope domain and can fail after forwarding.
- DKIM
- A digital signature added to the email. The receiving server uses a public key in DNS to confirm the message was signed by the expected service and that signed parts were not changed. It is authentication, not encryption.
- DMARC
- Checks whether SPF or DKIM passes in a way that aligns with the visible sender domain, tells receivers what to do on failure, and provides reports. Roll out with monitoring first, then move toward enforcement.
- Domain alignment
- The domain a recipient sees in the From field matches, or is suitably related to, the domain authenticated by SPF or DKIM under the DMARC rules.
- CNAME record
- Makes one domain name an alias for another. Used for branded tracking domains or service verification. Use tracking carefully: unnecessary tracking can affect privacy, trust, and deliverability.
- Warm-up
- Gradually increasing sending volume from a new mailbox so receiving systems build a normal sending history for it.
- Bounce rate
- The share of messages rejected by the receiving system. High bounce rates signal poor data quality and damage sending reputation.
- Inbox placement
- Where an accepted message actually lands. A message can be accepted by a mail server and still be filed as spam, which is why delivery rate and inbox placement are not the same thing.
Authentication supports trust, but it does not guarantee inbox placement. Relevance, recipient response, reputation, and sending behaviour also matter.
What large mailbox providers expect
These are minimum controls. They do not create permission to contact a person, and they do not replace local privacy and marketing law.
Google
Requires one-click unsubscribe for certain marketing and subscribed messages sent at more than 5,000 messages per day to Gmail accounts.
Yahoo
Tells bulk senders to keep spam complaint rates below 0.3 percent.
Microsoft
Requires SPF, DKIM, and DMARC for domains sending more than 5,000 messages per day to Outlook consumer addresses.
Frequently asked questions
Blog articles, the outbound readiness assessment, and the return calculator are planned for this section.
See whether outbound fits your market and offer.
In a short strategy call, we will review your ideal customer, offer, target market, current setup, and the next practical test.
No pressure, no obligation. We will tell you if outbound is not the right channel for your offer.