589
edits
Thunderbird:Autoconfiguration: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 87: | Line 87: | ||
#* 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. | ||