A B2B email can be useful and well written and still never get read, because it landed in spam or was rejected before it arrived. Mailbox providers have tightened their rules in recent years, and a domain set up carelessly can damage everything from your newsletter to your sales team's replies. The technical foundation is three DNS records: SPF, DKIM and DMARC. They are not hard to set up, but they are easy to get wrong, especially when a marketing tool, a CRM and a cold email platform all send on your behalf. This guide takes you through setup, testing and the reputation habits that matter just as much. For current rules, keep [Google's email sender guidelines](https://support.google.com/a/answer/81126) to hand.
What do SPF, DKIM and DMARC do?
Each one answers a different question for the receiving mail server.
| Record | Question it answers | How it works | Common mistake |
|---|---|---|---|
| SPF | Is this server allowed to send for this domain? | A DNS TXT record listing authorised senders | Two SPF records, or more than 10 DNS lookups |
| DKIM | Was this message signed by the domain, and is it unchanged? | A cryptographic signature checked against a public key in DNS | Tool sends with its own domain rather than yours |
| DMARC | What should happen when checks fail, and do the domains align? | A DNS policy, with reports sent to you | Staying at p=none forever, and never reading the reports |
Read the transcript
The lead came in at 9:02. Nobody called. You paid for that enquiry. It should not depend on someone checking a sheet.
Leads sit in inboxes, sheets and phones. Nobody is sure who should call. By the time someone does, the buyer has moved on.
Leads should not rely on someone remembering.
Every lead lands in one CRM. Routing and first contact happen automatically. Reps get a clear next step instead of a chase.
CRM and automation, with Rahul D Sarker. Book a call at rahuldsarker.co.
What does Gmail require from email senders?
Google's sender guidelines are the benchmark most teams work towards, and other providers have similar expectations. As they stand now:
All senders to personal Gmail accounts should:
- Set up SPF or DKIM for sending domains.
- Have valid forward and reverse DNS for sending IPs.
- Use TLS.
- Keep the spam rate in Postmaster Tools below 0.3%, with a recommended target below 0.1%.
- Follow standard message format rules, and avoid impersonating Gmail in the From header.
Senders of 5,000 or more messages a day to Gmail must also:
- Use SPF and DKIM, and publish a DMARC record. The policy can be set to none.
- Align the From domain with SPF or DKIM.
- For marketing and subscribed messages, support one-click unsubscribe and include a visible unsubscribe link in the body.
Even if you send far less, follow the larger sender rules. They are good practice, they protect you as you grow, and B2B recipients on Google Workspace or Microsoft 365 also rely on authentication. Check each provider's current rules, because these standards keep changing.
Step 1: list everything that sends email
Most setup errors happen because someone forgot a tool. Before touching DNS, list every system that sends email using your domain:
- Google Workspace or Microsoft 365.
- CRM and marketing automation: HubSpot, Zoho, Salesforce or similar.
- Newsletter tools.
- Transactional email, like app notifications or invoices.
- Sales engagement or cold email tools.
- Support desks.
- Website forms, booking tools and e-commerce platforms.
- Agency tools.
For each, record the sending domain or subdomain, who owns it, and whether it supports DKIM with your own domain. Then decide on a domain structure. A common and sensible pattern:
- yourdomain.com for human email and important business messages.
- mail.yourdomain.com or news.yourdomain.com for marketing.
- notify.yourdomain.com for transactional messages.
- A separate domain for cold outreach, if you do it. See below.
Separate subdomains help isolate reputation and make the reports easier to read, although reputation can still be linked to your parent domain, so subdomains are not a licence to send poor email.
Step 2: set up SPF
SPF is a TXT record on your domain listing who may send. A typical record for Google Workspace and one other sender might look like this:
v=spf1 include:_spf.google.com include:sendgrid.net ~all
Rules to follow:
- Publish only one SPF record per domain. Two records can cause SPF to fail. Merge them.
- Stay within 10 DNS lookups. Each include counts, along with what it nests. Exceed this and SPF returns an error. Remove old tools, and use subdomains if you hit this limit.
- End with ~all or -all. ~all (soft fail) is the common choice during setup. Tighten it once you are confident you have listed everything.
- Use each vendor's official value. Copy from their documentation.
- Remove old vendors. Every leftover include gives another company's systems some sending authority, and uses up lookups.
Remember that SPF checks the technical "envelope" sender and can break when mail is forwarded. That is one reason DKIM matters so much. SPF on its own is not sufficient.
Step 3: set up DKIM
DKIM attaches a signature that receiving servers can verify using a public key in your DNS. It usually survives forwarding, which makes it important for DMARC.
The steps vary by tool, but follow the same pattern:
- In the tool's admin area, find the domain authentication or DKIM section. In Google Workspace, it is under Gmail authentication in the admin console. In HubSpot and Zoho, it sits under domain settings.
- The tool gives you a selector and a value to publish, usually as a TXT or CNAME record.
- Add it in your DNS, wait for propagation and then click verify or start authentication.
- Send a test and confirm the signature uses your domain.
Check these:
- Use a key of at least 1024 bits. Google recommends 2048 bits where your system supports it.
- Make sure each sender signs using your domain or subdomain. A signature using the tool's domain will pass DKIM, but will not align with yours for DMARC.
- Rotate keys periodically, and remove old selectors for tools you no longer use.
- If you use a subdomain to send, set up DKIM for that subdomain.
Do this for every sending tool from your list, and test each one.
Step 4: set up DMARC and move towards enforcement
DMARC ties it all together. It checks that SPF or DKIM passes and aligns with the visible From domain, then tells receivers what to do if it fails. It also sends you reports.
Publish a TXT record at _dmarc.yourdomain.com. A starting point:
v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com
Move through three stages:
- Monitor (p=none). Nothing is blocked. Read the aggregate reports for a few weeks to find every legitimate sender. These reports are XML files, so use a DMARC analysis tool to read them.
- Quarantine (p=quarantine). Failing messages may go to spam. Start with a percentage if you need to, by adding pct=25, for example, and check what happens.
- Reject (p=reject). Failing messages are refused, which gives the strongest protection against spoofing.
Do not rush. Moving to reject before fixing every tool can block your invoices or customer emails. But do not stay at none indefinitely either, as you get reports but no protection. For many B2B firms this is also a security improvement, because attackers often impersonate company domains to commit invoice fraud.
Step 5: test it
Do not rely on tool screens saying "verified". Test real messages.
- Send to a personal Gmail account. Open the message, click "Show original" and check that SPF, DKIM and DMARC all pass, and for which domain.
- Test each sending tool. Your CRM, newsletter and support tool can all behave differently.
- Use a DNS checker. Look for syntax errors, duplicate SPF records and too many lookups.
- Set up Google Postmaster Tools. Verify your domain to see spam rate and authentication data. It needs a reasonable volume to show results.
- Check Microsoft recipients too. Many B2B buyers use Microsoft 365. Their Sender Network Data Services can help where relevant, and test sends can reveal differences.
- Test one-click unsubscribe on marketing messages, and make sure it works immediately in your tool.
- Check inbox placement. Seed tests provide only a rough signal, as individual engagement matters. Use them to spot big problems rather than to measure small changes.
Repeat these tests whenever you add a sending tool, change a domain or change agencies.
Is authentication enough for good deliverability?
Passing authentication means receivers know who you are. It does not mean they want your mail. Reputation depends on behaviour.
- Send to people who expect it. Purchased lists cause complaints, bounces and spam traps. Consent also matters legally: see our DPDP guide.
- Keep complaints low. Google asks for below 0.3%, and recommends below 0.1%.
- Remove hard bounces immediately, and validate old lists.
- Sunset inactive contacts. After a period of no engagement, reduce sending or remove them. Our email ROI calculator can help you see the value of a smaller active list.
- Warm up new domains and IPs gradually. Going from zero to thousands in a day raises flags.
- Be consistent. Sudden volume spikes look suspicious.
- Write like a person. Avoid misleading subject lines and heavy use of images with little text.
- Make unsubscribing easy. An unsubscribe is much better than a spam complaint.
- Use a recognisable sender name.
See our email marketing automation and lead nurturing services for how this fits a wider programme.
Should cold email use a separate domain?
If your sales team uses cold outreach, keep it separate. One bad campaign on your primary domain could affect normal business email, including proposals and invoices.
Sensible guardrails:
- Use a separate, clearly related domain, with its own SPF, DKIM and DMARC.
- Warm up mailboxes slowly and keep daily volume per mailbox modest.
- Verify email addresses before sending.
- Target narrowly with messages that are specific and relevant.
- Include your identity and a simple way to opt out.
- Stop contacting people who ask you to stop, across all tools.
- Track replies and complaints, and don't just count opens. Open tracking can be unreliable, and it may hurt deliverability.
Check the law in your target countries. CAN-SPAM, GDPR, UK rules and India's DPDP Act differ, and some restrict unsolicited business email. A separate domain does not change your obligations or hide who you are. Google's rules and spam filtering also apply. If you are building an outbound programme, see our broader demand generation work, which usually combines outreach with content and paid channels.
Diagnosing a sudden deliverability drop
If open rates or replies fall suddenly, or people say they are not receiving your messages, work through this list:
- Check authentication. Has anyone changed DNS or removed a record? Did a tool change its settings?
- Check the Postmaster Tools spam rate and authentication graphs.
- Check your bounce messages. They often state the reason.
- Look for a list change. Was a new list imported, or an old segment emailed?
- Look for a content or volume change. Did you send far more than usual?
- Check blocklists. Use a reputable lookup for your domain and IP.
- Separate by provider. Is the problem at Gmail, Microsoft or a specific corporate filter?
- Pause the risky stream. Protect the main stream while you investigate, and restart slowly.
Open rates alone can mislead, since privacy features can inflate them, so use clicks and replies too. If you need a review of your email, CRM and tracking together, a marketing automation audit can help you find what changed.
FAQ
Google requires it for the larger sender group, but it is still worth having at any size. It gives you reports and, once enforced, helps prevent others from impersonating your domain. Start with p=none and progress from there.
No. They prove identity and meet baseline requirements. Placement also depends on your reputation, complaints, engagement, list quality and content. Think of authentication as the entry ticket rather than the outcome.
Often, yes. A subdomain separates your marketing stream from day-to-day business email and makes reporting clearer. It does not fully isolate reputation, so you still need to send responsibly.
Usually because of alignment. DKIM may pass using your vendor's domain, while the From address uses yours. Set up custom DKIM for your domain in that tool, and retest using a real message.