unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: Teemu Likonen <tlikonen@iki.fi>, Notmuch Mail <notmuch@notmuchmail.org>
Subject: Re: filtering headers from forwarded messages
Date: Thu, 31 Dec 2020 17:39:23 -0500	[thread overview]
Message-ID: <87k0sxtxb8.fsf@fifthhorseman.net> (raw)
In-Reply-To: <87r1n7d11x.fsf@iki.fi>


[-- Attachment #1.1: Type: text/plain, Size: 1483 bytes --]

Hi Teemu--

On Wed 2020-12-30 12:46:02 +0200, Teemu Likonen wrote:
> I don't know any automatic way to remove headers from an email message
> that is stored as a MIME part.

The straightforward way seems to be to parse/interpret the message with
our knowledge of rfc5322, identify the headers to be removed, and then
re-render the message.

iirc, it worked for me until i started using emacs 27.1, too ☹

Obviously, if "Content-Type" or other structural headers are removed,
you'll break the message.  But the answer there is "don't do that", i
think.

> What about forwarding a message as MIME part which is just "text/plain"
> (and not "message/rfc822")?

This might be useful for some people, but doesn't really satisfy my
goals.  When i want to forward a message, i want to forward the whole
message -- multipart, with attachments, etc.  My goal when forwarding is
to *not* mangle the message, but rather to supply it to the new
recipient in a parseable way.  I just don't think that most recipients
need to have access to (for example) the headers that are added by all
the mail transport agents along my receipt path.  I want them filtered
for privacy, which i think isn't unreasonable.  (i recognize that if the
use case is debugging the MTA path itself, i probably *don't* want those
headers stripped, but that's a different use case than the most common
message forwarding)

so i'm still stuck with this regression, sadly.

        --dkg

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2020-12-31 23:01 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
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 [this message]
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=87k0sxtxb8.fsf@fifthhorseman.net \
    --to=dkg@fifthhorseman.net \
    --cc=notmuch@notmuchmail.org \
    --cc=tlikonen@iki.fi \
    /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).