• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Domainkeys with dk-milter

SuperBadConchord

New Pleskian
I need help setting up Domainkeys for my server with postfix, I know its pretty obsolete but need to do it. I also know of the option to turn it on through the web interface, but as I have had to set up DKIM with opendkim this doesn't apply it anymore. I have set it up using dk-milter and have the settings in /etc/sysconfig/dk-milter as below (from http://stevejenkins.com/blog/2011/0...el-5-centos-5-using-opendkim-and-dk-milter/):

USER="opendkim"
PORT="inet:[email protected]"
SIGNING_DOMAIN="domain.eu"
SELECTOR_NAME="default"
KEYFILE="/etc/opendkim/keys/${SIGNING_DOMAIN}/${SELECTOR_NAME}"
SIGNER=yes
VERIFIER=no
CANON=simple
REJECTION="bad=r,dns=t,int=t,no=a,miss=r"
EXTRA_ARGS="-h -l -D -i /etc/opendkim/TrustedHosts"
SYSCONFIG="/etc/sysconfig/dk-milter"
MILTER_GROUP="opendkim"


Once I restart everything I get fail (bad signature) from the tests I do, even though the key is the correct one for this domain. I have also set t=y; o=~ as one of the domainkeys in the dns. I have no idea why this is failing so if anybody has any ideas please share.

Nathan
 
Back
Top