unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: David Bremner <david@tethera.net>
To: NeilBrown <neil@brown.name>
Cc: notmuch@notmuchmail.org
Subject: Re: WIP: filter out envelope headers in notmuch-insert.
Date: Mon, 14 Feb 2022 22:15:25 -0400	[thread overview]
Message-ID: <87k0dwvps2.fsf@tethera.net> (raw)
In-Reply-To: <164488761286.17471.15404760359666744352@noble.neil.brown.name>

NeilBrown <neil@brown.name> writes:

> And on digging into postfix a bit, it seem that when forwarding to a
> program, it *doesn't* quote other "From " lines in the email, so
> splitting up the input would break things.  I wonder if that is a bug...
> the documentation is clear on the details of delivering to a program

It's a least partly "mbox is trainwreck, and they probably don't really
want to do mbox". Imagine a "From " line inside a signed part. But I
really don't know the intent of including a "From " line.

> So it seems... In the case of postfix the sender information is provided
> both in "From " and "Return-Path:", so just stripping "From " would be
> safe.  It is hard to argue against the extra caution of retaining the
> from line in an "X-Envolope-from" though.
>
> Thanks,
> NeilBrown

Thanks for thinking about these design issues with me.

d

      reply	other threads:[~2022-02-15  2:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-12  2:55 WIP: filter out envelope headers in notmuch-insert David Bremner
2022-02-12  2:55 ` [RFC PATCH 1/3] test: start new corpus of test messages for indexing code David Bremner
2022-02-12  2:55 ` [RFC PATCH 2/3] test: add known broken test for insert with mbox as input David Bremner
2022-02-12  2:55 ` [RFC PATCH 3/3] WIP: escape envelope from David Bremner
2022-02-12 11:34 ` WIP: filter out envelope headers in notmuch-insert David Bremner
2022-02-13 14:06   ` David Bremner
     [not found] ` <164481580222.17471.7090984749734305531@noble.neil.brown.name>
2022-02-14 11:16   ` David Bremner
2022-02-14 22:23     ` NeilBrown
2022-02-14 23:52       ` David Bremner
2022-02-15  1:13         ` NeilBrown
2022-02-15  2:15           ` David Bremner [this message]

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=87k0dwvps2.fsf@tethera.net \
    --to=david@tethera.net \
    --cc=neil@brown.name \
    --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).