diff options
| author | Jani Nikula <jani@nikula.org> | 2016-09-27 13:11:37 +0300 |
|---|---|---|
| committer | Jani Nikula <jani@nikula.org> | 2016-09-27 13:11:37 +0300 |
| commit | a366fdfc129df3c1dd54150145559d1a621632dc (patch) | |
| tree | 5924878229a79b15a63ccf10ea53cf0c98ef20d1 | |
| parent | 58425548f54e38f06b7cc6bc8083bc20009c8472 (diff) | |
faq: how do I search for the list-id: header
| -rw-r--r-- | faq.mdwn | 15 |
1 files changed, 15 insertions, 0 deletions
@@ -53,3 +53,18 @@ 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. |