Package: Evolution
Priority: Normal
Version: 1.0.8
Synopsis: Cannot reply to or forward inline PGP encrypted email
Bugzilla-Product: Evolution
Bugzilla-Component: Mailer

Description:
Have someone send you a PGP encrypted email that uses inline encoding
(Kmail 1.3.2 would be an example).  
Example headers look like this:
========================================
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Re: [...]
X-Mailer: VM 7.05 under 21.4 (patch 4) "Artificial Intelligence" XEmacs
        Lucid

-----BEGIN PGP MESSAGE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.6 and Gnu Privacy Guard
<http://www.gnupg.org/>
[encrypted message follows]
========================================

When you attempt to reply to (or forward) this message, the encrypted
version of the text is quoted.  The correct behavior would be to quote
the decrypted text.  (Evolution does this correctly when replying to
RFC2015 PGP/MIME email, such as produced by evolution or mutt.)

A similiar bug is that evolution does not recognize the existance of a
inline PGP signature if the email is a simple MIME quoted-printable with
no attachements.  But multipart MIME email that has inline signatures is
correctly detected.  By "inline" signatures I mean the email takes the
form:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
[message content]
-----BEGIN PGP SIGNATURE-----
[signature]
-----END PGP SIGNATURE-----
Again, the "detached signature" form used by evolution works great. 
Kmail can also be used to create such a email that will fail in
evolution.



Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.