Skip to content

mooserini/apple-and-icloud-mail

v0.1.0MIT

IMAPIIe Now — platform-agnostic IMAP setup guidance and bounded connection checks.

GitHub

IMAPIIe Now

IMAPIIe Now — MIT license IMAPIIe Now — GitHub release IMAPIIe Now — GitHub stars IMAPIIe Now — platform-agnostic

A platform-agnostic IMAP plugin. Portable setup guidance + bounded connection checks any agent platform can adapt.

IMAPIIe Now banner

Which door for IMAPIIe Now?

  • Copilot / Cursor / OpenClaw: zero changes — start with the skill.
  • Claude: a .claude-plugin wrapper is coming.
  • Hermes: tap today; catalog next.
  • OpenAI: directory submission pending.
  • Everyone else: keep reading.

Canonical package ID: apple-and-icloud-mail (directory + manifest name, unchanged).

IMAPIIe Now combines IMAP + IIe, a nod to the Apple IIe; no Apple affiliation or endorsement.

Calendar, Contacts, Drive, Photos, Keychain, and Apple Mail automation are outside scope.

What it is

Skills-only, MIT-licensed guidance for IMAP setup and exact-folder connection checks. No runtime, account, server, credential store, hook, watcher, MCP config, or executable mail helper is bundled. Himalaya and GigaMail remain separately installed dependencies on the host doing the work.

One skill, four capabilities:

  1. IMAP setup guidance and staged connection checks (authentication verified → exact-folder headers verified → scoped body read verified).
  2. Exact-folder bridge selection, with a configured Himalaya fallback.
  3. Per-user account and credential instructions.
  4. Explicit Mac-required / configured-host / remote-capable route labels.

Read the skill for the workflow. References: accounts · platforms · transports · proof-checks.

Insurance, not overcoverage

Two lanes, same app-specific password: GigaMail scoped reader primary, Himalaya fallback (proven first, zero provisioning — the rollback when one chokes). Same secret, same fate — different tool failure modes. Fallback never repairs a shared invalid credential; it covers tools, not trust.

Credentials: one copy, purge the rest

  • The human hand-places one app-specific password in their operator-approved host-side secret store (default: own .env as APPLE_IMAP_PWD). Agents verify around it — the value never enters model context, logs, or reports.
  • Live reads resolve that one stored value at call time (same pattern as Himalaya's password.command). No second copy in a bridge store, no symlink at the whole store.
  • Any bridge provisioning is transient: after the approved read, remove the provisioned secret and temp artifacts, verify back to one copy, report the cleanup. Retention as a working credential needs its own documented exception.
  • Why: even a harmless leftover in a shared folder confuses multi-agent hosts, shadowing rotation with stale creds.

Try it without authenticating

One-line prompt · Offline inventory · Scoped live-read proposal (separate authorization required).

Use IMAPIIe Now to review my IMAP setup without authenticating.

Offline inventory, manifest/skill validation, and link checks run with no mail access. Publishing honest docs needs no authentication; any live mail proof needs its own concrete authorization (exact host, account, folder, selection, route).

Provenance

Banner: grand-reveal art, operator-nominated (see assets/PROVENANCE.md). Original retained as canopy; crops are center-crops. Earlier smoke candidates live outside this package. Legacy lettering in the art predates the display name IMAPIIe Now.

Install / rollback

After review + separate authorization: copy this folder into a plugin directory, add one marketplace entry pointing at it (OpenAI packaging), test discovery in a fresh chat. Rollback = remove that entry + folder only. No accounts touched, no passwords revoked. Catalog submissions (Claude, Hermes, others) are tracked as next steps — this tree is the portable source they all adapt from.

License

MIT — see LICENSE (Thomas Kenny / mooserini) + NOTICE.md (retained hermes-openwhispr MIT notice for adapted docs).