Hi,

Once dkim_feature is activated on a list, the messages received from
sympa get mangled: the following headers are added *after* the messages
body (at the end of the message):

Message-Id: <…[random string from the server]…>
From: Sympa mailing list manager <…[list address]…>
Date: [date]

Because of that, the messages appear empty in any MUA (but are properly
added and visible in the web archive).

Please note that the DKIM-Signature header properly gets added on the
messages.

I’ve added the following options in robot.conf: dkim_private_key_path
and dkim_selector, and then activated dkim_feature for one list
(actually, I initially noticed the issue with “dkim_feature on” in
robot.conf, and removed it to not break all hosted lists). The server is
running on Buster.

Regards

David

Hello David,

that indeed seems a bug in Sympa, see https://github.com/sympa-community/sympa/issues/1036.

Regards
         Racke

Hello David,

that indeed seems a bug in Sympa, see https://github.com/sympa-community/sympa/issues/1036.

Regards
         Racke

Confirming fix - I built 6.2.60~dfsg-3 on Buster a couple weeks ago and
dkim has been working well. 

Due to recent enforcement at Yahoo and Gmail I needed to enable
DKIM/DMARC/ARC for all lists to get delivery.

Due to the FCGI problem I also switched over to systemd, which is
working (in the low-load configuration):

$ cat wwsympa.service
[Unit]
Description = WWSympa - Web interface for Sympa mailing list manager
(service)
After = syslog.target sympa.service

[Service]
User = sympa
Group = sympa
ExecStart = /usr/lib/cgi-bin/sympa/wwsympa.fcgi
StandardOutput = null
StandardInput = socket
StandardError = null
Restart=on-failure

[Install]
WantedBy = multi-user.target

$ cat wwsympa.socket
[Unit]
Description = WWSympa - Web interface for Sympa mailing list manager
(socket)

[Socket]
SocketUser = www-data
SocketMode = 0600
ListenStream = /run/sympa/wwsympa.socket

[Install]
WantedBy = sockets.target