git add release-0.23.mdwn

[notmuch-wiki] / faq.mdwn

diff --git a/faq.mdwn b/faq.mdwn
index 1cc224e8ed5d3c1602366c0a8e2a80a8db4f80a8..36a7669c44bc093726668b379a96bb0bbbd10725 100644 (file)
--- a/faq.mdwn
+++ b/faq.mdwn
@@ -45,7 +45,7 @@ Next, use that to query the messages:
 ## How do I search for punctuation, specific special characters, or regexp?
 
 Please see the [[notmuch-search-terms manual
-page|manpages/notmuch-search-terms-7]] first,
+page|manpages/notmuch-search-terms-7]] first.
 
 The main thing to understand is that Xapian, and therefore Notmuch, searches are
 closer to natural language searches than regular expression
@@ -53,3 +53,25 @@ searches. Punctuation is mostly ignored.
 
 The boolean prefix searches (see Boolean and Probabilistic Prefixes in the man
 page), such as tag: or path: searches, need an exact match.
+
+## 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.
+
+## Can I use notmuch with grsec?
+
+Sure! It works out of the box. If you have TPE enabled (trusted path execution),
+make sure the user is executing the script belongs to the
+`kernel.grsecurity.tpe_gid` (in debian this is grsec-tpe).
+This is required in order to run the `pre-new` and `post-new` hooks.