From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.204.155.88 with SMTP id r24cs9019bkw; Sun, 18 Jul 2010 15:46:50 -0700 (PDT) Received: by 10.231.184.16 with SMTP id ci16mr4346988ibb.23.1279493209137; Sun, 18 Jul 2010 15:46:49 -0700 (PDT) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id a4si9183314ibc.87.2010.07.18.15.46.48; Sun, 18 Jul 2010 15:46:49 -0700 (PDT) Received-SPF: pass (google.com: domain of sup-devel-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) client-ip=205.234.109.19; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-devel-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-devel-bounces@rubyforge.org Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 3DC26185837F; Sun, 18 Jul 2010 18:46:48 -0400 (EDT) Received: from dmz-mailsec-scanner-4.mit.edu (DMZ-MAILSEC-SCANNER-4.MIT.EDU [18.9.25.15]) by rubyforge.org (Postfix) with ESMTP id 1EEA7185836C for ; Sun, 18 Jul 2010 18:46:36 -0400 (EDT) X-AuditID: 1209190f-b7b0aae000000a7d-01-4c438450224e Received: from mailhub-auth-1.mit.edu (MAILHUB-AUTH-1.MIT.EDU [18.9.21.35]) by dmz-mailsec-scanner-4.mit.edu (Symantec Brightmail Gateway) with SMTP id 4E.41.02685.054834C4; Sun, 18 Jul 2010 18:46:40 -0400 (EDT) Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103]) by mailhub-auth-1.mit.edu (8.13.8/8.9.2) with ESMTP id o6IMkatw015438; Sun, 18 Jul 2010 18:46:36 -0400 Received: from localhost (ool-44c4de0a.dyn.optonline.net [68.196.222.10]) (authenticated bits=0) (User authenticated as ezyang@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.6/8.12.4) with ESMTP id o6IMkYOW029555; Sun, 18 Jul 2010 18:46:35 -0400 (EDT) From: "Edward Z. Yang" To: Damien Leone In-reply-to: <1278693172-sup-6247@mailer> References: <1278693172-sup-6247@mailer> Date: Sun, 18 Jul 2010 18:46:33 -0400 Message-Id: <1279492496-sup-3638@ezyang> User-Agent: Sup/git X-Brightmail-Tracker: AAAAAQCq+Kk= Cc: sup-devel Subject: Re: [sup-devel] Adding backward synchronization for Maildir sources X-BeenThere: sup-devel@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: Sup developer discussion List-Id: Sup developer discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-devel-bounces@rubyforge.org Errors-To: sup-devel-bounces@rubyforge.org Sup Damien, I cut over to your branch, plus one patch of my own making. THE GOOD NEWS It works! Whereby, messages are marked read in my webmail client and deleted messages go away. THE BAD NEWS It makes Sup very crashy and there's some strange behavior. This is probably the sixth time I'm composing this message (yeah, haven't learned my lesson.) In more detail... * You want the following OfflineImap patch, because otherwise the massive changes to labels that will surely be induced by backwards syncing will cause OfflineImap to CRAWL. diff --git a/offlineimap/folder/LocalStatus.py b/offlineimap/folder/LocalStatus.py index 157989d..7f4dc5b 100644 --- a/offlineimap/folder/LocalStatus.py +++ b/offlineimap/folder/LocalStatus.py @@ -33,7 +33,7 @@ class LocalStatusFolder(BaseFolder): self.messagelist = None self.repository = repository self.savelock = threading.Lock() - self.doautosave = 1 + self.doautosave = 0 self.accountname = accountname BaseFolder.__init__(self) Though, you probably want to undo this patch when you're done. Autosaving means partial progress is saved. * Backwards syncing appears to make old deleted mail show up again; I'm not sure if it's because touching the Maildir causes Sup to pick up on deleted tags again or something, but I had to go back and delete lots of deleted mail. * When Sup is deleting messages, it is /extremely/ unsafe to iterate over a list of all messages in the index and query them for info: the threading means that any given message might not exist anymore. I had a hook that kept triggering this bug, and earlier on in the process drawing functions would also frequently Nil error. This is probably under-tested codepaths in Sup that we should track down; unfortunately I didn't have the presence of mind to record traces until later (and the ones I got all look like my hooks fault). * In a similar vein, while messages are going away, '@' will occasionally return no messages (pressing again usually fixes it). Messages that are labelled inbox will show up in 'U', but not in the inbox view without a Sup restart. I haven't done a code review yet. Cheers, Edward _______________________________________________ Sup-devel mailing list Sup-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-devel