Forwarded to devs DKIM signing records/instructions are outdated

[pleskuser67553]

Username:

TITLE

DKIM signing records/instructions are outdated

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

Plesk Obsidian Version 18.0.63 Update #3, AlmaLinux 9.2, AMD

PROBLEM DESCRIPTION

DNS records created by Plesk, and signing instructions for external DNS contain a record DomainKey Root Outbound Signing Policy o=- which was part of a draft, but did not make it to the standard.

_domainkey.example.com. IN TXT "o=-"

See also DKIM, SPF, and DMARC Protection and ARC Support

STEPS TO REPRODUCE

1. Navigate to Tools & Settings > Mail Server Settings
2. Under DKIM spam protection check Allow signing outgoing mail if not already
3. Navigate to any domain in Plesk
4. Click on Mail > Mail Settings
5. Check Use DKIM spam protection system to sign outgoing email messages if not already and click Apply
6. Click How to configure external DNS to reveal the popup info
7. Observe the instruction to include the draft policy record _domainkey.example.com. IN TXT "o=-"
8. Navigate back to the domain
9. Click on Hosting & DNS > DNS
10. Click Enable if not already
11. Observe the generated draft policy record _domainkey.example.com. TXT o=-

ACTUAL RESULT

As described above, the draft policy record is included

EXPECTED RESULT

As described above, the draft policy record should not be included. The docs should also be updated.

ANY ADDITIONAL INFORMATION

Please consider making it easier and more obvious to retrieve the domainkey for configuring external DNS. For example, not behind a popup link, and instead retrievable with a single click on the visible record or button which copies the TXT value to clipboard. Also, perhaps a button to copy a BIND formatted version to clipboard including quoted string breaks at each 255 character count for really long keys.

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Confirm bug

 

[Sebahat.hadzhi]

@pleskuser67553 thank you for your report. We appreciate that you brought our attention to the issue. We investigated it and we were able to confirm that the DKIM signing policy entry is indeed obsolete. The behavior is confirmed as a bug with ID PPP-66197. A fix for the issue will be introduced in Plesk 18.0.64, which is scheduled for release in the middle of the month. You may observe our Change log here.