From: Brian Sniffen <bsniffen@akamai.com>
To: "notmuch@notmuchmail.org" <notmuch@notmuchmail.org>
Subject: Exchange mutilation of multipart/encrypted
Date: Mon, 1 Dec 2014 14:28:24 -0500 [thread overview]
Message-ID: <m2iohvf9uv.fsf@usma1mc-0csx92.kendall.corp.akamai.com> (raw)
My employer uses an Exchange server in place of an MTA. It mutilates
multipart/encrypted messages, so that when I receive a PGP/MIME message
the Emacs-notmuch interface shows me:
[ multipart/mixed ]
[ text/plain ]
[ ATT00002: application/pgp-encrypted ]
[ msg.asc: application/octet-stream ]
When I used Gnus heavily, I wrote a little program to un-mutilate
PGP/MIME mail:
~~~
(defun repair-multipart-encrypted (article)
"Switch a multipart/mixed header to multipart/encrypted.
This helps cope with broken Exchange servers."
(interactive (list (gnus-summary-article-number)))
(gnus-with-article article
(message-narrow-to-head)
(goto-char (point-min))
(search-forward "Content-Type")
(search-forward "mixed")
(replace-match "encrypted; protocol=\"application/pgp-encrypted\"" t t)
(widen))
(let (gnus-mark-article-hook)
(gnus-summary-select-article t t nil article)))
~~~
I'd love to have a way to tell Emacs-notmuch to treat a part as of a
different type, and provide parameters. Alternately, I'd be happy to
edit the file on disk and have it re-indexed---but that seems likely to
cause me regret. Any advice? I see
`notmuch-show-insert-bodypart-internal` and expect to call that
with a forced content-type.
Thanks,
Brian
--
Brian Sniffen
"I reserve the right to evolve my views, and state that views I previously
expressed may have been somehere along the spectrum from insufficiently
nuanced through ill-informed to dead wrong."
reply other threads:[~2014-12-01 19:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=m2iohvf9uv.fsf@usma1mc-0csx92.kendall.corp.akamai.com \
--to=bsniffen@akamai.com \
--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).