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

Unable to create an Office365 DKIM alias in Plesk

mr-wolf

Silver Pleskian
Plesk Guru
TITLE:
Unable to create an Office365 DKIM alias in Plesk
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE:
Plesk 17.5.3 / Ubuntu 16.0.4 LTS
PROBLEM DESCRIPTION:
For a client with Office365 mail I want to enable DKIM.
For this I follow the procedure described here;

Use DKIM to validate outbound email sent from your custom domain in Office 365: Exchange Online Help

I need to create 2 CNAME pointing to a Microsoft record
This is not possible using the GUI it is possible to do it with CLI


upload_2017-6-23_14-33-24.png
STEPS TO REPRODUCE:
Add this record using the GUI:

Code:
ACTION=add
DOMAIN=recyclevalley.nl
SUBDOMAIN=selector1._domainkey
TARGET=selector1-recyclevalley-nl._domainkey.recyclevalley.onmicrosoft.com

/usr/local/psa/bin/dns --${ACTION} ${DOMAIN} -cname ${SUBDOMAIN} -canonical ${TARGET}
ACTUAL RESULT:
upload_2017-6-23_14-33-24.png
EXPECTED RESULT:
Accept the entry​
ANY ADDITIONAL INFORMATION:
I think it is testing for valid characters. I suspect it doesn't like the underscores. These should be valid as they are quite commonplace for these kind of records.
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM:
Confirm bug
 
Thank you. We have already submitted this issue as PPPM-4301 and developers are working on it.
 
Back
Top