Tagged, signed. Available at 21:00 or soon thereafter.
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Jul 11 2016
Jul 8 2016
Built. Tagging now.
Rebuilding for Kolab 16
Rebuilding for Kolab Enterprise 14
Built for Winterfell
Submitted to Kolab 16
Submitted to Kolab Enterprise 14
The particular issue spawning this issue to become a ticket has been resolved. Either issues evolve in to subsequent tickets, or the other tickets must be closed a duplicate of this one.
Jul 7 2016
I've made the output more legible by using backticks (`) rather than tildes (~)
Jul 6 2016
Jul 5 2016
Jul 4 2016
Resolved in:
Jul 1 2016
Please take care to provide the action "request changes" to your comments in order to pop it back over in to my queue.
The patch on guam's hotfix/no_tls_server_response_fixup has been applied, and principally client's im- and explicit TLS connections seem OK ... but ...
Jun 30 2016
Jun 29 2016
Thank you @pokorra
Still an open ticket for delivery, but otherwise implemented successfully. Blocked by T1317: guam crashes on port 143 at the first connection opened though.
Jun 27 2016
This fixes the crash just fine.
Shipped the patches, cannot connect using STARTTLS client-side, per:
In T1317#21025, @seigo wrote:aseigo@serenity:~/src/kolab/eimap (develop)> git flow feature list
passthrough_capabilities_untouched
Jun 20 2016
Therefore resolved.
FWIW, configuring Guam to use IMAPS against the backend server will cause the client to not be presented with a STARTTLS capability:
For STARTTLS connections, this now renders: