unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Guyzmo <guyzmo+notmuch@m0g.net>
To: Harlan Lieberman-Berg <hlieberman@setec.io>
Cc: notmuch@notmuchmail.org
Subject: Re: Proposal: List-Id
Date: Mon, 16 Mar 2015 12:18:30 +0100	[thread overview]
Message-ID: <20150316111830.GJ27498@vilya.online.net> (raw)
In-Reply-To: <87wq2huan3.fsf@setec.io>

Hi Harlan,

On Sun, Mar 15, 2015 at 07:02:56PM -0400, Harlan Lieberman-Berg wrote:
> One of my (few) problems right now with notmuch is around mailing lists
> that are copied, either as CC or BCC, on various emails that go around.
> My filtering inside notmuch right now doesn't catch all the messages,
> since the only tag I can match on is "to:foo@bar.org" and not all
> messages have the to rewritten.

I'm not sure to correctly understand your issue. You're talking about
looking up all mails that are of a given mailing list?

Then I'm not sure it needs notmuch to be patched, as this can be added
pretty easily using an incoming mail filter. I'm personally using
procmail, so it'd be one such as:

    :0:notmuch.lock
    * ^List-[Ii][dD]:.*
    {
    TAGS="${TAGS} +ml -inbox"
    }

To have the inbox tag removed and the ml tag added.

Then I tend to use the right hand side of the `+` on incoming mail, so
that I can choose a unique tag for my mail filtering upon subscription
to the mailing list:

    :0:notmuch.lock
    * ^TO\/guyzmo\+[a-z0-9]+@m0g\.net
    * MATCH ?? ^guyzmo\+\/[a-z0-9]+
    {
    TAGS="+${MATCH}"
    }

As an example, just look my From header here ;-)

> The standard for identifying mailing lists seems to be List-Id, as per
> RFC 2919.  I can understand the desire to keep the number of headers
> included in the header block low, but I wonder if this might be a common
> enough use-case to suggest its inclusion.
> As a counter-argument, I can see the parallel to spam filtering which
> come with their own set of headers that are not special cased by
> notmuch, but there seems to be much more variety in headers there - as
> well as different user configurations.

One issue I can see for indexing `List-Id` is that even though there's
an RFC for that, the value given can be either a `name <mail>`, a
`mail` or a `name` field. There's no real rule and the content can
sometimes be quite unreliable when it comes to index search.

I believe that this discussion has happened in the past, and IIRC, the
output that it was not to be integrated.

HTH,

-- 
Guyzmo

  reply	other threads:[~2015-03-16 11:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-15 23:02 Proposal: List-Id Harlan Lieberman-Berg
2015-03-16 11:18 ` Guyzmo [this message]
2015-03-16 11:35 ` David Bremner
2015-03-16 15:28 ` Amadeusz Żołnowski
2015-03-16 17:03   ` guyzmo

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=20150316111830.GJ27498@vilya.online.net \
    --to=guyzmo+notmuch@m0g.net \
    --cc=hlieberman@setec.io \
    --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).