Cannot get it working properly and also a question or two.

[HHawk]

Hi!

First off, thank you for this script! Seems very promising as Plesk apparently leaves us out in the cold. Even with Obisdian the (Plesk) autodiscover is not working correctly.

Therefor I decided to do a search on autodiscover features for Plesk and stumbled upon your solution / script. But for some reason it's not working correctly.

I managed to get autodiscover working for Thunderbird on the first go, but it didn't work for Outlook 2016. So I decided to redo the (test) server installation once again. On the 2nd go also Thunderbird autodiscover didn't work anymore. So I will redo it a third time. Hopefully that's the charm.

And yes, I did follow the wiki, but it's not clear what I am doing wrong to be honest.

With Plesk Obsidian I disabled the "Enable mail autodiscover"-option under "Mail Server Settings". I guess this should be disabled, otherwise the script won't work, right?

I will give it a new go in a few on a fresh Plesk Obsidian installation in a few minutes. Maybe I overlooked something. As mentioned I managed to get the mailserver settings discovered in Thunderbird, but not in Outlook 2016 (so far every approach failed).

As for my question, probably not possible, we have adviced our clients to use the full hostname for the mailserver e.g. ns1.servername.com. I read the wiki and apparantly you have to set the hostname to servername.com instead. Would it still be possible to use ns1.servername.com as mailserver?

If not or it's too much, then nevermind. It would be great if we could keep using ns1.servername.com. So current customers don't need to change anything obviously.

Anyways, will report back later after I setup the new server freshly.

Regards,
Mik

[MegaS0ra]

Hi !

As Plesk released autodiscover in Obsidian version, we are not updating this project anymore.

Also, this autodiscover/autoconfig project was developped for Plesk Onyx, before Plesk implemented SNI and autodiscover; so we can't be sure how it reacts when installed on Plesk Obsidian.

--

I'm surprised none of these solutions are working for you. Does you domain name have a SSL cert ?
(btw, Plesk just relased an Obsidian update yesterday, that allows you to choose the server name used for autodiscover).

In our script, you can choose any name you want. You'll have to use the same name for the mail server certificate of course.

Regards

[HHawk]

Hi MegaS0ra,

Thanks for responding.

I understand, but...

I quote: "Warning: Outlook 2016/2019/Office 365 does not support autodiscover for IMAP/SMTP protocols."

From: https://support.plesk.com/hc/en-us/articles/360009747280-How-to-manage-mail-autodiscover-in-Plesk-Obsidian-

So the function in Plesk Obsidian is rather useless as it does NOT work for Outlook at all!?
Therefor we are still looking for a working solution obviously.

The hostname (with and even without ns1) have SSL certificates (used LE for it) and also the test domain has a SSL certificate (also LE).

[dna75]

Autodiscover works fine with Outlook!

[MegaS0ra]

I didn't know that, especially because our autodisover was tested for Outlook 2016 at least, but we did not test Plesk's autodiscover with Outlook. I will try both in a few days and let you know how it goes on my setup. Le 22 janvier 2020 18:41:08 HHawk <[email protected]> a écrit :

…

Hi MegaS0ra, Thanks for responding. I understand, but... I quote: "Warning: Outlook 2016/2019/Office 365 does not support autodiscover for IMAP/SMTP protocols." From: https://support.plesk.com/hc/en-us/articles/360009747280-How-to-manage-mail-autodiscover-in-Plesk-Obsidian- So the function in Plesk Obsidian is rather useless as it does NOT work for Outlook at all!? Therefor we are still looking for a working solution obviously. The hostname (with and even without ns1) have SSL certificates (used LE for it) and also the test domain has a SSL certificate (also LE). — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[dna75]

Have you turned on the Audiscover in the mail settings (global or the specific domain)?

[HHawk]

Tried both server-wide enabled (including the test domain) as disabled server-wide.

At dna75; I am talking about two things, if you didn't get it.
The script here (not working as mentioned in my first post) as well Plesk Obsidian's autodiscover for which Plesk states clearly that it does not work with several Outlook versions. Which you can read on their own KB from their website.

[MegaS0ra]

Hi,
I'm doing some tests to check compatibility with Outlook 2016/2019.

Did you try with another Outlook version or not ?

With our autodiscover solution, did you check if the following URL are accessible ?
For Outlook :
https://domain.tld/autodiscover/autodiscover.xml
For Thunderbird :
https://autoconfig.domain.tld/mail/config-v1.1.xml

Thanks

[HHawk]

Plesk and we are currently working on it. So far we got several things working with minor adjustments. Plesk expects a full working update in a month or two. So this is not needed anymore. :-) Op 5 feb. 2020 21:14, om 21:14, Sora Haiji <[email protected]> schreef:

…

Hi, I'm doing some tests to check compatibility with Outlook 2016/2019. Did you try with another Outlook version or not ? With our autodiscover solution, did you check if the following URL are accessible ? For Outlook : https://domain.tld/autodiscover/autodiscover.xml For Thunderbird : https://autoconfig.domain.tld/mail/config-v1.1.xml Thanks -- You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: #14 (comment)

[MegaS0ra]

Okay

Anyway, after testing, I can now confirm that :

• Our autodiscover solution works on both Plesk 17 & 18, and with Outlook 2016 & Outlook 2019.
• The Plesk autodiscover solution seems to work correctly with Outlook 2016 & Outlook 2019.

So not sure why Plesk says the opposite...

[HHawk]

Well Plesk support is still busy as it still does not work all the time on some occasions apparently. No clue why it's working for you with Oulook 2019, because here it doesn't. Even after Plesk support was working on it.

Also changed to Postfix and Dovecot (for SNI support) on the mailserver. Didn't help. It still wants to use the Plesk default certificate. And yes; server, domain, mailaccount, etc. are all protected with purchased SSL certificates.

This was Plesk support's last reply (by Renan Genova Ferreira):

We have exhausted every possibility to make autodiscover work in your environment considering your current mail server settings and the state of our product. But despite our best efforts, we confirmed that there's no 100% valid workaround for it. Nevertheless, please rest assured that we have raised this to our product team; The implementation of this feature is being tested by our development team and will be available in future product updates, though we do not have an exact ETA as of now.

Sigh. Oh well...

[UltimateByte]

@HHawk Well, that sounds weird.
About SNI: What's your Postfix and Dovecot version?
And more importantly, what's your distribution and version?

Also, I assume you did generate a certificate for your domain you're trying to connect to. But did you disable default website in your IP settings within Plesk?