Re: [Mutt] #2912: Unenlightening error message "Could not copy

To: email@xxxxxxx, brendan@xxxxxxxxxx
Subject: Re: [Mutt] #2912: Unenlightening error message "Could not copy
From: Mutt <fleas@xxxxxxxx>
Date: Thu, 26 Jun 2008 05:43:54 -0000
Cc: mutt-dev@xxxxxxxx
In-reply-to: <036.16c589bf45ea439322206c3dcb7eedec@xxxxxxxx>
List-post: <mailto:mutt-dev@mutt.org>
List-unsubscribe: send mail to majordomo@mutt.org, body only "unsubscribe mutt-dev"
Mail-followup-to: fleas@xxxxxxxx
References: <036.16c589bf45ea439322206c3dcb7eedec@xxxxxxxx>
Reply-to: fleas@xxxxxxxx
Sender: owner-mutt-dev@xxxxxxxx

#2912: Unenlightening error message "Could not copy message" when decryption 
fails

Changes (by brendan):

  * status:  new => closed
  * resolution:  => fixed

Comment:

 (In [e2780a423d96]) Make mutt_copy_message distinguish between fatal and
 non-fatal errors.
 Non-fatal errors should prevent moving messages, since they indicate
 data loss. But mutt should still attempt to display them, since being
 able to see some attachments is better than nothing.
 Also stop printing out non-PGP material in application/pgp
 attachments. Closes #2545, #2912.

-- 
Ticket URL: <http://dev.mutt.org/trac/ticket/2912#comment:4>

References:
- [Mutt] #2912: decrypt gnupg message fails with "Could not copy message"
  - From: Mutt

Prev by Date: Re: [Mutt] #2545: Cannot open message with pgp key attachment
Next by Date: Re: [Mutt] #2886: inconsistent use of backslash in regexps
Previous by thread: Re: [Mutt] #2912: Unenlightening error message "Could not copy
Next by thread: Re: [Mutt] #2912: Unenlightening error message "Could not copy
Index(es):
- Date
- Thread