Excerpts from Mark Alexander's message of 2010-03-19 16:35:38 -0400: > Excerpts from Michael Stapelberg's message of Fri Mar 19 15:47:53 -0400 2010: > > Excerpts from Ben Walton's message of 2010-03-19 20:35:31 +0100: > > > Isn't there a more portable solution? > > There is: Rich mentioned that proper move/delete handling for maildirs also > > solves the problem. > > I must have missed that message. What is the proposed solution? > How does it solve the problem of out-of-order maildir IDs?
Notmuch implements this correctly. They essentially keep a sorted list of mail filenames in the index and then iterate over that and the sorted list of the filenames that are currently in the maildir to detect inserts, deletes, and renames. I just rebased and pushed a multiple-locations branch I've had sitting around to mainline. It's probably buggy. It's been a while since I thought about this problem, but I think keeping track of multiple locations (source/source info) for a single message (identified by message-id) should make the maildir logic simpler. _______________________________________________ Sup-devel mailing list Sup-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-devel
