82
edits
Line 209: | Line 209: | ||
5.) The first valid '''TXT''' record shall be used in order to fetch the configuration file. In case the SSL secured server can not be chained to a trusted root, has a domain name mismatch or other failures, connection shall be aborted. TB may use the next valid '''TXT''' record if possible and repeat this step. | 5.) The first valid '''TXT''' record shall be used in order to fetch the configuration file. In case the SSL secured server can not be chained to a trusted root, has a domain name mismatch or other failures, connection shall be aborted. TB may use the next valid '''TXT''' record if possible and repeat this step. | ||
6.) The | 6.) TB shall include the originally requested email value as referrer information in its GET headers . The value of the referrer header shall have the format "''mailto:user@domain.com''". This allows serving of dynamically generated configuration files. | ||
7.) The user | 7.) The configuration file is downloaded and checked for sanity and parsed. At this stage the user is present with a UI dialog, stating the location of the configuration file (The actual '''URL''' from the which the config was fetched) and present other useful information. | ||
8.) The user | 8.) The user may make selections such as different choices (like POP3 versus IMAP or IMAP versus IMAPs etc.). Alternatively TB may use by default best and most secure protocols. | ||
9.) TB tries to use the new settings and prompt for passwords etc. as usual. | 9.) The user confirms his preferences (if any) and confirms the setup of the account. | ||
10.) TB tries to use the new settings and prompt for passwords etc. as usual. | |||
edits