| 1 | # .notmuch-config - Configuration file for the notmuch mail system |
| 2 | # |
| 3 | # For more information about notmuch, see https://notmuchmail.org |
| 4 | |
| 5 | # Database configuration |
| 6 | # |
| 7 | # The only value supported here is 'path' which should be the top-level |
| 8 | # directory where your mail currently exists and to where mail will be |
| 9 | # delivered in the future. Files should be individual email messages. |
| 10 | # Notmuch will store its database within a sub-directory of the path |
| 11 | # configured here named ".notmuch". |
| 12 | # |
| 13 | [database] |
| 14 | path=/home/amin/mail |
| 15 | |
| 16 | # User configuration |
| 17 | # |
| 18 | # Here is where you can let notmuch know how you would like to be |
| 19 | # addressed. Valid settings are |
| 20 | # |
| 21 | # name Your full name. |
| 22 | # primary_email Your primary email address. |
| 23 | # other_email A list (separated by ';') of other email addresses |
| 24 | # at which you receive email. |
| 25 | # |
| 26 | # Notmuch will use the various email addresses configured here when |
| 27 | # formatting replies. It will avoid including your own addresses in the |
| 28 | # recipient list of replies, and will set the From address based on the |
| 29 | # address to which the original email was addressed. |
| 30 | # |
| 31 | [user] |
| 32 | name=Amin Bandali |
| 33 | primary_email=amin@aminb.org |
| 34 | other_email=amin.bandali@uwaterloo.ca;mbandali@uwaterloo.ca;aminb@gnu.org; |
| 35 | |
| 36 | # Configuration for "notmuch new" |
| 37 | # |
| 38 | # The following options are supported here: |
| 39 | # |
| 40 | # tags A list (separated by ';') of the tags that will be |
| 41 | # added to all messages incorporated by "notmuch new". |
| 42 | # |
| 43 | # ignore A list (separated by ';') of file and directory names |
| 44 | # that will not be searched for messages by "notmuch new". |
| 45 | # |
| 46 | # NOTE: *Every* file/directory that goes by one of those |
| 47 | # names will be ignored, independent of its depth/location |
| 48 | # in the mail store. |
| 49 | # |
| 50 | [new] |
| 51 | tags=new; |
| 52 | #tags=unread;inbox; |
| 53 | ignore=.uidvalidity;.mbsyncstate |
| 54 | |
| 55 | # Search configuration |
| 56 | # |
| 57 | # The following option is supported here: |
| 58 | # |
| 59 | # exclude_tags |
| 60 | # A ;-separated list of tags that will be excluded from |
| 61 | # search results by default. Using an excluded tag in a |
| 62 | # query will override that exclusion. |
| 63 | # |
| 64 | [search] |
| 65 | exclude_tags=deleted;spam; |
| 66 | |
| 67 | # Maildir compatibility configuration |
| 68 | # |
| 69 | # The following option is supported here: |
| 70 | # |
| 71 | # synchronize_flags Valid values are true and false. |
| 72 | # |
| 73 | # If true, then the following maildir flags (in message filenames) |
| 74 | # will be synchronized with the corresponding notmuch tags: |
| 75 | # |
| 76 | # Flag Tag |
| 77 | # ---- ------- |
| 78 | # D draft |
| 79 | # F flagged |
| 80 | # P passed |
| 81 | # R replied |
| 82 | # S unread (added when 'S' flag is not present) |
| 83 | # |
| 84 | # The "notmuch new" command will notice flag changes in filenames |
| 85 | # and update tags, while the "notmuch tag" and "notmuch restore" |
| 86 | # commands will notice tag changes and update flags in filenames |
| 87 | # |
| 88 | [maildir] |
| 89 | synchronize_flags=true |
| 90 | |
| 91 | # Cryptography related configuration |
| 92 | # |
| 93 | # The following option is supported here: |
| 94 | # |
| 95 | # gpg_path |
| 96 | # binary name or full path to invoke gpg. |
| 97 | # |
| 98 | [crypto] |
| 99 | gpg_path=gpg |