Re: SSL error

Store - typo at my den (have kb-issues) Thanks and regards Goetz R Schultz >8 Quis custodiet ipsos custodes? /"\ \ / ASCII Ribbon Campaign X against HTML e-mail / \ 8< On 09/11/2022 21:28, Ruben Safir wrote: This

Re: SSL error

Ruben Safir wrote: > > This got nothing to with LE or own CA. Bottom line is, you need to > > add your own CA to the cert tore (ideally) > > what is a cert tore? Someone has probably already replied to this, but it's a typo: the OP wanted to say "store". The certificate you created was used to

Re: SSL error

> > This got nothing to with LE or own CA. Bottom line is, you need to > add your own CA to the cert tore (ideally) what is a cert tore? > - look in DuckDuckGo how > that works for your distri - Linux is different from BSD - for > example. > > That would be my line in FreeBSD, using a single

Re: SSL error

On 09/11/2022 18:19, Alexander Dalloz wrote: Am 09.11.2022 um 18:30 schrieb hi@zakaria.website: On 2022-11-09 16:59, Alexander Dalloz wrote: Am 09.11.2022 um 15:58 schrieb Ruben Safir: Hello I am getting this error and I have no idea why.  openssh is upto date You have a self-signed

Re: SSL error

Am 09.11.2022 um 18:30 schrieb hi@zakaria.website: On 2022-11-09 16:59, Alexander Dalloz wrote: Am 09.11.2022 um 15:58 schrieb Ruben Safir: Hello I am getting this error and I have no idea why.  openssh is upto date You have a self-signed certificate in place. The connecting client cannot

Re: SSL error

On 2022-11-09 16:59, Alexander Dalloz wrote: Am 09.11.2022 um 15:58 schrieb Ruben Safir: Hello I am getting this error and I have no idea why. openssh is upto date You have a self-signed certificate in place. The connecting client cannot valide whether to trust to answering server.

Re: SSL error

Am 09.11.2022 um 15:58 schrieb Ruben Safir: Hello I am getting this error and I have no idea why. openssh is upto date You have a self-signed certificate in place. The connecting client cannot valide whether to trust to answering server. Alexander

SSL error

Hello I am getting this error and I have no idea why. openssh is upto date client bash-5.1$ fetchmail --ssl -p POP3 -uruben mail2.boroparkmd.com Enter password for ru...@mail2.boroparkmd.com: fetchmail: Server certificate verification error: self signed certificate fetchmail: Missing trust

Re: SSL Error

.13 (7b14904) > >> # OS: Linux 4.4.0-45-generic x86_64 Ubuntu 16.04.6 LTS ext4 > > This is very dated version of dovecot, you might want to consider using > > e.g. https://repo.dovecot.org for new version. This is not necessarely the > > cause here. > > > > For the SSL error, can you describe more on what are you doing when you get > > the error? It looks a lot like trying plaintext connection to SSL port. > > > > Aki

Re: SSL Error

to consider using e.g. https://repo.dovecot.org for new version. This is not necessarely the cause here. For the SSL error, can you describe more on what are you doing when you get the error? It looks a lot like trying plaintext connection to SSL port. Aki

Re: SSL Error

6_64 Ubuntu 16.04.6 LTS ext4 This is very dated version of dovecot, you might want to consider using e.g. https://repo.dovecot.org for new version. This is not necessarely the cause here. For the SSL error, can you describe more on what are you doing when you get the error? It looks a lot like trying plaintext connection to SSL port. Aki

SSL Error

I just installed a certificate on my mail server to Postfix and Dovecot. The certificate is functional on Postfix, but for some reason I keep getting this error. Any suggestions on how to fix it? mail dovecot: imap-login: Error: SSL: Stacked error: error:1408A10B:SSL

Re: dovecot ssl error message from my own connections

message pretty much throughout the day/night, > which appears to come from my own mail clients (desktop or mobile). > I would like to resolve it, because it must me something (that is not > good--that I may not understand), that may have other ramifications. > > So, here it is. > &g

Re: dovecot ssl error message from my own connections

Thanks! I will have a look. -Original Message- From: @lbutlr via dovecot Reply-to: "@lbutlr" To: Davide Marchi via dovecot Subject: Re: dovecot ssl error message from my own connections Date: Sat, 30 Mar 2019 06:28:06 -0600 On 30 Mar 2019, at 06:20, Esteban L via dove

Re: dovecot ssl error message from my own connections

Opps, forgot that important requirment! sorry Dovecot 2.2.27 -Original Message- From: Aki Tuomi Reply-to: Aki Tuomi To: este...@little-beak.com, Esteban L via dovecot Subject: Re: dovecot ssl error message from my own connections Date: Sat, 30 Mar 2019 14:25:41 +0200 (EET) > On

