After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 202572 - does not copy over text when replying to gpg encrypted message
does not copy over text when replying to gpg encrypted message
Status: RESOLVED DUPLICATE of bug 217540
Product: evolution
Classification: Applications
Component: Mailer
pre-1.5 (obsolete)
Other All
: Normal minor
: ---
Assigned To: Jeffrey Stedfast
Evolution QA team
: 204021 204022 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2001-05-03 06:14 UTC by Wayne Davis
Modified: 2013-09-10 14:02 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Wayne Davis 2001-05-03 06:14:58 UTC 
When replying to a gpg encrypted message, after decrypting, the text is not
inserted into the compose window.

Is this the desired effect?
Comment 1 Jeffrey Stedfast 2001-05-11 22:34:38 UTC 
pretty sure this is what you want.
Comment 2 Dan Winship 2001-05-14 13:51:34 UTC 
I'm gonna have to disagree with that. When replying to an
encrypted message, IMHO the default should be to cite the
decrypted text and default to sending an encrypted reply.
(If you don't have the keys to be able to send an encrypted
reply, it should give you a warning before letting you into
the composer.)
Comment 3 Luis Villa 2001-07-05 05:37:52 UTC 
*** bug 204021 has been marked as a duplicate of this bug. ***
Comment 4 Luis Villa 2001-07-05 05:39:48 UTC 
*** bug 204022 has been marked as a duplicate of this bug. ***
Comment 5 Dan Berger 2001-07-06 05:35:44 UTC 
Note that this misbehavior also affects replying to PGP/GPG signed
messages - which is more common (and therefor more consistantly
annoying) than replying to encrypted messages.

It is also easier to fix, as I think it can be argued that replying to
a signed message requires no special treatment.  (It might be nice if
you could specify that responses to signed messages be signed, but
that could be treated as a sepperate feature request).
Comment 6 Jeffrey Stedfast 2001-07-10 17:32:09 UTC 
actually this does not affect multipart/signed messages. I just tested
it and it worked okay.
Comment 7 Jeffrey Stedfast 2001-07-17 19:55:11 UTC 
fixed in CVS
Comment 8 Dan Berger 2001-07-25 20:16:34 UTC 
I just tried replying to a PGP signed message, and the response
composer window is empty.  This is with .11.99.  It's quite annoying,
as I have to either cut and paste (and reformat) or just use mutt
(which is what I did in this case).

In this case, the message wasn't multipart/signed, it was 
application/pgp; format=text; x-action=sign
Comment 9 Dan Berger 2001-07-25 20:17:40 UTC 
See also bug 204111
Comment 10 Jeffrey Stedfast 2001-07-26 21:14:46 UTC 
The Bat! and it's broken application/pgp mime type should now work.
But if it doesn't, too bad - tell your friend to get a REAL mailer. If
this bug gets opened again, I'm just going to remove all support for
application/pgp.

This is an invalid method of doing pgp and I will not waste another
minute writing hack-arounds for it.
Comment 11 Dan Berger 2002-03-26 01:53:18 UTC 
It looks like this is still broken for in-line PGP content (not
application/pgp).

I don't have a pgp-mime message to test with, but the bug discussion
suggests it should work either way, so I'm reopening.
Comment 12 Jeffrey Stedfast 2002-03-26 19:48:53 UTC 

*** This bug has been marked as a duplicate of 217540 ***