On 3/22/20 4:08 AM, David Prévot wrote: > Package: sympa > Version: 6.2.40~dfsg-1 > Severity: normal > > 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 -- Ecommerce and Linux consulting + Perl and web application programming. Debian and Sympa administration. Provisioning with Ansible.
OpenPGP_signature
Description: OpenPGP digital signature
