Displaying 20 results from an estimated 2000 matches similar to: "SSL stops working after server upgrade"
2020 Apr 30
2
Dovecot IMAPS : Thunderbird SSL cert issue / Evolution OK
Recently thunderbird and Dovecot IMAPS cannot agree on SSL however
Evolution, on the exact same system, is working fine with the same
accounts. Tried recreating the Dovecot cert and also the thunderbird
accounts from scratch. The OpenSSL raw client works fine as well.
Would someone also confirm the openssl commands to create a selfsigned
cert for dovecot imaps. They cert created does work
2020 Apr 30
5
Dovecot IMAPS : Thunderbird SSL cert issue / Evolution OK
Hello,
This is a selfsigned cert. Both of the below methods were used.
May I ask for 1. pointer to info setting up "intermediate certs" and
where the certfile goes?
The objective is to generate a self-signed cert and use it for just
internal use with IMAPS dovecot.
Separately, what are your thoughts as to why evolution works and
thunderbird does not?
Thank you,
==1
openssl
2020 Apr 30
4
Dovecot IMAPS : Thunderbird SSL cert issue / Evolution OK
I would expect the public cert to be imported as a "server" not an "auth"
The attached image shows that TBird wants an httpS url for a webserver,
for the source.
Ages ago, I think it prompted for "do you want to trust this new cert"
and YES added it (assuming that is the public key) to the server list.?
A bit confused by this.
<see attached thunderbird
2020 Apr 30
0
Dovecot IMAPS : Thunderbird SSL cert issue / Evolution OK
<!doctype html>
<html><head>
<meta charset="UTF-8">
</head><body><div><br></div><blockquote type="cite"><div>On 30/04/2020 14:49 <a href="mailto:hanasaki@gmail.com">hanasaki@gmail.com</a> <<a href="mailto:hanasaki@gmail.com">hanasaki@gmail.com</a>>
2020 Apr 30
0
Dovecot IMAPS : Thunderbird SSL cert issue / Evolution OK
<!doctype html>
<html><head>
<meta charset="UTF-8">
</head><body><div>I see. You need to import the cert into thundebird's trusted ca certs.</div><div><br></div><div>Aki</div><blockquote type="cite"><div>On 30/04/2020 21:36 <a
2014 Jul 23
1
SSL certificate problem (SSL alert number 42)
Hello,
After client (Thunderbird, now version 31.0) updated today, it stopped connecting to Dovecot IMAP4S. The infamous "SSL alert number 42" is reported.
Mail server uses local (created for intranet) CA certificate as root.
I would appreciate pieces of advice on how to handle that without enabling plaintext authentication over insecure channels.
Other intranet services work with
2011 Oct 09
1
using ecc-certificates (ellyptic curve) will not establish connection
hi
I want to use ECC(ellyptic curve cryptography) for SSL-connections but somehow dovecot doesn't like my ECC-certificates :(
I tried to test using following scenario:
machine:
debian 6 (x64)
dovecot 2.0.15-0~auto+21 ((f6a2c0e8bc03) from http://xi.rename-it.nl/debian
openssl 1.0.0e-2 from testing (as the default 0.9.8o-4squeeze3 needs also the parameter -cipher ECCdraft for testing)
2019 Sep 04
0
TLS not working with iOS beta?
> Le 4 sept. 2019 ? 20:11, Henrik Johansson via dovecot <dovecot at dovecot.org> a ?crit :
>
> 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
2020 May 24
2
How to make IMAPS SSL Cert for Dovecot that works with Thunderbird
Hello all,
What are the instructions for making an SSL cert for Dovecot IMAPS?
Two methods have been tried, and work, with Evolution; however generate
the following error when Thunderbird tries to connect.
Thank you,
method 1 : self signed
openssl req -newkey rsa:4096 -sha512 -x509 -days 365 -nodes -keyout
mykey.key -out mycert.pem
method 2 : Let's Encrypt (LE) CA
Created with Certbot
2019 Sep 04
4
TLS not working with iOS beta?
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:
2015 Mar 15
2
Dovecot 2.1.7 still accepting SSLv3 though disabled?
Hello,
I came across a strange problem with my Dovecot 2.1.7 installation
(updated Debian Wheezy) in regards to SSL/TLS connections.
My configuration is as follows:
$ dovecot -n | grep ssl
service imap-login {
ssl = yes
...
}
ssl_cert = <......
ssl_cipher_list =
2013 Jul 11
3
SSL cert problem
Hi,
I'm running a new dovecot 2.0.9 under Centos 6.4. I'm having an issue with
SSL certificate not being accepted by the email client.
I have my own CA and I have generated certificates for web usage without a
problem.
For imaps and pop3s what I did was generate a certificate for the hostname
of my dovecot server and then cat that cert with the intermediate and root
CA certificates. No
2010 Feb 18
1
using signed certificates for TLS/SSL
Hi,
I have, in one customer, a web server running on a Verisign-signed
certificate SSL certificate. Everything works fine, IE and Firefox
connects on https without asking anything, which usually happens on
self-signed certificates. I'm trying to use that certificate on dovecot,
but clients (Thunderbird basically) keeps saying the certificate is not
valid.
yes i'm using,
2013 Dec 22
1
TLS SNI with Dovecot
Hi!
I've been using Dovecot for one single Domain with SSL certificates.
Now I would like to use Dovecot with several Domains and proper SSL
certificates. I tried to setup TLS SNI but it does not work. What I
basically did was just adding
local_name imap.samsoft.at {
ssl_cert = </etc/ssl/private/mailserver/imap.samsoft.at.crt
ssl_key =
2019 Sep 08
3
TLS not working with iOS beta?
> 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
2017 Nov 25
0
Upgrade to 2.2.32 from 2.2.15 failed
No, is that something that would make a difference between 2.2.15 and 2.2.32?
--Mark
On Fri, 24 Nov 2017 21:37:47 -0800 Gary <lists at lazygranch.com> wrote:
> Out of curiosity, do you do a !SSLv3 in the conf file?
>
>
> ? Original Message ?
>> From: mfoley at ohprs.org
>> Sent: November 24, 2017 9:04 PM
>> To: dovecot at dovecot.org
>> Subject:
2013 Feb 22
2
problems with imaps
hi,
i'm using dovecot 1.2.15 with self signed certificates
using starttls on ports 110/143 works ok with thunderbird 10.0.12 (and i
guess most other clients)
using imaps on port 993 works with outlook 2002.
with thunderbird 10.0.12 i can't connect to port 993 and get errors in
the logs like
TLS: SSL_read() failed: error:14094412:SSL
routines:SSL3_READ_BYTES:sslv3 alert bad
2017 Jul 12
0
Cannot Authenticate user with Kerberos/GSSAPI
My last message probably contained too much information. This one is more succient.
I have a user, 'mark', who has been running a Thunderbird client on Windows to Dovecot server
with Kerberos/GSSAPI authentication for over a year. I created a new Tbird account on a new
Linux workstation for 'mark', also with Kerberos/GSSAPI and that worked just fine.
I have another user,
2017 Jul 11
0
stopped being able to kerberos/GSSAPI authenticate with new email accounts
I've been running with Dovecot 2.2.15 on my mail server and Thunderbird on workstations with
Kerberos/GSSAPI authentication. This has been working for over a year for 10 users.
The other day, I replaced a user's workstation and set up this user with a Thunderbird client.
Unfortunately, I got the error:
"The Kerberos/GSSAPI ticket was not accepted by the IMAP server ... please
2017 Nov 25
3
Upgrade to 2.2.32 from 2.2.15 failed
I have a problem. I have been running Dovecot 2.2.15 and I'd like to upgrade. My distro
(Slackware) has dovecot 2.2.32 available. I downloaded and installed that, but it didn't work.
No one was able to get messages from the dovecot server on their workstations. The following is
the entire dovecot log file from startup to the last message generated. No more messages went
into the logfile