Hi,
It sounds to me like your domain for some reason isn't signing outgoing
Email if there are no DKIM signature headers. Try dkimvalidator.com.
There it gives you a random Email user value which you can use or you
can type one of your own. For example, if the edit box there says foobar
then you send an Email from your domain (not a Mailman message but just
a plain Email) to [email protected], then moments later have the
site check that. Assuming it received the message from your server, it
will then break down what is right and wrong about your message. Be
warned that at least the last time I checked, their Spamassassin checks
flag a false alarm with Spamhaus, that's nothing for you to worry about,
it's a problem at their end, not yours.
Jayson
On 1/4/2026 3:02 PM, 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:
<[email protected]>: host gmail-smtp-in.l.google.com[192.178.163.27] said:
550-5.7.1 [69.163.136.29 12] Gmail has detected that this message is
likely 550-5.7.1 unsolicited mail. To reduce the amount of spam sent to
Gmail, this 550-5.7.1 message has been blocked. For more information, go to
550 5.7.1 https://support.google.com/mail/?p=UnsolicitedMessageError
41be03b00d2f7-c1e7d1d12a2si62798268a12.385 - gsmtp (in reply to end of DATA
command)
Has anyone else experienced this? The list has been around for ~10 years and
this just started happening a week ago. It is very large - 7200 total members;
over half are Gmail accounts. Trying to get help from Dreamhost has been
extremely frustrating - I get a response from a new tech each time who can’t be
bothered to read the case history and says, Oh this is a spam problem, so we
can’t help 🙄
Going into the Google postmaster tools, I see they say DKIM is failing for the domain at
issue. When I run a DKIM checker<https://mxtoolbox.com/SuperTool.aspx> on the domain,
everything is fine. 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?) This
page<https://www.suped.com/guides/dkim/a-practical-guide-to-dkim-selector-name-examples>
says to look at the s= value in the DKIM-Signature: header for what the proper DKIM
selector should be for my domain, in an email sent from the domain. Should I be checking
the s= value in the ARC-Message-Signature: header of a digest email to confirm a valid DKIM
selector? Something else?
-Brie
------------------------------------------------------
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]
------------------------------------------------------
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]
