Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
The APS Catalog has been deprecated and removed from all Plesk Obsidian versions. Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.
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).
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.
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;