courier 1.1.15__tar.gz

courier-1.1.15/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025 Weiwu Zhang
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

courier-1.1.15/PKG-INFO

@@ -0,0 +1,264 @@
+Metadata-Version: 2.4
+Name: courier
+Version: 1.1.15
+Summary: Email toolkit for AI assistants and command-line scripting
+Author: Weiwu Zhang
+License: MIT
+Project-URL: Homepage, https://github.com/overseers-desk/courier
+Project-URL: Issues, https://github.com/overseers-desk/courier/issues
+Project-URL: Author, https://www.linkedin.com/in/weiwuzhang/
+Keywords: email,imap,mcp,ai,cli,gmail,automation
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: imapclient>=3.0.0
+Requires-Dist: markdown-it-py>=3.0.0
+Requires-Dist: python-dotenv>=1.0.0
+Requires-Dist: requests>=2.32.0
+Requires-Dist: sievelib>=1.5
+Requires-Dist: typer>=0.15.0
+Provides-Extra: mcp
+Requires-Dist: flask>=3.1.0; extra == "mcp"
+Requires-Dist: mcp>=1.0.0; extra == "mcp"
+Provides-Extra: dev
+Requires-Dist: pytest>=8.0.0; extra == "dev"
+Requires-Dist: pytest-cov>=6.0.0; extra == "dev"
+Requires-Dist: pytest-asyncio>=0.25.0; extra == "dev"
+Requires-Dist: ruff>=0.11.0; extra == "dev"
+Requires-Dist: black>=23.0.0; extra == "dev"
+Requires-Dist: isort>=5.10.0; extra == "dev"
+Requires-Dist: mypy>=0.982; extra == "dev"
+Requires-Dist: pre-commit>=2.19.0; extra == "dev"
+Dynamic: license-file
+
+# ![Courier](docs/logo.png)
+
+[![CI](https://github.com/overseers-desk/courier/actions/workflows/code_checks.yml/badge.svg)](https://github.com/overseers-desk/courier/actions/workflows/code_checks.yml)
+[![Python 3.11+](https://img.shields.io/badge/python-3.11%2B-blue)](https://www.python.org/downloads/)
+[![License: MIT](https://img.shields.io/badge/license-MIT-green)](LICENSE)
+
+Give your script or AI assistant access to your email.
+
+## Contents
+
+- [What your AI can do with it](#what-your-ai-can-do-with-it)
+- [Installation](#installation)
+- [Configuration](#configuration)
+- [Quick test](#quick-test)
+- [CLI usage](#cli-usage)
+- [Claude Code (terminal-based Claude)](#claude-code-terminal-based-claude)
+- [MCP server](#mcp-server)
+- [Scripting and automation](#scripting-and-automation)
+- [Faster searches](#faster-searches)
+- [Connection handling](#connection-handling)
+- [Security](#security)
+- [License](#license)
+
+Courier connects to your existing mailbox on Gmail, Outlook, Fastmail, or any IMAP provider. It does not create new email addresses or route mail through a third-party service.
+
+Commandline users, script authors, and AI assistants can search, read, download, reply, send, and organize email. Two interfaces serve different environments: a CLI that outputs JSON (for terminal-based agents, scripts, and automation) and an MCP server (for web-based AI chats and MCP clients). Both expose the same operations.
+
+## What your AI can do with it
+
+- Courier runs on your machine, with no service of ours between you and your mailbox.
+- Keep banking, OTPs, and sensitive senders out of the LLM's view, using per-mailbox Sieve rules.
+- Reply from the right alias, using our identity feature.
+- Gmail-style queries (`from:alice newer:3d is:unread`) work on any IMAP provider.
+- An optional local `mu` index makes archive-grade searches near-instant.
+- Search every mailbox in one call with `-A`.
+- Drafts on your server by default; `--send` is opt-in.
+- Handle a meeting invite (parse the `.ics`, draft an RSVP).
+- Chain searches and reads in one call: `courier search foo search bar read -f INBOX -u 42`.
+- Move, flag, or archive messages.
+- Download attachments, export messages as HTML, extract links.
+
+## Installation
+
+See [INSTALLATION.md](docs/INSTALLATION.md) for Homebrew, Debian/Ubuntu (.deb), Fedora/RHEL (.rpm), and source installs.
+
+## Configuration
+
+Copy the sample and fill in your credentials:
+
+```bash
+cp examples/config.sample.toml ~/.config/courier/config.toml
+```
+
+A small config has three top-level named-entity tables: an `[imap.NAME]` mailbox, an `[smtp.NAME]` outgoing endpoint, and an `[identity.NAME]` describing one sendable address pointing at the IMAP block:
+
+```toml
+[smtp.gmail]
+host = "smtp.gmail.com"
+port = 587
+
+[imap.personal]
+host = "imap.gmail.com"
+port = 993
+username = "you@gmail.com"
+# For Gmail, generate this at https://myaccount.google.com/apppasswords
+password = "abcdefghijklmnop"
+default_smtp = "gmail"
+
+[identity.personal]
+imap = "personal"
+address = "you@gmail.com"
+```
+
+(Smaller is also valid: `[imap.*]` alone reads but cannot send; `[identity.*]` with `bcc` plus `[smtp.*]` sends but cannot read.)
+
+For Gmail, the simpler path is the app-password example above. The alternative is OAuth2, which needs a Google Cloud project set up through Google's developer console (a much messier path); if you have already done that, the same `[imap.NAME]` block carries the OAuth2 keys instead of `password`:
+
+```toml
+[imap.personal]
+host = "imap.gmail.com"
+port = 993
+username = "you@gmail.com"
+client_id = "YOUR_CLIENT_ID"
+client_secret = "YOUR_CLIENT_SECRET"
+refresh_token = "YOUR_REFRESH_TOKEN"
+default_smtp = "gmail"
+```
+
+`[smtp.NAME]` blocks declare named SMTP endpoints. When the block omits credentials, courier inherits them from the `[imap.NAME]` block in scope at send time, the right shape for Gmail and Fastmail where IMAP and SMTP share one credential. When the block carries its own `username` and `password`, courier uses those, the right shape for AWS SES and similar smarthosts where one IAM SMTP user serves many From addresses.
+
+Sending requires at least one `[identity.NAME]` block pointing at the `[imap.NAME]`. A block with no identities is read-only for sending; drafting and reading still work. This is a valid state, not an error. Declaring identities explicitly avoids the registration-handle hazard, where an IMAP login (e.g. a Gmail handle that is not an intended sender) could otherwise become a sendable identity by accident.
+
+`courier config-check` validates the config (cross-references, identity addresses, send-route resolution) without performing any IMAP or SMTP traffic. The same warnings surface on `courier`, `courier --help`, `courier status`, and `courier list`.
+
+Gmail OAuth2 setup requires a Google Cloud project with the Gmail API enabled. See [GMAIL_SETUP.md](docs/GMAIL_SETUP.md) for the full walkthrough.
+
+For multi-account configs (multiple `[imap.*]` blocks, send-as through several identities, SES smarthost routing), see [docs/CONFIGURATION.md](docs/CONFIGURATION.md).
+
+## Quick test
+
+With uv (any platform):
+
+```bash
+uvx courier search "subject:invoice"
+```
+
+No installation step; `uvx` runs it directly. To install permanently:
+
+```bash
+uv tool install courier
+```
+
+On Debian and Ubuntu, the default install path is the `.deb` package from the GitHub release (see [INSTALLATION.md](docs/INSTALLATION.md)). As an alternative for running from a clone without installing, on Ubuntu 25.04 or later the CLI dependencies are all in the standard repositories:
+
+```bash
+sudo apt-get install python3-typer python3-dotenv python3-imapclient python3-requests
+python3 -m courier search "subject:invoice"
+```
+
+Courier looks for a config file at `~/.config/courier/config.toml`. Use `--config /path/to/config.toml` to point to a different location.
+
+The MCP server (`courier mcp`) requires the `mcp` Python package, which is not in apt. Use `uv` or `pip` for that. Many users prefer the CLI to MCP because the latter loads 80+ tools into every conversation; the CLI is the lighter footprint.
+
+## CLI usage
+
+Every command outputs JSON to stdout. Errors go to stderr. This makes Courier composable with `jq`, shell scripts, and AI agent skill definitions.
+
+```bash
+# Look up several keywords in one invocation; each gets its own outer key
+# in the result, so hits stay attributed to the keyword that matched them
+courier search "from:alice" search 'subject:"hotel booking"' search "is:unread"
+
+# What's unread in INBOX?
+courier search "is:unread" --folder INBOX --limit 10
+
+# Read an email
+courier read -f INBOX -u 4523
+
+# List and download attachments
+courier attachments -f INBOX -u 4523
+courier save -f INBOX -u 4523 --attachment itinerary.pdf -o /tmp/itinerary.pdf
+
+# Export an HTML email as a standalone file (images embedded)
+courier export -f INBOX -u 4523 -o /tmp/email.html
+courier export -f INBOX -u 4523 -o /tmp/email.eml --raw
+
+# Extract all links from several emails
+courier links -f INBOX -u 4523 -u 4524 -u 4525
+
+# Reply, saved to drafts by default; --send transmits via SMTP
+courier reply -f INBOX -u 4523 -b "Thanks, confirmed."
+courier reply -f INBOX -u 4523 -b "Invoice attached." --attach /tmp/invoice.pdf
+courier reply -f INBOX -u 4523 -b "Thanks, confirmed." --send
+
+# Compose a new message (--send requires --identity NAME, or
+# --smtp NAME --from EMAIL; see docs/CONFIGURATION.md)
+courier compose --to alice@example.com --subject "Meeting" \
+  -b "See attached." --send --identity work
+
+# Send a draft
+courier send-draft -f Drafts -u 4530
+
+# Organize
+courier move -f INBOX -u 4523 -t Archive
+courier mark-read -f INBOX -u 4524
+courier flag -f INBOX -u 4525
+```
+
+Run `courier --help` for the full command list.
+
+## Claude Code (terminal-based Claude)
+
+Run `courier install-claude-command` once after installation. This writes `~/.claude/commands/courier.md`, which tells Claude Code how to use the courier CLI for email tasks. After that, prompts like "find the booking confirmation from last week" or "reply to Alice's message" route through courier automatically.
+
+## MCP server
+
+For AI environments that cannot run shell commands (Claude web, Cursor, or any MCP client):
+
+```bash
+courier mcp
+```
+
+This starts an MCP server exposing the same operations as tools. The MCP package is only imported when this subcommand runs, so the CLI stays lightweight.
+
+## Scripting and automation
+
+Because every command returns JSON and uses non-zero exit codes on failure, Courier works as a building block in pipelines and cron jobs.
+
+```bash
+# Forward all emails from a sender to another folder
+courier search "from:sender@example.com" --folder INBOX \
+  | jq -r '.[].uid' \
+  | xargs -I{} courier move -f INBOX -u {} -t Forwarded
+
+# Daily digest: save today's unread subjects to a file
+courier search "is:unread" --folder INBOX \
+  | jq -r '.[].subject' > ~/daily-digest.txt
+
+# Auto-acknowledge incoming invoices
+courier search "is:unread subject:invoice" --folder INBOX \
+  | jq -r '.[].uid' \
+  | xargs -I{} courier reply -f INBOX -u {} -b "Received, processing." \
+      --send --identity work
+```
+
+AI agents with skill/hook systems call Courier the same way: define a skill that runs a shell command and parses the JSON output.
+
+## Faster searches
+
+Courier can answer `search` from a local Xapian index instead of IMAP, orders of magnitude faster, with transparent fallback to IMAP when the index can't serve the query. See [docs/LOCAL_CACHE.md](docs/LOCAL_CACHE.md) for the offlineimap+mu setup.
+
+## Connection handling
+
+IMAP servers drop idle connections after 10-30 minutes. AI assistants work in bursts: a flurry of operations, then thinking time. Courier tracks connection age and reconnects transparently before operations fail. The default idle timeout is 300 seconds; set `idle_timeout` in the config to adjust.
+
+## Security
+
+Courier accesses your email account. Store credentials outside your repository (environment variables, a secrets manager, or a config file in `.gitignore`). Use app-specific passwords or OAuth2 rather than your main account password. Restrict `allowed_folders` in the config to limit what the tool can see.
+
+For per-message control over what reaches the LLM, point an `[imap.NAME]` block's `redact` field at a Sieve script. Matching messages have subject, body, and party addresses blanked before courier returns them, so banking notices, OTPs, and other sensitive content stay out of the model's context window. See [examples/work-only.sieve](examples/work-only.sieve) for a starting policy.
+
+## License
+
+MIT. See [LICENSE](LICENSE).

courier-1.1.15/README.md

@@ -0,0 +1,224 @@
+# ![Courier](docs/logo.png)
+
+[![CI](https://github.com/overseers-desk/courier/actions/workflows/code_checks.yml/badge.svg)](https://github.com/overseers-desk/courier/actions/workflows/code_checks.yml)
+[![Python 3.11+](https://img.shields.io/badge/python-3.11%2B-blue)](https://www.python.org/downloads/)
+[![License: MIT](https://img.shields.io/badge/license-MIT-green)](LICENSE)
+
+Give your script or AI assistant access to your email.
+
+## Contents
+
+- [What your AI can do with it](#what-your-ai-can-do-with-it)
+- [Installation](#installation)
+- [Configuration](#configuration)
+- [Quick test](#quick-test)
+- [CLI usage](#cli-usage)
+- [Claude Code (terminal-based Claude)](#claude-code-terminal-based-claude)
+- [MCP server](#mcp-server)
+- [Scripting and automation](#scripting-and-automation)
+- [Faster searches](#faster-searches)
+- [Connection handling](#connection-handling)
+- [Security](#security)
+- [License](#license)
+
+Courier connects to your existing mailbox on Gmail, Outlook, Fastmail, or any IMAP provider. It does not create new email addresses or route mail through a third-party service.
+
+Commandline users, script authors, and AI assistants can search, read, download, reply, send, and organize email. Two interfaces serve different environments: a CLI that outputs JSON (for terminal-based agents, scripts, and automation) and an MCP server (for web-based AI chats and MCP clients). Both expose the same operations.
+
+## What your AI can do with it
+
+- Courier runs on your machine, with no service of ours between you and your mailbox.
+- Keep banking, OTPs, and sensitive senders out of the LLM's view, using per-mailbox Sieve rules.
+- Reply from the right alias, using our identity feature.
+- Gmail-style queries (`from:alice newer:3d is:unread`) work on any IMAP provider.
+- An optional local `mu` index makes archive-grade searches near-instant.
+- Search every mailbox in one call with `-A`.
+- Drafts on your server by default; `--send` is opt-in.
+- Handle a meeting invite (parse the `.ics`, draft an RSVP).
+- Chain searches and reads in one call: `courier search foo search bar read -f INBOX -u 42`.
+- Move, flag, or archive messages.
+- Download attachments, export messages as HTML, extract links.
+
+## Installation
+
+See [INSTALLATION.md](docs/INSTALLATION.md) for Homebrew, Debian/Ubuntu (.deb), Fedora/RHEL (.rpm), and source installs.
+
+## Configuration
+
+Copy the sample and fill in your credentials:
+
+```bash
+cp examples/config.sample.toml ~/.config/courier/config.toml
+```
+
+A small config has three top-level named-entity tables: an `[imap.NAME]` mailbox, an `[smtp.NAME]` outgoing endpoint, and an `[identity.NAME]` describing one sendable address pointing at the IMAP block:
+
+```toml
+[smtp.gmail]
+host = "smtp.gmail.com"
+port = 587
+
+[imap.personal]
+host = "imap.gmail.com"
+port = 993
+username = "you@gmail.com"
+# For Gmail, generate this at https://myaccount.google.com/apppasswords
+password = "abcdefghijklmnop"
+default_smtp = "gmail"
+
+[identity.personal]
+imap = "personal"
+address = "you@gmail.com"
+```
+
+(Smaller is also valid: `[imap.*]` alone reads but cannot send; `[identity.*]` with `bcc` plus `[smtp.*]` sends but cannot read.)
+
+For Gmail, the simpler path is the app-password example above. The alternative is OAuth2, which needs a Google Cloud project set up through Google's developer console (a much messier path); if you have already done that, the same `[imap.NAME]` block carries the OAuth2 keys instead of `password`:
+
+```toml
+[imap.personal]
+host = "imap.gmail.com"
+port = 993
+username = "you@gmail.com"
+client_id = "YOUR_CLIENT_ID"
+client_secret = "YOUR_CLIENT_SECRET"
+refresh_token = "YOUR_REFRESH_TOKEN"
+default_smtp = "gmail"
+```
+
+`[smtp.NAME]` blocks declare named SMTP endpoints. When the block omits credentials, courier inherits them from the `[imap.NAME]` block in scope at send time, the right shape for Gmail and Fastmail where IMAP and SMTP share one credential. When the block carries its own `username` and `password`, courier uses those, the right shape for AWS SES and similar smarthosts where one IAM SMTP user serves many From addresses.
+
+Sending requires at least one `[identity.NAME]` block pointing at the `[imap.NAME]`. A block with no identities is read-only for sending; drafting and reading still work. This is a valid state, not an error. Declaring identities explicitly avoids the registration-handle hazard, where an IMAP login (e.g. a Gmail handle that is not an intended sender) could otherwise become a sendable identity by accident.
+
+`courier config-check` validates the config (cross-references, identity addresses, send-route resolution) without performing any IMAP or SMTP traffic. The same warnings surface on `courier`, `courier --help`, `courier status`, and `courier list`.
+
+Gmail OAuth2 setup requires a Google Cloud project with the Gmail API enabled. See [GMAIL_SETUP.md](docs/GMAIL_SETUP.md) for the full walkthrough.
+
+For multi-account configs (multiple `[imap.*]` blocks, send-as through several identities, SES smarthost routing), see [docs/CONFIGURATION.md](docs/CONFIGURATION.md).
+
+## Quick test
+
+With uv (any platform):
+
+```bash
+uvx courier search "subject:invoice"
+```
+
+No installation step; `uvx` runs it directly. To install permanently:
+
+```bash
+uv tool install courier
+```
+
+On Debian and Ubuntu, the default install path is the `.deb` package from the GitHub release (see [INSTALLATION.md](docs/INSTALLATION.md)). As an alternative for running from a clone without installing, on Ubuntu 25.04 or later the CLI dependencies are all in the standard repositories:
+
+```bash
+sudo apt-get install python3-typer python3-dotenv python3-imapclient python3-requests
+python3 -m courier search "subject:invoice"
+```
+
+Courier looks for a config file at `~/.config/courier/config.toml`. Use `--config /path/to/config.toml` to point to a different location.
+
+The MCP server (`courier mcp`) requires the `mcp` Python package, which is not in apt. Use `uv` or `pip` for that. Many users prefer the CLI to MCP because the latter loads 80+ tools into every conversation; the CLI is the lighter footprint.
+
+## CLI usage
+
+Every command outputs JSON to stdout. Errors go to stderr. This makes Courier composable with `jq`, shell scripts, and AI agent skill definitions.
+
+```bash
+# Look up several keywords in one invocation; each gets its own outer key
+# in the result, so hits stay attributed to the keyword that matched them
+courier search "from:alice" search 'subject:"hotel booking"' search "is:unread"
+
+# What's unread in INBOX?
+courier search "is:unread" --folder INBOX --limit 10
+
+# Read an email
+courier read -f INBOX -u 4523
+
+# List and download attachments
+courier attachments -f INBOX -u 4523
+courier save -f INBOX -u 4523 --attachment itinerary.pdf -o /tmp/itinerary.pdf
+
+# Export an HTML email as a standalone file (images embedded)
+courier export -f INBOX -u 4523 -o /tmp/email.html
+courier export -f INBOX -u 4523 -o /tmp/email.eml --raw
+
+# Extract all links from several emails
+courier links -f INBOX -u 4523 -u 4524 -u 4525
+
+# Reply, saved to drafts by default; --send transmits via SMTP
+courier reply -f INBOX -u 4523 -b "Thanks, confirmed."
+courier reply -f INBOX -u 4523 -b "Invoice attached." --attach /tmp/invoice.pdf
+courier reply -f INBOX -u 4523 -b "Thanks, confirmed." --send
+
+# Compose a new message (--send requires --identity NAME, or
+# --smtp NAME --from EMAIL; see docs/CONFIGURATION.md)
+courier compose --to alice@example.com --subject "Meeting" \
+  -b "See attached." --send --identity work
+
+# Send a draft
+courier send-draft -f Drafts -u 4530
+
+# Organize
+courier move -f INBOX -u 4523 -t Archive
+courier mark-read -f INBOX -u 4524
+courier flag -f INBOX -u 4525
+```
+
+Run `courier --help` for the full command list.
+
+## Claude Code (terminal-based Claude)
+
+Run `courier install-claude-command` once after installation. This writes `~/.claude/commands/courier.md`, which tells Claude Code how to use the courier CLI for email tasks. After that, prompts like "find the booking confirmation from last week" or "reply to Alice's message" route through courier automatically.
+
+## MCP server
+
+For AI environments that cannot run shell commands (Claude web, Cursor, or any MCP client):
+
+```bash
+courier mcp
+```
+
+This starts an MCP server exposing the same operations as tools. The MCP package is only imported when this subcommand runs, so the CLI stays lightweight.
+
+## Scripting and automation
+
+Because every command returns JSON and uses non-zero exit codes on failure, Courier works as a building block in pipelines and cron jobs.
+
+```bash
+# Forward all emails from a sender to another folder
+courier search "from:sender@example.com" --folder INBOX \
+  | jq -r '.[].uid' \
+  | xargs -I{} courier move -f INBOX -u {} -t Forwarded
+
+# Daily digest: save today's unread subjects to a file
+courier search "is:unread" --folder INBOX \
+  | jq -r '.[].subject' > ~/daily-digest.txt
+
+# Auto-acknowledge incoming invoices
+courier search "is:unread subject:invoice" --folder INBOX \
+  | jq -r '.[].uid' \
+  | xargs -I{} courier reply -f INBOX -u {} -b "Received, processing." \
+      --send --identity work
+```
+
+AI agents with skill/hook systems call Courier the same way: define a skill that runs a shell command and parses the JSON output.
+
+## Faster searches
+
+Courier can answer `search` from a local Xapian index instead of IMAP, orders of magnitude faster, with transparent fallback to IMAP when the index can't serve the query. See [docs/LOCAL_CACHE.md](docs/LOCAL_CACHE.md) for the offlineimap+mu setup.
+
+## Connection handling
+
+IMAP servers drop idle connections after 10-30 minutes. AI assistants work in bursts: a flurry of operations, then thinking time. Courier tracks connection age and reconnects transparently before operations fail. The default idle timeout is 300 seconds; set `idle_timeout` in the config to adjust.
+
+## Security
+
+Courier accesses your email account. Store credentials outside your repository (environment variables, a secrets manager, or a config file in `.gitignore`). Use app-specific passwords or OAuth2 rather than your main account password. Restrict `allowed_folders` in the config to limit what the tool can see.
+
+For per-message control over what reaches the LLM, point an `[imap.NAME]` block's `redact` field at a Sieve script. Matching messages have subject, body, and party addresses blanked before courier returns them, so banking notices, OTPs, and other sensitive content stay out of the model's context window. See [examples/work-only.sieve](examples/work-only.sieve) for a starting policy.
+
+## License
+
+MIT. See [LICENSE](LICENSE).

courier-1.1.15/courier/__init__.py

@@ -0,0 +1,3 @@
+"""Email toolkit for AI assistants and command-line scripting."""
+
+__version__ = "1.1.15"