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 785840 - Avoid sending broken messages when submitting PGP/MIME encrypted emails with EWS
Avoid sending broken messages when submitting PGP/MIME encrypted emails with EWS
Status: RESOLVED WONTFIX
Product: evolution-ews
Classification: Other
Component: Mail
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Evolution EWS maintainer(s)
Evolution EWS maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2017-08-04 19:31 UTC by Ángel
Modified: 2017-08-07 13:50 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Ángel 2017-08-04 19:31:45 UTC
When using the EWS connector to send a PGP/MIME email, the receiving side of the server munges the structure in order to add a text/plain part, converting multipart/encrypted into multipart/mixed.

The connector should attempt to work around it so that it ends up sending a decent email that can be decrypted by other clients.

See the mailing list thread:
https://mail.gnome.org/archives/evolution-list/2017-July/msg00106.html
https://mail.gnome.org/archives/evolution-list/2017-July/msg00113.html
https://mail.gnome.org/archives/evolution-list/2017-July/msg00122.html
https://mail.gnome.org/archives/evolution-list/2017-July/msg00123.html
Comment 1 Milan Crha 2017-08-07 13:50:52 UTC
Thanks for a bug report, but as I wrote in that mailing list thread, I disagree. The statements above are also incorrect:
a) Evolution doesn't generate broken message structure, it generates proper
   message structure
b) it's not an evolution-ews issue, it can do SMTP too
c) it's all server side issue, on the Microsoft Exchange server, and such
   workaround may eventually change behaviour for an Exchange server version X,
   but not for version Y, or even when the server receives update to X.Z. In
   other words, any such code maintenance would be a nightmare, not talking
   about reverse-engineering, trying to figure out what message structure makes
   the Exchange server happy (and then we get into the server version problem).

Another thing is that the change in commit [1] makes that extra text/plain part visible, just in case in contains anything useful.

I'm not willing to add any such code, I'm not definitely willing to hunt for Exchange server changes which might broke it. The problem is there, not with Evolution, and that's it.

[1] https://git.gnome.org/browse/evolution/commit/?id=4643f76e049c83a2562b1c17dcd3764eaeb7f08b