Allow disabling Undo Send and Undo Delete delays

Open
#769 4 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@anhnt256 is already working on this.

Since Nov 14, 2026.

  • #791 by @anhnt256 — open

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
Domain
backend, frontend

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

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from maathimself/mailflow

All issues in maathimself/mailflow

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.