SMTP

   1 <?xml version="1.0"?>
   2 <clientConfig version="1.1">
   3     <emailProvider id="rockstable.it">
   4       <domain>rockstable.it</domain>
   5 
   6       <displayName>Rockstable Mail</displayName>
   7       <displayShortName>RSIT Mail</displayShortName>
   8 
   9       <!-- type=
  10            "imap": IMAP
  11            "pop3": POP3
  12            -->
  13       <incomingServer type="imap">
  14          <hostname>mx1.rockstable.it</hostname>
  15          <port>993</port>
  16            <!-- "plain": no encryption
  17                 "SSL": SSL 3 or TLS 1 on SSL-specific port
  18                 "STARTTLS": on normal plain port and mandatory upgrade to TLS via STARTTLS
  19                 -->
  20          <socketType>SSL</socketType>
  21          <!-- <username>%EMAILLOCALPART%</username> -->
  22          <username>%EMAILADDRESS%</username>
  23             <!-- Authentication methods:
  24                  "password-cleartext",
  25                           Send password in the clear
  26                           (dangerous, if SSL isn't used either).
  27                           AUTH PLAIN, LOGIN or protocol-native login.
  28                  "password-encrypted",
  29                            A secure encrypted password mechanism.
  30                            Can be CRAM-MD5 or DIGEST-MD5. Not NTLM.
  31                  "NTLM":
  32                            Use NTLM (or NTLMv2 or successors),
  33                            the Windows login mechanism.
  34                  "GSSAPI":
  35                            Use Kerberos / GSSAPI,
  36                            a single-signon mechanism used for big sites.
  37                  "client-IP-address":
  38                            The server recognizes this user based on the IP address.
  39                            No authentication needed, the server will require no username nor password.
  40                  "TLS-client-cert":
  41                            On the SSL/TLS layer, the server requests a client certificate and the client sends one (possibly after letting the user select/confirm one), if available. (Not yet supported by Thunderbird)
  42                  "OAuth2":
  43                            OAuth2. Works only on specific hardcoded servers, please see below. Should be added only as second alternative.
  44                  "none":
  45                            No authentication
  46                  -->
  47          <authentication>password-cleartext</authentication>
  48          <password>optional: the user's password</password>
  49       </incomingServer>
  50 
  51       <outgoingServer type="smtp">
  52          <hostname>mx1.rockstable.it</hostname>
  53          <port>587</port>
  54          <socketType>STARTTLS</socketType> <!-- see <incomingServer> -->
  55          <username>%EMAILADDRESS%</username> <!-- if smtp-auth -->
  56             <!-- smtp-auth (RFC 2554, 4954) or other auth mechanism.
  57                  For values, see incoming.
  58                  Additional options here:
  59                  "SMTP-after-POP":
  60                      authenticate to incoming mail server first
  61                      before contacting the smtp server.
  62                   Compatibility note: Thunderbird 3.0 accepts only "plain",
  63                   "secure", "none", and "smtp-after-pop".
  64                   It will ignore the whole XML file, if other values are given.
  65             -->
  66          <authentication>password-cleartext</authentication>
  67             <!-- If the server makes some additional requirements beyond
  68                  <authentication>.
  69                  "client-IP-address": The server is only reachable or works,
  70                      if the user is in a certain IP network, e.g.
  71                      the dialed into the ISP's network (DSL, cable, modem) or
  72                      connected to a company network.
  73                      Note: <authentication>client-IP-address</>
  74                      means that you may use the server without any auth.
  75                      <authentication>password-cleartext</> *and*
  76                      <restriction>client-IP-address</> means that you need to
  77                      be in the correct IP network *and* (should) authenticate.
  78                      Servers which do that are highly discouraged and
  79                      should be avoided, see {{bug|556267}}.
  80                 Not yet implemented. Spec (element name?) up to change.
  81             -->
  82          <restriction>client-IP-address</restriction>
  83          <!-- remove the following and leave to client/user? -->
  84          <addThisServer>true</addThisServer>
  85          <useGlobalPreferredServer>true</useGlobalPreferredServer>
  86          <password>optional: the user's password</password>
  87       </outgoingServer>
  88 
  89       <!-- A page where the ISP describes the configuration.
  90            This is purely informational and currently mainly for
  91            maintenance of the files and not used by the client at all.
  92            Note that we do not necessarily use exactly the config suggested
  93            by the ISP, e.g. when they don't recommend SSL, but it's available,
  94            we will configure SSL.
  95            The text content should contains a description in the native
  96            language of the ISP (customers), and a short English description,
  97            mostly for us.
  98       -->
  99       <!-- TODO
 100       <documentation url="http://www.example.com/help/mail/thunderbird">
 101          <descr lang="en">Configure Thunderbird 2.0 for IMAP</descr>
 102          <descr lang="de">Thunderbird 2.0 mit IMAP konfigurieren</descr>
 103       </documentation>
 104       -->
 105     </emailProvider>
 106 
 107     <!-- This allows to access the webmail service of the provider.
 108          The URLs are loaded into a standard webbrowser for the user.
 109          Specifying this is optional. -->
 110     <webMail>
 111       <!-- Webpage where the user has to log in manually by entering username
 112            and password himself.
 113            HTTPS required. -->
 114       <loginPage url="https://mx1.rockstable.it/" />
 115 
 116       <!-- Same as loginAutomaticDOM, but the website makes checks that
 117            the user comes from the login page. So, open the login page
 118            in the browser, get the page's DOM, fill out name and password
 119            fields for the user, and trigger the login button.
 120            The login button might not be an HTML button, just a div, so
 121            to trigger it, send a click event to it.
 122            HTTPS is required for the URL. -->
 123       <loginPageInfo url="https://mx1.rockstable.it/">
 124         <!-- What to fill into the usernameField.
 125              Format is the same as for <username> within <incomingServer>,
 126              including placeholders. See below for valid placeholders. -->
 127         <username>%EMAILADDRESS%</username>
 128         <!-- Allows to find the textfield on the page, to fill it out.
 129              The id attribute give the DOM ID,
 130              The name attribute give the DOM name attribute.
 131              One or both of id and name attributes must exist.
 132              Try the ID first (e.g. using getElementById()), if existing.
 133              Otherwise, try finding the element by name.
 134              Don't treat the IDs given in this XML file as trusted,
 135              but before using them, verify the format
 136              (e.g. only characters and digits for IDs).
 137              If you use powerful functions like jQuery, and the XML returns
 138              you code in the username ID, and you feed it unchecked to jQuery,
 139              it may be executed. -->
 140         <usernameField id="email_field" name="email" />
 141         <passwordField name="password" />
 142         <!-- The submit button to trigger the server submit
 143              after filling in the fields.
 144              id and name attributes: See <usernameField> -->
 145         <loginButton id="submit_button" name="login"/>
 146       </loginPageInfo>
 147     </webMail>
 148 </clientConfig>