Reformatted excerpts from Ben Gamari's message of 2009-09-28: > This does raise one important question, however. It seems that > offlineimap will delete messages if they are found to have been > deleted in the remote respository. Is there any way that you know of > to disable this behavior, such that it will only drop new messages > into the local repository, thus making it somewhat compatible with > sup's add-only source requirement?
Maybe someone who uses offlineimap can comment on this. In the worst case, I'm sure the patch wouldn't be too hard. > This actually brings up a larger question. How difficult would it be > to relax sup's assumption that sources are add-only? It's not difficult per se, it just requires scanning over the entire source, which is slow. Removing this assumption would be tantamount to running sup-sync -c every time you start up sup. Here's the idea: scanning over a mailstore is slow. Much of this slowness is due to Ruby. So let's rewrite this code in C. Then we would have something as fast as, say, Mutt. But Mutt bogs down on my mbox file because it's too big. So my *only* reasonable choice with a large mailstore is Sup and the assumption that the source is add only. -- William <[email protected]> _______________________________________________ sup-talk mailing list [email protected] http://rubyforge.org/mailman/listinfo/sup-talk
