ok.. now the forum seems to be stable enough for postinng.
another try posting the quotes of the source, even if don't understand which headers were missing (but i don't really understand how mail works internaly)
Yes that's bug 77. Content-Transfer-Encoding is specified, but unnecessarily, as there are only MIME parts present (which have their own Content-* declarations).
As a test, you could save the message, remove the line starting with "Content-Transfer-Encoding", and then import or open it again. Decryption should work.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
I have a similar problem to the one detailed in this thread:
http://sourceforge.net/p/enigmail/forum/support/thread/4add2b69/
The mail-body is blank and stays that way after clicking decrypt. It doesn't show any attachments.
If I save the mail and decrypt it with gpg, gpg can decrypt the mail correctly.
This is the (slightly censored) source of the mail in question:
User-Agent: KMail/4.8.5 (Linux/3.2.0-53-generic; KDE/4.8.5; i686; ; )
MIME-Version: 1.0
Content-Type: multipart/encrypted; boundary="nextPartyyy"; protocol="application/pgp-encrypted"
Content-Transfer-Encoding: quoted-printable
--nextPartyyy
Content-Type: application/pgp-encrypted
Content-Disposition: attachment
Version: 1
--nextPartyyy
Content-Type: application/octet-stream
Content-Disposition: inline; filename="msg.asc"
-----BEGIN PGP MESSAGE-----
Version: GnuPG v1.4.11 (GNU/Linux)
-----END PGP MESSAGE-----
--nextPartyyy--
Why doesn't this mail work with enigmail?
Thanks for any help!
Last edit: meinberg2 2014-02-17
I suspect that this is bug 77 ([bugs:#77]).
Can you please copy the complete set of message headers? You can omit those headers containing email addresses.
Related
Bugs:
#77ok.. now the forum seems to be stable enough for postinng.
another try posting the quotes of the source, even if don't understand which headers were missing (but i don't really understand how mail works internaly)
Last edit: Patrick Brunschwig 2014-02-20
Yes that's bug 77. Content-Transfer-Encoding is specified, but unnecessarily, as there are only MIME parts present (which have their own Content-* declarations).
As a test, you could save the message, remove the line starting with "Content-Transfer-Encoding", and then import or open it again. Decryption should work.