From mboxrd@z Thu Jan  1 00:00:00 1970
Received: by 10.204.80.67 with SMTP id s3cs90825bkk;
        Sun, 15 Aug 2010 17:19:49 -0700 (PDT)
Received: by 10.224.28.71 with SMTP id l7mr2762425qac.387.1281917988295;
        Sun, 15 Aug 2010 17:19:48 -0700 (PDT)
Return-Path: <sup-talk-bounces@rubyforge.org>
Received: from rubyforge.org (rubyforge.org [205.234.109.19])
        by mx.google.com with ESMTP id t26si9652714qco.131.2010.08.15.17.19.47;
        Sun, 15 Aug 2010 17:19:48 -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 9B39E19783BE;
	Sun, 15 Aug 2010 20:19:47 -0400 (EDT)
Received: from dmz-mailsec-scanner-6.mit.edu (DMZ-MAILSEC-SCANNER-6.MIT.EDU
	[18.7.68.35]) by rubyforge.org (Postfix) with ESMTP id B20D0185835A
	for <sup-talk@rubyforge.org>; Sun, 15 Aug 2010 19:58:05 -0400 (EDT)
X-AuditID: 12074423-b7cb4ae000000a9b-58-4c687eff8074
Received: from mailhub-auth-1.mit.edu (MAILHUB-AUTH-1.MIT.EDU [18.9.21.35])
	by dmz-mailsec-scanner-6.mit.edu (Symantec Brightmail Gateway) with
	SMTP id E0.43.02715.FFE786C4; Sun, 15 Aug 2010 19:57:51 -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 o7FNw4DV009759; 
	Sun, 15 Aug 2010 19:58:04 -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 o7FNw36X005917;
	Sun, 15 Aug 2010 19:58:04 -0400 (EDT)
From: "Edward Z. Yang" <ezyang@MIT.EDU>
To: Ben Walton <bwalton@artsci.utoronto.ca>
In-reply-to: <1280628833-sup-7698@pinkfloyd.chass.utoronto.ca>
References: <1280546878-sup-5384@ezyang>
	<1280575476-sup-2567@pinkfloyd.chass.utoronto.ca>
	<1280628309-sup-7092@ezyang>
	<1280628833-sup-7698@pinkfloyd.chass.utoronto.ca>
Date: Sun, 15 Aug 2010 19:58:03 -0400
Message-Id: <1281916596-sup-8793@ezyang>
User-Agent: Sup/git
X-Brightmail-Tracker: AAAAAQCq+Kk=
Cc: sup-talk <sup-talk@rubyforge.org>
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 <sup-talk.rubyforge.org>
List-Unsubscribe: <http://rubyforge.org/mailman/options/sup-talk>,
	<mailto:sup-talk-request@rubyforge.org?subject=unsubscribe>
List-Archive: <http://rubyforge.org/pipermail/sup-talk>
List-Post: <mailto:sup-talk@rubyforge.org>
List-Help: <mailto:sup-talk-request@rubyforge.org?subject=help>
List-Subscribe: <http://rubyforge.org/mailman/listinfo/sup-talk>,
	<mailto:sup-talk-request@rubyforge.org?subject=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

I've tracked down the regression to this merge: 45c3433c0 Merge remote branch 'origin/maildir'

I'd appreciate a quick san-check before I start investigating the merge more
closely: you can easily test for this bug by renaming your .sup directory away
and creating a fresh sup directory.
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk