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 212330 - encryption compatability
encryption compatability
Status: RESOLVED DUPLICATE of bug 210041
Product: evolution
Classification: Applications
Component: Mailer
unspecified
Other All
: Normal major
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2001-10-12 04:07 UTC by kengallo
Modified: 2001-10-12 14:35 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description kengallo 2001-10-12 04:09:55 UTC
Package: Evolution
Priority: Major
Version: 0.15.99
Synopsis: encryption compatability
Bugzilla-Product: Evolution
Bugzilla-Component: Mailer

Description:
Hello,

I've noticed that when the "Security-->PGP Encrypt" option is selected,
the resultant message is not quite right.

Evolution calls /usr/bin/gpg and produces an ascii-armored output. But
then, instead of including that text inline, Evolution actually makes
the text an attachment. This makes the messages incompatible with other
PGP aware mailers (Pine, Eudora, ...).

Please include the encrypted output inline, instead of as an attachment.
Or at least make it an option somewhere.

Other than that, I am really enjoying Evolution. You are doing a great
job!

Thanks,
Ken



Unknown reporter: kengallo@hotmail.com, changed to bugbuddy-import@ximian.com.

Comment 1 Heath Harrelson 2001-10-12 14:35:03 UTC
This has been discussed in a number of PGP/GPG-related bug reports, 
including bug 204091, bug 204486, and so on.  Apparently RFC 2051 
specifies the attachment behavior, so it stays.

However, I'll mark this bug as a duplicate of bug 210041, which is a 
feature request for just this behavior.  Maybe if enough people 
scream "me too" this will get implemented.

I'm all for following the specifications, but if nobody except 
Evolution follows the spec, it's kind of beside the point, isn't it?  
You just end up breaking all of the other mailers who hit upon a 
standard way of doing this beside, or in absence of, an RFC.

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