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
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: