From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.42.179.196 with SMTP id br4cs204738icb; Tue, 30 Nov 2010 05:55:06 -0800 (PST) Received: by 10.204.61.74 with SMTP id s10mr6679515bkh.91.1291125304215; Tue, 30 Nov 2010 05:55:04 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id o21si5634560vcr.49.2010.11.30.05.55.03; Tue, 30 Nov 2010 05:55:04 -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 86D8819782DB for ; Tue, 30 Nov 2010 08:55:03 -0500 (EST) Received: from mail-ww0-f54.google.com (mail-ww0-f54.google.com [74.125.82.54]) by rubyforge.org (Postfix) with ESMTP id 293961858354; Tue, 30 Nov 2010 08:01:37 -0500 (EST) Received: by wwb31 with SMTP id 31so4142967wwb.23 for ; Tue, 30 Nov 2010 05:01:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:subject :to:in-reply-to:references:mime-version:content-type:content-id; bh=ZefJ+cP3nrSwKWg3OXOkEARdx3WpianQkEhMVk9CVY4=; b=SIJGkJJKNCgMS5y44/YS8tWjY4F/NOtwH+Mb+Cylp320ZvzH2ByxpFfAcQ8d9+/40e Vlp0xz+PJ1cyP9+R2w6v/MclVUar71ii7nBm99R/FfFhmhe65hn41SYkrH4+plhthHnR A0/z1hsdQ0qJR/B1zeK9DPDj79O5nO4JjiqSg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:subject:to:in-reply-to:references:mime-version :content-type:content-id; b=D7pLb9LAGlnc8bPjEIQ264qMqJmPKVdEFmikDE9iy/hef6YB0MW68VP8t8OH2ooxtj r/BiLBoOPAP6OjWVS8bMYkvgnXkfChnkkWFAlvCdJPw16MXnp0bZnqtTejTVCx6c0MCh 67gvBKk9uh/IhpRLHPCNbnVnEcy/qL/JVZWuc= Received: by 10.227.28.228 with SMTP id n36mr910219wbc.70.1291122096951; Tue, 30 Nov 2010 05:01:36 -0800 (PST) Received: from localhost (sk.feydakins.org [94.23.4.142]) by mx.google.com with ESMTPS id 11sm1941762wbj.13.2010.11.30.05.01.35 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 30 Nov 2010 05:01:35 -0800 (PST) Message-ID: <4cf4f5af.8b02e30a.7219.ffff9349@mx.google.com> Date: Tue, 30 Nov 2010 05:01:35 -0800 (PST) From: Nicolas Pouillard To: Sup issue tracker , Sup developer discussion , sup-devel@rubyforge.org In-Reply-To: <1290856550.06.0.787394879314.issue133@masanjin.net> References: <1290856550.06.0.787394879314.issue133@masanjin.net> MIME-Version: 1.0 Content-ID: <16612.1291122094.1@sk.feydakins.org> Subject: Re: [sup-devel] [issue133] add support for the mh mailbox format 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 On Sat, 27 Nov 2010 11:15:50 +0000, anonymous wrote: > > New submission from anonymous: > > I've been using the mh format (via nmh) for years, and it would be fantastic if > sup could support it so people don't have to convert mailboxes to maildir or mbox > to be able to use sup. I'm in favor of this feature as well. The nmh format for mailboxes is pretty simple, just directories of email files plus some (one?) special file that sup can just ignore. In other terms this is just maildir without their complicated naming conventions of files and directories. -- Nicolas Pouillard http://nicolaspouillard.fr _______________________________________________ Sup-devel mailing list Sup-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-devel