+ <b>sup</b> The <b>sup</b> dump file format is specifically chosen to be
+ compatible with the format of files produced by
+ sup-dump. So if you've previously been using sup for
+ mail, then the <b>notmuch</b> <b>restore</b> command provides you a
+ way to import all of your tags (or labels as sup calls
+ them).
+
+ <b>batch-tag</b>
+ The <b>batch-tag</b> dump format is intended to more robust
+ against malformed message-ids and tags containing
+ whitespace or non-<b>ascii</b>(7) characters. See <a href='../notmuch-dump-1/'>not‐</a>
+ <a href='../notmuch-dump-1/'>much-dump</a>(1) for details on this format.
+
+ <b>notmuch</b> <b>restore</b> updates the maildir flags according to
+ tag changes if the <b>maildir.synchronize</b>_<b>flags</b> configu‐
+ ration option is enabled. See <a href='../notmuch-config-1/'>notmuch-config</a>(1) for
+ details.
+
+ <b>auto</b> This option (the default) tries to guess the format
+ from the input. For correctly formed input in either
+ supported format, this heuristic, based the fact that
+ batch-tag format contains no parentheses, should be
+ accurate.
+
+ <b>--include=(config|tags)</b>
+ Control what kind of metadata is restored.
+ <b>config</b>
+ Restore configuration data to the database. Each configu‐
+ ration line starts with "#@ ", followed by a space seper‐
+ ated key-value pair. Both key and value are hex encoded
+ if needed.
+
+ <b>tags</b>
+ Output per-message metadata, namely tags. See <u>format</u>
+ above for more details.
+
+ The default is to restore both tags and configuration informa‐
+ tion
+
+ <b>--input=<filename></b>
+ Read input from given file instead of stdin.
+</pre>
+
+<h2>GZIPPED INPUT</h2>
+<pre>
+ <b>notmuch</b> <b>restore</b> will detect if the input is compressed in <b>gzip</b>(1) for‐
+ mat and automatically decompress it while reading. This detection does
+ not depend on file naming and in particular works for standard input.