• 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.

Question Enable DKIM on all Domains

UweP

Regular Pleskian
Hi. How can I enable DKIM automatically on all domains. Or does that matter, if umm, a domains DNS server is not yet set to my server, and a dkim is present in the dns zone of the domain on my server? it should just not be used right?
 
Oh and, is this correct:

Received-SPF: pass (google.com: domain of [email protected] designates 2a01:4f8:110:12a1::2 as permitted sender) client-ip=2a01:4f8:110:12a1::2;
Authentication-Results: mx.google.com;
dkim=temperror (no key for signature) [email protected];
spf=pass (google.com: domain of [email protected] designates 2a01:4f8:110:12a1::2 as permitted sender) [email protected];
dmarc=pass (p=NONE dis=NONE) header.from=mydomain.tld
Received: from [192.168.2.107] (myhost.isp [my.isp.ip])
by baby.freakyonline.de (Postfix) with ESMTPSA id 3A35147E0081
for <[email protected]>; Mon, 21 Nov 2016 18:38:48 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mydomain.tld;
s=default; t=1479749928;
bh=somethignencryptedorhwat; l=8;
h=To:From:Subject;
b=somekeydunnoifishouldpost
To: [email protected]

because it says temperror but later shows a dkimg signature
oh it's missing the key - why is that? I've set up plesk to use dkim for mail for that domain?
 
Last edited:
Back
Top