Thunderbird:Autoconfiguration:DNSBasedLookup: Difference between revisions

Jump to navigation Jump to search
→‎Definitions: Don't use lower priority MX records
(Implementation problems for Thunderbird)
(→‎Definitions: Don't use lower priority MX records)
Line 17: Line 17:
The location of the configuration file shall be discovered by the following method:
The location of the configuration file shall be discovered by the following method:


1.) The '''MX''' record(s) of the user supplied email address is fetched from the DNS zone. In case no '''MX''' record exists, the '''A''' record of the base domain name is used [RFC 2821].  
1.) The '''MX''' record(s) of the user supplied email address is fetched from the DNS zone. In case no '''MX''' record exists, the '''A''' record of the base domain name is used [RFC 2821]. If there are '''MX''' records of different priorities, only the one with the highest priority is used, because lower priority ones may go to backup servers with a different setup.


2.) A '''TXT''' record with the content "''mailconf=https://''" is fetched from the DNS zone based on the highest priority '''MX''' record found. If no matching '''TXT''' record is found the next lower '''MX''' record shall be fetched. At last the '''A''' record of the domain is checked for a '''TXT''' record.  
2.) A '''TXT''' record with the content "''mailconf=https://''" is fetched from the DNS zone based on the lookup above.


3.) A sanity check shall be performed (correctness of the URL) and in case of failure proceed to the next possible '''TXT''' record as shown above. Only SSL secured locations are possible, meaning the protocol prefix ''https://'' '''must''' be present.
3.) A sanity check shall be performed (correctness of the URL) and in case of failure proceed to the next possible '''TXT''' record as shown above. Only SSL secured locations are possible, meaning the protocol prefix ''https://'' '''must''' be present.
Confirmed users
596

edits

Navigation menu