Auto-File iCloud Mail Attachments via IMAP

If your email is at @icloud.com, @me.com, or @mac.com, you've already discovered the bad news.

Apple has no automation API for iCloud Mail. There are no rules-based attachments-to-iCloud-Drive flows. There's no Shortcut that runs server-side when new mail arrives. There's no Apple-blessed equivalent of Power Automate. Mail.app on macOS has rules, but they only run while Mail.app is open on your laptop, which it usually isn't, and they can't write to iCloud Drive folders the way Drive's own UI can.

Apple has zero plans to add any of this. They've had 15 years to ship "save iCloud Mail attachments to iCloud Drive" and they've never even hinted at it. It's not on the roadmap because there is no public roadmap.

The workaround is older and uglier than any of this: IMAP. Same protocol your phone uses to talk to mail.example.com in 2003. Apple supports it for iCloud Mail, mostly because they have to. AutoFileEmail uses it.

This is the working setup for @icloud.com users.

Table of Contents

• What you'll need before you start
• Generating an app-specific password at appleid.apple.com
• Connecting iCloud Mail to AutoFileEmail
• Pick your destination cloud
• What the folder structure looks like
• The honest IMAP caveat
• Outlook (the other IMAP-friendly Apple alternative)
• What we don't do (and what Apple doesn't let us do)
• Setup recap
• TL;DR

What you'll need before you start

Three things:

1. An iCloud account with Mail enabled.
2. An app-specific password from Apple. (Two-factor auth required, which it should be already.)
3. Five minutes.

That's it. No developer account. No paid Apple Business plan. No Mac required - this all works from any browser.

Generating an app-specific password at appleid.apple.com

Apple won't let third-party apps log into iCloud Mail with your real password. You have to generate a one-off "app-specific password" instead. This is good. It means if AutoFileEmail's password gets compromised somehow, you revoke that one password and your real Apple ID is untouched.

The flow:

1. Go to appleid.apple.com and sign in.
2. Sign-In and Security section. Click "App-Specific Passwords."
3. Click "Generate an app-specific password."
4. Label it something like AutoFileEmail so you remember why it exists.
5. Apple shows you a password like abcd-efgh-ijkl-mnop. Copy it. You only see it once.

Keep that tab open. You'll paste the password in AutoFileEmail's IMAP form in the next step.

If you don't have two-factor auth on your Apple ID, Apple won't let you generate an app-specific password. Turn on two-factor first. Same Sign-In and Security page.

Connecting iCloud Mail to AutoFileEmail

In onboarding, after the cloud step, you'll see "Connect inbox" with three tiles: Gmail, Outlook, IMAP.

Click IMAP.

The form looks like this:

• Email address: you@icloud.com (or @me.com / @mac.com)
• App password: paste the one you just generated
• IMAP host: auto-fills to imap.mail.me.com
• IMAP port: auto-fills to 993
• TLS: auto-checked

The auto-fill is keyed off the @icloud.com / @me.com / @mac.com part of the address. You don't have to look anything up. Hit "Connect."

AutoFileEmail tries the IMAP login. If the password's right and Apple is happy, the form clears and you see "iCloud Mail connected" with a green checkmark. If something's off (most often a typo in the app password), the form shows the error and you re-paste.

Pick your destination cloud

Next step in onboarding: cloud destination. Three tiles: Google Drive, OneDrive, Dropbox.

Drive is most common for @icloud.com users in our data so far. Apple users tend to like Drive's drive.file scope (we only see folders we created, never the rest of your Drive) for the same reason they like Apple's privacy story - narrow scopes, sandboxed access.

OneDrive and Dropbox both support App folder mode, which is even tighter. Files land in /Apps/AutoFileEmail/ and we cannot see, list, or touch anything else in those clouds.

Honest take: a privacy-conscious Apple user filing iCloud Mail receipts via IMAP into Dropbox App folder mode is just about the leakiest-protected workflow you can pick. Apple doesn't trust us with anything beyond the IMAP credentials you generated specifically for us. Dropbox doesn't even let us see anything outside our sandbox. We can read receipts via IMAP, write them to one folder via App folder mode, and that's the end of our access in any direction.

For folder structure deep-dive across clouds, see the Outlook + OneDrive freelancer's filing setup - the same {vendor}/{YYYY}/{MM}/ layout applies regardless of cloud.

What the folder structure looks like

Whichever cloud you pick, the structure is identical:

/Apps/AutoFileEmail/
  amazon.com/
    2026/
      05/
  stripe.com/
    2026/
      04/
        2026-04-14-invoice.pdf
      05/
  apple.com/
    2026/
      05/
        2026-05-09-receipt.pdf
  notion.so/
    2026/
      05/

