From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.42.228.136 with SMTP id je8cs108205icb; Sun, 6 Mar 2011 12:29:28 -0800 (PST) Received: by 10.43.55.84 with SMTP id vx20mr3960854icb.49.1299443368520; Sun, 06 Mar 2011 12:29:28 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id gw41si5166728ibb.56.2011.03.06.12.29.28; Sun, 06 Mar 2011 12:29:28 -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; dkim=neutral (body hash did not verify) header.i=@gmail.com Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id DC0341858390 for ; Sun, 6 Mar 2011 15:29:27 -0500 (EST) Received: from mail-fx0-f50.google.com (mail-fx0-f50.google.com [209.85.161.50]) by rubyforge.org (Postfix) with ESMTP id DCA43185836C for ; Sun, 6 Mar 2011 14:15:29 -0500 (EST) Received: by fxm18 with SMTP id 18so4081073fxm.23 for ; Sun, 06 Mar 2011 11:15:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=//FxmBCw/rxVIG9N2hjK4aH9yYVz7qW8PtbymkEhyIM=; b=q5EBds4cSLucxUm6EipyifbbchPH+c7jA48CXhAzbsw/ap+W9zhd05L1zbJxdxBjIV nnmTb+JbQqUyzyf3roYPPSg9JS8v4PsIHvX8BFkaFy8IzH/g0g0TnhmDMk7nDLCt0q8y lrrKDOSesWq3gCrK/q1ork0zYxUAns/45RChE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=g12szpVoEGO3aaIMKIIfKC+tYhWhPycl5RMgTLCHEzqEQet8B8jGpi4EC/fttIRpe2 hxOuJCxxVogrws3OV0MrczKsSL2xH5fzyWddiFLjCTT+4so+Rr1/E5yWp+1TLq6tCKvD gwlVKoVl9tq2T9SfnT+fUY/IrKScKDwnngSYI= MIME-Version: 1.0 Received: by 10.223.54.213 with SMTP id r21mr1539580fag.54.1299438929111; Sun, 06 Mar 2011 11:15:29 -0800 (PST) Received: by 10.223.71.197 with HTTP; Sun, 6 Mar 2011 11:15:29 -0800 (PST) In-Reply-To: <1299436337-sup-4604@pruts.nl> References: <1299436337-sup-4604@pruts.nl> Date: Sun, 6 Mar 2011 14:15:29 -0500 Message-ID: From: Steve To: Sup developer discussion Subject: Re: [sup-devel] Mail-to-self does not end up in inbox 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: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-devel-bounces@rubyforge.org Errors-To: sup-devel-bounces@rubyforge.org This is a bug to me. Although, if I recall, sup did not used to behave this way. So likely someone thought the opposite was a bug. On Sun, Mar 6, 2011 at 1:34 PM, Ico Doornekamp wrote: > Hi all, > > Back in the old days when using mutt, I regularly used to send mails to > myself as reminders or short notes. Sup however shows intelligent > behaviour, recognizes the message is both sent and received, and > attaches a 'sent' label to it, and thus the mail does not show up in the > inbox. > > Is there a simple workaround for this ? Could this be considered a bug, > or is this just functioning as designed ? > > Thanks, > > Ico > > -- > :wq > ^X^Cy^K^X^C^C^C^C > _______________________________________________ > Sup-devel mailing list > Sup-devel@rubyforge.org > http://rubyforge.org/mailman/listinfo/sup-devel > _______________________________________________ Sup-devel mailing list Sup-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-devel