Re: mutt/2139: could not copy message

To: bug-any@xxxxxxxxxxxxx, 369857@xxxxxxxxxxxxxxx, Mutt Developers <mutt-dev@xxxxxxxx>
Subject: Re: mutt/2139: could not copy message
From: Christoph Berg <cb@xxxxxxxx>
Date: Mon, 29 Jan 2007 19:06:08 +0100
In-reply-to: <E1FEzVV-0002xo-MZ@xxxxxxxxxxxxxxxxxxxx>
List-unsubscribe: <mailto:mutt-dev-request@mutt.org?Subject="Unsubscribe Mutt Dev"?body=unsubscribe>
Mail-followup-to: bug-any@xxxxxxxxxxxxx, 369857@xxxxxxxxxxxxxxx, Mutt Developers <mutt-dev@xxxxxxxx>
References: <mutt-pr-2139@xxxxxxxxxxxxx> <E1FEzVV-0002xo-MZ@xxxxxxxxxxxxxxxxxxxx>
Sender: owner-mutt-dev@xxxxxxxx
User-agent: Mutt/1.5.13+cvs (2006-07-13)

forwarded 369857 http://bugs.mutt.org/2139
thanks

Hi,

I think http://bugs.debian.org/369857 is another instance of mutt PR
2139. The offending mbox is attached, mutt fails to open the contained
mail with "could not copy message". Changing the Content-Type not to
be application/pgp fixes that.

Christoph
-- 
cb@xxxxxxxx | http://www.df7cb.de/

Attachment: forsaker.mbox.gz
Description: Binary data

References:
- Re: mutt/2139: messages with base64-encoded CRLF pgp bits can't be read
  - From: Adeodato Simó

Prev by Date: Re: curses library version for mutt -v
Next by Date: Re: mutt/2139: could not copy message
Previous by thread: Re: mutt/2139: messages with base64-encoded CRLF pgp bits can't be read
Next by thread: mutt/2140: message-hook and patterns, [: invalid command
Index(es):
- Date
- Thread