commit 4f7d49084ae0e07e9d83dbcabd6409a42dfe80b8
Author: Oswald Buddenhagen <oswald.buddenha...@gmx.de>
Date: Sun May 24 19:12:43 2015 +0200
compatibility section cut down; refer to README instead
index.html | 9 +--------
1 files changed, 1 insertions(+), 8 deletions(-)
diff --git a/index.html b/index.html
index b8723a0..5629ad3 100644
--- a/index.html
+++ b/index.html
@@ -41,14 +41,7 @@ multiple replicas of a mailbox can be maintained.
<b>isync</b> should work fairly well with any IMAP4 compliant server;
particularily efficient with those that support the UIDPLUS and LITERAL+
extensions.<br>
-Courier 1.4.3 is known to be buggy, version 1.7.3 works fine.<br>
-c-client (UW-IMAP, Pine) is mostly fine, but versions less than 2004a.352 tend
-to change UIDVALIDITY pretty
-often when used with unix/mbox mailboxes, making isync refuse synchronization.
-The "cure" is to simply copy the new UIDVALIDITY from the affected mailbox to
-mbsync's state file. This is a Bad Hack (TM), but it works - use at your own
-risk (if the UIDVALIDITY change was genuine, this will delete all messages in
-the affected mailbox - not that this ever happened to me).
+Some servers require workarounds; see the README file for details.
<h2>Usage</h2>
While <b>isync</b> is the project name, mbsync is the current executable name;
------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel
