mirror of
https://github.com/cypht-org/cypht.git
synced 2026-04-25 04:56:03 +03:00
[GH-ISSUE #576] Delay-send / "Send later" / Scheduled sending #413
Labels
No labels
2fa
I18N
PGP
Security
Security
account
advanced_search
advanced_search
announcement
api_login
authentication
awaiting feedback
blocker
bug
bug
bug
calendar
config
contacts
core
core
devops
docker
docs
duplicate
dynamic_login
enhancement
epic
feature
feeds
framework
github
github
gmail_contacts
good first issue
help wanted
history
history
imap
imap_folders
inline_message
installation
keyboard_shortcuts
keyboard_shortcuts
ldap_contacts
mobile
need-ssh-access
new module set
nux
pop3
profiles
pull-request
question
refactor
release
research
saved_searches
smtp
strategic
tags
tests
themes
website
wordpress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/cypht#413
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @nekohayo on GitHub (Jul 15, 2022).
Original GitHub issue: https://github.com/cypht-org/cypht/issues/576
Originally assigned to: @amaninyumu1 on GitHub.
Issue #572 talks about snoozing (i.e. hiding a received email from the inbox for a certain amount of time), but what I'd like to suggest here is a different feature. The usecase for me is this:
Business or events-related outreach emails typically have a context/timing-sensitive aspect, so I'd like to be able to schedule them (especially considering the timezone of the person I'm contacting)
When dealing with public-facing businesses, it is often counterproductive to send emails on certain days or hours (ex: Friday afternoons, when you know everything is likely to be forgotten over the week-end), so you want to schedule your email for a better time during business hours (ex: Tuesday morning).
Human-centric staff managers and directors like me know that it is better to schedule mails to staffers to their business hours, avoiding emails that would arrive outside work hours and cause undue stress or cognitive load. Basically, mindfulness for staffers' "right to disconnect".
The corresponding issue in my local mail client (where some technical approaches are mentioned) is https://gitlab.gnome.org/GNOME/evolution/-/issues/411#note_874473
@marclaporte commented on GitHub (Oct 18, 2022):
See also: https://github.com/jasonmunro/cypht/issues/641
@dumblob commented on GitHub (Oct 18, 2022):
Yeah, I outlined an envisioned potential implementation in #641 . Feel free to take a look.
@dumblob commented on GitHub (Oct 18, 2022):
Regarding the proposal of the "local approach" in https://gitlab.gnome.org/GNOME/evolution/-/issues/411#note_874473 I do not think it is viable for Cypht. It simply has to be "fire and forget" - i.e. closing the web site (incl. suspending the web browser tab) must not hinder this functionality in any way.
@nekohayo commented on GitHub (Nov 3, 2022):
A bit like the "snooze" counterpart, I've requested clarification on JMAP side at https://github.com/jmapio/jmap/issues/373 because it is unclear to me (perhaps because I'm not familiar with such things as protocols and specs and whatnot)
@marclaporte commented on GitHub (Aug 12, 2023):
Is this supported by IMAP/SMTP?
If not (how) can this be done without a cron job?
@marclaporte commented on GitHub (Aug 12, 2023):
Some ideas from Roundcube: https://github.com/roundcube/roundcubemail/issues/8110
@marclaporte commented on GitHub (May 20, 2024):
Much to my surprise, this issue is number 3 for most reactions:
https://github.com/cypht-org/cypht/issues?q=is%3Aissue+is%3Aopen+sort%3Areactions
@marclaporte commented on GitHub (May 20, 2024):
Ok, let's do this with the proposed standards for JMAP and SMTP. Let's not try to do this in a non-standard way as it would be a lot of work:
Step 1: Find mail servers that implement https://www.rfc-editor.org/rfc/rfc4865 and sendAt https://www.rfc-editor.org/rfc/rfc8621.html#page-76
Step 2: Code it :-)
@marclaporte commented on GitHub (Mar 18, 2025):
Done!
https://github.com/cypht-org/cypht/pull/1091