Follow these steps to install OpenDKIM on Ubuntu and Plesk.
I will use domain.tld (as the primary domain) and example.com as my domains, I have enabled subdomains so mail from the server mail.domain.tld gets signed too as in this case mail.domain.tld is also the Posfix hostname and mailname…
1. First login as root as run…
1
2
# apt-get update
# apt-get install opendkim opendkim-tools
2. Create the folder structure…
1
2
# mkdir -p /etc/opendkim/keys/domain.tld
# mkdir -p /etc/opendkim/keys/example.com
3. Create a key, I’ll use “dkim” as the selector and create 1024bit keys
You will have two files in the folder, dkim.private and dkim.txt, the latter contains the DNS record for you to add in Plesk or at your domains registrar.
1
2
3
4
# cd /etc/opendkim/keys/domain.tld
# opendkim-genkey -s dkim -d domain.tld
# chown opendkim:opendkim dkim.private
# chmod 600 dkim.private
1
2
3
4
# cd /etc/opendkim/keys/example.com
# opendkim-genkey -s dkim -d example.com
# chown opendkim:opendkim dkim.private
# chmod 600 dkim.private
4. Now we’ll create the SigningTable and the KeyTable…
If you are running Plesk on a Ubuntu server and Bind fails to start the likely cause is AppArmor not being configured for Plesk’s chrooted environment.
All you have to do is add the path to the usr.sbin.named file.
1. Locate the file…
1
/etc/apparmor.d/local/usr.sbin.named
2. Add the following path to the file…
1
2
/var/named/run-root/** rw,
/var/named/run-root/usr/lib/**/libgost.so rm,
including the comma.
3. Now restart AppArmor…
1
service apparmor restart
4. Now you can start Bind…
1
service bind9 start
I hope that helps some people.
Note: We used the /etc/apparmor.d/local/usr.sbin.named file to make sure our addition is permanent, and the package manager doesn’t over write it.