On 19.04.2016 12:21, Philip Whitehouse wrote:
On 2016-04-19 10:32, Rüdiger Hahn wrote:
Hi all,

I am wondering why there is not even one Android email client that is
capable of using at least one of the three mechanisms which are
available for autoconfiguring email settings. Some desktop clients
(Windows, Linux, MacOS) and the iPhone email client are supposed to be
capable using at least one of the following autoconfiguration
mechanisms.

It looks like K9 also does not use any of the following three
autoconfiguration mechanisms. I could not find even any Android client
that would request the correct configuration settings. Some are just
guessing configuration settings, but none of the Android clients I
tested really use the information I provided in the following three
ways.

    * Autodiscover, xml based: created by Microsoft about 10 years ago.
Probably mostly for Outlook/Exchange accounts, but also works with any
other email account. This site should give all information needed for
implementation: https://technet.microsoft.com/en-us/library/cc511507(v=office.14).aspx
    * Autoconfig, xml based: created by the Mozilla foundation. Quite
simple xml configuration information originally created for
Thunderbird, in the meantime also being used by other clients.
Information about this mechanism can be found
here: https://wiki.mozilla.org/Thunderbird:Autoconfiguration:ConfigFileFormat
    * DNS-based configuration: created by IETF in 2011. SRV records give
all information for email configuration. Information about this way
can be found here: https://tools.ietf.org/html/rfc6186

With any of these configuration mechanisms a user would only have to
provide his email address and a password to get the correct
configuration settings for pop3, imap and smtp (submission).

I would really like if this was implemented in K9 Mail.

Is this planned for the future?

It's got an open issue in our tracker :)

I've added information on the DNS configuration.

https://github.com/k9mail/k-9/issues/865

It's probably never been a huge priority because:

a) Most people use the major hosting providers, which we can configure (in a more reliable way) in the app itself.
b) People who set-up their own hosting know all the details anyway
c) It's a one-time problem - it's not a persistent issue, so it only annoys the developer once d) There's more than one standard and it's hard to know how well even those are supported / deployed.

But it'll probably be done eventually.

- Philip Whitehouse


Hi Philip,

thank you for your reply. Concerning your reasons for the low priority I do agree with c) and d), but let me make some notes about a) and b):

a) You are right if you are talking about private accounts, but people who also have mail accounts with their companies will not be covered by this solution. I do really know this because I am supporting some mid size companies who have this email account configuration problems every time when there are new employees or when smartphones are being changed. b) It is true: in such companies people like me or any administrators know all the configuration details, but the employees normally don't. So administering the smartpones of such companies (20, 30 or more employees) would be incredible much easier when the email apps would use the information that we provide.

Rüdiger Hahn


--
--
You received this message because you are subscribed to the K-9 Mail Users List.
To post to this group, send email to [email protected]
To unsubscribe, email [email protected]
To report an issue with K-9 Mail, visit 
http://code.google.com/p/k9mail/issues/list
For more options, visit this group at http://groups.google.com/group/k-9-mail

--- You received this message because you are subscribed to the Google Groups "K-9 Mail" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to