Applicable to:
- Plesk Onyx for Linux
Note: This article has the reference to the issue with the fix available:
- #PPP-40448 "DKIM signing no longer uses the length tag in headers."
Fixed in:- Plesk Onyx 17.9 Preview 12 12 March 2019 (Linux)
Symptoms
-
The following error is shown when analyzing headers of an email message sent from a Plesk server in mxtoolbox.com Email Header Analyzer:
CONFIG_TEXT: Body Hash Did Not Verify
-
DKIM policy is configured in the Plesk.
-
Lenght tag can be found in the email header (
l=663):CONFIG_TEXT: v=1; a=rsa-sha256; c=relaxed/relaxed; d=wna.jp; s=default; t=1548437364; bh=XPOALMihvVieKHybTr2G8RH3tg93XgGJyTxTAoZreoI=; l=663; h=From:Subject:To; b=FlHzW/BaAAZibibuhoEvU45+nhJZncg59Jc/7dLsMhNr4alRyVYuPrnr6gNv3+b
Cause
Plesk bug PPPM-9978 (PPP-40448) which is already fixed in the upcoming major Plesk version.
For the current Plesk versions, the bug is planned to be fixed in future product updates.
Resolution
The upcoming major Plesk version is currently in the testing release tier and is not recommended for using in production.
Until the bug is fixed in the current Plesk versions, use the workaround depending on the operating system installed on the server:
-
Connect to the server using SSH.
-
Back up the original file:
# cp -a /usr/local/psa/handlers/hooks/dk_sign{,.bak}
-
Download the archive with the patched file and unpack it:
# wget https://support.plesk.com/hc/en-us/article_attachments/360029725134/dk_sign.COS7.tar.gz
# tar -xzvf dk_sign.COS7.tar.gz
-
Replace the original file with the patched one:
# mv -f dk_sign /usr/local/psa/handlers/hooks/dk_sign
-
Connect to the server using SSH.
-
Back up the original file:
# cp -a /usr/local/psa/handlers/hooks/dk_sign{,.bak}
-
Download the archive with the patched file and unpack it:
# wget https://support.plesk.com/hc/en-us/article_attachments/360030544733/dk_sign.Ubt16_04.tar.gz
# tar -xzvf dk_sign.Ubt16_04.tar.gz
-
Replace the original file with the patched one:
# mv -f dk_sign /usr/local/psa/handlers/hooks/dk_sign
Comments
6 comments
Hello,
I have the following error when i try to fix with the new file:
"Mar 20 19:40:24 ns1 /usr/lib/plesk-9.0/psa-pc-remote[25906]: handlers_stderr: /opt/psa/handlers/hooks/dk_sign: error while loading shared libraries: libboost_filesystem-plesk.so.1.65.1: cannot open shared object file: No such file or directory"
"root@ns1:~# dpkg -l | grep lesk-libboost-filesystem
ii plesk-libboost-filesystem1.65 1.65.1-ubuntu.16.04.171017.1047 amd64 Boost filesystem C++ library."
OS: Ubuntu 16.04
Latest Version of Plesk Onyx
Can someone help me?
Thanks,
Paulo
Hello @Paulo,
Please, make sure that the library file is owned by root and has permissions 755 :
# stat /usr/lib64/libboost-plesk-1.65/libboost_filesystem-plesk.so.1.65.1
File: `/usr/lib64/libboost-plesk-1.65/libboost_filesystem-plesk.so.1.65.1'
Size: 1300130 Blocks: 2544 IO Block: 4096 regular file
Device: 3ba0b621h/1000388129d Inode: 540736 Links: 1
Access: (0755/-rwxr-xr-x) Uid: ( 0/ root) Gid: ( 0/ root)
Hello @Ivan
In my OS the file are located at /usr/lib/x86_64-linux-gnu/libboost-plesk-1.65/libboost_filesystem-plesk.so.1.65.1
--
root@ns1:~# find /usr/ -name "libboost_filesystem-plesk.so.1.65.1"
/usr/lib/x86_64-linux-gnu/libboost-plesk-1.65/libboost_filesystem-plesk.so.1.65.1
--
--
root@ns1:~# stat /usr/lib/x86_64-linux-gnu/libboost-plesk-1.65/libboost_filesystem-plesk.so.1.65.1
File: '/usr/lib/x86_64-linux-gnu/libboost-plesk-1.65/libboost_filesystem-plesk.so.1.65.1'
Size: 107208 Blocks: 216 IO Block: 4096 regular file
Device: fd01h/64769d Inode: 293484 Links: 1
Access: (0644/-rw-r--r--) Uid: ( 0/ root) Gid: ( 0/ root)
Access: 2019-03-20 23:00:01.084472637 +0000
Modify: 1985-01-01 17:00:00.000000000 +0000
Change: 2018-10-17 13:27:15.357818000 +0100
Birth: -
--
Hello @Paulo,
Thank you for the provided information. I have double-checked the required permissions, 644 as you have is ok.
The case requires deeper investigation. I would suggest submitting a request for Plesk Support.
Hello @Paulo,
Let me correct the previous answer.
The attached fix is for CentOS, that's why it does not work on your system.
In a few hours, this information will be added to this article + we will add the fix that will suit you.
Hello @Ivan,
Thanks for your help. I will wait the fix for Ubuntu 16 :)
Thanks
Please sign in to leave a comment.