Sales and marketing news, data and thoughts for people who make things.

Guide · ABM and Outbound

35 of 75 manufacturers' email domains enforce no DMARC policy

If IT has published two SPF records for your domain, as two of the 75 manufacturers have, SPF cannot pass for any email your reps send.

A woman in a navy cardigan, seen partly from behind beside a window onto a yard of stacked wood pallets and a flatbed trailer, holds a mug at an oak desk, talking with a gray-bearded man in a maroon flannel shirt seated behind it at a keyboard and monitor.
A marketing manager talks with the plant's IT administrator at his desk in an office beside the shipping yard.

When a rep’s sequence starts landing in junk folders or bouncing, the list and the copy get the blame first, but cold email deliverability also depends on three DNS records your IT team controls: SPF, DKIM and DMARC. Of 75 US manufacturers’ domains we read, 35 either publish no valid DMARC record or publish one set to p=none, which asks receiving mail servers to take no action when a message claiming to come from that domain fails authentication. Thirty-one of the 75 publish no address for DMARC reports, so they cannot see which systems are sending mail as them.

The Gmail, Yahoo and Outlook.com rules that made DMARC a requirement for bulk senders govern mail to consumer inboxes, and they ask for no more than p=none. Moving past it means finding every system that sends as your domain and making each one authenticate, starting with the CRM and the sales engagement tool your sales team sends from.

What 75 manufacturers publish for DMARC

Seventeen of the 75 domains publish p=reject, which asks receivers to refuse mail that fails DMARC, and 23 publish p=quarantine, under which receivers treat failing mail as suspicious. Twenty-three publish p=none. Twelve have no valid DMARC record: 11 publish nothing at _dmarc, and one publishes a record that begins “=DMARC1” without the “v”, which RFC 7489, the DMARC specification, says receivers discard. None of the 75 publishes two DMARC records, which the same section says would also stop DMARC processing.

The policy covers only part of the failing mail at three of the 40 enforcing domains, whose pct values are 5, 10 and 25. Microsoft’s DMARC setup guide says values under 100 are for “testing and tuning” and that a record without pct counts as 100. Three enforcing domains also set sp=none, which RFC 7489 says “applies only to subdomains of the domain queried and not to the domain itself,” so their subdomains go unenforced.

A rua tag tells receivers where to send daily aggregate reports of who sent mail using your domain and whether it passed. Of the 23 p=none records, 11 carry no rua address, so those companies are neither enforcing nor collecting the reports that would let them start. Eight of the enforcing domains also publish no rua address.

Fig. 01DMARC policy published by 75 manufacturers' domains, by industry section
SectionDomainsp=rejectp=quarantinep=noneNo valid record
All 757517232312
Metals and Machining204583
Plastics and Rubber102530
Industrial Machinery and Equipment245676
Automation and Industrial Tech112351
Building Products62202
Industrial Distribution42200

"No valid record" includes one malformed record. Three quarantine records apply to 5 to 25 percent of failing mail. Section counts are too small for comparing industries. Source: Plant to Pipeline read of 75 manufacturers' public DNS records, Nov. 18, 2026.

Two SPF records break SPF for every message

SPF lists the servers allowed to send mail for a domain. The record ends in -all at 40 of the 75 domains, so receivers are told to fail mail from any server it does not list, and in ~all at 31, which marks such mail as a softfail. Two domains publish no SPF record. Two more publish two separate SPF records, each naming a different sending service, and RFC 7208, the SPF standard, says “A domain name MUST NOT have multiple records that would cause an authorization check to select more than one record.” Under its record-selection rule, more than one record produces a “permerror” result, so SPF cannot pass for any message the domain sends, from any tool.

The choice between -all and ~all matters less than these errors. DMARC passes when either SPF or DKIM passes and lines up with the From address, so a domain with two SPF records can still pass through DKIM from tools that sign with its domain.

One domain in the set shows the setup for a domain that sends no mail. Nercon’s website domain, nerconconveyors.com, has no mail server, an SPF record of “v=spf1 -all” and a DMARC record at p=reject, so no server may send as it. The company’s mail domain, nercon.com, also publishes p=reject.

Which Gmail, Yahoo and Microsoft sender rules apply to cold email

Google’s email sender guidelines cover “personal Gmail accounts”, addresses ending in @gmail.com or @googlemail.com. Since Feb. 1, 2024, every sender to them must “Set up SPF or DKIM email authentication for your sending domains” and keep spam rates in Postmaster Tools “below 0.3%”. Senders of more than 5,000 messages a day must also set up SPF and DKIM and DMARC, and “Your DMARC enforcement policy can be set to none.”

Yahoo’s sender requirements ask all senders to “Implement SPF or DKIM at a minimum” and bulk senders to “Publish a valid DMARC policy with at least p=none” and “Honor unsubscribes within 2 days.” Yahoo’s FAQ applies them to “all domains and consumer email brands hosted by Yahoo Mail”, defines a bulk sender as one “sending a significant volume of mail” and says “We will not specify a volume threshold.”

