YAST Install of DKIM not signing outbound mails.

I first posted this in the setup/install forum but got no replies at all, so I’m wondering if it is actually an application problem:

I set up mail with amavis and clamd and spamassassin but not DKIM and got that all successfully running.
I then additionally selected DKIM in the YAST email setup, and everything continued to work as before.
I ran /etc/amavisd showkeys, and obtained the key and installed it in my DNS.
I ran /etc/amavisd testkeys and got a “pass” result.
Inbound mails with DKIM signatures are being checked and passed.
However, the outgoing mails are not getting a DKIM signature.

My amavisd.conf file is as set up by YAST and includes the following lines:

$enable_db = 1; # enable use of BerkeleyDB/libdb (SNMP and nanny)

$enable_zmq = 1; # enable use of ZeroMQ (SNMP and nanny)

$nanny_details_level = 2; # nanny verbosity: 1: traditional, 2: detailed
$enable_dkim_verification = 1; # enable DKIM signatures verification
$enable_dkim_signing = 1;
dkim_key(‘this-domain.com’, ‘default’, ‘/var/db/dkim/this-domain.com.pem’); (With “this-domain” being my actual domain.)
@local_domains_maps = ( “.$mydomain”] ); # list of all local domains (with .$mydomain just as shown.)
@mynetworks = qw( ::1] [FE80::]/10 [FEC0::]/10 );

Please advise what I need to check next or what more info you need.



As this is a double post, which is not allowed, the other one is closed.

Next time, when you think you posted in the wrong (sub)forum, please ask for it to be moved (using the Report button, ! within triangle, that you find below a post).

Also, please understand that members here live all around the globe and some of them want to get some sleep from time to time. Thus it is not uncommon that it takes 24-48 hours before any reaction to your question is posted.

And of course it could be that your setup is not used by many and that thus the experience with it is not available here. :frowning:

In any case, please in the future use CODE tags around copied/pasted computer text in a post. It is the # button in the tool bar of the post editor. When applicable copy/paste complete, that is including the prompt, the command, the output and the next prompt.
It is the best way to communicate the difference between story telling and computer facts. It also will keep any layout (like columns) you see on the terminal window, will have fixed fonts like on the the terminal and prevent processing certain character combinations into smileys or URLs. And more.