Email Triage
Scan your IMAP inbox, classify emails into priority categories, and surface the ones that need attention. Uses a local LLM (Ollama) for intelligent classification with a rule-based heuristic fallback when Ollama is unavailable.
Prerequisites
- Python 3.10+
- IMAP-accessible email account (Gmail, Fastmail, self-hosted, etc.)
- Ollama (optional) — for AI-powered classification. Without it, the script uses keyword-based heuristics that still work well for common patterns.
Categories
| Icon |
Category |
Description |
| 🔴 |
urgent |
Outages, security alerts, legal, payment failures, time-critical |
| 🟡 |
needs-response |
Business inquiries, questions, action items requiring a reply |
| 🔵 |
informational |
Receipts, confirmations, newsletters, automated notifications |
| ⚫ |
spam |
Marketing, promotions, unsolicited junk |
Configuration
All configuration is via environment variables:
| Variable |
Required |
Default |
Description |
IMAP_HOST |
✅ |
— |
IMAP server hostname |
IMAP_PORT |
— |
993 |
IMAP port (SSL) |
IMAP_USER |
✅ |
— |
IMAP username / email address |
IMAP_PASS |
✅ |
— |
IMAP password or app-specific password |
EMAIL_TRIAGE_STATE |
— |
./data/email-triage.json |
Path to the JSON state file |
OLLAMA_URL |
— |
http://127.0.0.1:11434 |
Ollama API endpoint |
OLLAMA_MODEL |
— |
qwen2.5:7b |
Ollama model for classification |
Directories Written
EMAIL_TRIAGE_STATE (default: ./data/email-triage.json) — Persistent state file tracking classified emails and surfacing status
Commands
# Scan inbox and classify new unread emails
python3 scripts/email/email-triage.py scan
# Scan with verbose output (shows each classification)
python3 scripts/email/email-triage.py scan --verbose
# Dry run — scan and classify but don't save state
python3 scripts/email/email-triage.py scan --dry-run
# Show unsurfaced important emails (urgent + needs-response)
python3 scripts/email/email-triage.py report
# Same as report but JSON output (for programmatic use)
python3 scripts/email/email-triage.py report --json
# Mark reported emails as surfaced (so they don't appear again)
python3 scripts/email/email-triage.py mark-surfaced
# Show triage statistics
python3 scripts/email/email-triage.py stats
How It Works
- Connects to IMAP over SSL and fetches unread messages (up to 20 per scan).
- Deduplicates by Message-ID (or a hash of subject + sender as fallback) so emails are never classified twice.
- Classifies each email using Ollama if available, otherwise falls back to keyword heuristics.
- Stores state in a local JSON file — tracks category, reason, and whether the email has been surfaced.
report surfaces only unsurfaced urgent and needs-response emails, sorted by priority.mark-surfaced flags reported emails so they won't appear in future reports.- Auto-prunes state to the most recent 200 entries to prevent unbounded growth.
Integration Tips
- Heartbeat / cron: Run
scan periodically, then report --json to check for items needing attention.
- Agent workflow:
scan → report --json → act on results → mark-surfaced.
- Without Ollama: The heuristic classifier handles common patterns (automated notifications, marketing, urgent keywords) well. Ollama adds nuance for ambiguous emails.
- App passwords: If your provider uses 2FA, generate an app-specific password for IMAP access.
1---2name: email-triage3description: IMAP email scanning and triage with AI classification via a local Ollama LLM. Scans unread emails, categorizes them as urgent, needs-response, informational, or spam, and surfaces important messages for agent consumption. Works standalone with heuristic fallback — Ollama optional but recommended.4---5
6# Email Triage
7
8Scan your IMAP inbox, classify emails into priority categories, and surface the ones that need attention. Uses a local LLM (Ollama) for intelligent classification with a rule-based heuristic fallback when Ollama is unavailable.
9
10## Prerequisites
11
12- **Python 3.10+**
13- **IMAP-accessible email account** (Gmail, Fastmail, self-hosted, etc.)
14- **Ollama** *(optional)* — for AI-powered classification. Without it, the script uses keyword-based heuristics that still work well for common patterns.
15
16## Categories
17
18| Icon | Category | Description |
19|------|----------|-------------|
20| 🔴 | `urgent` | Outages, security alerts, legal, payment failures, time-critical |
21| 🟡 | `needs-response` | Business inquiries, questions, action items requiring a reply |
22| 🔵 | `informational` | Receipts, confirmations, newsletters, automated notifications |
23| ⚫ | `spam` | Marketing, promotions, unsolicited junk |
24
25## Configuration
26
27All configuration is via environment variables:
28
29| Variable | Required | Default | Description |
30|----------|----------|---------|-------------|
31| `IMAP_HOST` | ✅ | — | IMAP server hostname |
32| `IMAP_PORT` | — | `993` | IMAP port (SSL) |
33| `IMAP_USER` | ✅ | — | IMAP username / email address |
34| `IMAP_PASS` | ✅ | — | IMAP password or app-specific password |
35| `EMAIL_TRIAGE_STATE` | — | `./data/email-triage.json` | Path to the JSON state file |
36| `OLLAMA_URL` | — | `http://127.0.0.1:11434` | Ollama API endpoint |
37| `OLLAMA_MODEL` | — | `qwen2.5:7b` | Ollama model for classification |
38
39## Directories Written
40
41- **`EMAIL_TRIAGE_STATE`** (default: `./data/email-triage.json`) — Persistent state file tracking classified emails and surfacing status
42
43## Commands
44
45```bash
46# Scan inbox and classify new unread emails
47python3 scripts/email/email-triage.py scan
48
49# Scan with verbose output (shows each classification)
50python3 scripts/email/email-triage.py scan --verbose
51
52# Dry run — scan and classify but don't save state
53python3 scripts/email/email-triage.py scan --dry-run
54
55# Show unsurfaced important emails (urgent + needs-response)
56python3 scripts/email/email-triage.py report
57
58# Same as report but JSON output (for programmatic use)
59python3 scripts/email/email-triage.py report --json
60
61# Mark reported emails as surfaced (so they don't appear again)
62python3 scripts/email/email-triage.py mark-surfaced
63
64# Show triage statistics
65python3 scripts/email/email-triage.py stats
66```
67
68## How It Works
69
701. **Connects to IMAP** over SSL and fetches unread messages (up to 20 per scan).
712. **Deduplicates** by Message-ID (or a hash of subject + sender as fallback) so emails are never classified twice.
723. **Classifies** each email using Ollama if available, otherwise falls back to keyword heuristics.
734. **Stores state** in a local JSON file — tracks category, reason, and whether the email has been surfaced.
745. **`report`** surfaces only unsurfaced urgent and needs-response emails, sorted by priority.
756. **`mark-surfaced`** flags reported emails so they won't appear in future reports.
767. **Auto-prunes** state to the most recent 200 entries to prevent unbounded growth.
77
78## Integration Tips
79
80- **Heartbeat / cron:** Run `scan` periodically, then `report --json` to check for items needing attention.
81- **Agent workflow:** `scan` → `report --json` → act on results → `mark-surfaced`.
82- **Without Ollama:** The heuristic classifier handles common patterns (automated notifications, marketing, urgent keywords) well. Ollama adds nuance for ambiguous emails.
83- **App passwords:** If your provider uses 2FA, generate an app-specific password for IMAP access.
johnalbertini14-glitch