Displaying 20 results from an estimated 900 matches similar to: "Gmail and POP3"
2020 Oct 01
0
BUG: _presence_ of valid openssl.cnf Option = 'ServerPreference' causes Dovecot submission relay FAIL: "failed: Failed to initialize SSL: ..."
Hi,
In my Centos-8 server, it was not necessary using "Options =
ServerPreference" parameter.
My openssl.conf look like that :
openssl_conf = default_modules
[ default_modules ]
ssl_conf = ssl_module
[ ssl_module ]
system_default = crypto_policy
[ crypto_policy ]
*.include /etc/crypto-policies/back-ends/opensslcnf.config*
And /etc/crypto-policies/back-ends/opensslcnf.config :
2019 Dec 16
0
Gmail and POP3
* Yannick SIEGLER:
> auth: Debug: auth client connected (pid=21831)
> pop3-login: Debug: SSL: where=0x10, ret=1: before SSL initialization
Today's announcement[1] about "less secure apps" seems to imply that
POP3/IMAP will soon no longer be an option with G Suite accounts. You
may be better off searching for alternatives rather than trying to get
POP3 to work.
[1]
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
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
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
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 May 09
0
Unable to disable TLSv1.3 or fallback to TLSv1.2 when 1 cipher is disabled
On 08 May 2020, at 09:43, Steve Egbert <s.egbert at sbcglobal.net> wrote:
> I have an operational need to disable TLSv1.3 due to inadequate support to exclude certain ciphers.
There is no need to disable TLSv1.3 and attempts to do so will be flagged as ?downgrade attacks?.
> Much to my dismay, the `ssl_protocols` had been renamed and re-functionalized into `ssl_min_protocol`.
>
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 May 08
0
Unable to disable TLSv1.3 or fallback to TLSv1.2 when 1 cipher is disabled
Also, more testimony to the same problem (by others) is posted over at
ServerFault (StackOverflow):
https://serverfault.com/questions/975871/forcing-dovecot-2-3-4-1-to-use-tlsv1-2
On 5/8/20 11:50 AM, Steve Egbert wrote:
> I have an operational need to disable TLSv1.3 due to inadequate support
> to exclude certain ciphers.
>
> Much to my dismay, the `ssl_protocols` had been
2020 May 08
2
Unable to disable TLSv1.3 or fallback to TLSv1.2 when 1 cipher is disabled
I have an operational need to disable TLSv1.3 due to inadequate support
to exclude certain ciphers.
Much to my dismay, the `ssl_protocols` had been renamed and
re-functionalized into `ssl_min_protocol`.
Now, there is no way to exclude a specific group of one or more TLS
versions.
For a new bug report, I think we need two new settings:
* `ssl_tls13_ciphersuite` and
* `ssl_tls10_cipher`
2020 May 08
2
Unable to disable TLSv1.3 or fallback to TLSv1.2 when 1 cipher is disabled
I have an operational need to disable TLSv1.3 due to inadequate support
to exclude certain ciphers.
Much to my dismay, the `ssl_protocols` had been renamed and
re-functionalized into `ssl_min_protocol`.
Now, there is no way to exclude a specific group of one or more TLS
versions.
For a new bug report, I think we need two new settings:
* `ssl_tls13_ciphersuite` and
* `ssl_tls10_cipher`
2020 Oct 16
2
Dovecot won't accept IMAP TLS 1 connections from older devices [SOLVED]
I've spent days scouring the Internet and trying various solutions on a
problem with my Dovecot installation, so I thought I'd share what I
learned in hopes of saving other people a lot of time.? The dedicated
Dovecot hands will know all of the following already.? This is for those
of us that have to cover a lot of bases.
I upgraded my mail server from Ubuntu 18.04.1 to Ubuntu
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 =
2020 Aug 25
2
BUG: _presence_ of valid openssl.cnf Option = 'ServerPreference' causes Dovecot submission relay FAIL: "failed: Failed to initialize SSL: ..."
I've
dovecot --version
2.3.10.1 (a3d0e1171)
openssl version
OpenSSL 1.1.1g FIPS 21 Apr 2020
, atm on Fedora32.
I configure
/etc/pki/tls/openssl.cnf
to set preferences for apps' usage, e.g. Postfix etc; Typically, here
cat /etc/pki/tls/openssl.cnf
openssl_conf = default_conf
[default_conf]
ssl_conf = ssl_sect
[ssl_sect]
system_default = system_default_sect
2020 Sep 22
0
BUG: _presence_ of valid openssl.cnf Option = 'ServerPreference' causes Dovecot submission relay FAIL: "failed: Failed to initialize SSL: ..."
bump
On 8/24/20 5:17 PM, PGNet Dev wrote:
> I've
>
> dovecot --version
> 2.3.10.1 (a3d0e1171)
> openssl version
> OpenSSL 1.1.1g FIPS 21 Apr 2020
>
> , atm on Fedora32.
>
> I configure
>
> /etc/pki/tls/openssl.cnf
>
> to set preferences for apps' usage, e.g. Postfix etc; Typically, here
>
> cat /etc/pki/tls/openssl.cnf
>
2020 Sep 22
3
BUG: _presence_ of valid openssl.cnf Option = 'ServerPreference' causes Dovecot submission relay FAIL: "failed: Failed to initialize SSL: ..."
> On 22/09/2020 20:05 PGNet Dev <pgnet.dev at gmail.com> wrote:
>
>
> bump
>
> On 8/24/20 5:17 PM, PGNet Dev wrote:
> > I've
> >
> > dovecot --version
> > 2.3.10.1 (a3d0e1171)
> > openssl version
> > OpenSSL 1.1.1g FIPS 21 Apr 2020
> >
> > , atm on Fedora32.
> >
> > I configure
> >
>
2020 Oct 01
3
BUG: _presence_ of valid openssl.cnf Option = 'ServerPreference' causes Dovecot submission relay FAIL: "failed: Failed to initialize SSL: ..."
hi,
On 10/1/20 12:21 AM, JEAN-PAUL CHAPALAIN wrote:
> I had the same problem when migrating from Dovecot V2.2.36 on, Centos-7 to?Dovecot v2.3.8 on Centos-8
My report is specifically/solely about the addition/use of the
Options = ServerPreference
parameter.
I don't see that in your configuration.
Are you using it? In a config using Dovecot's submission proxy?
2013 Oct 07
2
Proxy to gmail not working
Hi,
I've been trying to build a password forwarding proxy to Gmail without
success... The SSL connection to Dovecot is happening no problem (as far as
I can tell), but for some reason the conversation between Dovecot and Gmail
is getting timed out.
I know this is supposed to be simple... :-( But could somebody please
give me some help by pointing what I'm not doing right?
No matter
2020 May 09
1
Unable to disable TLSv1.3 or fallback to TLSv1.2 when 1 cipher is disabled
>> I have an operational need to disable TLSv1.3 due to inadequate support to exclude certain ciphers.
>
> There is no need to disable TLSv1.3 and attempts to do so will be flagged as ?downgrade attacks?.
Let us ignore TLSv1.2 as a downgrade option. And focus on TLSv1.3 for
its entirety of this thread.
If the ciphersuite (not cipher for that's a TLSv1.2 term), but a
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