From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id 1743C431FBC for ; Fri, 24 Jan 2014 06:09:36 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: 0 X-Spam-Level: X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none] autolearn=disabled Received: from olra.theworths.org ([127.0.0.1]) by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B1p4Jwutorqh for ; Fri, 24 Jan 2014 06:09:28 -0800 (PST) Received: from yantan.tethera.net (yantan.tethera.net [199.188.72.155]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by olra.theworths.org (Postfix) with ESMTPS id 41687431FB6 for ; Fri, 24 Jan 2014 06:09:28 -0800 (PST) Received: from remotemail by yantan.tethera.net with local (Exim 4.80) (envelope-from ) id 1W6hRl-0004Pb-AD; Fri, 24 Jan 2014 10:09:25 -0400 Received: (nullmailer pid 5164 invoked by uid 1000); Fri, 24 Jan 2014 14:09:21 -0000 From: David Bremner To: Michael Hudson-Doyle , notmuch@notmuchmail.org Subject: Re: notmuch-emacs bug report -- infinite looping trying to select next message In-Reply-To: <877gzql7e3.fsf@canonical.com> References: <877gzql7e3.fsf@canonical.com> User-Agent: Notmuch/0.17+35~g3b36898 (http://notmuchmail.org) Emacs/24.3.1 (x86_64-pc-linux-gnu) Date: Fri, 24 Jan 2014 10:09:21 -0400 Message-ID: <87eh3xpj3i.fsf@zancas.localnet> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.13 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: Fri, 24 Jan 2014 14:09:36 -0000 Michael Hudson-Doyle writes: > The attached gzipped mbox appears to trip up the emacs interface. The > problem seems to come from the message with id > CAGNsrLCWv6=36q+q+5Hc_SzgdZ2ergeKkapT7T3xXvim=2cK+A@mail.gmail.com. > I can't reproduce this bug in current git, so I'm going to assume something fixed it in the intervening years. In particular our handling of error reporting for corrupted parts changed, so maybe that was it. Thanks so much for including a test case with your bug report, d