DKIM signing not working

[Kenchava]

Version

6.2.24

Installation method

apt (Mail:DKIM is installed)

Expected behavior

DKIM headers of received emails from lists should be populated.

Actual behavior

Message is not signed.

Additional information

/etc/sympa/sympa/sympa.conf:
dkim_feature off
dkim_add_signature_to robot,list
dkim_private_key_path /etc/sympa/sympa/dkim.private
dkim_signature_apply_on md5_authenticated_messages,smime_authenticated_messages,dkim_authenticated_messages,editor_validated_messages
dkim_signer_domain
dkim_selector sympalists

The TXT record containing the public key is deployed at sympalists._domainkey.

The DKIM feature is enabled on my test list as I cannot enable it globally for now.

/var/lib/sympa/list_data//config:
dkim_feature on

[ikedas]

Hi @Kenchava ,
Could you please show us these things?

• the log of Sympa from when you posted a test message to when the message was delivered, and
• full header of delivered message.

[Kenchava]

Hi @ikedas ,

Late last evening I was actually able to get everything working. DKIM signing began working once it was enabled globally in the sympa.conf file. Originally I had dkim_feature off within sympa.conf and dkim_feature on specified on a specific list.

[ikedas]

Hi @Kenchava ,

Hi @ikedas ,

Late last evening I was actually able to get everything working. DKIM signing began working once it was enabled globally in the sympa.conf file. Originally I had dkim_feature off within sympa.conf and dkim_feature on specified on a specific list.

Hmm, that behavior doesn't make sense. I'll submit a pr to fix it in a few days. Thanks for reporting.

[racke]

Looks like the following Debian bug report is also related to this problem: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954475

[ikedas]

@racke, I think that report on Debian looks discussiong on another problem.

[ikedas]

Hi @Kenchava and all,

A fix to this bug was included in the recent beta (6.2.59b.2 at 7 Dec). It will be very appreciated to confirm this fix.

[ikedas]

Previous pr #1050 was misleading.

I checked the code from when initially DKIM integration was added, and found that:

• dkim_feature parameter is available only in domain context (robot.conf or sympa.conf for the default).
• Configuration schema also defines it in list context (config) where it has been never used.

By a new pr I'll roll back previous change and remove dkim_feature parameter from list context.