From: Carl Worth <cworth@cworth.org>
To: Notmuch List <notmuch@notmuchmail.org>
Subject: Workaround for Exchange-corrupted PGP/Mime structure
Date: Wed, 20 Nov 2019 08:36:50 -0800 [thread overview]
Message-ID: <877e3ufqsd.fsf@wondoo.home.cworth.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1362 bytes --]
I recently received a GPG-encrypted message that notmuch was not able to
handle transparently as I'm used to. (That is, instead of decrypting the
message and verifying the signature inside, etc.—instead I was just
presented with an attachment that contained the encrypted message.)
After some poking around, it appears that the problem is that the
message was sent through Microsoft Exchange which corrupts PGP/mime
structure by changing the outer content-type from "multipart/encrypted"
to "multipart/mixed".
I've verified this bug by sending mail from notmuch through Exchange as
the MTA and it indeed does corrupt the mail in exactly this fashion.
It looks like this bug in Exchange is known[1] and there's evidence of
other MUAs working around the bug[2].
Have other notmuch users encountered this problem?
What would anyone think about a workaround where notmuch-emacs could
grub around inside a "multipart/mixed" structure looking for child parts
that look like they really should have been a part of a
"multipart/encrypted" container?
-Carl
[1] https://social.technet.microsoft.com/Forums/en-US/c5059734-5031-4d82-96eb-c74fe60b5e9e/quotthis-is-a-broken-pgpmime-message-from-msexchangequot
[2] https://gitlab.com/mikecardwell/gpgit/blob/master/gpgit.pl#L108
which also refers to Enigmail having a workaround for thi.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next reply other threads:[~2019-11-20 16:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-20 16:36 Carl Worth [this message]
2019-11-20 18:41 ` Workaround for Exchange-corrupted PGP/Mime structure Ralph Seichter
2019-11-20 19:19 ` David Bremner
2019-11-20 20:55 ` Carl Worth
2019-11-20 21:19 ` Carl Worth
2019-11-20 22:10 ` Brian Sniffen
2019-11-21 3:06 ` Daniel Kahn Gillmor
2019-11-21 2:24 ` Daniel Kahn Gillmor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877e3ufqsd.fsf@wondoo.home.cworth.org \
--to=cworth@cworth.org \
--cc=notmuch@notmuchmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).