- indicate user-supplied values):
-
- · from:<name-or-address>
-
- · to:<name-or-address>
-
- · subject:<word-or-quoted-phrase>
-
- · attachment:<word>
-
- · mimetype:<word>
-
- · tag:<tag> (or is:<tag>)
-
- · id:<message-id>
-
- · thread:<thread-id>
-
- · folder:<maildir-folder>
-
- · path:<directory-path> or path:<directory-path>/**
-
- · date:<since>..<until>
-
- · lastmod:<initial-revision>..<final-revision>
-
- · query:<name>
-
- The <b>from:</b> prefix is used to match the name or address of the sender of
- an email message.
-
- The <b>to:</b> prefix is used to match the names or addresses of any recipient
- of an email message, (whether To, Cc, or Bcc).
-
- Any term prefixed with <b>subject:</b> will match only text from the subject
- of an email. Searching for a phrase in the subject is supported by
- including quotation marks around the phrase, immediately following <b>sub-</b>
- <b>ject:</b>.
-
- The <b>attachment:</b> prefix can be used to search for specific filenames (or
- extensions) of attachments to email messages.
-
- The <b>mimetype:</b> prefix will be used to match text from the content-types
- of MIME parts within email messages (as specified by the sender).
-
- For <b>tag:</b> and <b>is:</b> valid tag values include <b>inbox</b> and <b>unread</b> by default
- for new messages added by <b>notmuch</b> <b>new</b> as well as any other tag values
- added manually with <b>notmuch</b> <b>tag</b>.
-
- For <b>id:</b>, message ID values are the literal contents of the Message-ID:
- header of email messages, but without the '<', '>' delimiters.
-
- The <b>thread:</b> prefix can be used with the thread ID values that are gen‐
- erated internally by notmuch (and do not appear in email messages).
- These thread ID values can be seen in the first column of output from
- <b>notmuch</b> <b>search</b>
-
- The <b>path:</b> prefix searches for email messages that are in particular
- directories within the mail store. The directory must be specified rel‐
- ative to the top-level maildir (and without the leading slash). By
- default, <b>path:</b> matches messages in the specified directory only. The
- "/**" suffix can be used to match messages in the specified directory
- and all its subdirectories recursively. <b>path:""</b> matches messages in
- the root of the mail store and, likewise, <b>path:**</b> matches all messages.
-
- The <b>folder:</b> prefix searches for email messages by maildir or MH folder.
- For MH-style folders, this is equivalent to <b>path:</b>. For maildir, this
- includes messages in the "new" and "cur" subdirectories. The exact syn‐
- tax for maildir folders depends on your mail configuration. For
- maildir++, <b>folder:""</b> matches the inbox folder (which is the root in
- maildir++), other folder names always start with ".", and nested fold‐
- ers are separated by "."s, such as <b>folder:.classes.topology</b>. For "file
- system" maildir, the inbox is typically <b>folder:INBOX</b> and nested folders
- are separated by slashes, such as <b>folder:classes/topology</b>.
-
- Both <b>path:</b> and <b>folder:</b> will find a message if <u>any</u> copy of that message
- is in the specific directory/folder.
-
- The <b>date:</b> prefix can be used to restrict the results to only messages
- within a particular time range (based on the Date: header) with a range
- syntax of:
-
- date:<since>..<until>
-
- See <b>DATE</b> <b>AND</b> <b>TIME</b> <b>SEARCH</b> below for details on the range expression, and
- supported syntax for <since> and <until> date and time expressions.
-
- The time range can also be specified using timestamps with a syntax of:
-
- <initial-timestamp>..<final-timestamp>
-
- Each timestamp is a number representing the number of seconds since
- 1970-01-01 00:00:00 UTC.
-
- The <b>lastmod:</b> prefix can be used to restrict the result by the database
- revision number of when messages were last modified (tags were
- added/removed or filenames changed). This is usually used in conjunc‐
- tion with the <b>--uuid</b> argument to <b>notmuch</b> <b>search</b> to find messages that
- have changed since an earlier query.
-
- The <b>query:</b> prefix allows queries to refer to previously saved queries
- added with <a href='../notmuch-config-1/'>notmuch-config</a>(1). Named queries are only available if not‐
- much is built with <b>Xapian</b> <b>Field</b> <b>Processors</b> (see below).
+ indicate user-supplied values).
+
+ If notmuch is built with <b>Xapian</b> <b>Field</b> <b>Processors</b> (see below) some of
+ the prefixes with <regex> forms can be also used to restrict the
+ results to those whose value matches a regular expression (see
+ <b>regex</b>(7)) delimited with //, for example:
+
+ notmuch search 'from:"/bob@.*[.]example[.]com/"'
+
+ <b>body:<word-or-quoted-phrase></b>
+ Match terms in the body of messages.
+
+ <b>from:<name-or-address></b> <b>or</b> <b>from:/<regex>/</b>
+ The <b>from:</b> prefix is used to match the name or address of the
+ sender of an email message.
+
+ <b>to:<name-or-address></b>
+ The <b>to:</b> prefix is used to match the names or addresses of any
+ recipient of an email message, (whether To, Cc, or Bcc).
+
+ <b>subject:<word-or-quoted-phrase></b> <b>or</b> <b>subject:/<regex>/</b>
+ Any term prefixed with <b>subject:</b> will match only text from the
+ subject of an email. Searching for a phrase in the subject is
+ supported by including quotation marks around the phrase, imme‐
+ diately following <b>subject:</b>.
+
+ <b>attachment:<word></b>
+ The <b>attachment:</b> prefix can be used to search for specific file‐
+ names (or extensions) of attachments to email messages.
+
+ <b>mimetype:<word></b>
+ The <b>mimetype:</b> prefix will be used to match text from the con‐
+ tent-types of MIME parts within email messages (as specified by
+ the sender).
+
+ <b>tag:<tag></b> <b>or</b> <b>tag:/<regex>/</b> <b>or</b> <b>is:<tag></b> <b>or</b> <b>is:/<regex>/</b>
+ For <b>tag:</b> and <b>is:</b> valid tag values include <b>inbox</b> and <b>unread</b> by
+ default for new messages added by <b>notmuch</b> <b>new</b> as well as any
+ other tag values added manually with <b>notmuch</b> <b>tag</b>.
+
+ <b>id:<message-id></b> <b>or</b> <b>mid:<message-id></b> <b>or</b> <b>mid:/<regex>/</b>
+ For <b>id:</b> and <b>mid:</b>, message ID values are the literal contents of
+ the Message-ID: header of email messages, but without the '<',
+ '>' delimiters.
+
+ <b>thread:<thread-id></b>
+ The <b>thread:</b> prefix can be used with the thread ID values that
+ are generated internally by notmuch (and do not appear in email
+ messages). These thread ID values can be seen in the first col‐
+ umn of output from <b>notmuch</b> <b>search</b>
+
+ <b>thread:{<notmuch</b> <b>query>}</b>
+ If notmuch is built with <b>Xapian</b> <b>Field</b> <b>Processors</b> (see below),
+ threads may be searched for indirectly by providing an arbitrary
+ notmuch query in <b>{}</b>. For example, the following returns threads
+ containing a message from mallory and one (not necessarily the
+ same message) with Subject containing the word "crypto".
+
+ % notmuch search 'thread:"{from:mallory}" and thread:"{subject:crypto}"'
+
+ The performance of such queries can vary wildly. To understand
+ this, the user should think of the query <b>thread:{<something>}</b> as
+ expanding to all of the thread IDs which match <b><something></b>; not‐
+ much then performs a second search using the expanded query.
+
+ <b>path:<directory-path></b> <b>or</b> <b>path:<directory-path>/**</b> <b>or</b> <b>path:/<regex>/</b>
+ The <b>path:</b> prefix searches for email messages that are in partic‐
+ ular directories within the mail store. The directory must be
+ specified relative to the top-level maildir (and without the
+ leading slash). By default, <b>path:</b> matches messages in the speci‐
+ fied directory only. The "/**" suffix can be used to match mes‐
+ sages in the specified directory and all its subdirectories
+ recursively. <b>path:""</b> matches messages in the root of the mail
+ store and, likewise, <b>path:**</b> matches all messages.
+
+ <b>path:</b> will find a message if <u>any</u> copy of that message is in the
+ specific directory.
+
+ <b>folder:<maildir-folder></b> <b>or</b> <b>folder:/<regex>/</b>
+ The <b>folder:</b> prefix searches for email messages by maildir or MH
+ folder. For MH-style folders, this is equivalent to <b>path:</b>. For
+ maildir, this includes messages in the "new" and "cur" subdirec‐
+ tories. The exact syntax for maildir folders depends on your
+ mail configuration. For maildir++, <b>folder:""</b> matches the inbox
+ folder (which is the root in maildir++), other folder names
+ always start with ".", and nested folders are separated by "."s,
+ such as <b>folder:.classes.topology</b>. For "file system" maildir, the
+ inbox is typically <b>folder:INBOX</b> and nested folders are separated
+ by slashes, such as <b>folder:classes/topology</b>.
+
+ <b>folder:</b> will find a message if <u>any</u> copy of that message is in
+ the specific folder.
+
+ <b>date:<since>..<until></b> <b>or</b> <b>date:<date></b>
+ The <b>date:</b> prefix can be used to restrict the results to only
+ messages within a particular time range (based on the Date:
+ header).
+
+ See <b>DATE</b> <b>AND</b> <b>TIME</b> <b>SEARCH</b> below for details on the range expres‐
+ sion, and supported syntax for <since> and <until> date and time
+ expressions.
+
+ The time range can also be specified using timestamps without
+ including the date prefix using a syntax of:
+
+ <initial-timestamp>..<final-timestamp>
+
+ Each timestamp is a number representing the number of seconds
+ since 1970-01-01 00:00:00 UTC. Specifying a time range this way
+ is considered legacy and predates the date prefix.
+
+ <b>lastmod:<initial-revision>..<final-revision></b>
+ The <b>lastmod:</b> prefix can be used to restrict the result by the
+ database revision number of when messages were last modified
+ (tags were added/removed or filenames changed). This is usually
+ used in conjunction with the <b>--uuid</b> argument to <b>notmuch</b> <b>search</b>
+ to find messages that have changed since an earlier query.
+
+ <b>query:<name></b>
+ The <b>query:</b> prefix allows queries to refer to previously saved
+ queries added with <a href='../notmuch-config-1/'>notmuch-config</a>(1). Named queries are only
+ available if notmuch is built with <b>Xapian</b> <b>Field</b> <b>Processors</b> (see
+ below).
+
+ <b>property:<key>=<value></b>
+ The <b>property:</b> prefix searches for messages with a particular
+ <key>=<value> property pair. Properties are used internally by
+ notmuch (and extensions) to add metadata to messages. A given
+ key can be present on a given message with several different
+ values. See <a href='../notmuch-properties-7/'>notmuch-properties</a>(7) for more details.
+
+ User defined prefixes are also supported, see <a href='../notmuch-config-1/'>notmuch-config</a>(1) for
+ details.
projects / notmuch-wiki / blobdiff