After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 760329 - Try to poke autodiscovery when creating new account
Try to poke autodiscovery when creating new account
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Mailer
3.18.x (obsolete)
Other Linux
: Normal enhancement
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on: 750564
Blocks:
 
 
Reported: 2016-01-08 17:53 UTC by Richard Hering
Modified: 2017-11-09 15:48 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Richard Hering 2016-01-08 17:53:01 UTC
Hi, I have my own server with mailhosting services. I tried my new automx-installation (https://automx.org). With Thunderbird it works perfectly, but with evolution not.

With Evolution I doesn't see any requests in my webserver logs. Here is the working autoconfig-link:

https://autoconfig.internethering.de/autodiscover/autodiscover.xml?emailaddress=test@internethering.de
Comment 1 Milan Crha 2016-01-29 13:45:43 UTC
Thanks for a bug report. I suppose you talk about "Look up mail server details based on the entered e-mail address" option provided when you are creating a new mail account, right?

That option doesn't do any destination server data sniffing, it asks a database with preconfigured options located at GNOME servers for settings base don the email address domain and preselects what it can.

I agree it would be nice to be able to do the autodiscovery in more general way.
Comment 2 Tobias Mueller 2017-06-01 09:11:09 UTC
There seem to be many ways.
The Thunderbird way: https://developer.mozilla.org/en/Thunderbird/Autoconfiguration
The Outlook way: https://technet.microsoft.com/en-ie/library/cc511507
And a more generic approach: https://tools.ietf.org/html/rfc6186 also exists.

K9 is tracking status here:  https://github.com/k9mail/k-9/issues/865
Comment 3 Milan Crha 2017-08-04 08:38:29 UTC
(In reply to Richard Hering from comment #0)
> https://autoconfig.internethering.de/autodiscover/autodiscover.xml?emailaddress=test@internethering.de

Unfortunately that links speaks of ActiveSync and it doesn't support GET method (as it says so). Could you provide a result of that page when it returns the XML content, please? Sanitize anything private in it, including user names, emails, server addresses and such. I'd like to see how the result look like.

There is an autodiscovery with Exchange server, which I can reach, but it doesn't show anything but Exchange Web Services, which is not the way to go here (the evolution-ews plugin can do it (and it does), but not evolution itself).

(In reply to Tobias Mueller from comment #2)
> And a more generic approach: https://tools.ietf.org/html/rfc6186 also exists.

I've just done that, (partly) as part of bug #750564. See it for more details.
Comment 4 Milan Crha 2017-11-09 15:48:35 UTC
And now also for evolution, when using Edit->Accounts->New->Collection Account, it can detect several types of server sources. It's extensible, using EConfigLookupWorker-s on top of an EConfigLookup instance.

The new collection account wizard has a Server advanced option, where one can specify additional servers or URLs or domains. As an example, users with hosted Google services, but without gmail.com domain in the email could configure such accounts in evolution, but it was, kindly said, inconvenient. This new account allows to enter:

   Email Address or Username: user@company.com
   Servers: gmail.com

and then everything will be configured as needed (there are some intermediate steps, like choosing which parts to configure, but those can be left mostly as offered by the code).

Another example are CalDAV/CardDAV servers. Those are slightly more complicated, because they can involve incorrect/self-signed server certificates and may eventually require to enter the password, but all that can be handled by:

   Email Address or Username: user
   Servers: webdav.example.com/dav/

Such entered Servers has automatically prepended https://, but if the URL already contains the scheme, then it is preserver. That means the https:// usage can be overwritten with:

   Servers: http://webdav.example.com/dav/

And that's basically it.

Created commit 1bd5a348be in evo master (3.27.2+)
Created commit_cd8fb9f2f7 in ews master (3.27.2+) [1]

[1] https://git.gnome.org/browse/evolution-ews/commit/?id=cd8fb9f2f7