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 268917 - Evolution doesn't track the crypto status of forwarded emails
Evolution doesn't track the crypto status of forwarded emails
Status: RESOLVED DUPLICATE of bug 252111
Product: evolution
Classification: Applications
Component: Mailer
2.0.x (obsolete)
Other All
: Normal enhancement
: Future
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2004-10-29 00:59 UTC by jhaar
Modified: 2005-02-07 12:46 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement



Description jhaar 2004-10-29 00:59:32 UTC
Distribution: Fedora Core release 2 (Tettnang)
Package: Evolution
Priority: Normal
Version: GNOME2.6. 2.0.2
Gnome-Distributor: Red Hat, Inc
Synopsis: Evolution doesn't track the crypto status of forwarded emails
Bugzilla-Product: Evolution
Bugzilla-Component: Mailer
Bugzilla-Version: 2.0.2
Description:
If I send a PGP signed message, and open it in evolution, it all works
fine

However, if I then FORWARD that message - Evolution doesn't
automatically also mark the new message as needing encryption - and I
think it should.
After all - if I send an encrypted email containing confidential
information (one of the primary reasons for using crypto ;-), but a
reply/forward is in cleartext - you have a problem. Most other crypto
mailers I know of do this

I assume this is a problem for reply functions as well as forwards. And
I guess it applies to S/MIME as well as PGP

Tried with Fedora Core 2 devel release - 2.0.2

Jason



Unknown reporter: jhaar@trimble.co.nz, changed to bugbuddy-import@ximian.com.
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.

Comment 1 André Klapper 2005-02-07 12:46:17 UTC

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