• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • 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.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

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