time for cyrus-imap v3.2?

[Michael Menge]

Hi all,

there are some bugs in cyrus 3.0/3.1 that i would like to see fixed
and I want to make sure that these changes will be able to be
included after 3.2 is released or will be fixed before 3.2 is released:

#2659 allow rename back from deleted mailbox when conversations is enabled
#2599 bug renaming/deleting special use folders in murder setup
#2598 squat search_engine not used

Also fixing "#2774 Murder does not work with TLS" would be
appreciate, if not possible the murder documentation should
at least been updated

Quoting my mail  
https://lists.andrew.cmu.edu/pipermail/cyrus-devel/2018-July/004297.html

> Quoting ellie timoney <ellie at fastmail.com>:
>>
>> Anyway, it looks to me like the STARTTLS support in mupdate is just  
>>  fundamentally broken at the moment, and my recommendation is to  
>> not  use it.  If your IMAP servers need to connect to an mupdate  
>> server  that's not within their trusted network, I guess you'd need  
>> to set  up a VPN for it or something along those lines (but I'm no  
>> network  specialist).
>>
> could you add a warning in the relevant murder/installation guides  
> and  manuals?

Quoting Bron Gondwana <brong at fastmailteam.com>:

> On Tue, Nov 5, 2019, at 12:04, Ricardo Signes wrote:
>> So, I think the plan was to cut a stable Cyrus 3.2 after we had  
>> stable JMAP. Is that time now? We talked about this on the Zoom  
>> call today.
>
> I think we're pretty close to it. The big question is: do we fork  
> what will eventually become 3.2 and keep stabilising on it while we  
> ship UUID mailboxes on master, or do we finish 3.2 before we merge  
> uuid mailboxes.
>
>> Cyrus master has pretty stable for JMAP core and mail. I think we  
>> need to do one more pass through to look for places where Cyrus  
>> extensions might leak through without the correct `using` options,  
>> but apart from that, I don't think we expect its mail API to change  
>> apart from bugfixes.
>
> Yep, legit. The one big thing still missing there is  
> PushSubscriptions. I'd be keen to finish writing that. I mean:
>
> https://github.com/cyrusimap/cyrus-imapd/issues?q=is%3Aopen+is%3Aissue+label%3A3.2
>
> We should probably do a push and resolve all of those, then boom let's go.
>

there are some bugs in cyrus 3.0/3.1 that i would like to see fixed
and I want to make sure that these changes will be able to be
included after 3.2 is released or will be fixed before 3.2 is released:

#2659 allow rename back from deleted mailbox when conversations is enabled
#2599 bug renaming/deleting special use folders in murder setup
#2598 squat search_engine not used

Also fixing "#2774 Murder does not work with TLS" would be
appreciate, if not possible the murder documentation should
at least been updated

Quoting my mail  
https://lists.andrew.cmu.edu/pipermail/cyrus-devel/2018-July/004297.html

> Quoting ellie timoney <ellie at fastmail.com>:
>>
>> Anyway, it looks to me like the STARTTLS support in mupdate is just  
>>  fundamentally broken at the moment, and my recommendation is to  
>> not  use it.  If your IMAP servers need to connect to an mupdate  
>> server  that's not within their trusted network, I guess you'd need  
>> to set  up a VPN for it or something along those lines (but I'm no  
>> network  specialist).
>>
> could you add a warning in the relevant murder/installation guides  
> and  manuals?






--------------------------------------------------------------------------------
M.Menge                                Tel.: (49) 7071/29-70316
Universität Tübingen                   Fax.: (49) 7071/29-5912
Zentrum für Datenverarbeitung          mail:  
michael.menge at zdv.uni-tuebingen.de
Wächterstraße 76
72074 Tübingen