Skip to Content.
Sympa Menu

en - Re: [en@sympa] Google, DKIM, and Reply-To

Subject: The mailing list for listmasters using Sympa

List archive

Chronological Thread  
  • From: "Mail administrator, Otto Makela" <address@concealed>
  • To: address@concealed
  • Subject: Re: [en@sympa] Google, DKIM, and Reply-To
  • Date: Fri, 9 Oct 2026 09:25:19 +0300

On 08/10/2026 21.05, Matt Taggart wrote:
> On 10/8/26 7:53 AM, Mail administrator, Otto Makela wrote:
>> A word of warning for those who try to run your Sympa mailing list
>> server so that SPF and DKIM rules get followed in the "classic" way.
>> Our mailing list has the SPF permission for its Sender address,
>> and we try to pass the message through unmolested, so the original
>> DKIM signatures verify.
[…]
> I am a little bit confused by your mail so I will ask some questions:
>
> Are you using sympa's "sender munging" feature to rewrite the sender
> from address? If so which settings do you have?

No, we are not. Please note that above I am of course talking about the
SMTP From when referring to the SPF permission, sorry about any confusion.

> Is your MTA (or MTAs) stripping and/or adding any DKIM signatures?

No, it is not, apart for our own domains, like the mailing list server
itself (which Sympa of course uses for its self-generated messages).

> I think if you aren't doing sender munging, it's known that mail delivery
> will fail on most receiving servers for sender domains with a strict
> policy (like gmail).
I contest this. I have found that if one takes care not to mess with
the messages while in transit through Sympa (like not add headers or
footers, or use custom_subject) you can get the vast majority of
messages through without DKIM problems.

I'm now working on the few remaining problem cases.

> But let us know more details if you were using this and something broke
> it.
I did try to explain the gotcha in my original message:
the Sympa default is to add a "Reply-To" header to the message
sender if none exists, and this makes DKIM signatures (like the
ones which Google produces) which include that header fail.

[Another interesting Google gotcha is that one needs to take care that
remove_headers includes "Sender", as Google enforces that there can
only be one such header in emails, while sending out messages from its
calendar which include slightly off-standard usage of this header.]

Now, did someone have a ready recipe to change the system-wide
settings for reply_to_header in sympa.conf/robot.conf?

--
address@concealed (Mail Administrator, Otto J. Makela)



Archive powered by MHonArc 2.6.19+.

Top of Page