Facebook
TwitterRafael_Tavares
New Pleskian
Please, how to configure dkim in plesk12, spf and domainkeys its ok, but dkim dont configure automatic.
Thx!
Thx!
-
Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
-
The BIND DNS server has already been deprecated and removed from Plesk for Windows.
If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release. -
The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
DKIM Plesk 12
- Thread starter Rafael_Tavares
- Start date
I hope this thread will help - http://talk.plesk.com/threads/how-to-enable-dkim-signature.282551/
The above thread didn't help.
I have CentOS 7 and Plesk 12.
When enabling "Use DomainKeys spam protection system to sign outgoing email messages" from domain's Mail settings, in domain's DNS appear two TXT records:
_domainkey.domainname.com. TXT o=-
default._domainkey.domainname.com. TXT p=xxxxxxxxxxxxxxxxxxxxxxxx;
but the e-mails aren't signed.
Also /etc/opendkim.conf, /etc/opendkim/KeyTable, /etc/opendkim/SigningTable and /etc/opendkim/TrustedHosts files are missing (if we consider that this is the correct way to install DKIM).
I have CentOS 7 and Plesk 12.
When enabling "Use DomainKeys spam protection system to sign outgoing email messages" from domain's Mail settings, in domain's DNS appear two TXT records:
_domainkey.domainname.com. TXT o=-
default._domainkey.domainname.com. TXT p=xxxxxxxxxxxxxxxxxxxxxxxx;
but the e-mails aren't signed.
Also /etc/opendkim.conf, /etc/opendkim/KeyTable, /etc/opendkim/SigningTable and /etc/opendkim/TrustedHosts files are missing (if we consider that this is the correct way to install DKIM).
Last edited:
U
UFHH01
Guest
Hi quark,
even that the definition "DomainKeys" and "DKIM" have parts in common, these two signing procedures have different installation packages, different paths, different modifications and what is most important, ONLY "DomainKeys" is used by Plesk. If you wish to use "DKIM" as well, you may find some ( working ) solutions over the forum search.
If you wish additional informations and/or help, please provide the used MTA ( qmail or postfix ) and describe your previous steps to install OpenDKIM ( "DKIM" ) on your server, which need some more steps, than only to use "yum install opendkim" to work. As well, mail - logs are usefull to help you to investigate possible failures/issues.
The part
even that the definition "DomainKeys" and "DKIM" have parts in common, these two signing procedures have different installation packages, different paths, different modifications and what is most important, ONLY "DomainKeys" is used by Plesk. If you wish to use "DKIM" as well, you may find some ( working ) solutions over the forum search.
If you wish additional informations and/or help, please provide the used MTA ( qmail or postfix ) and describe your previous steps to install OpenDKIM ( "DKIM" ) on your server, which need some more steps, than only to use "yum install opendkim" to work. As well, mail - logs are usefull to help you to investigate possible failures/issues.
The part
... is for "DomainKeys" and not for "DKIM", please keep that in mind, when checking your configuration(s)/modification(s) with for example "http://www.mail-tester.com/" or "http://www.port25.com/support/authentication-center/email-verification/" after your installation(s)/modification(s).
Similar threads