/Apps/AutoFileEmail/
  amazon.com/
    2026/
      05/
  stripe.com/
    2026/
      04/
        2026-04-14-invoice.pdf
      05/
  apple.com/
    2026/
      05/
        2026-05-09-receipt.pdf
  notion.so/
    2026/
      05/

(Drive omits the /Apps/ prefix; OneDrive and Dropbox include it because of App folder mode.)

One folder per registrable sender domain. noreply@email.apple.com becomes apple.com. do-not-reply@amazon.com becomes amazon.com. The whole point of registrable-domain routing is that two emails from the same vendor land in the same folder no matter which subdomain Apple/Amazon/Stripe used to send it.

Year and month subfolders. Files keep their original names with the email date prefixed.

The honest IMAP caveat

iCloud Mail rate-limits IMAP harder than Gmail does. This is real and worth knowing.

A fresh AutoFileEmail account talking to iCloud Mail will, on first connect, want to run the 30-day historical preview backfill. That's roughly 100-300 IDLE / FETCH operations against Apple's IMAP servers, depending on how busy your inbox is. Apple is fine with that pace.

What Apple is not fine with: hammering IMAP with parallel connections. The autofile worker pools connections (one IMAP connection per account, reused across fetches) so we don't trip Apple's per-account rate limits. You won't see a LOGIN throttled error in normal operation.

If you buy a Backfill Pack and run a full 3-year retroactive scan against an iCloud account, the backfill runs slower than it would against Gmail or Outlook. Think hours instead of minutes for a heavy inbox. Apple's IMAP throughput is the bottleneck, not us. You can close the tab and check back later - the job runs server-side regardless.

For comparison: a Gmail backfill of the same scope might finish in 20 minutes. iCloud might take 4 hours. Same eventual outcome, longer wait.

Outlook (the other IMAP-friendly Apple alternative)

Quick note for completeness: some Apple users run an @outlook.com or @hotmail.com Microsoft personal account alongside iCloud, because it's free and the spam filter is decent. If that's your stack, you can connect via Outlook OAuth instead of IMAP - same Mail.Read scope, same setup, less friction than the app-password dance.

For everyone whose primary mail is genuinely iCloud, IMAP is the only path and it works fine.

What we don't do (and what Apple doesn't let us do)

Worth being explicit:

• No outbound mail. IMAP read-only login. We can fetch messages and attachments. We cannot send, reply, mark-as-read, or change anything in your inbox. The IMAP commands for those exist; we don't issue them.
• No OCR. The PDF in your cloud folder is the same PDF the sender sent. Apple's privacy story means we'd never store parsed receipt data even if we wanted to.
• No "scan all your devices" magic. We don't have access to iMessage, Reminders, Notes, Photos, Health, or anything else on your iCloud account. The app-specific password gives us exactly one thing: IMAP read access to Mail.
• No on-device processing. Despite the iCloud branding, this all happens server-side, not on your iPhone or Mac. AutoFileEmail's backend talks to Apple's IMAP servers directly. Your devices don't need to be on or even logged in.

If Apple ships a real automation API for iCloud Mail in 2027, we'll add it. Until then, IMAP is the answer.

Setup recap

The full Apple-user setup, click by click:

1. appleid.apple.com - generate an app-specific password.
2. Sign up at autofile.email.
3. Pick your cloud destination (Drive, OneDrive, or Dropbox). OAuth into it.
4. Click IMAP, paste your @icloud.com address and the app-specific password, hit Connect.
5. Done. Polling starts in 30 seconds.

The 30-day historical preview backfill kicks off automatically. April's receipts populate in your destination cloud over the next few minutes (or hours, if you've got a heavy iCloud inbox).

If you want a full tax year retroactively filed, the $29 Tax Year Pack covers it. One-time. No subscription. Plan for the backfill to run longer than it would on Gmail because of Apple's IMAP throttling.

Full integration walkthrough at /integrations/imap-drive (the Drive variant; the OneDrive and Dropbox variants follow the same flow).

TL;DR

• iCloud Mail has no automation API. Apple has no plans to ship one. IMAP is the only path.
• Generate an app-specific password at appleid.apple.com, paste it into AutoFileEmail's IMAP form. Host and port auto-fill from the @icloud.com domain.
• Pick a destination cloud (Drive most common; Dropbox or OneDrive most privacy-tight via App folder mode).
• Files land in /Apps/AutoFileEmail/{vendor}/{YYYY}/{MM}/ (or /AutoFileEmail/... on Drive). Same structure as Gmail-based setups.
• iCloud rate-limits IMAP harder than Gmail; backfill jobs run slower against iCloud. AutoFileEmail's connection pool handles the throttling for you.

Free for one inbox + one cloud. 30-day historical preview included. The leakiest-protected receipt-filing workflow Apple users can pick is iCloud-via-IMAP into Dropbox App folder mode, and it takes five minutes to set up.

We don't read your receipts. We just file them.