From: Bernie M. <lis...@bl...> - 2004-12-21 13:45:12
|
Hi there! I'll admit I'm using an old version of mailsync (4.4.4, since that is the latest one ported as a FreeBSD port [sigh]). But I've had a quick glance at the current code in CVS, and so I am guessing that STL sets are still pretty fundamental to the implementation of mailsync. Unfortunately, this means it's pretty likely that that mailsync still exhibits a problem that I've observed in 4.4.4, and that is it cannot preserve the order of messages in synchronised folders (unless I am missing something). Is that the case? If so, how difficult would it be to keep the sorted list, iterate through that while testing against the appropriate set to decide whether a particular message should be copied? (That is, replace the MsgIdSet::iterator loop with something that preserves order.) As it stands, it's a bit irritating to synchronise high-traffic folders, because the destination gets jumbled. On an unrelated note, I notice also that any keywords I assign are lost in the copy. (The X-Keywords line is replaced by X-Original-X-Keywords.) However, I saw nothing in the mailsync sources to indicate that it was munging them, so perhaps that is a c-client problem? So I'm still searching for an ideal mail synchroniser. (Ideal for me, that is. Otherwise I've been pretty impressed with mailsync so far.) Cheers, Bernie |