# Lieer
<img src="https://gauteh.github.io/lieer/demo.png">
This program can pull, and send, email and labels (and changes to labels) from
your GMail account and store them locally in a maildir with the labels
synchronized with a [notmuch](https://notmuchmail.org/) database. The changes
to tags in the notmuch database may be pushed back remotely to your GMail
account.
## Disclaimer
Lieer will not and can not:
* Add or delete messages on your remote account (except syncing the `trash` or `spam` label to messages, and those messages will eventually be [deleted](https://support.google.com/mail/answer/7401?co=GENIE.Platform%3DDesktop&hl=en))
* Modify messages other than their labels
While Lieer has been used to successfully synchronize millions of messages and tags by now, it comes with **NO WARRANTIES**.
## Requirements
* Python 3
* `notmuch >= 0.25` python bindings
* `google_api_python_client` (sometimes `google-api-python-client`)
* `google_auth_oauthlib`
* `tqdm` (optional - for progress bar)
## Installation
After cloning the repository Lieer can be installed through pip by using the command ```pip install .```
# Usage
This assumes your root mail folder is in `~/.mail` and that this folder is _already_ set up with notmuch.
1. Make a directory for the lieer storage and state files (local repository).
```sh
$ cd ~/.mail
$ mkdir account.gmail
$ cd account.gmail/
```
All commands should be run from the local mail repository unless otherwise specified.
2. Ignore the `.json` files in notmuch. Any tags listed in `new.tags` will be added to newly pulled messages. Process tags on new messages directly after running gmi, or run `notmuch new` to trigger the `post-new` hook for [initial tagging](https://notmuchmail.org/initial_tagging/). The `new.tags` are not ignored by default if you do not remove them, but you can prevent custom tags from being pushed to the remote by using e.g. `gmi set --ignore-tags-local new`. In your notmuch config file (usually `~/.notmuch-config`):
```
[new]
tags=new
ignore=/.*[.](json|lock|bak)$/
```
3. Initialize the mail storage:
```sh
$ gmi init your.email@gmail.com
```
`gmi init` will now open your browser and request limited access to your e-mail.
> The access token is stored in `.credentials.gmailieer.json` in the local mail repository. If you wish, you can specify [your own api key](#using-your-own-api-key) that should be used.
4. You're now set up, and you can do the initial pull.
> Use `gmi -h` or `gmi command -h` to get more usage information.
## Pull
will pull down all remote changes since last time, overwriting any local tag
changes of the affected messages.
```sh
$ gmi pull
```
the first time you do this, or if a full synchronization is needed it will take longer. You can try to use the `--resume` option if you get stuck on getting the metadata and have to abort (this will cause local changes made in the interim to be ignored in the next push).
## Push
will push up all changes since last push, conflicting changes will be ignored
unless `-f` is specified. these will be overwritten with the remote changes at
the next `pull`.
```sh
$ gmi push
```
## Normal synchronization routine
```sh
$ cd ~/.mail/account.gmail
$ gmi sync
```
This effectively does a `push` followed by a `pull`. Any conflicts detected
with the remote in `push` will not be pushed. After the next `pull` has been
run the conflicts should be resolved, overwriting the local changes with the
remote changes. You can force the local changes to overwrite the remote changes
by using `push -f`.
> Note: If changes are being made on the remote, on a message that is currently being synced with `lieer`, the changes may be overwritten or merged in weird ways.
See below for more [caveats](#caveats).
## Sending
Lieer may be used as a simple stand-in for the `sendmail` MTA. A typical configuration for a MUA send command might be:
```sh
gmi send -t -C ~/.mail/account.gmail
```
Like the real sendmail program, the raw message is read from `stdin`.
Most sendmail implementations allow passing additional recipients in additional
arguments. However, the GMail API only supports the `-t` (`--read-recipients`) mode of
sendmail, without additional recipients.
We try to support valid combinations from MUAs that make use of recipients
passed as arguments. Additional recipients are ignored, but validated. The
following combinations are OK:
- When `-t` is passed, we need to check for the CLI-passed recipients to be
equal or a subset of the ones passed in the headers.
- When `-t` is not passed, all header-passed recipients need to be provided in
the CLI as well.
This avoids silently not sending mail to some recipients (pretending we did),
or sending mail to recipients we didn't want to send to again.
One of the implication of `-t` is you have to keep `Bcc:` header in your
message when passing it to `sendmail`. It is not enough to just put the
additional recipient on the command line. For `mutt`, this means setting
`write_bcc` option.
Lieer will try to associate the sent message with the existing thread if it has
an `In-Reply-To` header. According to the [Gmail
API](https://developers.google.com/gmail/api/v1/reference/users/messages/send#request-body)
the `Subject:` header must also match, but this does not seem to be necessary
(at least not where just `Re:` has been prepended).
> If the email address in the `From:` header does not match exactly the one of
> your account, it seems like GMail resets the from to your account _address_
> only.
Note that the following flags are ignored for `sendmail` compatibility:
- `-f` (ignored, set envelope `From:` yourself)
- `-o` (ignored)
- `-i` (always implied, not bothered by single `.`'s)
There are instructions for using this in your email client (for example Emacs) in the [wiki](https://github.com/gauteh/lieer/wiki/GNU-Emacs-and-Lieer).
# Settings
Lieer can be configured using `gmi set`. Use without any options to get a list of the current settings as well as the current history ID and notmuch revision.
**`Account`** is the GMail account the repository is synced with. Configured during setup with [`gmi init`](#usage).
**`historyId`** is the latest synced GMail revision. Anything since this ID will be fetched on the next [`gmi pull`](#pull) (partial).
**`lastmod`** is the latest synced Notmuch database revision. Anything changed after this revision will be pushed on [`gmi push`](#ush).
**`Timeout`** is the timeout in seconds used for the HTTP connection to GMail. `0` means the forever or system error/timeout, [whichever occurs first](https://github.com/gauteh/lieer/issues/83#issuecomment-396487919).
**`File extension`** is an optional argument to include the specified extension in local file names (e.g., `mbox`) which can be useful for indexing them with third-party programs.
*Important:* If you change this setting after synchronizing, the best case scenario is that all files will appear to not have being pulled down and will be re-downloaded (and duplicated with a different extension in the maildir). There might also be changes to tags. You should in theory be able to change it by renaming all files, but since this will update the lastmod you will get a check on all files.
**`Drop non existing labels`** can be used to silently ignore errors where GMail gives us a label identifier which is not associated with a label. See [Caveats](#caveats).
**`Replace slash with dot`** is used to replace the sub-label separator (`/`) with a dot (`.`). I think this is easier to work with. *Important*: See note below on [changing this setting after initial sync](#changing-ignored-tags-and-translation-after-initial-sync).
**`Ignore tags (local)`** can be used to specify a list of tags which should not be synced from local to remote (e.g. [`new`](#usage)). In addition to the user-configured tags these tags are ignored: `'attachment', 'encrypted', 'signed', 'passed', 'replied', 'muted', 'mute', 'todo', 'Trash', 'voicemail'`. Some are special tags in notmuch and some are unsupported by GMail. See [Caveats](#caveats) below for more explanations. *Note:* This setting expects [_translated_ tags](#translation-between-labels-and-tags).
*Important*: See note below on [changing this setting after initial sync](#changing-ignored-tags-and-translation-after-initial-sync).
**`Ignore tags (remote)`** can be used to specify a list of tags (labels) which should not be synced from remote (GMail) to local. By default the [`CATEGORY_*` type](https://developers.google.com/gmail/api/guides/labels) labels which are mapped to the Personal/Promotions/etc tabs in the GMail interface are ignored. You can specify that no label should ignored by doing: `gmi set --ignore-tags-remote ""`. *Note:* This setting expects [_*un*translated_ tags](#translation-between-labels-and-tags).
*Important*: See note below on [changing this setting after initial sync](#changing-ignored-tags-and-translation-after-initial-sync).
**`Local Trash Tag (local)`** can be used to set the local tag to which the remote GMail 'TRASH' label is translated.
*Important*: See note below on [changing this setting after initial sync](#changing-ignored-tags-and-translation-after-initial-sync).
**`Translation List Overlay`** can be used to add or change entries in the translation mapping between local and remote tags. Argument is a comment-separated list with an even number of items. This is interpreted as a list of pairs of (remote, local), where each pair is added to the tag translation overwriting any existing translation for that tag if any. For example,
`--translation-list-overlay CATEGORY_FORUMS,my_forum_tag` will translate Google's CATEGORY_FORUMS tag to my_forum_tag.')
*Important*: See note below on [changing this setting after initial sync](#changing-ignored-tags-and-translation-after-initial-sync).
## Changing ignored tags and translation after initial sync
If you change the [ignored tags](#settings) after the initial sync this will not update already synced messages. This means that if a change is made locally on an already synced message the previously ignored remote labels may be deleted. Conversely, if a change occurs remotely on a message which previously which has local tags that were ignored before, these ignored tags may be deleted.
The best way to deal with this is to do a full push or pull after having changed one of the settings. **Do not change both `--ignore-tags-locally` and `--ignore-tags-remote` at the same time.**
Before changing either setting make sure you are fully synchronized. After changing e.g. `--ignore-tags-remote` do first a dry-run and then a real run of full `gmi pull -f --dry-run`. This will fetch the full tag list for all messages and overwrite the local tags of all your messages with the remote labels.
When changing the opposite setting: `--ignore-tags-local`, do a full push (dry-run first): `gmi push -f --dry-run`.
The same goes for the options `--replace-slash-with-dot` and `--local-trash-tag`. I prefer to do `gmi pull -f --dry-run` after changing this option. This will overwrite the local tags with the remote labels.
# Translation between labels and tags
We translate some of the GMail labels to other tags. The default map of labels to tags are:
```py
'INBOX' : 'inbox',
'SPAM' : 'spam',
'TRASH' : 'trash',
'UNREAD' : 'unread',
'STARRED' : 'flagged',
'IMPORTANT' : 'important',
'SENT' : 'sent',
'DRAFT' : 'draft',
'CHAT' : 'chat',
'CATEGORY_PERSONAL' : 'personal',
'CATEGORY_SOCIAL' : 'social',
'CATEGORY_PROMOTIONS' : 'promotions',
'CATEGORY_UPDATES' : 'updates',
'CATEGORY_FORUMS' : 'forums',
```
The 'trash' local tag can be replaced using the `--local-trash-tag` option.
# Using your own API key
Lieer ships with an API key that is shared openly, this key shares API quota, but [cannot be used to access data](https://github.com/gauteh/lieer/pull/9) unless access is gained to your private `access_token` or `refresh_token`.
You can get an [api key](https://console.developers.google.com/flows/enableapi?apiid=gmail) for a CLI application to use for yourself. Store the `client_secret.json` file somewhere safe and specify it to `gmi auth -c`. You can do this on a repository that is already initialized, possibly using `-f` to force reauthorizing with the new client secrets.
# Privacy policy
Lieer downloads e-mail and labels to your local computer. No data is sent elsewhere.
Lieers use and transfer to any other app of information received from Google
APIs will adhere to [Google API Services User Data Policy](https://developers.google.com/terms/api-services-user-data-policy#additional_requirements_for_specific_api_scopes),
including the Limited Use requirements
# Caveats
* The GMail API does not let you sync `muted` messages. Until [this Google
bug](https://issuetracker.google.com/issues/36759067) is fixed, the `mute` and `muted` tags are not synchronized with the remote.
* The [`todo`](https://github.com/gauteh/lieer/issues/52) and [`voicemail`](https://github.com/gauteh/lieer/issues/74) labels seem to be reserved and will be ignored.
* The `draft` and `sent` labels are read only: They are synced from GMail to local notmuch tags, but not back (if you change them via notmuch).
* [Only one of the tags](https://github.com/gauteh/lieer/issues/26) `inbox`, `spam`, and `trash` may be added to an email. For
the time being, `trash` will be preferred over `spam`, and `spam` over `inbox`.
* `Trash` (capital `T`) is reserved and not allowed, use `trash` (lowercase, see above) to bin messages remotely.
* `archive` or `arxiv` are reserved and not allowed; see [issue/109](https://github.com/gauteh/lieer/issues/109) and [issue/171](https://github.com/gauteh/lieer/issues/171). To archive e-mails remove the `inbox` tag.
* Sometimes GMail provides a label identifier on a message for a label that does not exist. If you encounter this [issue](https://github.com/gauteh/lieer/issues/48) you can get around it by using `gmi set --drop-non-existing-labels` and re-try to pull. The labels will now be ignored, and if this message is ever synced back up the unmapped label ID will be removed. You can list labels with `gmi pull -t`.
* Sometimes GMail [indicates that there are more changes](https://github.com/gauteh/lieer/issues/120) when doing a partial pull, but an empty set is returned. The default is to fail, but you can ignore empty history by setting: `gmi set --ignore-empty-history`.
* You [cannot add any new files](https://github.com/gauteh/lieer/issues/54) (files starting with `.` will be ignored) to the lieer repository. Lieer uses the directory content an index of local files. Lieer does not push new messages to your account (note that if you send messages with GMail, GMail automatically adds the message to your mailbox).
* Make sure that you use the same domain for you GMail account as you initially created your account with: usually `@gmail.com`, but sometimes `@googlemail.com`. Otherwise you might get a [`Delegation denied` error](https://github.com/gauteh/lieer/issues/88).
# Development
Github actions are configured to check for python code formatted by [black](https://black.readthedocs.io/en/stable/integrations/github_actions.html).
Raw data
{
"_id": null,
"home_page": "https://github.com/gauteh/lieer",
"name": "lieer",
"maintainer": "",
"docs_url": null,
"requires_python": "",
"maintainer_email": "",
"keywords": "gmail notmuch synchronization tags",
"author": "Gaute Hope",
"author_email": "eg@gaute.vetsj.com",
"download_url": "https://files.pythonhosted.org/packages/16/41/d07b6318f7f3a2f6fc6faccb923c672b4d55ee6c2e4608bf368d0f2e7587/lieer-1.6.tar.gz",
"platform": null,
"description": "# Lieer\n\n<img src=\"https://gauteh.github.io/lieer/demo.png\">\n\nThis program can pull, and send, email and labels (and changes to labels) from\nyour GMail account and store them locally in a maildir with the labels\nsynchronized with a [notmuch](https://notmuchmail.org/) database. The changes\nto tags in the notmuch database may be pushed back remotely to your GMail\naccount.\n\n## Disclaimer\n\nLieer will not and can not:\n\n* Add or delete messages on your remote account (except syncing the `trash` or `spam` label to messages, and those messages will eventually be [deleted](https://support.google.com/mail/answer/7401?co=GENIE.Platform%3DDesktop&hl=en))\n* Modify messages other than their labels\n\nWhile Lieer has been used to successfully synchronize millions of messages and tags by now, it comes with **NO WARRANTIES**.\n\n## Requirements\n\n* Python 3\n* `notmuch >= 0.25` python bindings\n* `google_api_python_client` (sometimes `google-api-python-client`)\n* `google_auth_oauthlib`\n* `tqdm` (optional - for progress bar)\n\n## Installation\n\nAfter cloning the repository Lieer can be installed through pip by using the command ```pip install .```\n# Usage\n\nThis assumes your root mail folder is in `~/.mail` and that this folder is _already_ set up with notmuch.\n\n1. Make a directory for the lieer storage and state files (local repository).\n\n```sh\n$ cd ~/.mail\n$ mkdir account.gmail\n$ cd account.gmail/\n```\n\nAll commands should be run from the local mail repository unless otherwise specified.\n\n\n2. Ignore the `.json` files in notmuch. Any tags listed in `new.tags` will be added to newly pulled messages. Process tags on new messages directly after running gmi, or run `notmuch new` to trigger the `post-new` hook for [initial tagging](https://notmuchmail.org/initial_tagging/). The `new.tags` are not ignored by default if you do not remove them, but you can prevent custom tags from being pushed to the remote by using e.g. `gmi set --ignore-tags-local new`. In your notmuch config file (usually `~/.notmuch-config`):\n\n```\n[new]\ntags=new\nignore=/.*[.](json|lock|bak)$/\n```\n\n3. Initialize the mail storage:\n\n```sh\n$ gmi init your.email@gmail.com\n```\n\n`gmi init` will now open your browser and request limited access to your e-mail.\n\n> The access token is stored in `.credentials.gmailieer.json` in the local mail repository. If you wish, you can specify [your own api key](#using-your-own-api-key) that should be used.\n\n4. You're now set up, and you can do the initial pull.\n\n> Use `gmi -h` or `gmi command -h` to get more usage information.\n\n## Pull\n\nwill pull down all remote changes since last time, overwriting any local tag\nchanges of the affected messages.\n\n```sh\n$ gmi pull\n```\n\nthe first time you do this, or if a full synchronization is needed it will take longer. You can try to use the `--resume` option if you get stuck on getting the metadata and have to abort (this will cause local changes made in the interim to be ignored in the next push).\n\n## Push\n\nwill push up all changes since last push, conflicting changes will be ignored\nunless `-f` is specified. these will be overwritten with the remote changes at\nthe next `pull`.\n\n```sh\n$ gmi push\n```\n\n## Normal synchronization routine\n\n```sh\n$ cd ~/.mail/account.gmail\n$ gmi sync\n```\n\nThis effectively does a `push` followed by a `pull`. Any conflicts detected\nwith the remote in `push` will not be pushed. After the next `pull` has been\nrun the conflicts should be resolved, overwriting the local changes with the\nremote changes. You can force the local changes to overwrite the remote changes\nby using `push -f`.\n\n> Note: If changes are being made on the remote, on a message that is currently being synced with `lieer`, the changes may be overwritten or merged in weird ways.\n\nSee below for more [caveats](#caveats).\n\n## Sending\n\nLieer may be used as a simple stand-in for the `sendmail` MTA. A typical configuration for a MUA send command might be:\n\n```sh\ngmi send -t -C ~/.mail/account.gmail\n```\n\nLike the real sendmail program, the raw message is read from `stdin`.\n\nMost sendmail implementations allow passing additional recipients in additional\narguments. However, the GMail API only supports the `-t` (`--read-recipients`) mode of\nsendmail, without additional recipients.\n\nWe try to support valid combinations from MUAs that make use of recipients\npassed as arguments. Additional recipients are ignored, but validated. The\nfollowing combinations are OK:\n\n - When `-t` is passed, we need to check for the CLI-passed recipients to be\n equal or a subset of the ones passed in the headers.\n\n - When `-t` is not passed, all header-passed recipients need to be provided in\n the CLI as well.\n\nThis avoids silently not sending mail to some recipients (pretending we did),\nor sending mail to recipients we didn't want to send to again.\n\nOne of the implication of `-t` is you have to keep `Bcc:` header in your\nmessage when passing it to `sendmail`. It is not enough to just put the\nadditional recipient on the command line. For `mutt`, this means setting\n`write_bcc` option.\n\nLieer will try to associate the sent message with the existing thread if it has\nan `In-Reply-To` header. According to the [Gmail\nAPI](https://developers.google.com/gmail/api/v1/reference/users/messages/send#request-body)\nthe `Subject:` header must also match, but this does not seem to be necessary\n(at least not where just `Re:` has been prepended).\n\n> If the email address in the `From:` header does not match exactly the one of\n> your account, it seems like GMail resets the from to your account _address_\n> only.\n\nNote that the following flags are ignored for `sendmail` compatibility:\n\n - `-f` (ignored, set envelope `From:` yourself)\n - `-o` (ignored)\n - `-i` (always implied, not bothered by single `.`'s)\n\nThere are instructions for using this in your email client (for example Emacs) in the [wiki](https://github.com/gauteh/lieer/wiki/GNU-Emacs-and-Lieer).\n\n# Settings\n\nLieer can be configured using `gmi set`. Use without any options to get a list of the current settings as well as the current history ID and notmuch revision.\n\n**`Account`** is the GMail account the repository is synced with. Configured during setup with [`gmi init`](#usage).\n\n**`historyId`** is the latest synced GMail revision. Anything since this ID will be fetched on the next [`gmi pull`](#pull) (partial).\n\n**`lastmod`** is the latest synced Notmuch database revision. Anything changed after this revision will be pushed on [`gmi push`](#ush).\n\n**`Timeout`** is the timeout in seconds used for the HTTP connection to GMail. `0` means the forever or system error/timeout, [whichever occurs first](https://github.com/gauteh/lieer/issues/83#issuecomment-396487919).\n\n**`File extension`** is an optional argument to include the specified extension in local file names (e.g., `mbox`) which can be useful for indexing them with third-party programs. \n\n*Important:* If you change this setting after synchronizing, the best case scenario is that all files will appear to not have being pulled down and will be re-downloaded (and duplicated with a different extension in the maildir). There might also be changes to tags. You should in theory be able to change it by renaming all files, but since this will update the lastmod you will get a check on all files.\n\n**`Drop non existing labels`** can be used to silently ignore errors where GMail gives us a label identifier which is not associated with a label. See [Caveats](#caveats).\n\n**`Replace slash with dot`** is used to replace the sub-label separator (`/`) with a dot (`.`). I think this is easier to work with. *Important*: See note below on [changing this setting after initial sync](#changing-ignored-tags-and-translation-after-initial-sync).\n\n**`Ignore tags (local)`** can be used to specify a list of tags which should not be synced from local to remote (e.g. [`new`](#usage)). In addition to the user-configured tags these tags are ignored: `'attachment', 'encrypted', 'signed', 'passed', 'replied', 'muted', 'mute', 'todo', 'Trash', 'voicemail'`. Some are special tags in notmuch and some are unsupported by GMail. See [Caveats](#caveats) below for more explanations. *Note:* This setting expects [_translated_ tags](#translation-between-labels-and-tags).\n \n *Important*: See note below on [changing this setting after initial sync](#changing-ignored-tags-and-translation-after-initial-sync).\n\n**`Ignore tags (remote)`** can be used to specify a list of tags (labels) which should not be synced from remote (GMail) to local. By default the [`CATEGORY_*` type](https://developers.google.com/gmail/api/guides/labels) labels which are mapped to the Personal/Promotions/etc tabs in the GMail interface are ignored. You can specify that no label should ignored by doing: `gmi set --ignore-tags-remote \"\"`. *Note:* This setting expects [_*un*translated_ tags](#translation-between-labels-and-tags).\n \n *Important*: See note below on [changing this setting after initial sync](#changing-ignored-tags-and-translation-after-initial-sync).\n\n**`Local Trash Tag (local)`** can be used to set the local tag to which the remote GMail 'TRASH' label is translated.\n\n *Important*: See note below on [changing this setting after initial sync](#changing-ignored-tags-and-translation-after-initial-sync).\n\n**`Translation List Overlay`** can be used to add or change entries in the translation mapping between local and remote tags. Argument is a comment-separated list with an even number of items. This is interpreted as a list of pairs of (remote, local), where each pair is added to the tag translation overwriting any existing translation for that tag if any. For example,\n`--translation-list-overlay CATEGORY_FORUMS,my_forum_tag` will translate Google's CATEGORY_FORUMS tag to my_forum_tag.')\n\n *Important*: See note below on [changing this setting after initial sync](#changing-ignored-tags-and-translation-after-initial-sync).\n\n## Changing ignored tags and translation after initial sync\n\nIf you change the [ignored tags](#settings) after the initial sync this will not update already synced messages. This means that if a change is made locally on an already synced message the previously ignored remote labels may be deleted. Conversely, if a change occurs remotely on a message which previously which has local tags that were ignored before, these ignored tags may be deleted.\n\nThe best way to deal with this is to do a full push or pull after having changed one of the settings. **Do not change both `--ignore-tags-locally` and `--ignore-tags-remote` at the same time.**\n\nBefore changing either setting make sure you are fully synchronized. After changing e.g. `--ignore-tags-remote` do first a dry-run and then a real run of full `gmi pull -f --dry-run`. This will fetch the full tag list for all messages and overwrite the local tags of all your messages with the remote labels.\n\nWhen changing the opposite setting: `--ignore-tags-local`, do a full push (dry-run first): `gmi push -f --dry-run`.\n\nThe same goes for the options `--replace-slash-with-dot` and `--local-trash-tag`. I prefer to do `gmi pull -f --dry-run` after changing this option. This will overwrite the local tags with the remote labels.\n\n\n# Translation between labels and tags\n\nWe translate some of the GMail labels to other tags. The default map of labels to tags are:\n\n```py\n 'INBOX' : 'inbox',\n 'SPAM' : 'spam',\n 'TRASH' : 'trash',\n 'UNREAD' : 'unread',\n 'STARRED' : 'flagged',\n 'IMPORTANT' : 'important',\n 'SENT' : 'sent',\n 'DRAFT' : 'draft',\n 'CHAT' : 'chat',\n\n 'CATEGORY_PERSONAL' : 'personal',\n 'CATEGORY_SOCIAL' : 'social',\n 'CATEGORY_PROMOTIONS' : 'promotions',\n 'CATEGORY_UPDATES' : 'updates',\n 'CATEGORY_FORUMS' : 'forums',\n```\n\nThe 'trash' local tag can be replaced using the `--local-trash-tag` option.\n\n# Using your own API key\n\nLieer ships with an API key that is shared openly, this key shares API quota, but [cannot be used to access data](https://github.com/gauteh/lieer/pull/9) unless access is gained to your private `access_token` or `refresh_token`.\n\nYou can get an [api key](https://console.developers.google.com/flows/enableapi?apiid=gmail) for a CLI application to use for yourself. Store the `client_secret.json` file somewhere safe and specify it to `gmi auth -c`. You can do this on a repository that is already initialized, possibly using `-f` to force reauthorizing with the new client secrets.\n\n\n# Privacy policy\n\nLieer downloads e-mail and labels to your local computer. No data is sent elsewhere.\n\nLieers use and transfer to any other app of information received from Google\nAPIs will adhere to [Google API Services User Data Policy](https://developers.google.com/terms/api-services-user-data-policy#additional_requirements_for_specific_api_scopes),\nincluding the Limited Use requirements\n\n# Caveats\n\n* The GMail API does not let you sync `muted` messages. Until [this Google\nbug](https://issuetracker.google.com/issues/36759067) is fixed, the `mute` and `muted` tags are not synchronized with the remote.\n\n* The [`todo`](https://github.com/gauteh/lieer/issues/52) and [`voicemail`](https://github.com/gauteh/lieer/issues/74) labels seem to be reserved and will be ignored.\n\n* The `draft` and `sent` labels are read only: They are synced from GMail to local notmuch tags, but not back (if you change them via notmuch).\n\n* [Only one of the tags](https://github.com/gauteh/lieer/issues/26) `inbox`, `spam`, and `trash` may be added to an email. For\nthe time being, `trash` will be preferred over `spam`, and `spam` over `inbox`.\n\n* `Trash` (capital `T`) is reserved and not allowed, use `trash` (lowercase, see above) to bin messages remotely.\n\n* `archive` or `arxiv` are reserved and not allowed; see [issue/109](https://github.com/gauteh/lieer/issues/109) and [issue/171](https://github.com/gauteh/lieer/issues/171). To archive e-mails remove the `inbox` tag.\n\n* Sometimes GMail provides a label identifier on a message for a label that does not exist. If you encounter this [issue](https://github.com/gauteh/lieer/issues/48) you can get around it by using `gmi set --drop-non-existing-labels` and re-try to pull. The labels will now be ignored, and if this message is ever synced back up the unmapped label ID will be removed. You can list labels with `gmi pull -t`.\n\n* Sometimes GMail [indicates that there are more changes](https://github.com/gauteh/lieer/issues/120) when doing a partial pull, but an empty set is returned. The default is to fail, but you can ignore empty history by setting: `gmi set --ignore-empty-history`.\n\n* You [cannot add any new files](https://github.com/gauteh/lieer/issues/54) (files starting with `.` will be ignored) to the lieer repository. Lieer uses the directory content an index of local files. Lieer does not push new messages to your account (note that if you send messages with GMail, GMail automatically adds the message to your mailbox).\n\n* Make sure that you use the same domain for you GMail account as you initially created your account with: usually `@gmail.com`, but sometimes `@googlemail.com`. Otherwise you might get a [`Delegation denied` error](https://github.com/gauteh/lieer/issues/88).\n\n\n# Development\n\nGithub actions are configured to check for python code formatted by [black](https://black.readthedocs.io/en/stable/integrations/github_actions.html).\n",
"bugtrack_url": null,
"license": "GPLv3+",
"summary": "Fast fetch and two-way tag synchronization between notmuch and GMail",
"version": "1.6",
"project_urls": {
"Homepage": "https://github.com/gauteh/lieer"
},
"split_keywords": [
"gmail",
"notmuch",
"synchronization",
"tags"
],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "1641d07b6318f7f3a2f6fc6faccb923c672b4d55ee6c2e4608bf368d0f2e7587",
"md5": "a5330226657fbca3af81e3aa659a1c02",
"sha256": "080c35b52dd034333cc1d25ac9f284a9dc8666539ada53f7065b2b783df492a2"
},
"downloads": -1,
"filename": "lieer-1.6.tar.gz",
"has_sig": false,
"md5_digest": "a5330226657fbca3af81e3aa659a1c02",
"packagetype": "sdist",
"python_version": "source",
"requires_python": null,
"size": 48773,
"upload_time": "2023-11-03T08:26:46",
"upload_time_iso_8601": "2023-11-03T08:26:46.367810Z",
"url": "https://files.pythonhosted.org/packages/16/41/d07b6318f7f3a2f6fc6faccb923c672b4d55ee6c2e4608bf368d0f2e7587/lieer-1.6.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2023-11-03 08:26:46",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "gauteh",
"github_project": "lieer",
"travis_ci": false,
"coveralls": false,
"github_actions": true,
"requirements": [],
"lcname": "lieer"
}
JSON
