For existing messages, search for the sender, review the results, and use Gmail’s permanent-delete controls. For future messages, a filter can move mail to Trash, but permanent deletion requires a separate step. Decide whether you need a one-time cleanup or ongoing automation before granting a tool access.
Delete selected messages manually
- Open the intended Gmail account on a computer. Search
in:anywhere from:sender@example.com, replacing the example address.in:anywhereincludes Spam and Trash. Google’s search-operator reference. - Review the actual sender addresses and the selected messages. Conversation view can group replies from different people; do not delete a whole conversation without checking what it includes.
- For matching mail outside Trash or Spam, select only the intended messages and use Delete to move them to Trash.
- In Trash, search
in:trash from:sender@example.com, review the selection and use Delete forever. In Spam, searchin:spam from:sender@example.comand use Delete forever for only the intended messages. - Repeat the original search to check for remaining messages. Gmail may show only one page of results; review any option to select all matching conversations before using it.
Delete forever cannot be undone through Gmail’s normal recovery flow. Save anything you need before deleting it. Empty Trash and Delete all spam messages now are whole-folder operations, not sender-specific substitutes. Google’s deletion instructions.
Compare Gmail, BYE!, Block Sender and Clean Email
Permanent deletion is different from moving mail to Trash. The comparison below separates BYE!’s inspected code from competitors’ published instructions. It is not a hands-on ranking of the products.
| Option | Useful when | Limit to account for |
|---|---|---|
| Gmail filter | You want future matching messages moved out of the Inbox. | Delete it moves mail to Trash; it does not immediately purge it. |
| Google Apps Script + Gmail API | You can maintain code and want control over the search and schedule. | Requires authorization, narrow queries, error handling and quota monitoring. A time-driven trigger is not an instant delivery-time block. |
| BYE! 0.1.8 | You want a user interface for sender rules and periodic Trash cleanup. | Inspected automatic query covers Trash. It needs the extension runtime and backend; Spam clearing is a separate broad operation. |
| Block Sender | You want incoming messages matching a rule permanently deleted. Its guide documents a “Delete (skip trash)” option. | This is a vendor-documented feature, not a result from our own test. Existing Spam/Trash cleanup and browser-closed operation need separate verification. Block Sender instructions. |
| Clean Email | You want mailbox cleanup rules. Its documentation lists permanent Delete as an Auto Clean action, separately from Trash. | Its Block action and its permanent Delete action should not be treated as identical. Check the rule’s selected messages, folder and action before enabling it. We have not tested its deletion outcomes. Supported actions · Auto Clean rules. |
| Workspace administrator rule | Your organization wants to reject a sender before normal mailbox delivery. | Needs administrator access and appropriate configuration; not a personal Gmail control. |
A script need not run in a local browser: Apps Script time-driven triggers run on Google’s infrastructure. Conversely, BYE!’s inspected cleanup is initiated by the Chrome extension. Neither approach should be called universally safer, cheaper or more reliable without comparable testing.
Which option fits your Gmail problem?
For a one-time cleanup: use Gmail’s search and Delete forever controls after reviewing the messages. For ongoing sender cleanup in Trash: BYE! provides sender rules and periodic deletion while its extension can run. For broader automation: compare the exact folder scope and action in Block Sender or Clean Email; a product’s “Block” label alone does not tell you whether messages are permanently deleted.
If automatic sender-specific deletion from both Spam and Trash is essential, BYE!’s inspected 0.1.8 automatic path does not yet establish that coverage. Its separate Spam-clearing button empties the folder. Choose based on a disposable-mailbox test, not a promise that every “blocker” works the same way.
Competitor documentation checked September 12, 2026. Features may change. This comparison is published by BYE!’s maker and does not claim independent testing of competing products.
What we checked in BYE! 0.1.8
Eight isolated source-contract checks passed. They confirmed Trash-only sender searches, Gmail filter actions, batch-delete calls, no scheduled request when logged out, broad Spam-clearing queries, and alarm creation. No real messages were deleted in these tests.
A fresh installation requests a one-minute repeating alarm. The installer preserves an existing alarm, so an older interval can persist. Chrome can delay alarms, and sleep does not make a device wake for cleanup. A fixed “gone within one/five minutes” promise is therefore inappropriate. Chrome alarm behavior.
Before relying on automatic deletion, test your sender rules with disposable messages and include unrelated messages as controls. Check both correct sender matching and completion across large result sets.
Before choosing BYE!
Read the permissions and data-flow guide. Confirm the selected account and folder. Do not use whole-folder cleanup for a sender-only task. If you need continuous deletion while Chrome is fully stopped, the inspected extension path does not establish that capability.
Published by BYE!’s maker. Source inspection and mocked tests: September 12, 2026, extension 0.1.8. Live Gmail timing, folder interaction and deletion outcomes remain to be validated in a disposable test mailbox.