Since Plesk Obsidian RC4, users’ Microsoft Outlook and Thunderbird mail clients can now be automatically configured based on entered emails.
@G J Piper ... I did know that there exist at least 2 different specifications for the lookup process and for the data structure, and that "Autodiscovery" is only 1 name of them. But now with your summary it seems to be much more complex than one should think is enough. Perhaps this is the main reason why the PLESK devs are, erm..., hesitating^^. However, TB could successfully get data from an old Confixx-controlled system, and as many contributors here already said, other platforms also support this feature [to which extent is not clear to me.] ... so, it should be doable at least in a basic way for PLESK devs.)
@PLESK devs: Please convince your management guys to authorize you to build a more sophisticated solution, that way NOT only shifting the source of helpdesk-workload from (now) client-account-configuration to (then) wrong-POP3/IMAP-decision within client-account-configuration. Better solve both at the same time. Perhaps with configuration/preference options for all plesk interface user levels (e.g. with: mode:automatic [default] / pop3 / imap; and with automatic_unknownClientType: pop3 / smtp; and with updates of "useragents" and the respective default modes). Thank you.
@G J Piper ... ok i was not aware about that the autodiscovery service can mandate a protocol to the client. I had understood that the clients (which i checked) always propose imap to the user if the server is replying at expected port. But that may be the situation only in case if there is no autodiscovery server, and so a wrong-conclusion from me. I apologize.
So ... questions:
A: is each client identifying itself to (your) autodiscovery service, so the service can disguise between, let's say, device classes, and recommends either the one or the other protocol to the specific client, depending on its better-considered suitability?
B: what if the user changes the automatic selection - will the client perform a fresh lookup at the service about the recommended/required details? or will it just adjust the port number?
Even TB is nudging users to apply the autodiscover results. users can indeed ignore them, but the UI is optimized for accepting the autodiscover proposal with IMAP.
While you fear they could pull their mails via POP3 to their disk and have a breakdown (of what exactly? of their disk?), I have more experience with problems caused by them "not knowing a dime" about quota-related datacare and by syncing tons of data causing freezes by hardware resource shortages.
As said, I understand the benefits of IMAP in certain situations. But I'd love to see more user autonomy (that needs to be implemented by clients developers)
One thing I want to remind is that Autodiscover preselects/forces IMAP configuration and does not give the user the choice of POP3. Sure IMAP has its justification in certain situations, e.g. multiclient operation and complementing mobile opertion. But I believe it is favored over POP3 unjustly, just for "fashion".
However I acknowledge that this what I call "imap enforcement problem" applies by "modern" clients anyway, and is not being solved by plesk servers' autodiscover-non-support.
Does any follower here know whether mailaccount settings autoconfig/autodiscover/autodetect was officially/natively supported in Confixx? I use a third party operated shared hosting legacy environment with Confixx - soon to be retired - where Thunderbird-supported autoconfig/autodetect is running. Seems strange that on the successor environment driven by the 'more progressive' Plesk, from the same issuer as Confixx and operated by the same third party, there is no such support (by now). Anybody sleeping... 2.5 yrs?