Confirmed users
596
edits
Thunderbird:Autoconfiguration: Difference between revisions
Jump to navigation
Jump to search
→Implementation: Add heustics step, as implemented. I don't like it.
(→Proposal: Rename Proposal to Implementation, because most of it is now implemented) |
(→Implementation: Add heustics step, as implemented. I don't like it.) |
||
| Line 91: | Line 91: | ||
#* 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 the [[Thunderbird:Autoconfiguration:ConfigFileFormat|config file]] contains extra values to be filled in by the user, there's a screen inserted that provides textfields for this. | # If the [[Thunderbird:Autoconfiguration:ConfigFileFormat|config file]] contains extra values to be filled in by the user, there's a screen inserted that provides textfields for this. | ||
# | # 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 | # If all fails, we ask the user to enter the configuration manually. | ||
If we could find a configuration, we're done already, with that one screen. | If we could find a configuration, we're done already, with that one screen. | ||