From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.204.155.88 with SMTP id r24cs57597bkw; Sat, 31 Jul 2010 19:09:46 -0700 (PDT) Received: by 10.220.158.9 with SMTP id d9mr2644453vcx.250.1280628585524; Sat, 31 Jul 2010 19:09:45 -0700 (PDT) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id m9si3925792vcs.169.2010.07.31.19.09.44; Sat, 31 Jul 2010 19:09:45 -0700 (PDT) Received-SPF: pass (google.com: domain of sup-talk-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-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-talk-bounces@rubyforge.org Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id A763819782D4; Sat, 31 Jul 2010 22:09:44 -0400 (EDT) Received: from dmz-mailsec-scanner-7.mit.edu (DMZ-MAILSEC-SCANNER-7.MIT.EDU [18.7.68.36]) by rubyforge.org (Postfix) with ESMTP id 923121858396 for ; Sat, 31 Jul 2010 22:06:37 -0400 (EDT) X-AuditID: 12074424-b7c35ae000000a07-36-4c54d6af9d83 Received: from mailhub-auth-2.mit.edu (MAILHUB-AUTH-2.MIT.EDU [18.7.62.36]) by dmz-mailsec-scanner-7.mit.edu (Symantec Brightmail Gateway) with SMTP id 39.56.02567.FA6D45C4; Sat, 31 Jul 2010 22:06:39 -0400 (EDT) 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 o7126aAo010169; Sat, 31 Jul 2010 22:06: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 o7126Z55024344; Sat, 31 Jul 2010 22:06:36 -0400 (EDT) From: "Edward Z. Yang" To: Ben Walton In-reply-to: <1280575476-sup-2567@pinkfloyd.chass.utoronto.ca> References: <1280546878-sup-5384@ezyang> <1280575476-sup-2567@pinkfloyd.chass.utoronto.ca> Date: Sat, 31 Jul 2010 22:06:34 -0400 Message-Id: <1280628309-sup-7092@ezyang> User-Agent: Sup/git X-Brightmail-Tracker: AAAAAQCq+Kk= Cc: sup-talk Subject: Re: [sup-talk] Behavior for sent messages X-BeenThere: sup-talk@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: User & developer discussion of Sup 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-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org Excerpts from Ben Walton's message of Sat Jul 31 07:25:38 -0400 2010: > I'm running pretty close to the tip of git/next and that's not the > behaviour here. There are times, when using Maildir that the sent > message doesn't get added immediately, but it always pops up at the > next poll. Hello Ben, I tested your hypothesis and noted that the messages did not pop up with a poll. Since this behavior does not seem intentional, I guess it's a regression caused by some combination of factors (possibly the new backsync branch?) I'll try to reproduce on a clean Maildir with sup commit 900768918490a1040b55e2216f7f5429b2dadf84 Cheers, Edward _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk