Fwd: Re: [Mailsync-list] Preserving order of synced messages

[<tp...@so...>]

I forgot to Cc: the list. Here is my answer.
*t

----- Weitergeleitete Nachricht von tp...@so... -----
    Datum: Thu, 23 Dec 2004 11:37:42 +0100
    Von: tp...@so...
Antwort an: tp...@so...
 Betreff: Re: [Mailsync-list] Preserving order of synced messages
      An: Bernie Maier <lis...@bl...>

Zitat von Bernie Maier <lis...@bl...>:

> 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]).

I remember there was someone from *BSD here, since some patches for the
build were included, so there should be a port of mailsync available
somewhere...

>  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.)

You won't know untill you do it. I'd guess it wouldn't be difficult. I'd try
to replace set by vector. That way order should be preserved automatically.

> As it stands, it's a bit irritating to synchronise high-traffic folders,
> because the destination gets jumbled.

True. Could you fill a Feature Request for this?

> 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?

That's c-client.

> 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.)

How about patching mailsync ;-)?
*t

-------------------------------------------------
This mail sent through IMP: http://horde.org/imp/

----- Ende der weitergeleiteten Nachricht -----




-------------------------------------------------
This mail sent through IMP: http://horde.org/imp/