Table of contents
- 1. Mechanisms
- 2. How to add support for your domain
- 3. Configuration file
- 3.1. Definition
- 3.2. Example
- 3.3. How to probe mail servers
- 3.4. SSL / STARTTLS
- 3.5. Authentication
- 3.6. Username
- 3.7. Enable visiturl
- 3.8. Documentation URL
Author: Ben Bucksch
Editor's note: This is just a rough draft and unfinished. Please do not change this document - the master copy is an HTML file on the editor's computer.
Thunderbird 3.1 and later (and 3.0 to some degree) includes mail account autoconfiguration functionality. The goal of autoconfiguration is to make it very easy for users to configure the connection of Thunderbird to their email servers. In many cases, people should be able to download and install Thunderbird, enter their real name, email address and password in the Account Setup Wizard and have a fully functioning mail client and get and send their mail as securely as possible.
This document describes how Autoconfiguration in Thunderbird works, and what to do to allow mail servers to be autoconfigured.
Thunderbird gets the server settings via different means, each of which is intended for different cases:
The ISPDB is a central database, currently hosted by Mozilla Messaging, but free to use for any client. It contains settings for the world's largest ISPs. We hope that the database will soon have enough information to autoconfigure approximately 50% of our user's email accounts.
It was added merely because we cannot assume that all big ISPs (including Microsoft) will immediately set up a configuration server for Thunderbird.
- Configuration server at ISP
ISPs have the option to provide their configuration information themselves directly to users, by setting up a web server at autoconfig.<domain>, which simply returns a static XML file with the configuration, as described below. For more complicated setups, for example when the login name does not appear in the the email address, the XML file can also be generated by the ISP. In such complicated cases, this is the only way to allow an automatic setup.
- Configuration file on harddisk
Administrators may place a configuration file in the Thunderbird installation folder. This is mainly intended for companies who install Thunderbird on their employees' computers and want to enable easy account setup without having to set up a configuration server. This method is not practical for other use cases, because it is difficult to update the configuration file. Therefore, public ISPs should use a configuration server.
If all other mechanisms failed, Thunderbird tries to guess the configuration, by trying common server names like imap.<domain>, smtp.<domain>, mail.<domain> etc., and, when a mail server answers, checking whether it supports SSL, STARTTLS and encrypted passwords (CRAM-MD5).
- Manual configuration
If guessing fails the user must manually enter the configuration information. Users can may also manually modify the account settings even if configuration information is successfully obtained by the methods described above.
All the lookup mechanisms use the email address domain as base for the lookup. For example, for the email address email@example.com , the lookup is performed as (in this order):
- tb-install-dir/isp/example.com.xml on the harddisk
- check for autoconfig.example.com
- look up of "example.com" in the ISPDB
- look up "MX example.com" in DNS, and for mx1.mail.hoster.com, look up "hoster.com" in the ISPDB
- try to guess (imap.example.com, smtp.example.com etc.)
We may in the future add DNS SRV records as supported mechanism in the future, but we currently do not.
How to add support for your domain
If you are a big ISP (> 100,000 users) providing email addresses solely under a few domains like "example.com" and "example.de", you may either submit the configuration to the ISPDB or set up a configuration server.
If you support email aliases and the user's login name is not part of the email address (for example, users may have "firstname.lastname@example.org" as email address, but the IMAP/POP/SMTP login name is neither "hero" nor "email@example.com", but "u67578"), you need to set up a configuration server, which does the email address -> login name lookup.
If you host customer domains, i.e. you are "hoster.com", but your customers have "firstname.lastname@example.org" and "email@example.com" as domains, with only a few users per domain, you need to set up a configuration server (or rely on DNS MX).
If you are a small company installing Thunderbird on your employees' desktops, you can place a configuration file in the Thunderbird installation folder.
Database URL is <https://live.mozillamessaging.com/autoconfig/v1.1/>, append domain name, e.g. <https://live.mozillamessaging.com/autoconfig/v1.1/freenet.de>.
Current process: File a bug in Bugzilla, Product "Mozilla Messaging", Component "ispdb", with a configuration file that matches the requirements described below. Request review from bwinton, gozer or ben.bucksch.
Future: add the configuration to the ISPDB server app.
Configuration server at ISP
Given the email address "firstname.lastname@example.org", Thunderbird first checks <http://email@example.com> and then <http://example.com/.well-known/autoconfig/mail/config-v1.1.xml>.
If you are a small company, you can put the XML configuration file on your web server, at URL <http://example.com/.well-known/autoconfig/mail/config-v1.1.xml>. (This is not yet finalized and subject to change.)
If you are an ISP that hosts domains for your customers - for example, you are hoster.com and your customer registers fancy.com or example.com, and your servers accept and serve the mail for example.com -, you should set up an autoconfig server.
For each customer domain, you add a DNS record (in addition to the existing MX, A www etc. DNS records):
autoconfig A 10.2.3.4
autoconfig CNAME autoconfig.hoster.com
... where 10.2.3.4 and autoconfig.hoster.com are IP addresses / hostnames you own.
This allows Thunderbird to find you as hoster.
You set up a web server bound to a physical IP address. This may be on the same machine as other web servers, but you must dedicate one IP address to the autoconfig web server and the web server must be configured to the content to any requested domain.
In Apache terms, you must use an "ip-based virtual host", not a "name-based virtual host". In the Apache configuration files, that means something like:
Listen 10.2.3.4:80 (of course, you use a public IP address that you own) or (Listen *:80 ?)
<VirtualHost 10.2.3.4> DocumentRoot /www/autoconfig/ ServerName autoconfig.hoster.com ErrorLog ... CustomLog ... </VirtualHost>
TODO confirm that the Apache configurations works like this
Place the configuration file at the URL /mail/config-v1.1.xml on that host.
All config files must be served as
Content-Type: text/xml (or
application/xml), otherwise the file will be ignored. Also, they must use charset UTF-8 (esp. if there are any non-ASCII-characters).
<?xml version="1.0" encoding="UTF-8"?> <clientConfig version="1.1"> <emailProvider id="freenet.de"> <domain>freenet.de</domain> <displayName>Freenet Mail</displayName> <displayShortName>Freenet</displayShortName> <incomingServer type="imap"> <hostname>imap.freenet.de</hostname> <port>993</port> <socketType>SSL</socketType> <authentication>password-encrypted</authentication> <username>%EMAILADDRESS%</username> </incomingServer> <incomingServer type="imap"> <hostname>imap.freenet.de</hostname> <port>143</port> <socketType>STARTTLS</socketType> <authentication>password-encrypted</authentication> <username>%EMAILADDRESS%</username> </incomingServer> <incomingServer type="pop3"> <hostname>pop.freenet.de</hostname> <port>995</port> <socketType>SSL</socketType> <authentication>password-cleartext</authentication> <username>%EMAILADDRESS%</username> </incomingServer> <incomingServer type="pop3"> <hostname>pop.freenet.de</hostname> <port>110</port> <socketType>STARTTLS</socketType> <authentication>password-cleartext</authentication> <username>%EMAILADDRESS%</username> </incomingServer> <outgoingServer type="smtp"> <hostname>smtp.freenet.de</hostname> <port>465</port> <socketType>SSL</socketType> <authentication>password-encrypted</authentication> <username>%EMAILADDRESS%</username> </outgoingServer> <outgoingServer type="smtp"> <hostname>smtp.freenet.de</hostname> <port>587</port> <socketType>STARTTLS</socketType> <authentication>password-encrypted</authentication> <username>%EMAILADDRESS%</username> </outgoingServer> <documentation url="http://kundenservice.freenet.de/hilfe/email/programme/config/index.html"> <descr lang="de">Allgemeine Beschreibung der Einstellungen</descr> <descr lang="en">Generic settings page</descr> </documentation> <documentation url="http://kundenservice.freenet.de/hilfe/email/programme/config/thunderbird/imap-thunderbird/imap/index.html"> <descr lang="de">TB 2.0 IMAP-Einstellungen</descr> <descr lang="en">TB 2.0 IMAP settings</descr> </documentation> </emailProvider> </clientConfig>
How to probe mail servers
To determine a server's capabilities, you can contact the server directly and talk the POP/IMAP/SMTP protocol manually (assuming you already know the hostname).
For non-SSL, use
netcat -v hostname port (preferred) or
telnet hostname port as "client".
- POP3, port 110: when you see
+OK WEB.DE POP3-Serveror similar, enter
CAPA, hit return.
- IMAP, port 143: when you see
* OK mwinf2j04 IMAP4 server readyor similar, enter
1 CAPABILITY, hit return.
- SMTP, port 587 or 25: when you see
220 mail.gmx.net GMX Mailservices ESMTPor similar, enter
EHLO example.net, hit return.
In all cases, the server should respond with a list of capabilities.
SSL / STARTTLS
There are 2 SSL variants: normal SSL and STARTTLS.
The old-style SSL (including TLS, which is just the new name for SSL) has a special port:
- POP3 via SSL: port 995
- IMAP via SSL: port 993
- SMTP via SSL: port 465
On Linux, you can contact the server via
openssl s_client -connect hostname:port
You should see output about the SSL handshake and the certificate. Important is what is listed as "CN=". This must be the same as the hostname that you contacted, otherwise the certificate is not valid (or you need to use another hostname).
If you see nothing, then probably the server does not support SSL.
After that, you can have the same protocol exchange as with netcat on standard ports, as listed above.
STARTTLS is a special, new form of SSL, which works on the standard ports (e.g. port 143 for IMAP). You can contact the server via netcat as mentioned above. If you see "STARTTLS" (for IMAP, SMTP) or "STLS" (for POP) listed as one of the capabilities, the server should support STARTTLS.
To try it out, on Linux, you can contact the server via
openssl s_client -connect hostname:port -starttls proto
...where "proto" is
smtp. For example:
openssl s_client -connect imap.example.com:143 -starttls imap
You should get the same response as described above for openssl.
Configuration file format
Add the appropriate port and socket type for each server, depending on protocol and SSL support. For example,
for IMAP with SSL:
for IMAP with STARTTLS:
for IMAP without any SSL (deprecated!):
Please do not submit or serve any configurations without SSL! There's no reason in 2010 why users still need to read mail entirely unprotected.
If you are an ISP and think the server load is too high, try adding an SSL accelerator. They are cheap and widely used. In fact, even most freemail (!) providers these days support SSL, so if users pay you money for ISP service, that's all the more reason to give them proper service. But first simply try to enable software SSL - small servers may be fine with SSL and without any additional installations.
Either way, be sure to use a valid certificate:
- issued by a CA recognized by Firefox / Thunderbird
- not expired
- the CN in the cert must match the hostname that Thunderbird contacts and that is listed as <hostname> in the configuration file. If they don't match, Thunderbird must assume that the user may be under attack, otherwise the SSL guarantees no longer hold. Thunderbird either warns the user or ignores the server. (Note that you can get certificates for free these days, for example from startssl.com.)
Probe the mail server, as explained above for STARTTLS. If you see
APOP in the response, the server should support encrypted passwords. If you only see
PLAIN, or no
AUTH at all, the server probably does not support secure authentication. In the former case, select "Encrypted passwords" as "Authentication method" (in Thunderbird Account Settings UI, incoming server and SMTP server), and test whether you can actually log in with a real account (because some servers are unfortunately broken with regards to authentication, often due to a wrong or misconfigured SASL installation).
Configuration file format
In the configuration file, for each IMAP, POP and SMTP server, you need to specify the authentication method.
For plaintext passwords:
Discouraged settings (SMTP only):
If the SMTP server can only be used after checking incoming mail, please use
Note that RFC 4409 disallows that and requires the customer-facing SMTP server to support proper authentication via AUTH.
If the SMTP server can only be used within the ISP's network, and requires no authentication, use:
or, if it requires authentication in addition to the user being in the ISP network, use e.g.:
However, that means that users on the road or in the office are unable to send mail, which is a real problem for many of our users. This violates RFC 4409 as well and is an outdated configuration. Please try find a configuration that works in all cases, for the sake of the users.
Please support MD5 passwords
Please support authentication with CRAM-MD5. It is simple to implement, and to set up, and you can still use RADIUS or a database that stores passwords in plaintext, so you don't need to make changes to your mail server or authentication infrastructure apart from installing some software and configuring it correctly. CRAM-MD5 is particularly important when no SSL is used: Never make users send their passwords in plaintext over the network! (Not even in your ISP network.) We warn users in the Mail Account Creation dialog about such insecure configurations, and we reserve the right to block them in the future.
As an ISP, you should ideally store passwords in encrypted format, which removes the risk of mass password theft (and possibly reuse on other sites) if somebody hacks your servers. You can still support plaintext passwords in this case, and encrypt passwords on the fly before comparing. (Users who use plaintext passwords would still be somewhat exposed, but at least you don't have the risk of the whole plaintext password database being stolen.) You can use both plaintext and encrypted authentication transmission with plaintext or encrypted password databases - the two issues are independent.
If the user's IMAP login name is the same as his email address (for example, if "firstname.lastname@example.org" is the login name), add:
If the login name is the same as the first segment before the @ of the email address (for example, if the login name for "email@example.com" is just "fred"), use:
Aliases, or username not part of email address
Note that the above must be true for any email address that the user would set up - even for aliases.
You can ignore aliases like info@, if that's an alias for fred@ (or both fred@ and wilma@) and Fred would set up firstname.lastname@example.org in Thunderbird, not info@.
If, however, Fred can set up email@example.com as alias for firstname.lastname@example.org, and neither "hero" nor "email@example.com" would work as login name on your IMAP server, you need to set up a lookup of alias -> username on your autoconfig server. So, if you get a request for <http://autoconfig.example.com/mail/c...firstname.lastname@example.org>, your autconfig server must have a script which responds to /mail/config-v1.1.xml and returns the concrete username, for example:
... (or <username>email@example.com</username>, as appropriate) for firstname.lastname@example.org. This is the only way to enable automatic configuration without users having to remember what their primary login name was, which is a serious problem in practical experience. Even if you have told them all the necessary information in your welcome letter, they usually cannot find the letter. That's exactly where autoconfiguration tries to help.
Some providers do not provide IMAP or POP service by default, but require it to be enabled via a web UI. If that is the case, add the URL that a logged-in user would use into this field, and the application can prompt the user to visit it.
This is not yet supported by Thunderbird 3.1, but should be in the future, so please add this critical information where it applies.
If you are an ISP, please by all means avoid this. It's one of those "walls" against which users run the hard way.
If the configuration is (partially) based on a help webpage of the ISP that describes the configuration that end users should use, you can record its URL here. You may add several of them, as several element. It is for informational purposes only and mainly for the maintenance of the config file, the client currently does not use them at all.