From 6bf9ee9a1e1c704490489f682dfe106f2c1ee46a Mon Sep 17 00:00:00 2001 From: Guilhem Moulin Date: Tue, 8 Mar 2016 22:56:53 +0100 Subject: interimap: improve manpage. --- interimap.1 | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'interimap.1') diff --git a/interimap.1 b/interimap.1 index a73117b..93e463e 100644 --- a/interimap.1 +++ b/interimap.1 @@ -33,7 +33,7 @@ Conceptually, the synchronization algorithm is derived from [RFC4549] with the [RFC7162, section 6] amendments, and works as follows: .nr step 1 1 -.IP \n[step]. 8 +.IP \n[step]. 4 SELECT (on both servers) a mailbox the current UIDNEXT or HIGHESTMODSEQ values of which differ from the values found in the database (for either server). Use the QRESYNC SELECT parameter from [RFC7162] to list @@ -353,7 +353,7 @@ authentication if \(lq\fISSL_verify\fR=YES\(rq. Performance is better for servers supporting the following extensions to the IMAP4rev1 [RFC3501] protocol: -.IP \[bu] +.IP \[bu] 4 LITERAL+ [RFC2088] non-synchronizing literals (recommended), .IP \[bu] MULTIAPPEND [RFC3502] (recommended), @@ -366,7 +366,7 @@ UNSELECT [RFC3691]. .SH KNOWN BUGS AND LIMITATIONS -.IP \[bu] +.IP \[bu] 4 Using \fBInterIMAP\fR on two identical servers with a non-existent or empty database will duplicate each message due to the absence of local/remote UID association. -- cgit v1.2.3