Microsoft’s post on Outlook’s high-volume sender requirements, published April 2, 2025, covers hotmail.com, live.com and outlook.com addresses and domains sending more than 5,000 emails a day. SPF and DKIM must pass and DMARC must be “At least p=none”. Its April 29 update says failing messages will be rejected, though an older passage on the page still describes routing them to Junk first.

A rep sending 40 emails a day to engineers and buyers at other manufacturers is far below the 5,000-a-day lines Google and Microsoft draw, and most of those recipients use company mailboxes. Of the 75 domains we read, 33 point their MX records at Microsoft 365, 10 at Google and 17 at one of three email security gateway providers. If your buyers look like these companies, your outbound lands in a corporate system that runs its own filtering. The consumer rules still reach a sales team in two ways: any send to an @gmail.com or Yahoo-hosted address falls under that provider’s all-sender rules at any volume, and corporate filters check the same authentication.

What p=none means for spoofing and for your own outbound

Microsoft’s DMARC setup guide shows how Microsoft 365 treats incoming mail that fails DMARC when its “Honor DMARC record policy” setting is on, which Microsoft recommends. Mail from a p=reject domain is “Rejected during SMTP”, mail from a p=quarantine domain goes to the Junk Email folder by default, and for p=none there is “No DMARC-specific action. Other filtering still applies.” So if someone forges your sales manager’s address in a message to a distributor on Microsoft 365, your DMARC policy decides whether that distributor’s system refuses it outright or leaves it to the spam filter. Your own outbound is judged on whether it authenticates, along with your sending reputation and content; the policy you publish tells receivers only what to do with mail that fails.

Microsoft’s post for high-volume senders tells senders using outside email vendors that “authentication is tied to your domain,” and calls p=reject “the most effective at thwarting domain spoofing” once legitimate sources are aligned, advising a gradual move from none to quarantine to reject. Along the way, the rua reports show you the CRM, the marketing platform, the ERP that emails invoices and the website form that send as your domain without passing.

CAN-SPAM applies to cold sales email

The FTC’s CAN-SPAM compliance guide says, “The law makes no exception for business-to-business email.” A commercial message must carry accurate header information, a valid physical postal address and a clear way to opt out, and opt-out requests must be honored within 10 business days. “Each separate email in violation of the CAN-SPAM Act is subject to penalties of up to $53,088.” The guide says the responsibility stays with your company when another firm sends the email for you.

What to ask IT for, in order

  1. The current records: the SPF TXT record at your domain, the TXT record at _dmarc.yourdomain.com and the DKIM selectors in use. You can read the first two yourself at dns.google/resolve with type=TXT.
  2. A list of every system that sends as your domain: the mail platform, CRM, marketing automation, sales engagement tool, ERP, website forms, quoting tool and any distributor or dealer portal.
  3. One SPF record that includes every sender on that list. If you find two, merge them. Microsoft’s FAQ warns that more than 10 DNS lookups can make the SPF check fail.
  4. DKIM signing with your own domain turned on in each of those systems.
  5. A DMARC record at p=none with a rua address that someone reads, if you have no record or no rua today.
  6. A move to p=quarantine and then p=reject once the reports show every legitimate sender passing, with pct removed or set to 100 at the end.
  7. “v=spf1 -all” and p=reject on any domain you own that sends no mail.

Before the next sequence goes out, add your postal address and an opt-out line to every template. The target account list guide covers which accounts belong on the list, and the CRM guide covers which system should be the record for each contact, which is where an opt-out has to be stored.

How we did this

On Nov. 18, 2026, we read the SPF and DMARC TXT records and the MX hosts of the website domains of 75 US manufacturers across six industry sections, the same companies as our Nov. 16 paid search sample. Each domain was read through Google Public DNS and again through Cloudflare’s DNS over HTTPS service, twice that day, and the reads agreed on every SPF and DMARC record. We counted a DMARC record missing its “v” tag as no record and two SPF records as an error. For one company the website domain is not its mail domain. DKIM was not checked, because its keys sit under selector names a domain does not publish. Seventy-five companies are a sample and do not describe all manufacturers.

Sources

  1. Google, Email sender guidelines
  2. Yahoo, Sender best practices
  3. Yahoo, Sender FAQs
  4. Microsoft Tech Community, Outlook's new requirements for high-volume senders (April 2, 2025)
  5. Microsoft Learn, Set up DMARC
  6. FTC, CAN-SPAM Act: A Compliance Guide for Business
  7. RFC 7208, Sender Policy Framework (SPF)
  8. RFC 7489, Domain-based Message Authentication, Reporting, and Conformance (DMARC)
  9. Google Public DNS JSON resolver
  10. Cloudflare DNS over HTTPS

See an error? Email editor@planttopipeline.com with what is wrong. We fix errors and log them on the corrections page.

Filed under

Filed under

The Tuesday issue

One idea, one number and one example from a company like yours. Every Tuesday, under five minutes.

We use your email to send our newsletter and marketing emails. Unsubscribe anytime. Read our privacy policy.