<<< Date Index >>>     <<< Thread Index >>>

Re: mutt/2110: decode-copy decode-save create empty parts / messages in case of decoding errors



The following reply was made to PR mutt/2110; it has been noted by GNATS.

From: TAKAHASHI Tamotsu <ttakah@xxxxxxxxxxxxxxxxx>
To: bug-any@xxxxxxxxxxxxx
Cc: 
Subject: Re: mutt/2110: decode-copy decode-save create empty parts / messages 
in case of decoding errors
Date: Tue, 11 Oct 2005 09:12:36 +0900

 > >Number:         2110
 > >Category:       mutt
 > >Synopsis:       decode-copy decode-save create empty parts / messages in 
 > >case of decoding errors
 
 Thanks for the report.
 I don't like this behaviour, too.
 But I don't know how to fix it.
 
 > >Description:
 > Mutt creates empty messages if there's some error while decode-{copy,save} 
 > e.g. wrong passphrase.
 
 True.
 
 > It gives an error for pgp/mime types (Could not decrypt PGP message / Could 
 > not copy message) or if check-traditional-pgp is used.
 
 True.
 
 > Nontheless a message with an empty body is copied/saved.
 
 True.
 While decode-copying, mutt tries to decrypt the message *after*
 copying the header. So, only the header is left even if aborted.
 Hmmm...
 
 > This should not happen. In case of decode-save it could result in mail loss.
 
 No. The original message won't be deleted if decode-save fails.
 So both decode-copy and decode-save don't lose any messages.
 (Because Brendan fixed bug #1919, IIRC.)
 
 > Mutt should warn the user about the error and either copy the message as is 
 > (encoded) or refuse to write the message at all.
 
 IMHO, "copy-as-is" would cause more confusion.
 
 -- 
 tamo