Skip to main content
NewNMC’s advertising guidelines for doctors are in force from 6 Oct 2026. See what to change, and get a free compliance auditNew NMC advertising rules for doctors: what to change
AI & Automation

Email Deliverability for Hospitals: SPF, DKIM, DMARC and the Bulk Sender Rules

How to authenticate a hospital domain that sends from several systems, what Gmail and Yahoo require of bulk senders, and how to audit sources, alignment and unsubscribe headers.

Email Deliverability for Hospitals: SPF, DKIM, DMARC and the Bulk Sender Rules

This article is for hospital marketing and IT teams whose emails, such as appointment confirmations, patient newsletters, lab-report notices and bills, are landing in spam or not arriving. It is also for anyone told by a vendor that the domain needs "SPF, DKIM and DMARC" without being told what that means in a hospital with half a dozen systems sending as the same name.

Hospitals are harder to authenticate than most businesses. The hospital information system sends billing mail. A diagnostics platform sends reports. The CRM or email platform sends newsletters. The website form plugin sends enquiries. The corporate mailbox sends everything else. Each of them may claim to be the hospital's domain, and each needs authorising separately. Miss one and its mail fails authentication, which now has consequences that did not exist a few years ago.

We cover the three protocols, the current sender requirements from Gmail and Yahoo, a method for inventorying your sources, and the headers needed for unsubscribe. A sister article walks through the phased move to a strict DMARC policy.

Why this matters more since 2024

Gmail and Yahoo introduced requirements for bulk senders in early 2024. Google's email sender guidelines say that senders who send more than 5,000 messages a day to Gmail accounts must meet additional requirements, on top of baseline rules that apply to every sender. A hospital with a patient newsletter and daily appointment mail can cross that line without noticing, since the count is per sending domain across all systems.

The baseline and bulk requirements overlap in these areas:

  • Authentication. All senders need SPF or DKIM. Bulk senders need SPF, DKIM and DMARC. Google states that the DMARC policy can be set to none.
  • Alignment. For direct mail, the domain in the visible From address must align with the SPF domain or the DKIM domain.
  • DKIM key length. Google requires a key of 1024 bits or longer for personal Gmail recipients and recommends 2048 bits if your provider supports it.
  • TLS and DNS. Mail must travel over TLS, and sending IPs need valid forward and reverse DNS.
  • Unsubscribe. Marketing and subscribed messages must support one-click unsubscribe and carry a clearly visible unsubscribe link in the body.
  • Complaint rate. Google asks senders to keep their spam rate in Postmaster Tools below 0.10 percent and to avoid reaching 0.30 percent or higher.

Yahoo's sender best practices set out a parallel list. Bulk senders implement SPF and DKIM, publish a DMARC policy of at least none, support one-click unsubscribe, honour unsubscribes within two days and keep complaints below 0.3 percent. Yahoo's page does not define a numeric volume threshold for bulk senders, so a hospital should assume the rules apply once it sends meaningful volume.

Large hospital chains will often be bulk senders by volume. Smaller clinics may not be, but the same setup protects their mail from being spoofed, so it is worth doing regardless.

The three protocols in plain terms

SPF (Sender Policy Framework) is a DNS record that lists which servers may send mail for your domain's envelope address. Receivers check whether the connecting server is on the list.

DKIM (DomainKeys Identified Mail) adds a cryptographic signature to each message. The sending system signs with a private key, and the receiver verifies using a public key published in DNS at a name of the form selector._domainkey.yourdomain.

DMARC (Domain-based Message Authentication, Reporting and Conformance) ties them together. It requires that the domain the reader sees in the From field aligns with either the SPF or DKIM domain that passed, and it tells receivers what to do with failures: nothing, quarantine or reject. It also requests reports. The tags are defined in RFC 7489, including the policy tag p, the subdomain policy sp, the report address rua and the alignment modes adkim and aspf.

The detail that trips up hospitals is alignment. SPF can pass for the vendor's bounce domain, and DKIM can pass for the vendor's own domain, while neither matches the From address your patient sees. That mail passes the individual checks and still fails DMARC. The fix is to have the vendor sign with your domain (a custom DKIM selector) and, where possible, to use a custom return-path domain.

Inventory every system that sends as your domain

Begin with a source inventory, not DNS edits. Collect:

  1. Every system that sends mail with an address on your domain in the From field: HIS, LIS and radiology systems, patient portal, appointment engine, CRM, email marketing platform, payment gateway, careers site, website forms, helpdesk, and the mailboxes in Google Workspace or Microsoft 365.
  2. For each, the owner (internal or vendor), the sending domain or subdomain, the approximate monthly volume and the purpose.
  3. Whether the system supports a custom DKIM selector and a custom return-path.

Then check the evidence. The best source is DMARC aggregate reports, which you start receiving once you publish a record with an rua address. Even at p=none, they list every IP and source that sent mail claiming to be your domain, with pass or fail results. Expect surprises: an old survey tool, a shared mailbox used by a department, and a vendor that a previous team set up without telling IT.

Use subdomains to separate mail streams

A clean architecture is to separate streams by subdomain:

StreamExample subdomainWhy
Corporate mailboxesRoot domainStaff email, highest trust
Transactional alertsalerts.Confirmations, OTPs, reports
Marketing and newslettersnews.Complaint-prone, isolated reputation
Vendor-managed systemsPer vendorEasier to revoke

