GNOME Bugzilla – Bug 201350
S/MIME support
Last modified: 2013-09-10 14:03:17 UTC
We should support S/MIME. (Split out from #107)
http://www.mozilla.org/projects/security/pki/nss/smime/ http://www.mozilla.org/projects/security/pki/nss/ref/nssfunctions.html#smime
I apologize for the spam; re-setting all target milestones to 'future' in preparation for evolution 1.0. If you have any questions, please feel free to write louie@ximian.com.
(No, this is a blocker, just for 1.1 rather than 1.0.)
Setting the goal for this to 1.1.
Because of the decision to remap 1.1->1.2 and 1.2->1.4, I'm going to be moving a large number of bugs around in the bugzilla. You can just search on 'body contains' 'Because of the decision to remap' and mark all as read. Please direct all questions about this change to evolution@ximian.com, not the bug. Luis
Moving to critical for triage purposes; blocker should be reserved for crashers.
We may want to look at the larger goals described here: http://www.gnupg.org/aegypten/ which looks to become a government set standard in at least Germany.
*** bug 218390 has been marked as a duplicate of this bug. ***
*** bug 224757 has been marked as a duplicate of this bug. ***
evolution does not support one of the 3 types of signed messages. It is a pity because it could display the e-mail correctly without checking the signature... I sure, it would be easy to fix... The format not supported is: Content-Type: application/octet-stream; name=smime.p7m
franck: this is already fixed in development CVS (the displaying of multipart/signed parts that we cannot handle yet) S/MIME however, is not yet implemented.
*** bug 233738 has been marked as a duplicate of this bug. ***
*** bug 234631 has been marked as a duplicate of this bug. ***
Is this a 1.4 goal?
no.
set milestone to 1.6
I would like to voice my support for increasing the priority on this item. I have to keep other mailers around becasue of lack of s/mime support and it's making my telecommuting setup a challenge to say the least. Thanks for your consideration.
Shuold this be ready for 1.5.1?
Setting milestone
We are going to close this general bug in favour of going forward with more specific bugs. In general the S/MIME stuff is all in place.