Your Counterfeit Face
You sent mail as a domain you don't own. You wore someone else's identity like a coat. In the inbox, that's phishing — and The Postmaster doesn't forget a face.
Deliverability Case Study: "Your Counterfeit Face"
"Your Counterfeit Face" is the album's centerpiece — garage rock fury at maximum volume, controlled and certain. The track covers the gravest violation in The Postmaster's rulebook: spoofing. Sending mail that appears to originate from a domain you don't own is impersonation, phishing, and the most harmful act a sender can commit against the identity infrastructure that email depends on. The Postmaster doesn't explain himself here. He doesn't need to.
The Postmaster is a 10-track album based on Google's Top 10 Gmail Sender Issues — the official Gmail Help Center list of the most common sender violations. This track covers issue #9: Don't spoof.Here is the technical breakdown of the deliverability concepts detailed in the song:
Verse 1: Domain Impersonation — The Painted Car
"You painted your car to look like mine! / But you're driving on the wrong side of the line! / I can see your face right through the paint!"
- The Deliverability Context: "Painting the car to look like mine" describes display name spoofing or lookalike domain spoofing — using a display name, domain name, or visual element that mimics a trusted brand. Examples include
paypal-secure.comimpersonatingpaypal.com, or displaying "Apple Support" in the From: display name while sending fromapple-verify-id.net. The receiving infrastructure "sees through the paint" via authentication: when the claimed From: domain and the actual sending domain don't match, DMARC alignment">DMARC alignment fails, and Gmail's phishing classifier flags the message. "The wrong side of the line" is literal — spoofing crosses from spam into phishing, which triggers a different, more aggressive response from receiving infrastructure. - How Gmail Detects It: Gmail's phishing detection is separate from spam classification. It specifically looks for authentication mismatches (DMARC alignment failures), lookalike domain patterns (homograph attacks, typosquatting), and From: display names that claim affiliation with known brands while sending from different domains.
Verse 2: Forged Sending Credentials
"You forged a key to open my door! / Walking all over my hardwood floor! / I read the ledger, I know the name! / You're playing a very dangerous game!"
- The Deliverability Context: "Forged a key" describes the technical mechanics of SMTP spoofing: a sender sets their SMTP
MAIL FROM(RFC5321 envelope sender) orFrom:header to an address they don't control — forging the credential that authenticates the message. Before DMARC was widely deployed, this was trivially easy: the SMTP protocol has no native authentication requirement. "I read the ledger, I know the name" is DMARC working as designed: aggregate reports (rua=) show The Postmaster exactly which senders are claiming a domain and whether their authentication passes. DMARC atp=rejectcloses the door — forged mail is blocked before it reaches recipients. - The Criminal Dimension: Email spoofing for the purpose of deceiving recipients into providing credentials, financial information, or system access is phishing — a federal crime under the Computer Fraud and Abuse Act (US), the Fraud Act (UK), and equivalent legislation in most jurisdictions.
Chorus: The Verdict Is DMARC
"Take off the crown! / But you ain't from this town! / Get out! Get out! Get out of my place! / Take back your counterfeit face!"
- The Deliverability Context: The chorus maps to DMARC enforcement. "You ain't from this town" is identifier alignment failure: the sending domain doesn't match the From: header domain, so DMARC alignment fails regardless of whether SPF or DKIM pass on the actual sending domain. "Get out of my place" is
p=reject: the message is blocked at the receiving MTA before reaching the inbox. - DMARC as Defense for the Spoofed Domain: A domain without DMARC enforcement can be impersonated without consequence — spoofed mail reaches recipients. Publishing DMARC at
p=rejectmeans receiving servers actively block mail that claims your domain but fails alignment. It's the only defense a legitimate sender has against their domain being weaponized.
Understand What Spoofing Is
Spoofing is presenting a sending identity — domain, display name, or header — that doesn't accurately represent the actual sender. It covers a spectrum from brand impersonation to outright phishing.
- Display name spoofing: Using a well-known brand name in the From: display name while sending from a different domain. Example: "Amazon Security"
<verify@amzn-security-notice.com>. - Domain spoofing: Sending from a lookalike domain (homograph, typosquatting) designed to be confused with a legitimate domain.
- Direct domain spoofing: Forging the From: header to show a domain you don't control. This is blocked by DMARC alignment checking.
- All three are violations of Google's sender guidelines, CAN-SPAM, and — in cases that target credentials or financial information — federal and international cybercrime law.
Deploy DMARC to Protect Your Domain
The only technical defense against your domain being spoofed is DMARC enforcement. Without it, anyone can send mail that appears to come from your domain.
p=none(monitoring only): spoofed mail still reaches recipients. Use this phase to collect aggregate reports and verify your own authentication.p=quarantine: spoofed mail is routed to spam. Most recipients don't see it.p=reject: spoofed mail is blocked at the receiving MTA. Recipients never see it. This is the only level that fully protects your domain from impersonation.- Escalate deliberately. Move from
none→quarantine→rejectonly after verifying SPF and DKIM pass for all your legitimate sending sources.
Prevent Authentication Mismatches on Your Own Mail
DMARC alignment failure is what makes spoofing detectable. Understanding alignment prevents false positives on your own legitimate mail.
- SPF alignment: the RFC5321
MAIL FROM(envelope sender) domain must match the visible From: header domain. When sending through an ESP, configure a custom return-path on your own domain to achieve alignment. - DKIM alignment: the DKIM
d=tag domain must match the visible From: header domain. Configure custom DKIM signing for your own domain rather than using the ESP's default domain. - Either SPF or DKIM alignment is sufficient for DMARC. Having both aligned is the most resilient configuration.
Recognize Active Spoofing of Your Domain
If your domain is being impersonated, DMARC aggregate reports are your first line of detection.
- Review DMARC aggregate reports (
rua=) regularly using a DMARC analytics service (Dmarcian, Valimail, EasyDMARC, or similar). Reports show every server claiming your domain, whether they pass authentication, and from which IP addresses. - Unexplained authentication failures in aggregate reports often indicate active spoofing — servers you don't control sending mail claiming your domain.
- Google Safe Browsing and Microsoft Smart Screen maintain phishing domain databases. Filing a report if a lookalike domain is targeting your customers can result in browser warnings that reduce campaign effectiveness.
Conclusion
The defense against spoofing is in the DNS. DMARC at p=reject closes the door on impersonation — for your domain, and for the recipients being targeted by spoofed mail claiming your brand. Every day your domain operates at p=none is a day someone can wear your face without consequence.
- DMARC published and actively escalating toward
p=reject. - SPF alignment: custom return-path domain matches From: header domain.
- DKIM alignment: custom DKIM
d=tag matches From: header domain. - DMARC aggregate reports reviewed regularly via a DMARC analytics service.
- No lookalike domains of your brand left unmonitored.
Deliverability is a moving target. This content reflects our best understanding at time of writing — but RFCs get updated, ISP policies shift, and best practices evolve. Spot an error or outdated info? Let us know and we'll fix it.