-
Notifications
You must be signed in to change notification settings - Fork 114
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature request: Snoozing messages #225
Comments
Sounds reasonable, and indeed it is functionality provided by other mail clients/systems. There is an expired internet-draft about a snooze extension to IMAP and JMAP. A quick skim makes me think the expected implementation is also to move a message to temporary snooze mailbox (or perhaps a hierarchy within a snooze mailbox), with the messages being moved back when the timer expires. The IMAP extension would make it possible to set desired end date/time. But clients won't support it. Your approach of moving a message to a mailbox with the name of a schedule seems like a good way to make it work with any existing client. The webmail client could get its own functionality. I think the new implementation concept for mox would be the timer that activates at the end of the snooze time, to move the message back. It won't be too complicated to implement. But does mean mox should probably parse all account message index database files, and schedule a timer for the first message to expire, or keep info about the earliest snooze deadline for each account in a single database file it opens at startup (this latter option seems better). It may also be possible to use labels/tags/flags to trigger snooze functionality: setting a flag like "snooze:2 days" on a message would add the flag, and also move the message to the snooze folder (and perhaps clear the snooze label immediately, or when it is moved out of the snooze folder). However, there will be clients (like Thunderbird) that don't use the IMAP flags/labels/tags directly, they create flags like "$label1" and only use the human-entered title within the mail client (so mox can't see and act on it). I won't have time to work on this any time soon, but I can give pointers to anyone interested in implementing it. |
Thank you for consideration. I fully understand there are probably more important things right now. Thinking about it again: Mox already executes "special behavior" when messages are moved to the Junk folder, doesn't it? It shouldn't bee too hard to implement, then. I might have some more time early next year, so I may have a Go at it then. |
Correct. And also for a few other mailboxes (configurable). See https://github.com/search?q=repo%3Amjl-%2Fmox%20JunkFlagsForMailbox&type=code. The difference is that the snooze functionality requires a timer, to make changes later on. The junk/notjunk flags action can be taken immediately. But indeed the snooze functionality may have to be triggered at the same kind of places (in the code). |
Some mail providers allow you to "snooze" a message for a given time. The message will be removed from your Inbox, and re-appear as an unread message at the time you specified.
Before switching to Mox, I used a script similar to Dovecot Snooze for this purpose, which ran as a simple cronjob.
I think the implementation is simple, yet effective. A special
Snooze
folder is created, and with it a set of subfolders likeSnooze.Until Friday 18:00
. At the mentioned time, all messages within that folder will be moved toInbox
and marked as unread. Mail clients will generally trigger a new message notification when this happens.Discussion questions:
I consider this a low priority/nice to have feature, but I find it very useful and I wanted to mention it.
What do you think?
The text was updated successfully, but these errors were encountered: