Allow disabling Undo Send and Undo Delete delays
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- javascript
Research direction
Start in the frontend ComposeModal, where the issue says the 10-second delay is set, and inspect the existing Settings → Behavior options. Read the send.undo.test.js tests to confirm how undoSeconds: 0 is handled, then trace the Undo Delete countdown to its corresponding frontend and backend paths. Done means users can configure both delays, with zero performing the action immediately; the issue does not identify the relevant files or tests for Undo Delete.
Written by the indexing model from the issue text.
Description
Currently, MailFlow uses a fixed 10-second Undo Send delay in the frontend (ComposeModal), which sends undoSeconds: 10 to the backend.
The backend already supports undoSeconds: 0 for immediate sending, as confirmed by the existing send.undo.test.js tests.
It would be great to have a configurable option to disable this delay entirely.
Suggested implementation:
Add a setting under Settings → Behavior to configure the Undo Send delay (0, 5, 10, 20 seconds).
Setting the delay to 0 should send emails immediately.
Ideally, provide a similar option for Undo Delete, allowing messages to be moved to Trash immediately without displaying a countdown.
Optionally, support a Docker environment variable for setting the default behavior.
This would be especially useful for users who prefer immediate actions rather than delayed execution.
I'd prefer to keep using the official Docker images without maintaining custom frontend patches.
Thanks for considering this feature!
- Dominant language
- JavaScript
- Stars
- 518
- Forks
- 50
- Avg merge
- 4d 45m
- Merged PRs (30d)
- 43
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
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 maathimself/mailflow
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
maathimself/mailflow#801 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
maathimself/mailflow#784 ·
Maintainers usually reply within 1 day
-
defaultShortcuts tests fail on macOSPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
maathimself/mailflow#783 ·
Maintainers usually reply within 1 day
-
Stored mail loses blockquote type=cite, so AI actions read Apple Mail and Thunderbird quoted historyOpen
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
maathimself/mailflow#782 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
maathimself/mailflow#799 ·
Maintainers usually reply within 1 day
All issues in maathimself/mailflow
Similar issues
-
marketing
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Feyisara2108/stellargive#1378 ·
Maintainers usually reply within 1 day
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
blixvip/solana-token-meta#17 ·
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
blixvip/solana-tx-parse#18 ·