• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Question DKIM entry for hostname

dicker

Basic Pleskian
Server operating system version
Ubuntu 22.04.5 LTS
Plesk version and microupdate number
Plesk Obsidian 18.0.66 Update 2
Hello,
I can see the DKIM entries for the individual customer domains.

Where can I see the DKIM entry for the hostname?
The hostname is used when sending mail, so I have to have a DKIM entry there too, otherwise emails get stuck in the mail queue.
My hostname is a subdomain.
 
The DKIM would be signed by the domain's DNS, not the main hostname. If emails is getting stuck in the mail queue, please review the mail logs to see what the actual issue is cause I can bet it isn't because of the DKIM but for something else.
 
Emails are declared as being deferred in the mail queue.
I am constantly shown a link where dkim is requested.

4.0.0 deferred (host mx00.emig.gmx.net[212.227.15.9] said: 451-Requested action aborted 451-Reject due to policy restrictions. 451 For explanation visit 451 Requested action aborted Reject due to policy restrictions. (in reply to end of DATA command))

<customer email: host mx00.emig.gmx.net[212.227.15.9] said: 451-Requested action aborted 451-Reject due to policy restrictions. 451 For explanation visit 451 Requested action aborted Reject due to policy restrictions. (in reply to end of DATA command)
recipient=customer email
offset=1230
dsn_orig_rcpt=rfc822;customer email
status=4.0.0
action=delayed
diag_type=smtp
diag_text=451-Requested action aborted 451-Reject due to policy restrictions. 451 For explanation visit 451 Requested action aborted Reject due to policy restrictions.
mta_type=dns
mta_mname=mx00.emig.gmx.net
reason=host mx00.emig.gmx.net[212.227.15.9] said: 451-Requested action aborted 451-Reject due to policy restrictions. 451 For explanation visit 451 Requested action aborted Reject due to policy restrictions. (in reply to end of DATA command)

<s2.joserv-server.de> Password reminder from Plesk
Date: Jan 20 14:40:58
Size: 948.00 B
[email protected]
 
Plesk currently doesn't support DKIM singing for the Plesk email notifications. There is an existing feature request on the Plesk UserVoice page for having notifications DKIM signed by default, which you can vote for: Implement support of SPF, DMARC and DKIM anti-spam methods for Plesk email notifications

This post outlines a possible workaround you can use to send Plesk email notifications with DKIM anyway:
 
Last edited:
Back
Top