similar to: Dovecot send duplicated certificates when using ssl_alt_cert

On 17.05.2018 16:33, @lbutlr wrote: > On 2018-05-16 (08:54 MDT), Jean-Daniel Dupas <jddupas at xooloo.com> wrote: >> My problem is that when connecting, dovecot includes 2 copies of Let's Encrypt Authority X3 in the certificate chain. > I think Dovecot 2.2 also has this issue, if I remember previous posts accurately. Recommendations to include the full chain in the cert

> Le 27 juil. 2019 ? 14:30, Stephan Bosch <stephan at rename-it.nl> a ?crit : > > On 23/07/2019 17:13, Jean-Daniel Dupas via dovecot wrote: >> Hello, >> >> I'm having trouble configuring the submission proxy. >> >> I have configured the submission service as follow: >> >> submission_host = smtp.example.com >>

On 2018-05-16 (08:54 MDT), Jean-Daniel Dupas <jddupas at xooloo.com> wrote: > > My problem is that when connecting, dovecot includes 2 copies of Let's Encrypt Authority X3 in the certificate chain. I think Dovecot 2.2 also has this issue, if I remember previous posts accurately. Recommendations to include the full chain in the cert didn't seem to work. -- Eyes the shady

> Le 13 sept. 2019 ? 09:29, Gerben Wierda via dovecot <dovecot at dovecot.org> a ?crit : > > Nobody? > >> On 10 Sep 2019, at 11:58, Gerben Wierda via dovecot <dovecot at dovecot.org <mailto:dovecot at dovecot.org>> wrote: >> >> I am new to dovecot administration. I?ve read the Wiki but that hasn?t given me the understanding I need. >>

Hello, I'm having trouble configuring the submission proxy. I have configured the submission service as follow: submission_host = smtp.example.com submission_relay_host = localhost submission_relay_port = 8587 submission_relay_rawlog_dir = /var/log/dovecot/ submission_relay_trusted = yes My main issue is that until I login, dovecot-submission won't connect to the backend and query the

I just added an ECDSA certificate to my mail server using ssl_alt_cert (the RSA certificate is specified by ssl_cert), both certificate files contain the certificate and a single intermediate (which currently happens to be the same intermediate from Let?s Encrypt). When connecting to the server using either RSA or ECDSA ciphers, the server sends the proper certificate, but also sends two

service submission-login { ? inet_listener submissions { ? ? haproxy = no ? ? port = 465 ? ? reuse_port = no ? ? ssl = yes ? } } Shouldn't the port be 587 here? My config file looks like: service submission-login { ? inet_listener submission { ??? #port = 587 ? } } The # comment must also mean something.. On 7/27/19 3:21 PM, Jean-Daniel via dovecot wrote: > > >> Le 27

On Thursday 29 August 2019 15:45:44 Gordon Messmer wrote: > On 8/29/19 3:03 AM, Gary Stainburn wrote: > > https://us-east.repo.webtatic.com/yum/el7/x86_64/repodata/repomd.xml: [Errno 14] curl#60 - "Peer's Certificate issuer is not recognized." > > > What do you see when you run: > > ??? openssl s_client -showcerts -connect us-east.repo.webtatic.com:443

> On 4 Sep 2019, at 21:35, Jean-Daniel <jddupas at xooloo.com> wrote: > > Just a wild guess as I didn?t try to configure Mail on Catalina yet, but it looks like your server only supports ?DHE-RSA?? ciphers. > I think that modern systems prefers using ECDHE key exchange and would not be surprise if iOS requires it. > Well I got the OpenSSL parts working now, but newer

Hello Dovecot-List, so Ubuntu users now can get the latest dovecot version. As I am just building a production mailserver for customers, this could come in handy, maybe. For a live production system, is it reasonable to switch from the main Ubuntu Dovecot release to your newer packages? How long will the Dovecot team build these packages? When the team don't want to build these packages

