Re: Proposal: List-Id

diff --git a/f9/cd592bfaa2df6a852f15892be809298fe2ecf3 b/f9/cd592bfaa2df6a852f15892be809298fe2ecf3
new file mode 100644 (file)
index 0000000..6f20a53
--- /dev/null
+++ b/f9/cd592bfaa2df6a852f15892be809298fe2ecf3
@@ -0,0 +1,112 @@
+Return-Path: <guyzmo@vilya.m0g.net>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+       by olra.theworths.org (Postfix) with ESMTP id 828E5431FCF\r
+       for <notmuch@notmuchmail.org>; Mon, 16 Mar 2015 04:18:41 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: 2.438\r
+X-Spam-Level: **\r
+X-Spam-Status: No, score=2.438 tagged_above=-999 required=5\r
+       tests=[DNS_FROM_AHBL_RHSBL=2.438] autolearn=disabled\r
+Received: from olra.theworths.org ([127.0.0.1])\r
+       by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
+       with ESMTP id Asu2Ef-Fzonn for <notmuch@notmuchmail.org>;\r
+       Mon, 16 Mar 2015 04:18:38 -0700 (PDT)\r
+Received: from mail.m0g.net (vilya.m0g.net [195.154.74.47])\r
+       by olra.theworths.org (Postfix) with ESMTP id 3E2A5431FB6\r
+       for <notmuch@notmuchmail.org>; Mon, 16 Mar 2015 04:18:38 -0700 (PDT)\r
+Received: from localhost (localhost [127.0.0.1])\r
+       by mail.m0g.net (Postfix) with ESMTP id DF2403E536C;\r
+       Mon, 16 Mar 2015 12:18:35 +0100 (CET)\r
+X-Virus-Scanned: Debian amavisd-new at vilya.m0g.net\r
+Received: from mail.m0g.net ([127.0.0.1])\r
+       by localhost (sd-38500.dedibox.fr [127.0.0.1]) (amavisd-new, port 10024)\r
+       with ESMTP id QYccPse6qP7j; Mon, 16 Mar 2015 12:18:34 +0100 (CET)\r
+Received: by mail.m0g.net (Postfix, from userid 1000)\r
+       id 0CB543E536E; Mon, 16 Mar 2015 12:18:33 +0100 (CET)\r
+Date: Mon, 16 Mar 2015 12:18:30 +0100\r
+From: Guyzmo <guyzmo+notmuch@m0g.net>\r
+To: Harlan Lieberman-Berg <hlieberman@setec.io>\r
+Subject: Re: Proposal: List-Id\r
+Message-ID: <20150316111830.GJ27498@vilya.online.net>\r
+References: <87wq2huan3.fsf@setec.io>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain; charset=us-ascii\r
+Content-Disposition: inline\r
+In-Reply-To: <87wq2huan3.fsf@setec.io>\r
+User-Agent: Mutt/1.5.23.1-rc1 (2014-03-12)\r
+Cc: notmuch@notmuchmail.org\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.13\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+       <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
+List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
+List-Post: <mailto:notmuch@notmuchmail.org>\r
+List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
+List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Mon, 16 Mar 2015 11:18:41 -0000\r
+\r
+Hi Harlan,\r
+\r
+On Sun, Mar 15, 2015 at 07:02:56PM -0400, Harlan Lieberman-Berg wrote:\r
+> One of my (few) problems right now with notmuch is around mailing lists\r
+> that are copied, either as CC or BCC, on various emails that go around.\r
+> My filtering inside notmuch right now doesn't catch all the messages,\r
+> since the only tag I can match on is "to:foo@bar.org" and not all\r
+> messages have the to rewritten.\r
+\r
+I'm not sure to correctly understand your issue. You're talking about\r
+looking up all mails that are of a given mailing list?\r
+\r
+Then I'm not sure it needs notmuch to be patched, as this can be added\r
+pretty easily using an incoming mail filter. I'm personally using\r
+procmail, so it'd be one such as:\r
+\r
+    :0:notmuch.lock\r
+    * ^List-[Ii][dD]:.*\r
+    {\r
+    TAGS="${TAGS} +ml -inbox"\r
+    }\r
+\r
+To have the inbox tag removed and the ml tag added.\r
+\r
+Then I tend to use the right hand side of the `+` on incoming mail, so\r
+that I can choose a unique tag for my mail filtering upon subscription\r
+to the mailing list:\r
+\r
+    :0:notmuch.lock\r
+    * ^TO\/guyzmo\+[a-z0-9]+@m0g\.net\r
+    * MATCH ?? ^guyzmo\+\/[a-z0-9]+\r
+    {\r
+    TAGS="+${MATCH}"\r
+    }\r
+\r
+As an example, just look my From header here ;-)\r
+\r
+> The standard for identifying mailing lists seems to be List-Id, as per\r
+> RFC 2919.  I can understand the desire to keep the number of headers\r
+> included in the header block low, but I wonder if this might be a common\r
+> enough use-case to suggest its inclusion.\r
+> As a counter-argument, I can see the parallel to spam filtering which\r
+> come with their own set of headers that are not special cased by\r
+> notmuch, but there seems to be much more variety in headers there - as\r
+> well as different user configurations.\r
+\r
+One issue I can see for indexing `List-Id` is that even though there's\r
+an RFC for that, the value given can be either a `name <mail>`, a\r
+`mail` or a `name` field. There's no real rule and the content can\r
+sometimes be quite unreliable when it comes to index search.\r
+\r
+I believe that this discussion has happened in the past, and IIRC, the\r
+output that it was not to be integrated.\r
+\r
+HTH,\r
+\r
+-- \r
+Guyzmo\r