Skip to content

mooserini/apple-and-icloud-mail

v0.1.0MIT

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

Changelog — IMAPIIe Now

IMAPIIe Now is an independent community project with no Apple affiliation or endorsement. Its canonical package ID remains apple-and-icloud-mail.

[0.1.0] — Unreleased

Initial release-prep tree; this section describes the candidate, not a published release or proof of live mail access.

Added

  • Portable, skills-only MIT package with a root plugin.json manifest, display name IMAPIIe Now, and an offline setup-review default prompt.
  • icloud-mail-setup skill plus account, execution-platform, transport, and proof-check references. Guidance distinguishes offline inventory, authentication, exact-folder headers, and scoped body-read evidence.
  • Exact host/account/folder/selection/route authorization boundaries, verified Apple IMAP TLS, non-mutating read requirements, and scoped Himalaya fallback guidance for separately configured tools.
  • One operator-held app-specific password policy with internal call-time resolution, transient provisioning cleanup, and explicit rotation boundaries.
  • Security reporting and privacy policies; Git ignore rules for secrets, private keys, and operator configuration.
  • Three examples: a one-line unauthenticated setup review, an offline inventory, and an explicitly scoped live headers-only authorization template.
  • README, MIT license and retained attribution notices, banner assets with provenance notes, and IMAPIIe Now icon assets.

Scope and limitations

  • No runtime, mail account, server, credential store, hook, watcher, MCP configuration, or executable mail helper is bundled. GigaMail and Himalaya remain separate dependencies on the approved execution host.
  • No Apple Mail automation or Calendar, Contacts, Drive, Photos, or Keychain integration. No sending, moves, deletion, flag changes, or background scans are authorized by installation.
  • Portable instructions do not prove host discovery, remote live access, authentication, unread-flag preservation, or secret-safe live failures. Offline, synthetic, and live evidence must be reported separately.
  • Release publication, catalog submissions, and live checks require their own review and authorization; this tree does not claim they have occurred.