On 1/4/26 13:02, Brie Yoder via Mailman-Users wrote:
[Using MM 2.1.39 hosted at dreamhost.com]

Starting Dec 27, the Mailman list I admin started getting bounces to Gmail 
accounts, but only for digest messages - the individual messages have been 
going through without (apparent) problem. Sample bounce error:

Dealing with gmail has become a nightmare. For example, even though gmail publishes a DMARC policy of `none`, they require mail From: the gmail.com domain to pass DMARC. You can apply DMARC mitigations to mail From: gmail.com addresses by putting

^.*@gmail\.com$

Privacy options...->Sender filters->dmarc_moderation_addresses

but this doesn't affect digests which are From: the list and should pass DMARC as long as they are DKIM signed by the list domain and pass SPF.

Looking in a digest email header, there are no DKIM-Signature: headers, but 
there are ARC-Seal: and ARC-Message-Signature: headers. (Is this expected or is 
this a bug?)

The ARC-* headers are probably added by some downstream MTA and not by the list server. It makes no sense that the list server would be adding ARC-* headers and not DKIM signing the mail.

Digest mail should definitely be DKIM signed by the list host. This is a Dreamhost (nightmarehost?) issue. They need to to configure their servers to DKIM sign all outgoing list mail from the list domain. This is something Dreamhost needs to do. It is not something over which you have any control.

--
Mark Sapiro <[email protected]>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

------------------------------------------------------
Mailman-Users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/[email protected]/
   https://mail.python.org/archives/list/[email protected]/
Member address: [email protected]

Reply via email to