Re: Dovecot 2.3.0 TLS

> Le 18 juil. 2019 à 11:21, Alexandre Urban via dovecot a > écrit : > > Hello, > > I don’t know who will read this message, but I found this thread: > https://www.mail-archive.com/[email protected]&q=subject:%22Dovecot+2.3.0+TLS%22&o=newest > And I’m expected the same issue, I w

Re: Dovecot 2.3.0 TLS

Hello, I don't know who will read this message, but I found this thread: https://www.mail-archive.com/[email protected]&q=subject:%22Dovecot+2.3.0+TLS%22&o=newest And I'm expected the same issue, I will try to explain to you (english is not my native language, sorry) Since Buster upd

Re: Dovecot 2.3.0 TLS

Hi Aki and all, Thanks for the feedback. I have removed the home-made root CA and the home-made server cert signed by the root CA, replaced it with valid Let's Encrypt cert and all works well. Whilst the home-made certs have always worked well (years) with Thunderbird clients and iOS 12.x, the n

Re: Dovecot 2.3.0 TLS

On 4.7.2019 12.14, @lbutlr via dovecot wrote: > On 3 Jul 2019, at 02:55, Peter Kahl via dovecot wrote: >> I failed to disclose that the described problem occurs on iOS 13.0 beta. >> >> After trying again and again, it appears that a bug in iOS 13.0 beta is the >> likely culprit. I am readin

Re: Dovecot 2.3.0 TLS

On 3 Jul 2019, at 02:55, Peter Kahl via dovecot wrote: > I failed to disclose that the described problem occurs on iOS 13.0 beta. > > After trying again and again, it appears that a bug in iOS 13.0 beta is the > likely culprit. I am reading on Reddit that there is some bug in iOS with > cer

Re: Dovecot 2.3.0 TLS

Hi Aki, I failed to disclose that the described problem occurs on iOS 13.0 beta. After trying again and again, it appears that a bug in iOS 13.0 beta is the likely culprit. I am reading on Reddit that there is some bug in iOS with certificate trust... https://www.reddit.com/r/signal/comments/c2q

Re: Dovecot 2.3.0 TLS

On 2.7.2019 8.06, Peter via dovecot wrote: >    On 11.01.2018 13:20, Hauke Fath wrote: >    >/On Thu, 11 Jan 2018 12:20:45 +0200, Aki Tuomi wrote: />>/Was the > certificate path bundled in the server certificate? />/No, as a > separate file, provided from the local (intermediate) CA: > />//>/ssl_

Re: Re: Dovecot 2.3.0 TLS

On 11.01.2018 13:20, Hauke Fath wrote: >/On Thu, 11 Jan 2018 12:20:45 +0200, Aki Tuomi wrote: />>/Was the certificate path bundled in the server certificate? />/No, as a separate file, provided from the local (intermediate) CA: />//>/ssl_cert = /ssl_key = /ssl_ca = //>/Worked fine with 2.2

Re: Re: Dovecot 2.3.0 TLS

On 11.01.2018 13:20, Hauke Fath wrote: >/On Thu, 11 Jan 2018 12:20:45 +0200, Aki Tuomi wrote: />>/Was the certificate path bundled in the server certificate? />/No, as a separate file, provided from the local (intermediate) CA: />//>/ssl_cert = /ssl_key = /ssl_ca = //>/Worked fine with 2.2

Re: Dovecot 2.3.0 TLS

On Tue, Jan 23, 2018 at 10:05 AM, Aki Tuomi wrote: > > > On January 23, 2018 at 7:09 PM Arkadiusz Miśkiewicz > wrote: > > > > > > On Thursday 11 of January 2018, Aki Tuomi wrote: > > > > > Seems we might've made a unexpected change here when we revamped the > ssl > > > code. > > > > Revamped, in

Re: Dovecot 2.3.0 TLS

> On January 23, 2018 at 7:09 PM Arkadiusz Miśkiewicz wrote: > > > On Thursday 11 of January 2018, Aki Tuomi wrote: > > > Seems we might've made a unexpected change here when we revamped the ssl > > code. > > Revamped, interesting, can it support milions certs now on single machine? > (so

Re: Dovecot 2.3.0 TLS

On Thursday 11 of January 2018, Aki Tuomi wrote: > Seems we might've made a unexpected change here when we revamped the ssl > code. Revamped, interesting, can it support milions certs now on single machine? (so are certs loaded by demand and not wasting memory) > Aki -- Arkadiusz Miśkiewicz

Re: Dovecot 2.3.0 TLS

