From 329738ebb74815d8a49feee63efb23d9baa557ee Mon Sep 17 00:00:00 2001 From: Guilhem Moulin Date: Tue, 6 Dec 2016 17:51:04 +0100 Subject: [PATCH] Minor manpage fixes. --- interimap.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/interimap.md b/interimap.md index b923933..4a321f1 100644 --- a/interimap.md +++ b/interimap.md @@ -37,7 +37,7 @@ message with UID smaller than `UIDNEXT` have been replicated to the other server, and that the metadata (such as flags) of each message with MODSEQ at most `HIGHESTMODSEQ` have been synchronized. Conceptually, the synchronization algorithm is derived from [RFC 4549] -with the [RFC 7162] (section 6) amendments, and works as follows: +with the [RFC 7162] (sec. 6) amendments, and works as follows: 1. `SELECT` (on both servers) a mailbox the current `UIDNEXT` or `HIGHESTMODSEQ` values of which differ from the values found in the database (for @@ -85,7 +85,7 @@ However if some extra argument are provided on the command line, `interimap` ignores said options and synchronizes the given *MAILBOX*es instead. Note that each *MAILBOX* is taken “as is”; in particular, it must be [UTF-7 encoded][RFC 2152], unquoted, and the list -wildcards ‘\*’ and ‘%’ are not interpolated. +wildcards ‘\*’ and ‘%’ are not expanded. If the synchronization was interrupted during a previous run while some messages were being replicated (but before the `UIDNEXT` or -- 2.39.2