Each subdomain has its own SPF and DKIM. DMARC at the root can apply to subdomains through sp, or each subdomain can publish its own record. The point is that a complaint spike on the newsletter should not damage the delivery of appointment confirmations. Google's guidance on DMARC setup notes that subdomains inherit the parent policy unless sp is set, and that strict alignment can reject mail from subdomains you do not control.

Want this applied to your practice? Get a free ai & automation audit.

Book my free audit

Building SPF without breaking it

An SPF record is a TXT record at the root of the sending domain. A hypothetical example for a hospital using Google Workspace and one email platform looks like this:

v=spf1 include:_spf.google.com include:mail.example-esp.com -all

Three practices matter.

Respect the lookup limit. RFC 7208, section 4.6.4, limits SPF evaluation to ten DNS-querying terms, counting include, a, mx, ptr, exists and redirect. Exceeding the limit produces a permanent error, and a receiver may treat the mail as failing. Hospitals with many vendors reach this limit easily. When you are near it, move streams to subdomains instead of stacking every include on the root.

Publish one record per domain. Two SPF records on the same name produce an error. Merge them.

Start with softfail, end with a decision. Many teams begin with a softfail qualifier while they gather data, then move to a hard fail once the inventory is complete. Do not leave it at the softfail position indefinitely.

Building DKIM correctly

For each sending system:

  • Generate a 2048-bit key if the system supports it, or at least 1024 bits to meet Gmail's minimum.
  • Publish the public key as a TXT or CNAME at the selector name the vendor provides.
  • Check that the signing domain (the d= value) is your domain or a subdomain, not the vendor's. Otherwise alignment fails.
  • Rotate keys on a schedule and keep a register of selectors and owners.

Many platforms also sign with a default key under their own domain. That signature can pass while being useless for DMARC. Look for the aligned one in message headers: the DKIM-Signature header with your domain, and an Authentication-Results line showing dkim=pass with your domain.

One-click unsubscribe headers

For marketing and subscribed mail, add the headers that make unsubscribe a single action. RFC 8058 defines List-Unsubscribe-Post: List-Unsubscribe=One-Click alongside an HTTPS List-Unsubscribe URI. The same document requires those headers to be covered by a valid DKIM signature and says the sender must not respond with a redirect. Most email platforms offer this setting. Confirm it by sending a test to a Gmail inbox and looking for the unsubscribe control beside the sender name.

Honour unsubscribes quickly and consistently across systems. If the newsletter platform and the CRM keep separate lists, a patient who unsubscribed in one will still receive mail from the other.

Do not put one-click unsubscribe on transactional mail such as a lab report notice. Keep transactional and marketing separate, which is another reason for the subdomain split. Our transactional email service explains how.

Monitoring after setup

  • Register the domain in Google Postmaster Tools and watch the spam rate against the thresholds above.
  • Read DMARC aggregate reports weekly, using a reporting tool or a dedicated mailbox, since raw XML is not practical.
  • Track bounce types: unknown user versus blocked.
  • Test new systems before first send by checking headers for aligned SPF or DKIM.
  • Keep an owner for the inventory. Deliverability decays when new vendors are added without a check.

If your newsletters also carry patient information, review the privacy angle, as covered in our guide to healthcare email marketing. Authentication stops spoofing but does not make a message appropriate to send.

Where to start

  1. Build the sender inventory with owners.
  2. Publish a DMARC record at p=none with an rua mailbox, which collects evidence without affecting delivery.
  3. Fix alignment system by system, starting with the highest volume and the highest patient impact.
  4. Separate marketing and transactional streams onto subdomains.
  5. Add one-click unsubscribe to marketing mail.
  6. Check Postmaster Tools weekly.
  7. Plan the move to enforcement once reports are clean.

Our email deliverability service can audit the current setup. Requirements from mailbox providers change, so check the Google and Yahoo pages before relying on any threshold in this article.

Filed underemail deliverability hospital dmarcspf dkim dmarc hospital domaingmail yahoo bulk sender requirementshospital email going to spamone-click unsubscribe list-unsubscribe

About the author

Co-Founder & CTO · Gurugram, India

Arush builds the systems the rest of the company runs on — the patient-acquisition pipelines, the AI chatbots, the analytics that tie a single click to a booked appointment. If a campaign reports a number, it's because something his team built is tracking it.

Free guide · 15 pages

The Patient Acquisition Blueprint

A 90-day plan from first search to booked appointment.

The Pioneers Brief — one essay, three benchmarks, one teardown, every Thursday. Subscribe free →

Free ai & automation audit

Your next chapter starts with a conversation.

Three quick questions. We come prepared with a plan for your specialty and city.

  • A 30-minute call with a healthcare specialist
  • Your top three growth opportunities, in writing
  • Honest advice — even if that means not hiring us
  • No obligation and no hard sell
You’ll speak with a senior strategist
Consultations are hosted by Arush Thapar’s team.
Step 1 of 3Takes 30 seconds

What do you want to improve first?

Details stay privateNo obligationReply within 1 working day

Client portfolio · BTL & activations

Work relevant to email deliverability for hospitals spf dkim dmarc and the bulk.

Explore client work →