On 10/03/18 14:06, Aki Tuomi wrote: > >> On 10 March 2018 at 14:49 John Fawcett < john at voipsupport.it >> <mailto:john at voipsupport.it>> wrote: >> >> >> On 08/03/18 18:43, Peter Linss wrote: >>> I just added an ECDSA certificate to my mail server using >>> ssl_alt_cert (the RSA certificate is specified by ssl_cert), both

> On 10 March 2018 at 16:05 Aki Tuomi <aki.tuomi at dovecot.fi> wrote: > > > > > On 10 March 2018 at 15:20 John Fawcett <john at voipsupport.it> wrote: > > > > > > On 10/03/18 14:06, Aki Tuomi wrote: > > > > > >> On 10 March 2018 at 14:49 John Fawcett < john at voipsupport.it > > >> <mailto:john at

https://dovecot.org/releases/2.2/rc/dovecot-2.2.31.rc1.tar.gz https://dovecot.org/releases/2.2/rc/dovecot-2.2.31.rc1.tar.gz.sig Unless new bugs are found, this will be the final v2.2.31 release, which will be released on Monday. * LMTP: Removed "(Dovecot)" from added Received headers. Some installations want to hide it, and there's not really any good reason for anyone to

https://dovecot.org/releases/2.2/rc/dovecot-2.2.31.rc1.tar.gz https://dovecot.org/releases/2.2/rc/dovecot-2.2.31.rc1.tar.gz.sig Unless new bugs are found, this will be the final v2.2.31 release, which will be released on Monday. * LMTP: Removed "(Dovecot)" from added Received headers. Some installations want to hide it, and there's not really any good reason for anyone to

On 08/03/18 18:43, Peter Linss wrote: > I just added an ECDSA certificate to my mail server using ssl_alt_cert (the RSA certificate is specified by ssl_cert), both certificate files contain the certificate and a single intermediate (which currently happens to be the same intermediate from Let?s Encrypt). > > When connecting to the server using either RSA or ECDSA ciphers, the server sends

> On 10 March 2018 at 16:53 Aki Tuomi <aki.tuomi at dovecot.fi> wrote: > > > > > On 10 March 2018 at 16:05 Aki Tuomi <aki.tuomi at dovecot.fi> wrote: > > > > > > > > > On 10 March 2018 at 15:20 John Fawcett <john at voipsupport.it> wrote: > > > > > > > > > On 10/03/18 14:06, Aki Tuomi wrote: > >

> On 10 March 2018 at 15:20 John Fawcett <john at voipsupport.it> wrote: > > > On 10/03/18 14:06, Aki Tuomi wrote: > > > >> On 10 March 2018 at 14:49 John Fawcett < john at voipsupport.it > >> <mailto:john at voipsupport.it>> wrote: > >> > >> > >> On 08/03/18 18:43, Peter Linss wrote: > >>> I just added

<!doctype html> <html> <head> <meta charset="UTF-8"> </head> <body> <div> <br> </div> <blockquote type="cite"> <div> On 10 March 2018 at 14:49 John Fawcett < <a href="mailto:john@voipsupport.it">john@voipsupport.it</a>> wrote: </div> <div>

Hi, Have anyone else experienced problems using Dovecot with the mail app in beta releases of iOS/iPadOS 13? TLS is failing for my, it have worked fine for years and I am on the latest Dovecot version now, it works fine with older clients but not with the ones upgraded: Sep 04 19:49:16 imap-login: Debug: SSL: where=0x10, ret=1: before/accept initialization Sep 04 19:49:16 imap-login: Debug:

https://dovecot.org/releases/2.3/dovecot-2.3.2.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.2.tar.gz.sig v2.3.2 is mainly a bugfix release. It contains all the changes in v2.2.36, as well as a bunch of other fixes (mainly for v2.3-only bugs). Binary packages are already in https://repo.dovecot.org/ * old-stats plugin: Don't temporarily enable PR_SET_DUMPABLE while opening