2022-02-17 10:30:08 +01:00
<?xml version="1.0"?>
<clientConfig version= "1.1" >
<emailProvider id= "edgarpierre.fr" >
<domain > edgarpierre.fr</domain>
<displayName > Edgar P. Burkhart</displayName>
<displayShortName > Aconcagua</displayShortName>
<!-- type=
"imap": IMAP
"pop3": POP3
-->
<incomingServer type= "imap" >
<hostname > imap.edgarpierre.fr</hostname>
<port > 143</port>
<!-- "plain": no encryption
"SSL": SSL 3 or TLS 1 on SSL-specific port
"STARTTLS": on normal plain port and mandatory upgrade to TLS via STARTTLS
-->
2022-02-17 10:46:43 +01:00
<socketType > SSL</socketType>
2022-02-17 10:30:08 +01:00
<username > %EMAILLOCALPART%</username>
<!-- Authentication methods:
"password-cleartext",
Send password in the clear
(dangerous, if SSL isn't used either).
AUTH PLAIN, LOGIN or protocol-native login.
"password-encrypted",
A secure encrypted password mechanism.
Can be CRAM-MD5 or DIGEST-MD5. Not NTLM.
"NTLM":
Use NTLM (or NTLMv2 or successors),
the Windows login mechanism.
"GSSAPI":
Use Kerberos / GSSAPI,
a single-signon mechanism used for big sites.
"client-IP-address":
The server recognizes this user based on the IP address.
No authentication needed, the server will require no username nor password.
"TLS-client-cert":
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)
"OAuth2":
OAuth2. Works only on specific hardcoded servers, please see below. Should be added only as second alternative.
"none":
No authentication
-->
<authentication > password-cleartext</authentication>
</incomingServer>
<outgoingServer type= "smtp" >
<hostname > smtp.edgarpierre.fr</hostname>
<port > 587</port>
<socketType > STARTTLS</socketType> <!-- see <incomingServer> -->
<username > %EMAILLOCALPART%</username> <!-- if smtp - auth -->
<!-- smtp - auth (RFC 2554, 4954) or other auth mechanism.
For values, see incoming.
Additional options here:
"SMTP-after-POP":
authenticate to incoming mail server first
before contacting the smtp server.
Compatibility note: Thunderbird 3.0 accepts only "plain",
"secure", "none", and "smtp-after-pop".
It will ignore the whole XML file, if other values are given.
-->
<authentication > password-cleartext</authentication>
<!-- If the server makes some additional requirements beyond
<authentication > .
"client-IP-address": The server is only reachable or works,
if the user is in a certain IP network, e.g.
the dialed into the ISP's network (DSL, cable, modem) or
connected to a company network.
Note: <authentication > client-IP-address< />
means that you may use the server without any auth.
<authentication > password-cleartext< /> *and*
<restriction > client-IP-address< /> means that you need to
be in the correct IP network *and* (should) authenticate.
Servers which do that are highly discouraged and
should be avoided, see {{bug|556267}}.
Not yet implemented. Spec (element name?) up to change.
-->
<addThisServer > true</addThisServer>
</outgoingServer>
</emailProvider>
</clientConfig>