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 531262 - PGP encrypted mail sent from MS Outlook are not displayed decrypted
PGP encrypted mail sent from MS Outlook are not displayed decrypted
Status: RESOLVED INVALID
Product: evolution
Classification: Applications
Component: Mailer
2.22.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-05-03 18:51 UTC by Mattias Persson
Modified: 2008-05-07 09:09 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description Mattias Persson 2008-05-03 18:51:27 UTC
Confirmed Environments:
Ubuntu 7.10 (amd64), Evolution 2.12.1, GnuPG 1.4.6
Ubuntu 8.04 (amd64), Evolution 2.22.1, GnuPG 1.4.6

Problem:
It works fine to send GPG encrypted mails from Evolution to MS Outlook or to another Evolution client, but when an email sent from MS Outlook encrypted with PGP Desktop then Evolution can not parse the message and thereby does not decrypt and display the message. I have no problems with reading encrypted emails sent from another evolution client so there is nothing wrong my keys. I expected the messages in the emails to be displayed but the received emails from MS Outlook are instead displayed like this in evolution:

**** Bug submitters note: the content that evolution displays starts below this line ****
Could not parse PGP/MIME message
gpg: armor header: Version: PGP Desktop 9.8.2 (Build 3005)
gpg: public key is 004BEC3A
gpg: encrypted with RSA key, ID 004BEC3A
gpg: decryption failed: secret key not available
****** Bug submitters note: content ended on the previous line ********