Re: dovecot ssl error message from my own connections

On 30 Mar 2019, at 06:20, Esteban L via dovecot wrote: > date time myserver dovecot: imap-login: Debug: SSL error: SSL_read() > syscall failed: Connection reset by peer I don't get that particular message, but in general Debug messages are informational, not errors or warnings. Seem

Re: dovecot ssl error message from my own connections

rstand), that may have other ramifications. So, here it is. date time myserver dovecot: imap-login: Debug: SSL error: SSL_read() syscall failed: Connection reset by peer Anyone have a suggestion of what this

dovecot ssl error message from my own connections

something (that is not good--that I may not understand), that may have other ramifications. So, here it is. date time myserver dovecot: imap-login: Debug: SSL error: SSL_read() syscall failed: Connection reset by peer Anyone have a suggestion of what this might hint to, other than obvious SSL. I

Re: Dovecot (doveadm, ssl, sync) - SSL error

for replication. Thanks in advance. dovecot: doveadm: Error: safe_mkstemp(/tmp/dovecot.doveadm.) failed: Permission denied Arkadiusz Majewski From: Arkadiusz Majewski Sent: Sunday, December 3, 2017 7:38 PM To: 'dovecot@dovecot.org' Subject: Dovecot (doveadm, ssl, sync) - SSL error Hello

Re: SSL error after upgrading to 2.31

On 05/30/18 10:41, A. Schulze wrote: In the third case an administrator has to provide files with certificates. And these files are required (by best practice) Do you have any pointers to support such a strong statement? to include any chain-certificates excluding the self signed root. Our

Re: SSL error after upgrading to 2.31

Aki Tuomi: There is already ssl_client_ca, for verifying clients. ssl_ca verifies certs when dovecot is connecting somewhere. For clarification: there is a third use case an admin may need intermediate certificates: And that's where dovecot act as server providing imap/pop3/lmtp/sieve

Re: SSL error after upgrading to 2.31

On Mon, 28 May 2018 15:03:29 +0300, Aki Tuomi wrote: >> Sounds good. How about (re)naming them ssl-{client,server}_ca? > > There is already ssl_client_ca, for verifying clients. ssl_ca verifies > certs when dovecot is connecting somewhere. So there's three? I had no idea... Cheerio, hauke --

Re: SSL error after upgrading to 2.31

On 28.05.2018 14:30, Hauke Fath wrote: > On Mon, 28 May 2018 13:52:01 +0300, Aki Tuomi wrote: >> I'm sure. But putting it as ssl_ca makes no sense, since it becomes >> confused what it is for. > I guess - I haven't had a need for client certs, and only ever used > ssl_ca for the server ca

Re: SSL error after upgrading to 2.31

On Mon, 28 May 2018 13:52:01 +0300, Aki Tuomi wrote: > I'm sure. But putting it as ssl_ca makes no sense, since it becomes > confused what it is for. I guess - I haven't had a need for client certs, and only ever used ssl_ca for the server ca chain. > We can try restoring this as ssl_cert_chain

Re: SSL error after upgrading to 2.31

On 28.05.2018 13:05, Hauke Fath wrote: > On 05/28/18 11:08, Aki Tuomi wrote: >> >> >> On 28.05.2018 12:06, Hauke Fath wrote: >>> On 05/21/18 17:55, Aki Tuomi wrote: ssl_ca is used only for validating client certificates. >>> >>> But it was used (though not documented, IIRC) for validating

Re: SSL error after upgrading to 2.31

On 05/28/18 11:08, Aki Tuomi wrote: On 28.05.2018 12:06, Hauke Fath wrote: On 05/21/18 17:55, Aki Tuomi wrote: ssl_ca is used only for validating client certificates. But it was used (though not documented, IIRC) for validating server certs, too. Since intermediate CA certs are usually

Re: SSL error after upgrading to 2.31

On 28.05.2018 12:06, Hauke Fath wrote: > On 05/21/18 17:55, Aki Tuomi wrote: >> ssl_ca is used only for validating client certificates. > > But it was used (though not documented, IIRC) for validating server > certs, too. Since intermediate CA certs are usually valid a lot longer > than the

Re: SSL error after upgrading to 2.31

On 05/21/18 17:55, Aki Tuomi wrote: ssl_ca is used only for validating client certificates. But it was used (though not documented, IIRC) for validating server certs, too. Since intermediate CA certs are usually valid a lot longer than the server certs, having to concat the certs is awkward,

Re: SSL error after upgrading to 2.31

