Imap Idle Review

This skill appears to implement IMAP IDLE → webhook behavior as described, but review before installing: - Verify webhook_url points to your own OpenClaw gateway (default is localhost). If you set the webhook to a remote service it will receive your email metadata — that is expected behavior but must be intentional. - Inspect the included Python files yourself (scripts/listener.py, scripts/setup.py). The older file scripts/listener_old.py contains personalized logic (hardcoded account and mention checks) and should be removed or audited; leftover code can be a maintenance / privacy risk. - The docs reference an `imap-idle` CLI wrapper (./imap-idle start) which is not obviously present in the shipped files; confirm how the skill is expected to be launched on your system (use scripts/listener.py directly or create your own wrapper). - Prefer OS keyring on desktops; for headless servers follow the SECURITY.md advice: chmod 600 on config, run as a dedicated non-root user, limit network egress, and use disk encryption or secrets management for containers. - Test in an isolated environment or non-production account first. Ensure logs and config files are restricted (600) and monitor network traffic if you want to verify there are no unexpected outbound endpoints. If you want, I can point out the exact lines in the files that reference the hardcoded account/mention logic, and suggest minimal edits to remove or sanitize leftovers.