Closed morenonardelliunitn closed 4 months ago
Hi @morenonardelliunitn ,
Please show us the steps to reproduce, i.e.:
Hi @ikedas
the DKIM configuration was carried out at the robot.conf level by:
in /etc/sympa/sympa.conf file inserting the following lines:
dkim_feature on
dkim_add_signature_to robot
dkim_signature_apply_on any
in every robot.conf files inserting the following lines:
dkim_private_key_path /etc/sympa/domain-keys/sub-domain.private
dkim_signer_domain sub.domain.it
dkim_selector selector-subdom
all files in the folder /etc/sympa/domain-kays/ are owned by the user sympa with 600 permission:
-rw------- 1 sympa sympa 887 Feb 3 2021 sub-domain.private
in the list has set custom messages for welcome or goodbye template. These automatic communications occur from the sender nomelista-request@sub.domain.it and are not signed by DKIM. (you can see a mail's header in the my previus second example)
Other communications such as those relating to errors carried out based on moderation operations which have the sender sympa-request@sub.domain.it are correctly signed DKIM (you can see a mail's header mail in the my previus first example)
This issue is a duplicate of #1739 and will be fixed on the next release. @morenonardelliunitn , thank you for reporting bug! This issue is closed.
On our Sympa system we have activated and configured the DKIM and ARC signature as per the guide. The configurations are implemented at the subdomain in the various robot.conf files. However, we have noticed that some system messages are not signed with DKIM. The relationship found is that messages sent from an envelope from "nomelista-owner@dominio.it" are not signed while those with evelop from "sympa-request@dominio.it" are signed correctly
Version
Sympa 6.2.72
Installation method
rpm package on RHEL 8.7
Expected behavior
I expect Sympa to sign all its system messages
Actual behavior
At the moment this is not the case
Additional information
correct mail:
wrong email: