Changes

Jump to: navigation, search

Thunderbird:Autoconfiguration:ConfigFileFormat

1,516 bytes added, 02:52, 18 March 2008
Document user input fields
The [http://developer.mozilla.org/en/docs/Thunderbird_ISP_hooks old/current RDF file format] seems good in structure, but needs to be cleaned up to remove the RDF bits, Mozilla specifics etc.. It would be processed as normal XML, e.g. using E4X in Thunderbird.
 
The email address (before @ or with domain) that the user entered can be used as placeholder in the config file, so the file is the same for all users (i.e. static).
<pre>
</clientConfig>
</pre>
 
= Placeholders =
 
The email address (before @ or with domain) that the user entered can be used as placeholder in the config file, so the file is the same for all users (i.e. static).
Placeholders:
These placeholders can be used as value or value part in most settings which take a string.
= User input fields = For some ISPs, the IMPA/POP/SMTP username (and maybe other fields) has no relation to the email address and has to be entered separately. E.g. Email address is ben.bucksch@wong.com (chosen by user), but username is G675476 (provided by ISP). In this case, an <inputfield> can be added for the username. It will let the client show a textfield to the user, the user-visible label is the one provided in the <inputfield label=""> attribute, to allow the ISP to use custom terminology for "username". The result is written into a placeholder %key%, where key is the content of the <inputfield key=""> attribute. The placeholder can then be used in other settings, specifically the IMAP/POP and SMTP username. For example, a <userinput label="Username" key="%USERNAME%">D123456</userinput> would result in a UI like: Username: [ ] example: D123456and cound be used elsewhere in the config file like: <username>%USERNAME%</username>and if the user enters "D32198", it would be automatically filled in like: <username>D32198</username>i.e. using D32198 as username for IMAP, POP or SMTP. The system is generic, so that it can in theory be used for other values as well. No other such purpose is currently known, apart from a separate POP and SMTP username maybe. It should not be used to let the user supply hostnames, as that would defeat the purpose of the autoconfig and be worse than the manual config UI provided by the client. = TODO:= 
* IMAP
* All settings and enum values
Confirm
596
edits

Navigation menu