DKIM not working on SMG on SLES appliance

  • 7024383
  • 24-Jan-2020
  • 19-Feb-2020

Environment

GWAVA (Secure Messaging Gateway) 7
SLES appliance

Situation

DKIM signing is not working after moving to SMG on SLES. The smg-scanner log shows the following error:

[139878458124032] 2020-01-24 09:11:32 (dksn)<2> Processing DKIM signing service: DKIM Sign
[139878458124032] 2020-01-24 09:11:32 (srpt)<2> Processing SPAM REPORTING service: Spam Reporting
[139878458124032] 2020-01-24 09:11:32 (sigh)<2> Applying HTML footer to message
[139878458124032] 2020-01-24 09:11:32 (sigt)<2> Applying TEXT footer to message
[139878458124032] 2020-01-24 09:11:32 (dksn)<2> Applying DKIM signature
[139878458124032] 2020-01-24 09:11:32 (dksn)<2> DKIM service at 127.0.0.1:4932 is unavailable

Resolution

If the smg-scanner log is showing the above error, then DKIM is most likely not running. Do the following to make it so it will start:

1) From a command prompt type: vi /etc/opendkim/opendkim.conf

2) Hit 'Insert'

3) Scroll down to line 765 and change it from SOCKET="inet:4932" to SOCKET net:4932@localhost (removing the quotes and = and adding a space after SOCKET and @localhost after the port 4932)

4) Save changes by hitting 'esc' :wq

5) Start the opendkim service by typing: service opendkim start

6) To have it start automatically upon reboot type: systemctl enable opendkim service
Reboot the server.

DKIM should not start on it's own upon reboot.

Feedback service temporarily unavailable. For content questions or problems, please contact Support.