On Thu, Jun 26, 2014 at 05:13:20PM +0200, Robert Schetterer wrote:
Am 26.06.2014 11:53, schrieb Adi Kriegisch:
On Wed, May 21, 2014 at 09:14:26PM +0200, Robert Schetterer wrote:
Am 21.05.2014 19:47, schrieb Sebastian Goodrick:
I just installed the (rapid-ssl) certificate and it works now.
On Wed, May 21, 2014 at 09:14:26PM +0200, Robert Schetterer wrote:
Am 21.05.2014 19:47, schrieb Sebastian Goodrick:
I just installed the (rapid-ssl) certificate and it works now.
Needless to say that I don't understand it. The old certificate worked
with all other clients but win8/outlook,
On Thu, 26 Jun 2014 11:53:49 +0200, Adi Kriegisch stated:
On Wed, May 21, 2014 at 09:14:26PM +0200, Robert Schetterer wrote:
Am 21.05.2014 19:47, schrieb Sebastian Goodrick:
I just installed the (rapid-ssl) certificate and it works now.
Needless to say that I don't understand it. The old
On Thu, 26 Jun 2014 11:53:49 +0200, Adi Kriegisch stated:
I am struggling with the same issue for some time now: win8/outlook isn't
able to connect to dovecot 2.2.9 (from Debian/backports); the error on the
outlook side of things is 0x800CCC0E which is really helpful.
A listing of all of
Hi!
I am struggling with the same issue for some time now: win8/outlook isn't
able to connect to dovecot 2.2.9 (from Debian/backports); the error on the
outlook side of things is 0x800CCC0E which is really helpful.
A listing of all of Window's error codes:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 26 Jun 2014, Adi Kriegisch wrote:
I am struggling with the same issue for some time now: win8/outlook isn't
able to connect to dovecot 2.2.9 (from Debian/backports); the error on the
outlook side of things is 0x800CCC0E which is really
Hey!
0x800CCC0E IXP_E_FAILED_TO_CONNECT Cannot connect to server
Pretty helpful error message after all... ;-)
Well, _did_ you've verified that the connection is started at all?
Yup. As written in my first mail, the client tears down the connection
after the ssl key exchange with a FIN,ACK.
Am 26.06.2014 11:53, schrieb Adi Kriegisch:
On Wed, May 21, 2014 at 09:14:26PM +0200, Robert Schetterer wrote:
Am 21.05.2014 19:47, schrieb Sebastian Goodrick:
I just installed the (rapid-ssl) certificate and it works now.
Needless to say that I don't understand it. The old certificate worked
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
every official up2date ssl crt should work, also dont forget to
include intermediate crt/pem in your ssl dove chain
I just installed the (rapid-ssl) certificate and it works now.
Needless to say that I don't understand it. The old certificate
Am 21.05.2014 19:47, schrieb Sebastian Goodrick:
every official up2date ssl crt should work, also dont forget to
include intermediate crt/pem in your ssl dove chain
I just installed the (rapid-ssl) certificate and it works now.
Needless to say that I don't understand it. The old
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Sebastian, sorry for the delay ,i could not reproduce your
problem, speculate you have wrong settings in your server/client
setup and/or you have firewall loadbalancers, proxies between
server and client which fail with some ciphers
Thank you
Am 18.05.2014 20:04, schrieb Sebastian Goodrick:
Hi Sebastian, sorry for the delay ,i could not reproduce your
problem, speculate you have wrong settings in your server/client
setup and/or you have firewall loadbalancers, proxies between
server and client which fail with some ciphers
Thank
Am 09.05.2014 08:29, schrieb Sebastian Goodrick:
my speculate was, it leaves too less ciphers left
OK, but does the old dovecot/openssl version provide less ciphers than
the new install?
sorry i am short in time
dovecot hast setup options for ciphers related to your openssl version
please
Am 08.05.2014 21:29, schrieb Sebastian Goodrick:
perhaps this has impact...just an idea
http://blogs.technet.com/b/secguide/archive/2014/04/07/why-we-re-not-recommending-fips-mode-anymore.aspx
so my specutlation, on win 8 fips mode enabled ,is default
currently, ( please verify this ) ,
14 matches
Mail list logo
