GNOME Bugzilla – Bug 758856
[GPG] Option to prefer inline sign/encrypt of pure text/plain mails
Last modified: 2015-12-03 07:57:55 UTC
Hi there, it sometimes happens that I send a signed mail with Evolution and get reply from the recipient that my signature is considered invalid. I then resend my mails like this (and then it works) cat text | gpg --clearsign | mail recipient@mail.org but of course it would be nice to be able to choose the gpg --clearsign method from within Evolutions mail composer. Thanks, Fabian
Thanks for a bug report. Evolution(-data-server) always signs as multipart/signed, it doesn't generate inline signatures. The option you want might change it, if I understand the --clearsign option properly.
I am not a GPG expert, but yes I believe that the --clearsign parameter signs inlined. I think the problems with the current approach arise when e.g. mailing lists add footers to the mails and change some of the header lines?
The message headers are not a problem, especially when they do not change Content-Type and other Content-related headers of the message, but the message list footers can be really a problem. I saw a message encoded in base64, after which was added a message list footer in a plain text. It wasn't a new sub-part, it was just added text at the end of the base64 encoded bytes. I do not think evolution can do anything real with it (there is opened a bug report about it here).
> I do not think evolution can do anything real with it AFAIUI for signed messages this problem could be mitigated by offering support for inline-signing. I am not sure, though, how this support should look like. I mean, it should probably not be possible to select inlined signing as a default. Maybe it should be offered on a per-message base, e.g. with an extra option in the menu "Send this message inline-signed"?
I did some investigation and I'd do it per-account setting. Furthermore, only text/plain messages can be signed/encrypted inline, once it's HTML or has attachments, the Enigmail (Thunderbird extension) is confused with it. I'm currently facing issue with Content-Transfer-Encoding, the message doesn't want to use it for some reason. Otherwise it seems to work fine.
This is great news Milan, thank you very much! I have to say that it's really refreshing how responsive, polite, helpful and open-minded you are by answering my requests. Especially given the size of the project you maintain. It's really a breeze to work with someone like you on the other side of the bug tracker. Keep up the good work! [ Please show this to your employer ;) ] Thank again, Fabian
I added the option to the account preferences, at the Security tab. The messages is GPG signed/encrypted inline only if the option is set and if the messages is a pure text/plain. If it has attachments or it is anything else than text/plain, then the sign/encrypt fallbacks to the multipart sign/encrypt. Created commit b83f07b in eds master (3.19.3+) Created commit_2c2cec7 in evo master (3.19.3+) [1] [1] https://git.gnome.org/browse/evolution/commit/?id=2c2cec7
Excellent!