unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Jeff Templon <templon@nikhef.nl>
To: Martin Jambor <mjambor@suse.cz>,
	David Bremner <david@tethera.net>, Carl Worth <cworth@cworth.org>,
	Daniel Kahn Gillmor <dkg@fifthhorseman.net>
Cc: notmuch@notmuchmail.org
Subject: Re: tell me how to do this right (mail sent to lists)
Date: Thu, 11 Oct 2018 14:13:27 +0200	[thread overview]
Message-ID: <m2pnwg65qw.fsf@simeto.nikhef.nl> (raw)
In-Reply-To: <ri6y3b4vnvv.fsf@suse.cz>

Hi Martin,

Martin Jambor <mjambor@suse.cz> writes:

> Then the post-hook is executed, which in your case I presume runs afew
> somehow, and typically that hook goes over all messages with the tag
> new, process them in an arbitrary way, sometimes adding further tags
> according to the contents, and eventually drops the new tag.
>
> I guess a potential problem is that notmuch sees the message the first
> time when you send it and it adds the new tag and post-hook processes
> the outgoing version.  When it arrives back, I believe notmuch does not
> apply the new tag to it anymore.  This means that post-hook does not get
> to process the incoming version, which might be a problem if you want to
> see stuff added by a remote party, for example when you want to grep the
> file and look for Sender header in order to mark it as coming from a
> particular mailing list.

Thanks for your clarification, this is indeed what I meant when I said
that what happens is dependent on the order in which notmuch encounters
the message files / copies possessing the same messageID.

Rereading the afew documentation (not very clear) it hints at this
point:

   "SentMailFilter"

   It can be used for example to easily tag posts sent to mailing lists
   which at this stage don’t have List-Id field.

without making it explicit, unfortunately, that if you choose not to use
this, messages you send to the mailing list won't be tagged in the same
way as those received from others through the mailing list.

> Perhaps it would be a good idea to split the tags entry in [new] section
> into two, one for tags added to each previously unknown message-id
> (default would be unread and inbox) and a new one for each new file
> (default new)?

If I understand you correctly, you're suggesting that newly-detected
files always have their messageIDs tagged as "new" even if that
messageID has already been "seen"?  Maybe that solves my case here, I
guess it would depend on how the message files are fed from notmuch to
afew.

JT

  reply	other threads:[~2018-10-11 12:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-09 15:02 tell me how to do this right (mail sent to lists) Jeff Templon
2018-10-09 16:08 ` Daniel Kahn Gillmor
2018-10-09 20:53   ` Jeff Templon
2018-10-09 22:02     ` Carl Worth
2018-10-10  7:16       ` Jeff Templon
2018-10-10 19:03         ` David Bremner
2018-10-10 21:35           ` Jeff Templon
2018-10-11  0:50             ` David Bremner
2018-10-11  9:22             ` Martin Jambor
2018-10-11 12:13               ` Jeff Templon [this message]
2018-10-12 18:02             ` Carl Worth
2018-10-15 11:02               ` Jeff Templon

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=m2pnwg65qw.fsf@simeto.nikhef.nl \
    --to=templon@nikhef.nl \
    --cc=cworth@cworth.org \
    --cc=david@tethera.net \
    --cc=dkg@fifthhorseman.net \
    --cc=mjambor@suse.cz \
    --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).