From: Teemu Likonen <tlikonen@iki.fi>
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>,
Notmuch Mail <notmuch@notmuchmail.org>
Subject: Re: filtering headers from forwarded messages
Date: Mon, 30 Dec 2019 15:16:59 +0200 [thread overview]
Message-ID: <87eewmlzqs.fsf@iki.fi> (raw)
In-Reply-To: <877e2qbzms.fsf@fifthhorseman.net>
[-- Attachment #1: Type: text/plain, Size: 1009 bytes --]
Daniel Kahn Gillmor [2019-12-20T13:50:03-05] wrote:
> In notmuch-emacs, i can manually filter the headers by editing the
> reply compose buffer, of course, but it's kind of a pain, and it'd be
> nice to have it done automatically for me.
> Has anyone else considered this use case, or thought about how to make
> it easy/simple to do the right thing when using Notmuch? Are there
> other factors that are worth considering?
The underlying message-mode has these variables:
message-forward-as-mime
message-forward-before-signature
message-forward-ignored-headers
message-forward-included-headers
message-forward-show-mml
I have not studied those very closely but at least I know that when
-as-mime is nil user can use -included-headers to set what headers user
wants to include.
--
/// OpenPGP key: 4E1055DC84E9DFF613D78557719D69D324539450
// https://keys.openpgp.org/search?q=tlikonen@iki.fi
/ https://keybase.io/tlikonen https://github.com/tlikonen
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 694 bytes --]
next prev parent reply other threads:[~2019-12-30 13:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-20 18:50 filtering headers from forwarded messages Daniel Kahn Gillmor
2019-12-30 13:16 ` Teemu Likonen [this message]
2020-01-08 15:25 ` Daniel Kahn Gillmor
2020-01-16 20:20 ` Daniel Kahn Gillmor
2020-12-24 17:56 ` Daniel Kahn Gillmor
2020-12-30 10:46 ` Teemu Likonen
2020-12-31 22:39 ` Daniel Kahn Gillmor
2021-01-03 7:48 ` Teemu Likonen
2021-01-03 17:35 ` 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=87eewmlzqs.fsf@iki.fi \
--to=tlikonen@iki.fi \
--cc=dkg@fifthhorseman.net \
--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).