DMARC and Listserves (Gmail 30Apr2025 edition)

Traditionally, listserves have kept the author's email address in the From header, while delivering the email from the listserve's servers to the subscribers of  the mailing list.

The DMARC specification ignores tradition, and allows ISP's to specify which servers are the only servers that can send out that ISP's email.

Yahoo was the first ISP to turn on the DMARC protocol.  They do so via a DNS record that looks like this.

v=DMARC1; p=reject; pct=100; rua=mailto:[email protected]; ruf=mailto:[email protected];

Which says to reject any messages from a Yahoo email address, that does not come from its IP addresses.

Mail-List.com will look up the current DMARC policy, and alter the From header if the policy is quarantine or reject.

See https://help.mail-list.com/m/59124/l/946163-dmarc-how-mail-list-com-handles-dmarc-reject-settings

Today 30Apr2025, Gmail says their DMARC policy is none.  

v=DMARC1; p=none; sp=quarantine; rua=mailto:[email protected]

Per https://mxtoolbox.com/SuperTool.aspx?action=mx%3agmail.com&run=toolpage#

dig _dmarc.gmail.com txt

Says the same thing

_dmarc.gmail.com. 472 IN TXT "v=DMARC1; p=none; sp=quarantine; rua=mailto:[email protected]"

And yet Gmail people are complaining that emails from other subscribers that also happen to use gmail are going into spam.

They show me this

From:    Joh Doe <[email protected]>

To:    [email protected]

Subject:    [xxxxx] Notes - Monday April 28th Rehearsal

SPF:    PASS with IP 204.236.130.174 Learn more

DKIM:    'PASS' with domain mail-list.com Learn more

DMARC:    'FAIL' Learn more

Which makes it appear that wrong DMARC pushed it into the Spam folder.

In summary, listserve email from a fellow gmail user, will go to spam for all gmail subscribers on the listserve.  Gmail is making things worse.

If Gmail had announced via DNS, that they were enforcing quarantine, then Mail-List.com would have made an exception to tradition, and altered the From: header to meet their criteria.  In real time.

I have sent an email on 28Apr2025 to [email protected] asking them why the discrepancy, but have not heard back.

Gmail DMARC Update  9May2025

I have not heard back from Gmail Postmaster and probably never will.

In summary,

the recent problem of placing listserve email from other gmail users, into their Spam folder.  Not from other domains, just fellow gmail users.

It appears gmail right hand is using DMARC to reduce spam, and gmail left hand does not want to update their DNS to reflect this.

I see - (after running the command

dig _dmarc.gmail.com txt

)

; <<>> DiG 9.11.3-1ubuntu1.15-Ubuntu <<>> _dmarc.gmail.com txt

;; global options: +cmd

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 23656

;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:

; EDNS: version: 0, flags:; udp: 65494

;; QUESTION SECTION:

;_dmarc.gmail.com. IN TXT

;; ANSWER SECTION:

_dmarc.gmail.com. 213 IN TXT "v=DMARC1; p=none; sp=quarantine; rua=mailto:[email protected]"

;; Query time: 1 msec

;; SERVER: 127.0.0.53#53(127.0.0.53)

;; WHEN: Fri May 09 20:31:26 UTC 2025

;; MSG SIZE  rcvd: 129

 

I read that as

p=none; sp=quarantine;

Policy is none and Subdomain Policy is quarantine.  

Since there are no subdomains involved, Gmail is saying they are not enforcing DMARC (which listserves violate).

For Mail-List.com List Moderators, who want a workaround.

First of all, you can be Admin and change the setting in the  

Misc Settings section of Customize Your List. Change this setting  

 

Sender Receives List Address in From Header  

 

Have List Address in the From Header  

 

Change the radio button to  

 

From Address Is List Address  

 

That will turn on DMARC for all subscribers, including Gmail people, so that other Gmail subscribers don't get the listserve message in their spam folder.

Or any other ISP that is not announcing their true DMARC policy.

At the cost of obscuring the author of that message to the listserve.

 

Make sense ?  

 

Let me know if not.  

Thanks

mark