From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.42.229.71 with SMTP id jh7cs172434icb; Wed, 19 Jan 2011 06:39:52 -0800 (PST) Received: by 10.229.13.196 with SMTP id d4mr651313qca.292.1295447991920; Wed, 19 Jan 2011 06:39:51 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id a6si14422569qck.94.2011.01.19.06.39.51; Wed, 19 Jan 2011 06:39:51 -0800 (PST) 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 5ADA819782F8; Wed, 19 Jan 2011 09:39:51 -0500 (EST) X-Greylist: delayed 300 seconds by postgrey-1.31 at rubyforge.org; Wed, 19 Jan 2011 09:13:29 EST Received: from dmz-mailsec-scanner-1.mit.edu (DMZ-MAILSEC-SCANNER-1.MIT.EDU [18.9.25.12]) by rubyforge.org (Postfix) with ESMTP id 8F9A318582E2 for ; Wed, 19 Jan 2011 09:13:29 -0500 (EST) X-AuditID: 1209190c-b7ba9ae0000009f8-b2-4d36f05a39aa Received: from mailhub-auth-2.mit.edu ( [18.7.62.36]) by dmz-mailsec-scanner-1.mit.edu (Symantec Brightmail Gateway) with SMTP id FA.F8.02552.A50F63D4; Wed, 19 Jan 2011 09:08:26 -0500 (EST) Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103]) by mailhub-auth-2.mit.edu (8.13.8/8.9.2) with ESMTP id p0JE8PnW014841 for ; Wed, 19 Jan 2011 09:08:25 -0500 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 p0JE8OD8004893 for ; Wed, 19 Jan 2011 09:08:25 -0500 (EST) From: "Edward Z. Yang" To: sup-devel Date: Wed, 19 Jan 2011 09:08:23 -0500 Message-Id: <1295445524-sup-9310@ezyang> User-Agent: Sup/git X-Brightmail-Tracker: AAAAAQCq+Kk= Subject: [sup-devel] Strange maildir/OfflineImap/maildir-sync behavior 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 One day, I opened up an old thread to reread an email, and much to my dismay, it was GONE! Instead, there was one of those little red flags that Sup sticks on mail that is referenced by other threads, but which you don't have a copy of. This was a bit bothersome, because no one likes it when their mail mysteriously disappears. (It harkens back to a time when I accidentally deleted my entire inbox, tried to undo, but Sup crashed in the process and then offlineimap decided to sync the changes back to my main account, so I had to restore from backup and run with maxage... but that's a story for another time...) Some sleuthing, however, revealed that the messages had not disappeared; they were still in my Maildir. And sure enough, when I made Sup repoll the entire Maildir (by restarting it), the messages reappeared (along with another 50 messages that I /swear/ I archived). So my question is, why did Sup lose track of the messages? Did it pick them up while they were in new and then OfflineIMAP moved them and they got lost? Can I make Sup tell me where it thinks a message should be living on my filesystem so I can track these things? Is this actually OfflineIMAP's fault? Cheers, Edward P.S. Hey Damien, I know you're not planning on working on getting maildir-sync merged to master until later this January, but I was wondering if a version of the branch rebased on master would be of any use to you. _______________________________________________ Sup-devel mailing list Sup-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-devel