Hi Sebastian,

Without comment on the technical merits of your proposal, this message is not 
how new work is introduced into the IETF. It is not in the right form, nor does 
it fall within the charters of either of the working groups you have sent it to.

The following web page contains the information you need to bring new work to 
the IETF.
https://www.ietf.org/process/new-work/

-andy, ART AD

On 29-05-2026 7:38 PM, [email protected] wrote:

*Dear IETF/Orie Steele/Andy Newton/Charles Eckler*

**

*AI SPAM Blocker*

**

*Sender Policy Domains (SPD): Brand-Authorized Sending Domains* 
*draft-spd-email-00* *May 2026*

**

*Abstract* This document defines Sender Policy Domains (SPD), a new DNS TXT 
record that allows a brand owner to publish the complete list of domains 
authorized to send email on its behalf. Mail servers that receive an email 
containing a registered brand name in the Subject or From header MUST check the 
SPD record and mark the message as spam if the sending domain is not listed. 
SPD is designed to work alongside SPF, DKIM, and DMARC and provides simple, 
effective protection against brand impersonation.

**

*1. Introduction* Current email authentication (SPF/DKIM/DMARC) verifies the 
sending domain but does not protect brand names appearing in the Subject line. 
SPD solves this by letting any company publish an explicit list of every domain 
it actually uses to send mail. Example: If an email has “Lowes” in the Subject 
and arrives from xydh.com (not listed in Lowes’ SPD record), the receiving 
server MUST mark it as spam.

**

*2. SPD DNS Record Format* The SPD record is a TXT record published at the brand’s apex 
domain. Format: v=spd1 domains="example.com example.net sub.example.com"

  * v=spd1 – version tag (MUST be present and exact)
  * domains= – space-separated list of all authorized sending domains (maximum 10 
domains; each <= 253 characters)

Multiple TXT records are NOT permitted; only the first valid SPD record is used.

**

*3. Receiver Validation Rules* Upon receipt of an email:

 1. Extract the brand name from the Subject header (case-insensitive match 
against a short list of registered brands).
 2. Query the SPD TXT record for that brand’s domain.
 3. If the sending domain (from the envelope or From header) is NOT in the 
domains= list, the server MUST:
      * Add header: X-SPD-Status: fail
      * Mark the message as spam (or reject with 5.7.1)
 4. If the domain IS listed, add: X-SPD-Status: pass and continue normal 
processing.

**

*4. Example* lowes.com publishes: v=spd1 domains="lowes.com lowes.email lowes.co 
lowesmail.com"

An incoming email with Subject: “Lowes Memorial Day Sale” from xydh.com fails 
the SPD check and is marked spam.

**

*5. Deployment Considerations*

  * Brands register their SPD record at their own apex domain.
  * Receivers cache results for up to 1 hour (TTL from the TXT record).
  * No changes required to SMTP; fully backward compatible.
  * Early adopters: Gmail, Outlook, Yahoo, and major corporate filters are 
expected to implement first.

**

*6. Security Considerations* SPD prevents brand spoofing in the Subject line. 
It does not replace SPF/DKIM/DMARC; it complements them. DNSSEC is RECOMMENDED 
for SPD records.

**

*Appendix A. IANA Considerations* A new registry for SPD version tags will be 
created under “Email Authentication Methods”.

*Sebastian Lee*
*Service**2**Client****LLC**
**214 453 8879*

**

w: https://www.service2client.com <https://www.service2client.com/>

e: [email protected] <mailto:[email protected]>

t: helpdesk.service2client.com <https://helpdesk.service2client.com/>

Schedule Time 
<https://mail.s2csecuremail.com/interface/schedule-appointment/c2xlZUBzZXJ2aWNlMmNsaWVudC5jb20%3d/76fb244232fa44fcbbb25b6d0f021494#/>

Upload A File 
<https://www.icfiles.com/app/ClientSignup.asp?customstyle=sebastian>

This transmission and/or attachment(s) may be confidential communication or may 
otherwise be privileged or confidential. If you are not the intended recipient, 
you are hereby notified that you have received this transmission in error; any 
review, dissemination, distribution or copying of this transmission is 
prohibited. If you have received this transmission and/or attachment(s) in 
error, please notify us immediately by email reply and immediately delete this 
transmission and all of its attachments. Thank you.

------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------


_______________________________________________
dmarc mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to