On 23 January 2018 at 10:35, Aki Tuomi wrote: > > > On 22.01.2018 22:14, Odhiambo Washington wrote: > > > > On 22 January 2018 at 23:10, Matthias Fechner wrote: > >> Dear Odhiambo, >> >> Am 22.01.2018 um 19:58 schrieb Odhiambo Washington: >> >> ...and I am still unable to successfully compile 2.

Re: Dovecot 2.3.0 TLS

On 22.01.2018 22:14, Odhiambo Washington wrote: > > > On 22 January 2018 at 23:10, Matthias Fechner > wrote: > > Dear Odhiambo, > > Am 22.01.2018 um 19:58 schrieb Odhiambo Washington: >> ...and I am still unable to successfully compile 2.3RC on FreeBSD >>

Re: Dovecot 2.3.0 TLS

On 22 January 2018 at 23:10, Matthias Fechner wrote: > Dear Odhiambo, > > Am 22.01.2018 um 19:58 schrieb Odhiambo Washington: > > ...and I am still unable to successfully compile 2.3RC on FreeBSD 8.4 and > 9.3 > and my reports were ignored, so should I assume support for those has > been drop

Re: Dovecot 2.3.0 TLS

Dear Odhiambo, Am 22.01.2018 um 19:58 schrieb Odhiambo Washington: > ...and I am still unable to successfully compile 2.3RC on FreeBSD 8.4 > and 9.3 > and my reports were ignored, so should I assume support for those > has been dropped? Support for FreeBSD 8.4 stopped August 1, 2015. Support

Re: Dovecot 2.3.0 TLS

On 11 January 2018 at 14:29, Aki Tuomi wrote: > > > On 11.01.2018 13:28, Hauke Fath wrote: > > On Thu, 11 Jan 2018 13:22:07 +0200, Aki Tuomi wrote: > >> Can you try if it works if you concatenate the cert and cert-chain > >> to single file? We'll start looking if this is misunderstanding or bug.

Re: Dovecot 2.3.0 TLS

On 01/11/2018 12:22 PM, Aki Tuomi wrote: On 11.01.2018 13:20, Hauke Fath wrote: On Thu, 11 Jan 2018 12:20:45 +0200, Aki Tuomi wrote: Was the certificate path bundled in the server certificate? No, as a separate file, provided from the local (intermediate) CA: ssl_cert = Seems we might've

Re: Dovecot 2.3.0 TLS

On Thu, 11 Jan 2018 13:29:02 +0200, Aki Tuomi wrote: > You might want to invest into a test environment, by the way. It's > far more safe to try out new major releases and stuff. =) Fair enough. With SSL certs, this gets a bit involved, though. This is a small site with a few dozen users, so I

Re: Dovecot 2.3.0 TLS

On 11.01.2018 13:28, Hauke Fath wrote: > On Thu, 11 Jan 2018 13:22:07 +0200, Aki Tuomi wrote: >> Can you try if it works if you concatenate the cert and cert-chain >> to single file? We'll start looking if this is misunderstanding or bug. > This is a production machine, so I would rather stick wi

Re: Dovecot 2.3.0 TLS

On Thu, 11 Jan 2018 13:22:07 +0200, Aki Tuomi wrote: > Can you try if it works if you concatenate the cert and cert-chain > to single file? We'll start looking if this is misunderstanding or bug. This is a production machine, so I would rather stick with the downgrade until you've looked into the

Re: Dovecot 2.3.0 TLS

On 11.01.2018 13:20, Hauke Fath wrote: > On Thu, 11 Jan 2018 12:20:45 +0200, Aki Tuomi wrote: >> Was the certificate path bundled in the server certificate? > No, as a separate file, provided from the local (intermediate) CA: > > ssl_cert = ssl_key = ssl_ca = > Worked fine with 2.2.x, 2.3 give

Re: Dovecot 2.3.0 TLS

On Thu, 11 Jan 2018 12:20:45 +0200, Aki Tuomi wrote: > Was the certificate path bundled in the server certificate? No, as a separate file, provided from the local (intermediate) CA: ssl_cert =

Re: Dovecot 2.3.0 TLS

On 11.01.2018 12:18, Hauke Fath wrote: > All, > > our dovecot installation provides a bundle of intermedia CA > certificates using the ssl_ca option. > > 2.3.0 does not supply the bundle, resulting in various clients either > complaining about an unverifiable server cert, or quietly not > conn

Dovecot 2.3.0 TLS

All, our dovecot installation provides a bundle of intermedia CA certificates using the ssl_ca option. 2.3.0 does not supply the bundle, resulting in various clients either complaining about an unverifiable server cert, or quietly not connecting. The log has Jan 5 17:01:46 Bounce dovecot: im