## How do I search for the `List-Id:` header?
-Currently there is no way to search for `List-Id:`. As a workaround, try using a
-`to:` prefix search (which covers both `To:` and `Cc:` headers) on the mailing
-list address.
-
-Limitations in the duplicate message handling are the main reason for not
-indexing the `List-Id:` header. If you receive the same message via both the
-list and directly (by way of `To:` or `Cc:`), only the first message encountered
-will be indexed. Only the message received via the list will have `List-Id:`,
-but you would expect a `List-Id:` search to find the message, regardless of the
-order in which the duplicates were received. This is a more general problem than
-just `List-Id:`, and once this has been resolved, adding `List-Id:` indexing is
-trivial.
+See `index.header.<prefix>` in `notmuch-config(1)` for details. TLD;R:
+
+ notmuch config set index.header.List List-Id
## Can I use notmuch with grsec?
See [notmuch-extract-patch](https://github.com/aaptel/notmuch-extract-patch).
+## T150-tagging.sh is failing with Xapian 1.4.6
+
+This is (probably) a bug in this point release of Xapian, should be
+fixed in 1.4.7. Try reverting Xapian commit
+`093999529acc2f86900d91fed0c7f7af301ab94a`, e.g. with the following
+patch.
+
+
+ index 80e578b85..a47f14a68 100644
+ --- a/xapian-core/backends/glass/glass_postlist.cc
+ +++ b/xapian-core/backends/glass/glass_postlist.cc
+ @@ -759,7 +759,7 @@ GlassPostList::open_nearby_postlist(const std::string & term_,
+ (void)need_pos;
+ if (term_.empty())
+ RETURN(NULL);
+ - if (!this_db.get() || this_db->postlist_table.is_modified())
+ + if (!this_db.get() || this_db->postlist_table.is_writable())
+ RETURN(NULL);
+ RETURN(new GlassPostList(this_db, term_, cursor->clone()));
+ }
+