The entire email looks like like this (I have put X's in the ip- and email-addresses):

****** Bug submitters note: full email starts below this line *******
Return-path: <email address hidden>
Received: from Mattes (unverified [XXX]) by XXX.net
        (Rockliffe SMTPRA 6.0.11) with ESMTP id <email address hidden> for
        <email address hidden>; Fri, 18 Apr 2008 10:02:24 +0200
Received: from Mattes by Mattes (PGP Universal service); Fri, 18 Apr 2008
        10:09:03 +0100
X-PGP-Universal: processed; by Mattes on Fri, 18 Apr 2008 10:09:03 +0100
From: "Me" <email address hidden>
To: <email address hidden>
Subject: outlook to evolution
Date: Fri, 18 Apr 2008 10:08:42 +0200
Message-ID: <000b01c8a12b$7722e3a0$6568aae0$@XXX.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcihK2pvnwvEmJx4SZqMBC6ZFUC1RQ==
X-PGP-Encoding-Format: MIME
X-PGP-Encoding-Version: 2.0.2
Content-Type: multipart/encrypted; boundary="PGP_Universal_812F09E6_E522C593_E5CCA7F3_B45E5D2A"; protocol="application/pgp-encrypted"
X-Evolution-Source: pop://XXX%<email address hidden>/

--PGP_Universal_812F09E6_E522C593_E5CCA7F3_B45E5D2A
Content-Type: application/pgp-encrypted; x-mac-type=54455854; name=Version.txt
Content-Disposition: attachment; filename=Version.txt

Version: 1

--PGP_Universal_812F09E6_E522C593_E5CCA7F3_B45E5D2A
Content-Type: application/octet-stream; x-mac-type=70674546; name=Message.pgp
Content-Disposition: attachment; filename=Message.pgp

-----BEGIN PGP MESSAGE-----
Version: PGP Desktop 9.8.2 (Build 3005)

qANQR1DBwEwDm/RgmgBL7DoBB/9pnLmLW0T0Zv1xHjEsG2TKHbZ9EQEZ2dLZ93de
bTFb+3zK0GJMuCWBzQn1qq4FMdgyPox3N4bsiXFo6uHsw6vH8dIIjhL/qMbyYSiF
cydhyNW7wRZWNRkTjDSngY97MlGUnXPB/qb3b+d+ST1W1ZPpTd2gVgQSyTJjmRWO
emSc/KDrROCYz35wPRqpq0K5g9I4htqmM1+/CBq6mTjc3t7ge/oJnyu0kfLsx7rB
mEv2qIJPeu0nr+g7lw2BVjWeWnPYsfX0Sf0A4aD+8dsn+wZqQUR4Bn5oXuPbDGPe
Z7DmtnqlrDqeZ1jxBLAA5tJjEqM9K90pZaVjE9kiiUNN6J0Z0sUQASo31KLmC+KA
1IgeVAISYzwnC6kx7eGEFLEE0VZ0GquAnCItIpoDHN4ubOHBIyeqQcN9pE8e6xyj
Xi4dNN63ryx3nk9PTV/HNOTdNH+0+xzr0rPVRrxFn0nAzX4ozEILfCU35QCpXamd
1wVGXqlaRMPZRLx2o6N+0TauVbH0Jv/gc72eAPRaNjjnuyXo1s1ivXFwr5Dmzs+c
Z52JXa7EzDUT+uRZxPakmdPuF9a9OW9opCeHXiGfgeNARHW8AZaZ1ZZBJH2MvPeE
sQMfhuVgghazsLdMP/qIxqhMiVHMe+zr1mJFbzfDsIsHdcyhS8YuVlYbMz/iEcUp
vY5f8qt660akSf5tn4x9M/hCp7hS+uDbJXSFeTJr7kmUPGYKT0ltI2jfsCl5a9SL
M77QRgMKY7FMx74SQZFInDq0SoscgLuLjHtf5rUGnIFVHcs38Ytkzbc8aRH1OfQv
mSHIPTq4DAwYJLOHsY9fmKDK0d9RubitMybBVshhRERk8ytdEOSP5+9CP2f5JYVJ
ZNQeqOATxUjDipO0kJzGZhbvtSoTAPMLfdLqM/NGzDEToWIy9c0uBZLJWewg0Wpb
8g40Z9VpM6tqeJLW6jJC8YW7HtJJRSW9WbNCZOlTGCOw7r2nnS2xSuuZWfXXcU9s
if8nwAR6WqK4J1WFocRhGvyVYDdxEGGCEbUbe2Ra8DYWvsA4fibOmiy1yu7wksbu
ZLu7WCLZZtPOn4V7LbQ0iV0l/fJK8b8Ay4M63JQdhInfD60Ll9BctvZpAOEQjGJL
N4kARcuuo+j9Pvi9COX9sRMSpPk81DsayE1tkbeKlb5cm/dd9YN9GRNSY5gAmsej
LMHr3/wykvLgO3Xt8YxrfyxpuKZcWS+BRW8FO63U4HQfijVdZ658bRsQkdwLmoe2
eeBx56wU9c+vUAAhAVEezsBzLEG65oPaDOVXpPRKAImUJ4PqhsIDJBwwBnq0Za23
86vfiWDx27H3cHQYUzzuwHgpaGKHwZeg8rhp2NITPjzDBCvC9Xy1te6ODHhS3S6z
V4Byj1PncXvTKd0T6jDfii+MLV62HfqW/UYXqtVf+4u9FihAwmjUvlvWOyWhiYlJ
XA3fY4XetfLbt8qKOa3QNoiwmjTMRSAL69Z0RQWpEm3Mpw4WdQYmpM3hE6rCgyd2
BShR1+lge5WjbIg8FDH6m/tRPhfRX4BpE8CJDFiY0nGG+LUl+hWyp1I9QWMzwHCi
YxzE8IWKuWulIUeg3QEKH+TsLAyxs4Q3FcQYcgD5gEkM59LhhqunxPMgOiihyckg
k3gf2+AlNbv0WAtB3iXNBdIuGnxQ+WXMhsrGwbXxlg/i87f4tt/UyMY46Zoz69UH
Ozv0xR/5HhaSMx1NHJ5Tp5YzP6bPfHgdxH0JwFK8rCxVumehW+Ng0P/8jV0H7B9T
UdcJYlixBSaWj/voXa5V6X8CPf7F5rm1lVOweQ9xkaXZdkDt8Yh4YlrFozd524SO
fyOJHD02DC1Yp5+JNP1r4nt7APgAoC/5BoLcSc6Db6Sv96BvUNvP9CvHJIsefZbk
krmC+EanbPVa+ejS3nRrdnioCz22txvZxh9PfBcQp9Xk7tE+KDKus1mSJTduKmXp
QKcR56GYD/ZZl13ct76X+OeM0OuL00/E9VetO/cT/BppGM1UFwfnOVuDEIRJVZm2
s6C+lyp2PT1vOs3qM6WO0wWfYgiuld5Yx2ytAxzeuPo/nJ8nQcg0oHplh2DWz5ou
iGFGsELg2fvP896nb1p0qlGQpzdnLE2d55RQUOLMIYoNaYeCBnNxFW28s0lTBilI
TOJK/G58KuMZSWtYQIOteAqBNBqhDCq4RUzdTU9/q8lLmRU8LsIX0ZY8BW+C7KyC
BRfUv0e1KSUQZBhP1sloKoSjxunazL5mkOFl/F6GWoUf75J4o30lbe4w2mQDurg9
7vfLFzEsXzXMu+gaWqfuFtEogEq39AZndJqe1GIfG/d1jhvVu2XE
=2AGg
-----END PGP MESSAGE-----

--PGP_Universal_812F09E6_E522C593_E5CCA7F3_B45E5D2A--
******* Bug submitters note: full email ended on the previous line *******
Comment 1 André Klapper 2008-05-06 18:49:30 UTC
gpg: decryption failed: secret key not available

not an evolution issue.
Comment 2 Mattias Persson 2008-05-06 20:52:15 UTC
Please read the ENTIRE bug report. It says clearly that the secret key is available since I'm able to read other encrypted emails sent from another Evolution mailer. I do believe that this is an evolution issue and that evolution is UNABLE to find the key but that doesn't mean that the key is not available (because it evidently is available).
Comment 3 Jeffrey Stedfast 2008-05-06 21:33:23 UTC
gpg: armor header: Version: PGP Desktop 9.8.2 (Build 3005)
gpg: public key is 004BEC3A
gpg: encrypted with RSA key, ID 004BEC3A
gpg: decryption failed: secret key not available


You need to import the secret key into gpg otherwise gpg can't decrypt it.

the message you sent from evolution must have been using a different key to encrypt to.
Comment 4 Mattias Persson 2008-05-06 22:11:48 UTC
Please, here me out. Evolution decrypts all other emails for me but not the ones sent from PGP Desktop. I only have one keypair so there is no other key that could have been used. Could you consider the possibility that the header sent from PGP Desktop is different from what evolution expects and that is root of the problem ("Could not parse PGP/MIME message")? Please verify that you can't repeat the problem before you close the bug report.

If you give me your public key I can send you an encrypted email from PGP Desktop so you can properly verify the bug / invalidate it.
Comment 5 Jeffrey Stedfast 2008-05-07 00:28:20 UTC
Evolution just pipes the message to gpg and gpg is saying that it doesn't have the secret key needed to decode it.

there's really nothing Evolution-specific to this bug report.

If you don't believe me, copy the ---BEGIN PGP MESSAGE--- text, paste it into a file, and then run gpg --decrypt on it. You'll get the error message.
Comment 6 André Klapper 2008-05-07 09:02:55 UTC
1) please run "gpg --decrypt" as described by jeffrey and tell us the output.
2) i have no idea what "PGP Desktop" is.
Comment 7 Mattias Persson 2008-05-07 09:09:33 UTC
You're right, my apologies. To my defense though, this is my own (bad) attempt to reproduce an actual bug I've encountered many times. I have therefore submitted a new bug report (#531912) which describes the problem I tried to reproduce.