-* <span id="receive_mail">**Receive mail**</span>
-
- Notmuch requires either [maildir
- flag](http://cr.yp.to/proto/maildir.html) or a "mh"-style
- maildirectory to operate on. Basically any setup in which each mail
- is in a file of its own will work. Here are some generally
- well-regarded mail retrieval tools:
-
- * [offlineimap](https://github.com/nicolas33/offlineimap/) -
- quite useful and widely tested, it also offers a handy hook that
- will come in useful a bit later in our setup. Also supports
- "presynchook" and "postsynchook" command that will get run
- whenever you sync. Point _postsynchook_ to a script that gets run
- on every sync and that will do the automatic updating and tagging
- of your notmuch database.
-
- * [mbsync](http://isync.sourceforge.net/)
-
- * [getmail](http://pyropus.ca/software/getmail/)
-
- * [fetchmail](http://fetchmail.berlios.de/)
-
- See the [[initial_tagging]] page for more info on initial tagging of messages.
-
-* <span id="python">**Use notmuch from python**</span>
-
- Notmuch includes python bindings to the notmuch shared
- library. Extensive API documentation [is
- available](http://notmuchmail.readthedocs.org/).
-
- The bindings are very simple to use. As an example, given you have
- the python bindings installed (or simply set your PYTHONPATH
- environment variable to point to the .../bindings/python directory),
- this snippet will produce a list of mails matching the given
- expression:
-
- >>> import notmuch
- >>> db = notmuch.Database()
- >>> query = db.create_query('tag:inbox AND NOT tag:killed')
- >>> list(query.search_messages()) # doctest:+ELLIPSIS
- [...]
-
-* <span id="sync_maildir_flags">**Sync notmuch tags and maildir flags**</span>
-
- notmuch **since version 0.5** syncs maildir flags and respective
- tags in both directions. This part applies only to notmuch prior to
- version 0.5:
-
- Some IMAP users rely on maildir flags that convey the status "seen",
- "replied", "trashed", in order to synchronize the status of their
- mail across mail clients (a [maildir
- flag](http://cr.yp.to/proto/maildir.html) is simply a defined part
- of their filename). Notmuch will by default happily ignore those
- flags and will never modify them either, as there is no built-in
- support for synchronizing your notmuch tags with your imap maildir
- flags (seen, replied, trashed, etc). However there are currently 2
- ways in which you can achieve synchronization.
-
- [notmuchsync](http://spaetz.github.com/notmuchsync/) is a utility
- (based on the cnotmuch python bindings) that allows synchronization
- in either direction, as well as pruning of deleted files.
-
- The second solution allows for fast maildir flag to notmuch tag
- synchronization (and only in that direction) requires patching the
- notmuch source code. The patch has been posted in this mail
- *id:1267450136-31749-1-git-send-email-Sebastian@SSpaeth.de* and can
- be viewed as a [source diff in this git
- repository](http://github.com/spaetz/notmuch-all-feature/commit/df3b087cefb85e9d16fd17540e348bcb854dd7ee).
-
-* <span id="print_filenames">**Using notmuch with Mutt**</span>
-
- Notmuch is a great mail indexing tool that can also be used *in conjunction*
- with existing Mail User Agents (MUA) instead of replacing them. The advantage
- of such mixed solutions is that users can benefit from notmuch features (such
- as full-text search and thread reconstruction) without *having to* change
- MUA.
-
- A popular geek MUA is [the Mutt e-mail client](http://www.mutt.org);
- integrating notmuch with Mutt is fairly straightforward. An
+[[!toc levels=2]]
+
+## <span id="debian_packages">**Debian squeeze packages outdated**</span>
+
+The notmuch package(s) in Debian squeeze are very old (version 0.3).
+It's better to start off with an up to date version from
+[backports](http://backports-master.debian.org/).
+
+## <span id="receive_mail">**Receive mail**</span>
+
+Notmuch does not fetch mail for you. For that, you need to use an
+external mail syncing utility. Some recommended utilities are listed
+below.
+
+Notmuch requires that every individual message be in it's own file.
+The well-supported [maildir](http://cr.yp.to/proto/maildir.html) or
+"mh"-style storage formats are compatible with notmuch. Basically any
+setup in which each mail is in a file of its own will work. The older
+mbox mail store formats is not supported, but fortunately it is very
+easy to [[convert mbox to maildir|howto/#mbox]] . The following
+utilities support these formats:
+
+* [offlineimap](http://offlineimap.org/) -
+ quite useful and widely tested, it also offers a handy hook that
+ will come in useful a bit later in our setup. Also supports
+ "presynchook" and "postsynchook" command that will get run
+ whenever you sync. Point _postsynchook_ to a script that gets run
+ on every sync and that will do the automatic updating and tagging
+ of your notmuch database.
+
+* [mbsync](http://isync.sourceforge.net/)
+
+* [getmail](http://pyropus.ca/software/getmail/)
+
+* [fetchmail](http://fetchmail.berlios.de/)
+
+See the [[initial_tagging]] page for more info on initial tagging of
+messages.
+
+## <span id="sync_maildir_flags">**Sync notmuch tags and maildir flags**</span>
+
+notmuch has the ability to synchronize maildir flags and respective tags in both
+directions. For more information on maildir flags see the [maildir
+page](http://cr.yp.to/proto/maildir.html), and for the respective tags see your
+notmuch configuration file. This feature is enabled by default, but if you don't
+need it, it is simple to disable it with the 'notmuch config' command:
+
+ $ notmuch config set maildir.synchronize_flags false
+
+The maildir flags may, in turn, be synchronized with IMAP flags by another tool,
+such as offlineimap.
+
+For safety reasons, and because
+[[notmuch does not support delete operations|deleting]], notmuch does
+not sync the "trashed" flag. For discussion on this topic please
+refer to the mailing list.
+
+## <span id="python">**Use notmuch from python**</span>
+
+Notmuch includes python bindings to the notmuch shared library. Please
+refer to the nice and extensive
+[notmuch python API documentation](http://notmuch.readthedocs.org/).
+
+The bindings are very simple to use. As an example, given you have
+the python bindings installed (or simply set your PYTHONPATH
+environment variable to point to the .../bindings/python directory),
+this snippet will produce a list of mails matching the given
+expression:
+
+ >>> import notmuch
+ >>> db = notmuch.Database()
+ >>> query = db.create_query('tag:inbox AND NOT tag:killed')
+ >>> list(query.search_messages()) # doctest:+ELLIPSIS
+ [...]
+
+## <span id="print_filenames">**Using notmuch with Mutt**</span>
+
+Notmuch is a great mail indexing tool that can also be used *in conjunction*
+with existing Mail User Agents (MUA) instead of replacing them. The advantage
+of such mixed solutions is that users can benefit from notmuch features (such
+as full-text search and thread reconstruction) without *having to* change
+MUA.
+
+A popular geek MUA is [the Mutt e-mail client](http://www.mutt.org);
+integrating notmuch with Mutt is not seamless, but fairly straightforward.
+There are two principal possibilities, each with its own ups and downs:
+
+* Using mutt-notmuch, which will create a "virtual" maildir folder with
+ search results whenever a search is made. The upside is that you can
+ search all your folders simultanously; the downside is that your
+ modifications in the results listing do not carry over, also having
+ to switch folders comes with some more annoyances.
+
+ An