diff options
| author | Guilhem Moulin <guilhem@fripost.org> | 2019-11-06 03:46:36 +0100 |
|---|---|---|
| committer | Guilhem Moulin <guilhem@fripost.org> | 2019-11-06 05:35:43 +0100 |
| commit | 30276bbc82ca770500531d872666f48493749285 (patch) | |
| tree | 875799414c9cd23f1bb217eb7e24d8839fba5521 | |
| parent | e764f7517749d8055ba3af8ae00a0c75a3bccaa7 (diff) | |
interimap.1.md: Document that DELETE and RENAME commands should be avoided.
| -rw-r--r-- | doc/interimap.1.md | 9 |
1 files changed, 8 insertions, 1 deletions
diff --git a/doc/interimap.1.md b/doc/interimap.1.md index 8fa5def..42db381 100644 --- a/doc/interimap.1.md +++ b/doc/interimap.1.md @@ -437,7 +437,7 @@ Known bugs and limitations empty *database* will duplicate each message due to the absence of local ↔ remote UID association. Hence one needs to manually empty the mail store on one end when migrating to `interimap` from another - synchronisation solution. + synchronization solution. * `interimap` is single threaded and doesn't use IMAP command pipelining. Synchronization could be boosted up by sending @@ -452,6 +452,13 @@ Known bugs and limitations was deleted while another one (which is replicated again) was added to the other mailbox in the meantime. + * Because the [IMAP protocol][RFC 3501] doesn't provide a way for + clients to determine whether a disapeared mailbox was deleted or + renamed, `interimap` aborts when a known mailbox disapeared from one + server but not the other. The `--delete` (resp. `rename`) command + should be used instead to delete (resp. rename) the mailbox on both + servers as well as within `interimap`'s internal database. + * `PLAIN` and `LOGIN` are the only authentication mechanisms currently supported. |