• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

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