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

Question SSL Setup Outlook

jonny_alex

Basic Pleskian
Hey Pleskians

My customers always have to set up their Outlook manually and enter all details like server SSL encription and ports.
First of all, is it possible to make this happen automatically so the only enter their mail and password and all else will install automatically?

Second of all, if i set their account up, even if i use Let's encrypts on every mail and domain the error:
The server you are connected to is using a security certificate that cannot be verified. The target principal name is incorrect.

Shows up in every Outlook restart..

Does anyone have a step by step guide to solve it?

I already tried the guide How to secure a Plesk mail server with different SSL certificates (SNI support)

My Result:


echo 'Q' | openssl s_client -connect localhost:465 -servername nail-barbara.ch -showcerts 2>&1 | grep -Eo 'CN=[^/]+' | uniq
CN=nail-barbara.ch
CN=Let's Encrypt Authority X3
CN=DST Root CA X3
CN=nail-barbara.ch
CN=Let's Encrypt Authority X3

But still the error appears...?
 
I had a similar issue, with an expired cert I got re-issued under the same name handle. It turned out that it still delivered the expired cert, although the newer one was selected. I deleted these certs and started over and then it worked.
 
Concerning the SSL issue (maybe this will not help): Is the domain entered in Outlook as inbound and outbound mail server the domain for which you set the mail server certificate?

I mean, if you have the certificate for example.com there should not be mail.example.com or something like this in Outlook.
 
Back
Top