+ Some people are crazy enough to archive e.g. their Spam in their
+ Maildir and perhaps they'd prefer not having them indexed on notmuch.
+
+ Having a configuration option to exclude or include certain subparts of
+ the user's Maildir would be a very nice feature to have.
+
++ Index more headers. Some desired headers:
+
+ + Received: allows for searches based on the arrival path
+ + Reply-To: allows for searches based on the return address
+
++ Allow anchors in searches
+
+ `notmuch search from:domain.org$` only matches if "domain.org" is
+ at the end of the From: header
+
+ `notmuch search from:^username` only matches if "username" is at
+ the beginning of the From: header (right after the ':')
+
+ This leaves the interesting question if we want a way to bind to
+ the actual address component.
+
++ Add folder tags to mail automatically
+
+ Add the name of the IMAP folder as the tag for mails. This way,
+ server-side filtering can be directly used by notmuch to tag all
+ incoming mail.
+
++ Make message store code modular
+
+ Notmuch is built on the assumption that the message store is a
+ collection of message files in directories (roughly Maildir
+ format). This performs suboptimally for a wide range of systems,
+ especially with large numbers of messages. Modularising the
+ message store code to move this assumption into the implementation
+ rather than the interface would allow adding support for different
+ message stores like the traditional [mbox
+ formats](http://homepage.ntlworld.com./jonathan.deboynepollard/FGA/mail-mbox-formats.html)
+ as well as more experimental approaches like using git as an object
+ storage (similar to how [[nmbug]] operates).
+
++ Put content of all non-multipart content-types in results of `notmuch show --format=json ...`
+
+ In the JSON-format output of the `show` command, only text/plain
+ parts' content is included. Including the content of parts having any
+ non-multipart content-type would assist with those who wished to access
+ their mail through notmuch's `show` command (because of having written
+ their MUA in a language with no library bindings or access to them
+ [e.g. Perl, Lua or shell]) and also had a mailcap or similar MIME-type
+ mapping system with which to actually view HTML files, images and the like.
+
+## 3rd party apps