Fails on larger numbers of folders.

A workaround configuration that aligns the behaviour of listeners with the behaviour of imap_servers may look as follows, splitting the backend configuration in to one imap_server with { tls, starttls } and one with { tls, true }:

Closed in favour of T928.

Closed in favour of T928.

EDIT: Not the comment I wanted here.

No task description.

No task description.

No task description. Please clarify and reopen if necessary.

Using a { port, 143 }, { tls, starttls } backend does present the client with the necessary capabilities and allows the client to use STARTTLS.

In further troubleshooting, of course this happens while the frontend is on a STARTTLS port, but the backend is on an implicit SSL port -- the capabilities presented to the client match those of the server w/ implicit SSL.

Not sure what commit(s) were related to this ticket for it to have been allowed to move to the Review column, but rG93aef46dc20861092df417703405545e1e0f76b8 with rEIc50001375e81662cae40914dcae9745273765f7b does not present STARTTLS LOGINDISABLED to the client;

There's quite some items that may fall out of the actual implementation of just the collaborative editing server and client components not being as feature-complete as a full desktop client, with priorities to be established on a case-by-case basis.

Could be resolved now, re-open as necessary.

Rather than articularing a domain model based on current functionality and perceived interactions / dependencies between components, we need to re-iterate what is what and how we intend to use things, then model based on that narrative.