From: David Bremner <david@tethera.net>
To: Harlan Lieberman-Berg <hlieberman@setec.io>, notmuch@notmuchmail.org
Subject: Re: Proposal: List-Id
Date: Mon, 16 Mar 2015 12:35:35 +0100 [thread overview]
Message-ID: <878uex2n08.fsf@maritornes.cs.unb.ca> (raw)
In-Reply-To: <87wq2huan3.fsf@setec.io>
Harlan Lieberman-Berg <hlieberman@setec.io> writes:
>
> 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.
>
I think the real blocker at this point is that some copies of a message
may have list-id header and some not. Currently we only index the first
copy of a message that arrives. Indexing all copies would probably be a
good step in any case, but e.g. handling deletion of files requires some
care in that case.
d
next prev parent reply other threads:[~2015-03-16 11:36 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
2015-03-16 11:35 ` David Bremner [this message]
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=878uex2n08.fsf@maritornes.cs.unb.ca \
--to=david@tethera.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).