From: Michael Hudson-Doyle <michael.hudson@canonical.com>
To: David Bremner <david@tethera.net>, notmuch@notmuchmail.org
Subject: Re: notmuch-emacs bug report -- infinite looping trying to select
	next message
In-Reply-To: <87eh3xpj3i.fsf@zancas.localnet>
References: <877gzql7e3.fsf@canonical.com> <87eh3xpj3i.fsf@zancas.localnet>
User-Agent: Notmuch/0.17~rc1+4~g7f07bfd (http://notmuchmail.org)
	Emacs/24.3.50.2 (x86_64-pc-linux-gnu)
Date: Mon, 27 Jan 2014 09:18:08 +1300
Message-ID: <871tzuzedb.fsf@canonical.com>
MIME-Version: 1.0
Content-Type: text/plain
Precedence: list

David Bremner <david@tethera.net> writes:

> Michael Hudson-Doyle <michael.hudson@canonical.com> 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.

I find the same.

> In particular our handling of error reporting for corrupted parts
> changed, so maybe that was it.

When I load up the thread that caused the problem I end up with this in
the buffer:

         [ message/external-body ]
         !!! Bodypart insert error: Couldn't find access type !!!
         [ text/plain ]

so I think it's pretty likely your guess is accurate.

> Thanks so much for including a test case with your bug report,

No problem, thanks for checking this ancient report!  (And thanks to
myself for including the message-id in the report...)

Cheers,
mwh