<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hello,<br>
<br>
thanks for your reply.<br>
<br>
<div class="moz-cite-prefix">Am 15.02.2019 um 17:34 schrieb Michael
Slusarz via dovecot:<br>
</div>
<blockquote type="cite"
cite="mid:1229848574.2094.1550248454209@appsuite.open-xchange.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<meta charset="UTF-8">
<blockquote type="cite"> On February 15, 2019 at 3:35 AM Hajo
Locke via dovecot <a class="moz-txt-link-rfc2396E" href="mailto:dovecot@dovecot.org"><dovecot@dovecot.org></a> wrote: <br>
<br>
Thanks for your reply, so iam not the only one. I think
downgrading is not an option for me. Ubuntu 18.04 comes with
openssl 1.1.0 and it seems that older versions like 2.2.22 not
compile successful. <br>
Best way for me would be a patch from Ubuntu-side, but without
any errormessage or something its wasted time to file a
bugreport. Though Ubuntu 18.04 should run for next 5 years. <br>
</blockquote>
<div class="default-style"> <a href="https://repo.dovecot.org/"
moz-do-not-send="true">https://repo.dovecot.org/</a> </div>
<div class="default-style"> <br>
</div>
<div class="default-style"> michael <br>
</div>
</blockquote>
Without statement of dovecot developers i dont like upgrading. I
want to explain: One should think that latest versions in 2.2 tree
are almost bugfree and stable. But this one is ugly. dovecot
crashes its index without noticing by itself and hiding new mails.
To be particular dovecot is not usable in a classic mbox setup with
this versions. <br>
Obviously this problem is unknown to developers, else i expected a
short answer. So it is still thinkable that this problem still
exists in 2.3 versions. At this point it's frustrating and
disappointing that this case is ignored by developers. My first
mail was 11 days ago. <br>
Not every user is an early adopter with 2.3 versions/mdbox etc. the
bigger the company the slower upgrades are deployed. We have several
hundreds of affected servers with 2.2.33.2, we have several
thousands servers with older versions without this problem, which
should get updated next weeks/months.<br>
For upgrading i need a version where this problem is fixed (we can
package by ourselfes if needed). we dont need newest features, just
a stable classic imapd. we cant use our customers as dummies and
test different versions to see if a bug is fixed or may be other
issues appear.<br>
I hope there is an understanding for our situation.<br>
<br>
Thanks,<br>
Hajo<br>
<br>
<br>
</body>
</html>