---
name: inbox-cleanup
description: Use when someone has an overloaded email inbox with thousands of old messages and wants a one-off cleanup (archive everything older than a date, mass unsubscribe, filters) followed by a maintenance habit. Distinct from [[3-21-0-inbox-system]] (an ongoing routine, not a backlog clearance), [[focus-blocker]] (limits access to distractions), and [[text-shortcut-system]] (speeds up typing replies).
---

# Inbox Cleanup

An overloaded inbox is mostly old mail nobody will read, plus a smaller
number of messages that need action. A one-off cleanup separates the two
quickly: archive the backlog, cut the incoming flood at its source, set
filters, and leave a short maintenance habit. This skill produces a
step-by-step plan for the user's own email service.

## Input required

- **Email service and client** (web, desktop, phone) and whether more
  than one account is involved.
- **Size of the backlog**, roughly: how many messages, how far back.
- **What must be kept**: receipts, legal, work records, anything with a
  retention need.
- **Who sends the volume**: newsletters, shops, notifications, lists.
- **Current habits**: when and how often they check.

## Questions to ask first

Ask in **one batch of at most five questions**, skipping any already
answered:

1. Which email service do you use, and roughly how many messages are in
   the inbox?
2. Is there an obvious date before which nothing is likely to be urgent?
3. Which messages must you keep for records (receipts, contracts, tax)?
4. Which senders send you the most mail you do not read?
5. Does your service support filters or rules, labels or folders, and
   search by date?

## Method

1. **Back up first if the stakes are high.** If the mailbox holds
   important records, check that the service can export or that the
   important mail is already saved elsewhere before bulk actions.
2. **Protect the recent and the essential.** Star, label, or move to a
   folder the messages that really need action now. Keep this set small.
3. **Archive the backlog by date.** Pick a cutoff, search for everything
   older than that date, select all matches (including beyond the visible
   page, where the service offers it), and archive. Archiving removes
   mail from the inbox but keeps it searchable. Deleting removes it,
   possibly permanently after a trash period. Choose archive when unsure.
4. **Find the loudest senders.** Sort or search by sender, or use the
   service's bulk views, to see who sends the most.
5. **Unsubscribe in bulk, carefully.**
   - Prefer the unsubscribe link or button the email service itself
     provides, or the sender's own account settings.
   - Be careful with unsubscribe links in mail from senders you do not
     recognize. For suspicious, unexpected, or spam messages, the link may
     confirm your address is live or lead to a phishing page. Mark those
     as spam or junk instead.
   - Never enter passwords or payment details on a page reached through
     an unsubscribe link.
   - Expect a few messages to arrive after unsubscribing; check the
     sender's own wording for how long it takes.
6. **Add filters for what remains.** Create rules to label, skip the
   inbox, or auto-archive predictable mail such as receipts, alerts, and
   newsletters the user wants but not immediately. Name labels clearly
   and test each filter on existing messages first.
7. **Set the inbox's job.** Decide the inbox is for items needing a
   decision only. Everything else is archived, labeled, or filtered.
8. **Install a maintenance habit.** Short, scheduled processing with a
   clear rule for each message: reply, do, delegate, defer, or archive.
   For an ongoing routine see [[3-21-0-inbox-system]].

## Output format

- **Cutoff date** and the exact search or filter to use.
- **Keep list:** what to protect before archiving.
- **Unsubscribe list:** sender, action, and suspicious ones to mark as
  spam instead.
- **Filter list:** condition and action for each.
- **Maintenance habit:** frequency, length, and the decision rule.
- **Undo notes:** where archived mail lives and how to restore it.

## Ground rules

- **Archive, do not delete,** unless the user explicitly chooses to
  delete and understands it may be permanent.
- **Warn about unsubscribe links** from unknown senders; prefer the mail
  service's own control or mark as spam.
- **Never ask for passwords** or message contents containing sensitive
  data. Describe steps; the user runs them.
- **Check records and retention.** Business, legal, or tax mail may have
  a required retention period that varies by country and organization;
  check current official guidance.
- **Describe capabilities, not menus,** since each service's interface
  and limits differ.

## Self-check before answering

- Is the cutoff date explicit, with archive as the default action?
- Are important records protected before the bulk action?
- Are suspicious senders handled as spam, not by clicking unsubscribe?
- Are filters tested before they are trusted?
- Is the maintenance habit short enough to keep?

## Common pitfalls

- **Deleting instead of archiving** — mail the user later needs is gone.
- **Clicking unsubscribe on spam** — confirms the address or reaches a
  scam page.
- **Cleaning once, with no habit** — the inbox refills within weeks.
- **Overbroad filters** — important mail is auto-archived and missed.
- **Selecting only the visible page** — the backlog barely shrinks.
- **Archiving before protecting action items** — real tasks disappear
  from view.

## Example prompt

> My inbox has about 30,000 messages and I can't find anything. Help me
> plan a one-time cleanup: archive everything older than the start of
> last year, unsubscribe from the senders I never read, add filters for
> receipts and newsletters, and set a simple habit to keep it clear.

## Learn more

- [[3-21-0-inbox-system]] for the ongoing routine after the cleanup.
- [[text-shortcut-system]] for answering recurring emails faster.
- [[information-diet]] for choosing which newsletters deserve a place.
- [[tab-management]] for the same clutter approach in the browser.