diff options
Diffstat (limited to 'interimap.md')
| -rw-r--r-- | interimap.md | 21 | 
1 files changed, 12 insertions, 9 deletions
diff --git a/interimap.md b/interimap.md index 4a321f1..4d85eaf 100644 --- a/interimap.md +++ b/interimap.md @@ -140,8 +140,8 @@ Options  `--config=`*FILE*  :   Specify an alternate [configuration file](#configuration-file). -    Relative paths start from *$XDG_CONFIG_HOME*, or *~/.config* if the -    `XDG_CONFIG_HOME` environment variable is unset. +    Relative paths start from *$XDG_CONFIG_HOME/interimap*, or *~/.config/interimap* +    if the `XDG_CONFIG_HOME` environment variable is unset.  `--target={local,remote,database}` @@ -192,9 +192,9 @@ Configuration file  ==================  Unless told otherwise by the `--config=FILE` command-line option, -`interimap` reads its configuration from *$XDG_CONFIG_HOME/interimap* -(or *~/.config/interimap* if the `XDG_CONFIG_HOME` environment variable -is unset) as an [INI file]. +`interimap` reads its configuration from *$XDG_CONFIG_HOME/interimap/config* +(or *~/.config/interimap/config* if the `XDG_CONFIG_HOME` environment +variable is unset) as an [INI file].  The syntax of the configuration file is a series of `OPTION=VALUE`  lines organized under some `[SECTION]`; lines starting with a ‘#’ or  ‘;’ character are ignored as comments. @@ -332,9 +332,10 @@ Valid options are:  :   A space-separated list of SSL protocols to enable or disable (if      prefixed with an exclamation mark `!`.  Known protocols are `SSLv2`, -    `SSLv3`, `TLSv1`, `TLSv1.1`, and `TLSv1.2`.  Enabling a protocol is -    a short-hand for disabling all other protocols. -    (Default: `!SSLv2 !SSLv3`, i.e., only enable TLSv1 and above.) +    `SSLv3`, `TLSv1`, `TLSv1.1`, `TLSv1.2`, and `TLSv1.3`.  Enabling a +    protocol is a short-hand for disabling all other protocols. +    (Default: `!SSLv2 !SSLv3 !TLSv1 !TLSv1.1`, i.e., only enable TLSv1.2 +    and above.)  *SSL_cipher_list* @@ -398,7 +399,9 @@ Known bugs and limitations   * Using `interimap` on two identical servers with a non-existent or     empty *database* will duplicate each message due to the absence of -   local ↔ remote UID association. +   local ↔ remote UID association.  Hence one needs to manually empty +   the mail store on one end when migrating to `interimap` from another +   synchronisation solution.   * `interimap` is single threaded and doesn't use IMAP command     pipelining.  Synchronization could be boosted up by sending  | 
