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

Resolved the target principal name is incorrect outlook 2016

occinodo

Basic Pleskian
When users set their domain name as the mailserver users receive an error that the target principal name is incorrect

Since putting the hostname of the server would mean that the user needs to alter this when a subscription is moved from one server to the other I'm wondering if there is any solution for this error.

Thanks in advance!
 
There is no real solution for this - you have the following options:

1) The users don't use SSL / TLS when connecting (not ideal)

2) Your users connect to the server hostname and SSL / TLS will be verified but if you move between servers they will need to update the IMAP / POP3 hostname

3) If you have few enough users, you could purchase a multi-domain certificate that will verify all their domains but this is really limiting in terms of numbers

As far as I am aware you cannot purchase a completely wildcarded SSL certificate that would work for any domain name, for obvious reasons.

We just use the server hostname and then notify users when they need to be moved, we obviously keep migrations to a minimum.

Rob
 
Back
Top