You forgot to cc the list. ssl_ca is used only for validating client certificates. ---Aki TuomiDovecot oy Original message From: Marc Perkel <m...@perkel.com> Date: 21/05/2018 18:25 (GMT+02:00) To: Aki Tuomi <aki.tu...@dovecot.fi> Subject: Re: SSL error after upgra

Re: SSL error after upgrading to 2.31

Does ssl_cert file contain intermediates? ---Aki TuomiDovecot oy Original message From: Marc Perkel <m...@perkel.com> Date: 21/05/2018 16:32 (GMT+02:00) To: dovecot@dovecot.org Subject: SSL error after upgrading to 2.31 After upgrading to 2.31 I'm g

RE: Dovecot (doveadm, ssl, sync) - SSL error

. dovecot: doveadm: Error: safe_mkstemp(/tmp/dovecot.doveadm.) failed: Permission denied Arkadiusz Majewski From: Arkadiusz Majewski <maje...@gmail.com> Sent: Sunday, December 3, 2017 7:38 PM To: 'dovecot@dovecot.org' <dovecot@dovecot.org> Subject: Dovecot (doveadm, ssl,

Dovecot (doveadm, ssl, sync) - SSL error

Hello! I've got a problem to run syncing between both dovecot services on the separate servers. The error indicates to the problem with SSL. Directly using openssl command to connect from one server to other and vice versa is passed without any errors. OS: FreeBSD 11.1-RELEASE-p4 Dovecot:

Re: doveadm ssl error when upgrading from 2.2.27 to 2.2.29

g.to.this.host): Debug: SSL alert: where=0x4008, ret=552: fatal handshake failure doveadm(replicating.to.this.host): Debug: SSL: where=0x2002, ret=-1: error doveadm(replicating.to.this.host): Debug: SSL error: SSL_accept() failed: error:1417A0C1:SSL routines:tls_post_process_client_hello:no shared

Re: doveadm ssl error when upgrading from 2.2.27 to 2.2.29

On 07.06.2017 15:16, Pallissard, Matthew wrote: > I'm starting to see the following error when upgrading from 2.2.27 to 2.2.29. > > doveadm(ip.add.re.ss): Error: doveadm client disconnected before handshake: > SSL_accept() failed: error:1417A0C1:SSL > routines:tls_post_process_client_hello:no

doveadm ssl error when upgrading from 2.2.27 to 2.2.29

I'm starting to see the following error when upgrading from 2.2.27 to 2.2.29. doveadm(ip.add.re.ss): Error: doveadm client disconnected before handshake: SSL_accept() failed: error:1417A0C1:SSL routines:tls_post_process_client_hello:no shared cipher Downgrading from 2.2.27 resolves, error

doveadm sync SSL error when upgrading from 2.2.27 -> 2.2.29

I'm starting to see the following error from doveadm when upgrading from 2.2.27 to 2.2.29. > doveadm(ip.add.re.ss): Error: doveadm client disconnected before handshake: > SSL_accept() failed: error:1417A0C1:SSL > routines:tls_post_process_client_hello:no shared cipher I'm using a cert/key

Re: SSL error

On Thu, Oct 13, 2016 at 10:30 AM Christian Kivalo wrote: > > > > > On 2016-10-13 10:12, arnaud gaboury wrote: > > > On Thu, Oct 13, 2016 at 8:48 AM Christian Kivalo > > > wrote: > > > > > >> > > >> > > >> > > >> > > >> Am 13. Oktober 2016 08:41:06 MESZ,

Re: SSL error

On 2016-10-13 10:12, arnaud gaboury wrote: On Thu, Oct 13, 2016 at 8:48 AM Christian Kivalo wrote: Am 13. Oktober 2016 08:41:06 MESZ, schrieb arnaud gaboury < arnaud.gabo...@gmail.com>: >I run dovecot + postfix as my email server. Everything is working as

Re: SSL error

On Thu, Oct 13, 2016 at 8:48 AM Christian Kivalo wrote: > > > > > Am 13. Oktober 2016 08:41:06 MESZ, schrieb arnaud gaboury < > arnaud.gabo...@gmail.com>: > > >I run dovecot + postfix as my email server. Everything is working as > > >expected, but I see an error in the

Re: SSL error

Am 13. Oktober 2016 08:41:06 MESZ, schrieb arnaud gaboury : >I run dovecot + postfix as my email server. Everything is working as >expected, but I see an error in the dovecot logs: > >lmtp(7331): Error: SSL context initialization failed, disabling SSL:

SSL error

I run dovecot + postfix as my email server. Everything is working as expected, but I see an error in the dovecot logs: lmtp(7331): Error: SSL context initialization failed, disabling SSL: ENGINE_init(dynamic) failed Dovecot is running and emails are OK. I wonder why this error and how I can fix