Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 955587 - Do not consider PGP and S/MIME subparts as attachments
Do not consider PGP and S/MIME subparts as attachments
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: evolution-data-server (Show other bugs)
6.4
Unspecified Unspecified
unspecified Severity low
: beta
: ---
Assigned To: Matthew Barnes
Desktop QE
: Patch
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-04-23 07:06 EDT by David Jaša
Modified: 2015-01-07 09:39 EST (History)
5 users (show)

See Also:
Fixed In Version: evolution-data-server-2.32.3-3.el6
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-11-21 00:12:44 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
sample s/mime message (6.83 KB, text/plain)
2013-04-23 09:42 EDT, David Jaša
no flags Details
evolution-data-server-2.28.3-attachment-flag-2.patch (1.35 KB, patch)
2013-04-24 03:00 EDT, Milan Crha
no flags Details | Diff
sample pgp-signed message (2.60 KB, text/plain)
2013-04-24 06:13 EDT, David Jaša
no flags Details


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2013:1540 normal SHIPPED_LIVE Low: evolution security, bug fix, and enhancement update 2013-11-20 19:40:51 EST

  None (edit)
Description David Jaša 2013-04-23 07:06:21 EDT
Description of problem:
evolution shows in msg list all s/mime-signed messages as messages with attachment, this is incorrect as the signature implementation should be transparent to the user. PGP/MIME-signed messages aren't displayed as messages with attachment either

Version-Release number of selected component (if applicable):
evolution-2.28.3-30.el6.x86_64

How reproducible:
always

Steps to Reproduce:
1. display a folder with s/mime-signed message that has no attachments
2.
3.
  
Actual results:
the s/mime message is displayed as having attachments

Expected results:
the s/mime message does not have attachments

Additional info:
Comment 2 David Jaša 2013-04-23 09:42:52 EDT
Created attachment 739004 [details]
sample s/mime message

The bug applies to Evo 3.6.4 in Fedora 18 as well.
Comment 3 Milan Crha 2013-04-24 02:18:48 EDT
Thanks for a bug report. I guess you generated the email in Evolution, right? The reason why the message is marked as "with attachments" is this:
   Content-Disposition: attachment; filename="smime.p7s"
which is set on the
   Content-Type: application/x-pkcs7-signature; name="smime.p7s"
part. I see (and didn't know) that evolution itself sets this 'attachment' disposition too, for some reason. I guess the logic to recognize messages with and without attachments should be extended (git master is also "affected").
Comment 4 Milan Crha 2013-04-24 03:00:34 EDT
Created attachment 739293 [details]
evolution-data-server-2.28.3-attachment-flag-2.patch

for evolution-data-server;

The same patch committed upstream as 682ce13 for git master (3.9.1+) and as 8fb7cbf for git gnome-3-8 (3.8.2+). Selecting a message is enough to let it reconsider whether the message has an attachment or not.
Comment 5 David Jaša 2013-04-24 06:13:09 EDT
Created attachment 739376 [details]
sample pgp-signed message

Yes, the s/mime message was also sent using evo.

Note that the attached message that looks like pgp/mime to me already isn't displayed as a message with attachment.
Comment 14 errata-xmlrpc 2013-11-21 00:12:44 EST
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2013-1540.html
Comment 15 David Jaša 2015-01-07 09:39:50 EST
Removing needinfo on closed bugs.

Note You need to log in before you can comment on or make changes to this bug.