Skip to content

Feature Suggestion: Scheduled send and send delay#322

Open
lucas-gaitzsch wants to merge 24 commits into
bulwarkmail:mainfrom
lucas-gaitzsch:feature/scheduled-send
Open

Feature Suggestion: Scheduled send and send delay#322
lucas-gaitzsch wants to merge 24 commits into
bulwarkmail:mainfrom
lucas-gaitzsch:feature/scheduled-send

Conversation

@lucas-gaitzsch
Copy link
Copy Markdown
Contributor

@lucas-gaitzsch lucas-gaitzsch commented May 22, 2026

Summary

This PR adds and hardens Scheduled Send support, including scheduled message listing, cancellation, editing, rescheduling, undo behavior, and compose flows. It also improves composer recipient fields for password managers and fixes an empty mail list after returning from settings. The changes address edge cases around S/MIME scheduled messages, attachment-warning sends, multi-account identity capability checks, and preventing normal mailbox actions from bypassing scheduled-send cancellation.

Changes

  • Add Scheduled Send UI flows for listing, viewing, cancelling, editing, and rescheduling scheduled emails.
  • Fix S/MIME scheduled-send cancellation so imported raw emails are deleted instead of being restored as normal drafts.
  • Preserve the selected scheduled-send time when sending anyway from the attachment warning.
  • Use the selected identity’s composer client for delayed-send capability checks in multi-account / Pro Compose flows.
  • Avoid marking scheduled replies/forwards as answered or forwarded until they are actually sent.
  • Enable Scheduled context-menu actions in the Scheduled view and wire cancel/edit/reschedule handlers through the email list.
  • Hide normal hover mailbox actions for scheduled emails to avoid archive/delete/spam/tag actions bypassing scheduled-send cancellation.
  • Add password-manager ignore attributes to recipient fields in the mail composer.
  • Fix an empty mail list after reloading on the settings page and returning to mail.

Related Issues

_

Type of Change

  • Bug fix (non-breaking change that fixes an issue)
  • New feature (non-breaking change that adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update
  • Refactor / code quality improvement
  • Chore / dependency update / CI change

Checklist

  • I have read the Contributing Guide
  • My code follows the project's code style and conventions
  • I have run npm run typecheck && npm run lint and there are no errors
  • The build passes (npm run build)
  • I have tested my changes locally
  • I have added or updated documentation if needed
  • I have updated translations (locales/) if my changes affect user-facing text
  • I have included screenshots or a screen recording for UI changes

Screenshots / Demo

Bildschirmfoto_20260522_180658 Bildschirmfoto_20260522_182013 Bildschirmfoto_20260522_180905

Notes for Reviewers

Please focus on the Scheduled Send edge cases, especially S/MIME scheduled messages, rescheduling from both viewer and list context menus, and ensuring regular mailbox actions are unavailable for scheduled emails.
S/MIME needs thorough review and testing because I do not have or use an S/MIME setup locally.

https://github.com/lucas-gaitzsch/bulwark-webmail/pkgs/container/bulwark-webmail-feature%2Fscheduled-send

@lucas-gaitzsch
Copy link
Copy Markdown
Contributor Author

If you want to merge, please merge as squash commit

@rathlinus
Copy link
Copy Markdown
Member

I will take a look at it tomorrow, thank you very much

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants