[FEATURE] Select and delete all matching emails across all pages
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 52/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- rust
- Domain
- full-stack
Research direction
Start by tracing the archived email list’s current-page “Select all” behavior, then follow how account, folder, and search filters reach deletion and its confirmation. Implement selection across all matching results while preserving those filters and keeping source-provider deletion separate. Done means the confirmation shows the total and the full matching selection can be deleted across pages.
Written by the indexing model from the issue text.
Description
Description
Please add an option to select and delete all matching archived emails across all pages.
Currently, “Select all” only selects the emails displayed on the current page. There is no option to extend the selection to all results.
Suggested behavior:
- Select all emails on the current page.
- Display an option such as “Select all N emails matching this view.”
- Allow deletion of the entire selection.
- Show a confirmation stating the total number of emails to be deleted.
The selection should respect the current account, folder, and search filters.
Purpose / Use Case
Cleaning up a large archive currently requires selecting and deleting emails page by page. This is repetitive and time-consuming when there are thousands of messages.
Selecting all matching results would make bulk deletion much easier.
Additional Information
Bichon version: 2.32.
This request concerns deleting archived emails within Bichon. Any deletion from the source email provider should remain a separate, explicit action.
- Dominant language
- Rust
- Stars
- 2.1k
- Forks
- 91
- Avg merge
- 14h 54m
- Merged PRs (30d)
- 6
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from rustmailer/bichon
-
[BUG] Incremental sync warns "no stored highest_uid" on every round for folders with no new mailOpenbug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
rustmailer/bichon#411 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
rustmailer/bichon#331 · 8 comments ·
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 48/100
rustmailer/bichon#409 · 4 comments ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 38/100
rustmailer/bichon#407 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 22/100
rustmailer/bichon#403 · 2 comments ·
All issues in rustmailer/bichon
Similar issues
-
bug UI
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
wardian-app/Wardian#1746 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
jlcodes99/cockpit-tools#3125 ·
Maintainers usually reply within 2 days
-
bug user-sprint
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Vondor/KassenSturz#967 ·
Maintainers usually reply within 1 day
-
area/ci
Difficulty 1/5 Under an hour Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
ImageGen generate-batch aborts valid JSONL jobs containing a Unicode line separator in poster textOpenbug imagen skills
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day