#41 Rework "subscribed" mailbox semantics

Open
opened 1 month ago by epilys · 0 comments
epilys commented 1 month ago

Right now, mailboxes have to be “subscribed” in order to be shown in meli. That comes in opposition with the concept of server-side subscription in remote backends such as IMAP.

Questions to be resolved:

  • Should configuration file subscriptions be ignored in favour of server side subscription? Should it be an error?
  • How to communicate the existence of unsubscribed mailboxes to the user?
  • Server side subscription can be set with commands. What is a better word to call config-file subscription to avoid this conflict in meanings?
Right now, mailboxes have to be "subscribed" in order to be shown in `meli`. That comes in opposition with the concept of server-side subscription in remote backends such as IMAP. Questions to be resolved: * Should configuration file subscriptions be ignored in favour of server side subscription? Should it be an error? * How to communicate the existence of unsubscribed mailboxes to the user? * Server side subscription can be set with commands. What is a better word to call config-file subscription to avoid this conflict in meanings?
epilys added this to the release milestone 1 month ago
epilys added the
invalid
label 1 month ago
epilys added the
question
label 1 month ago
epilys added the
IMAP
label 1 month ago
epilys added the
JMAP
label 1 month ago
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.