2014-01-28 17:12:37 +01:00
|
|
|
===========
|
|
|
|
|
notmuch-new
|
|
|
|
|
===========
|
|
|
|
|
|
|
|
|
|
SYNOPSIS
|
|
|
|
|
========
|
|
|
|
|
|
2014-04-19 07:29:06 +02:00
|
|
|
**notmuch** **new** [options]
|
2014-01-28 17:12:37 +01:00
|
|
|
|
|
|
|
|
DESCRIPTION
|
|
|
|
|
===========
|
|
|
|
|
|
|
|
|
|
Find and import any new messages to the database.
|
|
|
|
|
|
|
|
|
|
The **new** command scans all sub-directories of the database,
|
|
|
|
|
performing full-text indexing on new messages that are found. Each new
|
|
|
|
|
message will automatically be tagged with both the **inbox** and
|
|
|
|
|
**unread** tags.
|
|
|
|
|
|
|
|
|
|
You should run **notmuch new** once after first running **notmuch
|
|
|
|
|
setup** to create the initial database. The first run may take a long
|
|
|
|
|
time if you have a significant amount of mail (several hundred thousand
|
|
|
|
|
messages or more). Subsequently, you should run **notmuch new** whenever
|
|
|
|
|
new mail is delivered and you wish to incorporate it into the database.
|
|
|
|
|
These subsequent runs will be much quicker than the initial run.
|
|
|
|
|
|
|
|
|
|
Invoking ``notmuch`` with no command argument will run **new** if
|
|
|
|
|
**notmuch setup** has previously been completed, but **notmuch new** has
|
|
|
|
|
not previously been run.
|
|
|
|
|
|
|
|
|
|
**notmuch new** updates tags according to maildir flag changes if the
|
|
|
|
|
**maildir.synchronize\_flags** configuration option is enabled. See
|
|
|
|
|
**notmuch-config(1)** for details.
|
|
|
|
|
|
|
|
|
|
The **new** command supports hooks. See **notmuch-hooks(5)** for more
|
|
|
|
|
details on hooks.
|
|
|
|
|
|
|
|
|
|
Supported options for **new** include
|
|
|
|
|
|
|
|
|
|
``--no-hooks``
|
|
|
|
|
Prevents hooks from being run.
|
|
|
|
|
|
|
|
|
|
``--quiet``
|
|
|
|
|
Do not print progress or results.
|
|
|
|
|
|
2017-10-21 04:25:46 +02:00
|
|
|
``--try-decrypt=(true|false)``
|
|
|
|
|
|
|
|
|
|
If true, when encountering an encrypted message, try to
|
|
|
|
|
decrypt it while indexing. If decryption is successful, index
|
|
|
|
|
the cleartext itself. Be aware that the index is likely
|
|
|
|
|
sufficient to reconstruct the cleartext of the message itself,
|
|
|
|
|
so please ensure that the notmuch message index is adequately
|
|
|
|
|
protected. DO NOT USE ``--try-decrypt=true`` without
|
|
|
|
|
considering the security of your index.
|
|
|
|
|
|
|
|
|
|
See also ``index.try_decrypt`` in **notmuch-config(1)**.
|
|
|
|
|
|
2016-11-26 03:40:37 +01:00
|
|
|
EXIT STATUS
|
|
|
|
|
===========
|
|
|
|
|
|
|
|
|
|
This command supports the following special exit status code
|
|
|
|
|
|
|
|
|
|
``75 (EX_TEMPFAIL)``
|
2017-07-18 00:16:02 +02:00
|
|
|
A temporary failure occurred; the user is invited to retry.
|
2016-11-26 03:40:37 +01:00
|
|
|
|
2014-01-28 17:12:37 +01:00
|
|
|
SEE ALSO
|
|
|
|
|
========
|
|
|
|
|
|
2017-10-17 18:57:21 +02:00
|
|
|
**notmuch(1)**,
|
|
|
|
|
**notmuch-config(1)**,
|
|
|
|
|
**notmuch-count(1)**,
|
|
|
|
|
**notmuch-dump(1)**,
|
|
|
|
|
**notmuch-hooks(5)**,
|
|
|
|
|
**notmuch-insert(1)**,
|
|
|
|
|
**notmuch-reply(1)**,
|
|
|
|
|
**notmuch-restore(1)**,
|
|
|
|
|
**notmuch-search(1)**,
|
|
|
|
|
**notmuch-search-terms(7)**,
|
|
|
|
|
**notmuch-show(1)**,
|
|
|
|
|
**notmuch-tag(1)**
|
