Confirmed users
596
edits
Thunderbird:Autoconfiguration: Difference between revisions
→Implementation: Move provider fetch up: just restoring what was deleted earlier.
(→Implementation: Restore spec for lookup XML at provider, and DNS, add DNS SRV) |
(→Implementation: Move provider fetch up: just restoring what was deleted earlier.) |
||
| Line 82: | Line 82: | ||
# Config files on harddisk, in <installdir>/isp/*.xml. Same file format as below. This is only for intranet deployments, we won't be shipping any configs by default anymore, in favor of the following alternatives. | # Config files on harddisk, in <installdir>/isp/*.xml. Same file format as below. This is only for intranet deployments, we won't be shipping any configs by default anymore, in favor of the following alternatives. | ||
# Try to get the configuration from the provider (not yet implemented) | |||
#* Try to contact https://autoconfig.<i>emailaddressdomain</i>/mail/mozilla.xml?emailaddress=<i>emailaddress</i> and see whether that host/URL exists. | |||
#* and/or, define a DNS TXT record on domain example.net (for my.account@example.net) which contains an URL like e.g. https://www.example.net/mozilla.xml . A similar, but slightly different proposal is described in detail on [[Thunderbird:Autoconfiguration:DNSBasedLookup|DNSBasedLookup]]. | |||
#* and/or use DNS SRV records _imap._tcp.example.com etc. | |||
#* That file contains the mail configuration. Content is described on [[Thunderbird:Autoconfiguration:ConfigFileFormat|ConfigFileFormat]]. | |||
# Try to find the config at the Mozilla server (if the email provider does not provide the configuration) | # Try to find the config at the Mozilla server (if the email provider does not provide the configuration) | ||
#* Fetch https://autoconfig.mozillamessaging.com/mail.xml?domain=<i>emailaddressdomain</i>. (Email address of user is not passed, otherwise Mozilla would have a list of email addresses of all users.) | #* Fetch https://autoconfig.mozillamessaging.com/mail.xml?domain=<i>emailaddressdomain</i>. (Email address of user is not passed, otherwise Mozilla would have a list of email addresses of all users.) | ||
| Line 87: | Line 92: | ||
#* It will not work for corporate email accounts. | #* It will not work for corporate email accounts. | ||
#* If a provider disagrees with a setting there, it can override the configuration by simply providing the config server in step 2. | #* If a provider disagrees with a setting there, it can override the configuration by simply providing the config server in step 2. | ||
# If we couldn't find any configuration file, we try to guess the configuration using some heuristics. We try imap.<i>domain</i>, pop.<i>domain</i>, pop3.<i>domain</i>, smtp.<i>domain</i> and mail.<i>domain</i>, and for each, try the common 2-3 ports. We check whether SSL is available, which authentication algorithms are announces by the server in the CAPABILITIES etc.. | # If we couldn't find any configuration file, we try to guess the configuration using some heuristics. We try imap.<i>domain</i>, pop.<i>domain</i>, pop3.<i>domain</i>, smtp.<i>domain</i> and mail.<i>domain</i>, and for each, try the common 2-3 ports. We check whether SSL is available, which authentication algorithms are announces by the server in the CAPABILITIES etc.. | ||
# If all fails, we ask the user to enter the configuration manually. | # If all fails, we ask the user to enter the configuration manually. | ||