DanielW’s Blog

July 26, 2009

Email auto-config using DNS?

Filed under: Uncategorized — Tags: — DanielW @ 5:48 pm

In response to How to configure a mail client (no comments there).

Rolf proposes a XML config file standard to quickly setup email accounts in mail clients. I always had the idea of a DNS based auto config system for mail clients. (maybe there is already such a thing?)

It would work like that:

  • the user enters his mail address in his mail client i.e. someuser@kde.org
  • the client would then ask for a TXT dns record for something like __mailautoconfig.kde.org
  • from that record the client would get all needed information (smtp,imap,pop3 servers and so on)
  • in best case the user now only needs to enter the password and would be done

Together with the obvious things like smtp/pop3/imap server address and ports, it could contain information about supported encryption and authentication modes and if smtp auth is needed. Also the url of a web mail interface for the mail address could be published.

Very important to make things easy for the user is the “login-field” to store how the login name is created out of the mail address, with values like “address” = complete mail address as username, “user” = only the user part of the mail address or “manual” = the user has to enter his login )

And yes, there are security implications, but the information published over dns that way isĀ  public availableĀ  (for bigger mail providers at least) anyway.

So, what do you think? Stupid idea which has already been thought of and thrown away for an obvious reason I’m missing?

(And yes I know that some mail client already have such an auto config feature, but they use their own database (local or over the net) to map mail addresses to settings. Smaller mail services will not get into it and they may not always be up to date.)

6 Comments »

  1. It’s already possible to use SRV records to point at services. XMPP uses these, for example, as does Microsoft’s Active Directory.

    For email, you could have a set of SRV records like:
    _smtp._tcp.example.com => mail.example.com:25
    _pop3._tcp.example.com => mail.example.com:110
    _imap._tcp.example.com => mail.example.com:143

    It doesn’t handle any of the more advanced features you suggest, and I don’t think anyone actually uses SRV records in this way.

    Comment by Stuart — July 26, 2009 @ 6:50 pm

  2. Write an RFC :P

    Comment by Troy Unrau — July 26, 2009 @ 8:17 pm

  3. By DNS ok, but why not by using DHCP ? (like browsers’ proxy auto-config - alias WPAD)

    Comment by yoho — July 27, 2009 @ 10:20 am

  4. @yoho: DHCP would not allow you to configure an email client against remote email services. My primary email provider is separate from my ISP, so I would not be able to use DHCP to auto-configure my email client with that service.

    Comment by Karellen — July 27, 2009 @ 10:44 am

  5. I like the idea very much.

    Comment by derdestiller — July 28, 2009 @ 2:10 am

  6. The Microsoft stuff is a bit more complex than just using DNS SRV records.

    I won’t post a link to MSDN, but a search for MS-OXDISCO and MS-OXDSCLI will give you the specs.

    Comment by Brad Hards — July 28, 2009 @ 2:29 am

RSS feed for comments on this post. TrackBack URL

Leave a comment

Powered by WordPress