From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by arlo.cworth.org (Postfix) with ESMTP id 0EBB06DE2788 for ; Thu, 6 Jul 2017 11:47:25 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: -0.001 X-Spam-Level: X-Spam-Status: No, score=-0.001 tagged_above=-999 required=5 tests=[AWL=0.010, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=disabled Received: from arlo.cworth.org ([127.0.0.1]) by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nBFGnQMoQaiE for ; Thu, 6 Jul 2017 11:47:23 -0700 (PDT) Received: from fethera.tethera.net (fethera.tethera.net [198.245.60.197]) by arlo.cworth.org (Postfix) with ESMTPS id 00C916DE277C for ; Thu, 6 Jul 2017 11:47:22 -0700 (PDT) Received: from remotemail by fethera.tethera.net with local (Exim 4.84_2) (envelope-from ) id 1dTBkw-0005wG-Dm; Thu, 06 Jul 2017 14:44:02 -0400 Received: (nullmailer pid 8255 invoked by uid 1000); Thu, 06 Jul 2017 18:47:14 -0000 From: David Bremner To: Lauren Weinstein , cesar mena Cc: notmuch@notmuchmail.org, Stefano Zacchiroli Subject: Re: maildir and nmh/mh In-Reply-To: <20170706183602.GA25389@vortex.com> References: <20170706010111.GA22268@vortex.com> <87inj53dad.fsf@cmena.pobox.com> <20170706183602.GA25389@vortex.com> Date: Thu, 06 Jul 2017 15:47:14 -0300 Message-ID: <87y3s1qu6l.fsf@tesseract.cs.unb.ca> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jul 2017 18:47:25 -0000 Lauren Weinstein writes: > After fixing the find syntax I got mh2maildir working. However, it does not > appear practical in my situation, since I'm dealing with more than 25 years of archived > mh messages! The conversion would take ages with too many manual exceptions. > So unless there's some way to correctly index these natively with notmuch, I guess > this is a dead end. But thanks. For what it's worth, I suspect the problem is not with notmuch proper but with the notmuch-mutt script. Unfortunatately zack (in copy) is really the only one who knows very much about the script. If you could make a small tar ball of an MH directory that causes problems for notmuch-mutt, zack could probably be tricked into looking at it. d