// SENDER PURGE

SCAN THE SENDERS.
UNSUBSCRIBE IN BULK.

The problem is not “another mail client.” The problem is years of subscription mail. InboxPurge connects Gmail through Composio OAuth (no Google Cloud Console app). Scan unique senders by volume, unsubscribe headers, classify marketing/notification/transactional/ personal/spam via dispatch (haiku-class, ≤150 unclassified per run). Filter chips, domain filter, sortable table. Detail: metadata, cached mail, action history. Body in sandboxed iframe from Composio. Actions: unsubscribe, whitelist, ignore, restore — 1–100 bulk. RFC 8058 one-click POST with mailto/http-visit/manual fallbacks and SSRF/domain allowlist. Daily cron: 10 days later, still getting mail? verified or failed. Grace window indicators. Never SMTP-sends as you. Login; public landing. Not Gmail’s UI.

Premier Composio OAuth RFC 8058 SSRF guard
Open InboxPurge How it works
150
Classify batch
100
Bulk cap
10d
Verify cron
OAuth
Composio
// HOW IT WORKS

Five steps from OAuth to a verified unsubscribe

One-click POST is not a guaranteed List-Unsubscribe-Post success. The 10-day check is the honesty.

01
Connect Gmail
Composio OAuth. No GCP client you manage.
02
Scan senders
Volume, unread, headers, dates.
03
Classify optional
AI ≤150. Chips + domain filter.
04
Act
Unsub/whitelist/ignore/restore, bulk 1–100. RFC 8058 + fallbacks + SSRF allowlist.
05
Verify later
Cron at +10 days. Grace indicators.
Open InboxPurge
// TABLE

Senders by volume — CSS mock

Not Gmail. Not Superhuman. Not a harvested inbox screenshot.

meltuc.tech/inboxpurge/app — CSS mock, not a product screenshot
Sortcount/date/name
Classmarketing…spam
Bulk1–100
// UNSUB

RFC 8058 with a guardrail

SSRF/domain allowlist. mailto and visit fallbacks.

meltuc.tech/inboxpurge/app · unsub — CSS mock, not a product screenshot
POSTone-click
Fallbackmailto/http
GuardSSRF
// VERIFY

Ten days later, did it actually stop?

verified vs failed. Not a toast that lied on day 0.

meltuc.tech/inboxpurge · cron — CSS mock, not a product screenshot
Wait10 days
Gracewindow UI
Bodysandboxed iframe
// PRIVACY

Your Gmail, your session

Public landing has no sender list. Bodies stay behind login + sandbox.

// WHAT IT REFUSES

No GCP app setup. No unguarded fetch.

Will not send mail as you except the RFC unsubscribe POST. Will not dump the inbox on /inboxpurge/.

// WHO THIS IS FOR

Someone with a 40k inbox

Focused purge session. Not Email Manager, not ReplyCraft.

// FEATURES

Connect, cluster, cut, verify

Cards match InboxPurge README.

🔑
Composio OAuth
No GCP console.
📊
Sender rollup
Volume + headers.
🧠
Classify
≤150 / run.
🔎
Filters
AI chips + domain.
📋
Detail
History + cached mail.
🖼
Sandbox body
iframe live fetch.
🚫
Unsub bulk
RFC 8058 + fallbacks.
🛡
SSRF guard
Allowlist.
✅
10-day verify
Cron honesty.
// GET STARTED

Connect Gmail. Cut the list, not the archive blindly.

Login for /inboxpurge/app. This page is not your inbox.

Open InboxPurge

Requires a MelTuc account. Create one free.

// SAID SLOWLY

What stays true over time

Gmail inbox cleanup — discover mass senders, unsubscribe in bulk, reclaim your inbox. Health stays cheap. If this page disagrees with the signed-in app, trust the app — the product contract and tests enforce that rule.