HVAC tune-up emails go to spam most often because of how they are sent rather than what they say. Gmail and Yahoo both require bulk senders to authenticate mail with SPF and DKIM, publish a DMARC record, align the From domain with whatever signed the message, and offer one-click unsubscribe on marketing mail.
What gets checked before a reader ever sees the subject line
Four things decide delivery before the content matters: whether the sending domain authenticates, whether the From address lines up with what signed the message, whether the list can be left in one click, and what share of recipients mark the mail as spam. Gmail and Yahoo both publish those requirements, as of October 2026.
The split that most advice misses is between what every sender has to do and what a bulk sender has to do. Google's sender guidelines ask all senders for SPF or DKIM, and ask bulk senders for SPF, DKIM and DMARC together. Both documents cover mail to personal Gmail accounts rather than to Google Workspace recipients, which is most of a maintenance list.
| Requirement | Every sender | Bulk sender | Where it actually lives |
|---|---|---|---|
| Authentication | SPF or DKIM | SPF and DKIM both, plus a DMARC record at p=none or stricter | DNS on your sending domain |
| From alignment | Recommended | The From domain aligns with the SPF or DKIM domain | The message header against the signing domain |
| One-click unsubscribe | Not required | A List-Unsubscribe header supporting one click | The header your sending platform writes |
| Honoring opt-outs | No platform deadline stated | Within 48 hours (Google), two days (Yahoo) | Your list, and the platform holding it |
| Spam complaint rate | Below 0.3% | Below 0.3%, and Google says to stay under 0.1% | Postmaster Tools, daily |
| Connection and DNS | TLS, valid forward and reverse DNS | Same, enforced with a 5.7.29 error | Your mail server or sending platform |
Google puts the bulk threshold at roughly 5,000 messages to Gmail accounts in a 24-hour period, totaled by primary domain, so mail from a subdomain counts toward the same figure. That is worth knowing before a shop decides it is safely under: a 4,000-name list sent twice in a day is not.
SPF, DKIM and DMARC, in the order to set them up
SPF, DKIM and DMARC are three DNS records answering three different questions: which servers may send for your domain, whether the message carries a valid signature from that domain, and what a receiver should do when the first two disagree with the From address. All three live in DNS rather than in your email tool.
Order matters because each depends on the last. SPF lists the sending sources. DKIM signs the message, and Google requires a key of at least 1,024 bits for mail to personal Gmail accounts, recommending 2,048 where the DNS provider supports it; Yahoo states the same minimum. DMARC then tells receivers what to do with a failure, and a policy of p=none satisfies both platforms, as of October 2026.
The From header is where a shop sending through a platform fails
Alignment is the requirement a shop fails without changing a word of its email. Google and Yahoo both ask that the From domain match whichever domain passed SPF or DKIM. A reminder addressed from your own domain but signed only by the platform sending it does not align, and DMARC reads that as a failure even though both checks passed.
That is the common shape for a shop whose dispatch software sends the reminders: the mail is authenticated, just not for the domain in the From line. The fix is a DNS record rather than a subject line. Ask the platform for the CNAME or DKIM key that signs your sending domain, then confirm the two match. Yahoo accepts relaxed alignment, so a subdomain of your own domain is enough.
One-click unsubscribe is a header, not the link in the footer
One-click unsubscribe is a message header rather than the link at the bottom of the email. Google asks bulk senders to send marketing mail with an RFC 8058 List-Unsubscribe header carrying a single HTTPS URL, says an unsubscribe link in the body does not satisfy the requirement on its own, and asks that requests be honored within 48 hours.
Yahoo lands in the same place with a different emphasis: it recommends the RFC 8058 POST method most strongly, accepts a mailto address, expects a visible body link as well, asks that requests be processed within two days, and states that unsubscribing must not require a login. Building to the stricter reading satisfies both.
The complaint rate that decides the next send
Spam complaint rate is the number that decides whether the next blast arrives at all. Google says to keep it under 0.1% and never let it reach 0.3%, calculated daily in Postmaster Tools, and Yahoo asks senders to stay below 0.3% as well. A sender above 0.3% stops being eligible for mitigation until it posts seven consecutive days underneath it.
The defense is segmentation rather than volume control: send to customers with a service record and a reason to hear from you this month, stage by last service date, and register the domain in Postmaster Tools, whose compliance dashboard Google makes available to every sender rather than only to bulk ones.
What to check before the heating reminder goes out
Check the sending side before the seasonal reminder goes out rather than after it underperforms. The heating blast is the year's largest send for most Charlotte shops, and a maintenance list that has sat untouched since spring is the one most likely to generate complaints, because nobody on it has heard from you in six months.
- 1Pull the DNS records for your sending domain and confirm SPF, DKIM and DMARC all resolve, instead of trusting a green check in your email tool.
- 2Send one test to a personal Gmail address and read the raw headers: SPF pass, DKIM pass, and the signing domain next to your From domain.
- 3Confirm a marketing send carries the List-Unsubscribe header and that the link works without a login.
- 4Read the Postmaster Tools compliance dashboard before the send, not after the complaints.
- 5Stage the send by last service date so a bad segment cannot take the whole domain with it.
- 6Write the heating message for a heat pump and aux heat, because relevance is what keeps complaints down.
That last point is not a style note. The 2020 Residential Energy Consumption Survey counted 1.54 million North Carolina homes on a central heat pump as main heating equipment, 38% of the state's 4.01 million, so one box carries both seasons here. A fall message about equipment much of your list does not own reads as mass mail, and mass mail gets reported.
Whose name is on the sending domain when the reminders run?
Whose name is on the Business Profile, the ad accounts and the sending domain is the question to settle before the first reminder goes out. Here the DNS records sit on the shop's own domain, the list and consent records stay in the shop's name, and the authentication travels with the shop on the day the relationship ends.
Built out, the sending side is four parts: the three DNS records on your domain, a platform signing as that domain, a List-Unsubscribe header on every marketing send, and a segment read off the job record so the message has a reason to exist. Mirastart builds those as software and runs the marketing on top, which is why the reminder, the booking link inside it and the report naming what it produced are one project rather than three vendors.
The same mechanics are visible before you call: the Carolina Sky Painting website, the online booking and repair-status software Quick Auto NC runs its bays on, the live-availability booking behind this site's own discovery-call page, and the Sushi Hana Club app.
Sources
- Google, Email sender guidelines (Gmail Help) - Requirements for all senders (SPF or DKIM, TLS, valid forward and reverse DNS, RFC 5322 formatting, a DKIM key of at least 1,024 bits with 2,048 recommended) and the added bulk-sender requirements (SPF, DKIM and DMARC together, From alignment, one-click unsubscribe). Read October 2026; Google notes the guidelines cover mail to personal Gmail accounts rather than Google Workspace recipients.
- Google, Email sender guidelines FAQ (Gmail Help) - The bulk-sender threshold of roughly 5,000 messages to Gmail accounts in a 24-hour period totaled by primary domain; spam rate kept under 0.1% and never reaching 0.3%, with mitigation eligibility regained after seven consecutive days below it; RFC 8058 one-click unsubscribe on marketing mail with requests honored within 48 hours. Read October 2026.
- Yahoo, Sender Best Practices - Yahoo's own requirements: SPF and DKIM with a 1,024-bit minimum key, a passing DMARC record at p=none or stricter, From alignment with relaxed alignment accepted, a rua address recommended during setup, List-Unsubscribe with the RFC 8058 POST method preferred, a visible body link, no login to unsubscribe, requests processed within two days, complaints below 0.3%, and marketing mail separated from user and transactional mail by IP or DKIM domain. Read October 2026.
- Google, Postmaster Tools dashboards (Gmail Help) - The dashboards behind the numbers above, including the compliance status view covering DMARC, one-click unsubscribe and honoring unsubscribes. Read October 2026.
- U.S. Energy Information Administration, Highlights for space heating in U.S. homes by state, 2020 (RECS) - North Carolina: 4.01 million homes, 1.54 million (38%) with a central heat pump as main heating equipment. 2020 survey year; final data released March 2023.