Rework "subscribed" mailbox semantics #69

Closed
opened 2020-07-05 19:24:25 +03:00 by Manos Pitsidianakis · 1 comment

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?
Manos Pitsidianakis added this to the release milestone 2020-07-05 19:24:25 +03:00
Manos Pitsidianakis added the
invalid
question
IMAP
JMAP
labels 2020-07-05 19:24:25 +03:00

Closed in #169

Closed in #169
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: meli/meli#69
There is no content yet.