Skip to main content

imap-idle

Enables event-driven email monitoring with IMAP IDLE protocol, providing instant notifications and reducing token usage.

Install this skill

or
0/100

Security score

The imap-idle skill was audited on Feb 9, 2026 and we found 41 security issues across 4 threat categories, including 14 high-severity. Review the findings below before installing.

Categories Tested

Security Issues

medium line 256

Curl to non-GitHub URL

SourceSKILL.md
256curl -X POST http://127.0.0.1:18789/hooks/wake \
medium line 3

Webhook reference - potential data exfiltration

SourceSKILL.md
3description: Event-driven email monitoring using IMAP IDLE protocol. Replaces polling with instant push notifications via OpenClaw webhooks. Use when setting up email monitoring, replacing hourly emai
medium line 28

Webhook reference - potential data exfiltration

SourceSKILL.md
28### 1. Enable OpenClaw Webhooks
medium line 66

Webhook reference - potential data exfiltration

SourceSKILL.md
66- OpenClaw webhook URL and token
low line 116

Webhook reference - potential data exfiltration

SourceSKILL.md
116"webhook_url": "http://127.0.0.1:18789/hooks/wake",
low line 117

Webhook reference - potential data exfiltration

SourceSKILL.md
117"webhook_token": "your-webhook-token",
medium line 127

Webhook reference - potential data exfiltration

SourceSKILL.md
127- `webhook_url` - OpenClaw webhook endpoint
medium line 128

Webhook reference - potential data exfiltration

SourceSKILL.md
128- `webhook_token` - Webhook authentication token (from openclaw.json)
medium line 132

Webhook reference - potential data exfiltration

SourceSKILL.md
132- `debounce_seconds` - Batch events for N seconds before webhook (default: 10 sec)
medium line 186

Webhook reference - potential data exfiltration

SourceSKILL.md
1866. **Webhook**: Sends batched events via webhook (single or grouped)
medium line 191

Webhook reference - potential data exfiltration

SourceSKILL.md
191- **Debouncing**: Batches emails for 10 seconds before webhook to prevent flooding during spikes (e.g., GitHub mention storms)
medium line 193

Webhook reference - potential data exfiltration

SourceSKILL.md
193- **UID Tracking**: Tracks last processed message UID per account to prevent duplicate webhooks
medium line 244

Webhook reference - potential data exfiltration

SourceSKILL.md
244**Duplicate webhooks:**
medium line 253

Webhook reference - potential data exfiltration

SourceSKILL.md
253**No webhooks triggering:**
medium line 254

Webhook reference - potential data exfiltration

SourceSKILL.md
254- Test webhook manually:
medium line 30

Access to hidden dotfiles in home directory

SourceSKILL.md
30Edit `~/.openclaw/openclaw.json`:
medium line 103

Access to hidden dotfiles in home directory

SourceSKILL.md
103Config file: `~/.openclaw/imap-idle.json`
low line 118

Access to hidden dotfiles in home directory

SourceSKILL.md
118"log_file": "~/.openclaw/logs/imap-idle.log",
low line 162

Access to hidden dotfiles in home directory

SourceSKILL.md
162# Edit ~/.openclaw/imap-idle.json and remove "password" field
medium line 240

Access to hidden dotfiles in home directory

SourceSKILL.md
240- Check config file exists: `cat ~/.openclaw/imap-idle.json`
high line 50

Access to system keychain/keyring

SourceSKILL.md
50**Optional but recommended:** Install keyring for secure password storage:
medium line 53

Access to system keychain/keyring

SourceSKILL.md
53pip3 install keyring --user --break-system-packages
high line 56

Access to system keychain/keyring

SourceSKILL.md
56With keyring, passwords are stored in your system's secure keychain (macOS Keychain, GNOME Keyring, etc.) instead of plain text in config files.
high line 134

Access to system keychain/keyring

SourceSKILL.md
134## Secure Password Storage (Keyring)
high line 136

Access to system keychain/keyring

SourceSKILL.md
136**🔐 Recommended:** Store passwords in system keychain instead of config file.
high line 138

Access to system keychain/keyring

SourceSKILL.md
138### Setup with Keyring
high line 140

Access to system keychain/keyring

SourceSKILL.md
140When you run `./imap-idle setup`, the wizard will ask if you want to use keyring. If you say yes:
high line 141

Access to system keychain/keyring

SourceSKILL.md
141- Passwords are stored in your system's secure keychain
high line 143

Access to system keychain/keyring

SourceSKILL.md
143- Keyring uses OS-level encryption
high line 145

Access to system keychain/keyring

SourceSKILL.md
145### Manual Keyring Setup
high line 147

Access to system keychain/keyring

SourceSKILL.md
147If you already have a config with plain text passwords, migrate to keyring:
medium line 150

Access to system keychain/keyring

SourceSKILL.md
150# Install keyring
medium line 151

Access to system keychain/keyring

SourceSKILL.md
151pip3 install keyring --user --break-system-packages
medium line 155

Access to system keychain/keyring

SourceSKILL.md
155import keyring, getpass
medium line 158

Access to system keychain/keyring

SourceSKILL.md
158keyring.set_password('imap-idle', username, password)
high line 165

Access to system keychain/keyring

SourceSKILL.md
165### How Keyring Works
high line 167

Access to system keychain/keyring

SourceSKILL.md
167The listener automatically tries keyring first, then falls back to config:
high line 168

Access to system keychain/keyring

SourceSKILL.md
1681. Try `keyring.get_password('imap-idle', username)`
high line 175

Access to system keychain/keyring

SourceSKILL.md
175- ✅ OS-level encryption (macOS Keychain, GNOME Keyring, Windows Credential Manager)
low line 116

External URL reference

SourceSKILL.md
116"webhook_url": "http://127.0.0.1:18789/hooks/wake",
low line 256

External URL reference

SourceSKILL.md
256curl -X POST http://127.0.0.1:18789/hooks/wake \
Scanned on Feb 9, 2026
View Security Dashboard
Installation guide →
GitHub Stars 2.2K
Rate this skill
Categorysales
UpdatedApril 10, 2026
openclaw/skills