TLS Handshake Problems

2017-11-28 Thread Nikolaos Milas
Hello, I have just started using in production a mail server running Postfix 3.2.4 on CentOS 7.4 (fully patched) with openssl 1.0.2k. This is a new server, replacing an old CentOS 5.11 with Postfix 2.6.11 and OpenSSL 0.9.8e. On the new server I see errors on particular servers as follows; t

Re: TLS Handshake Problems

2017-11-28 Thread Viktor Dukhovni
On Tue, Nov 28, 2017 at 09:27:49PM +0200, Nikolaos Milas wrote: > Nov 28 12:55:43 vmail2 postfix/smtp[782]: SSL_connect error to > rcs12.rc.auth.gr[155.207.51.12]:25: lost connection > Nov 28 12:55:43 vmail2 postfix/smtp[782]: 4623A80004F2F: Cannot start TLS: > handshake failure > Nov 28 12:55:4

Re: TLS Handshake Problems

2017-11-28 Thread Nikolaos Milas
On 28/11/2017 9:57 μμ, Viktor Dukhovni wrote: This is expected. ... Thank you Viktor for the detailed analysis and for your time. I appreciate it very much. All the best, Nick

Kerberos principal name mismatch

2017-11-28 Thread Anvar Kuchkartaev
‎Hello I configured 2x postfix instances which uses shared disk as mail storage and they act as MX server and smtp server at same time. First server mx0.example.com and mx1.example.com and smtp.example.com points to ip address of both servers. The service principal smtp/mx0.example@example.com

What am I missing in this client check???

2017-11-28 Thread Bill Cole
I fear that I've misunderstood something for a very long time... Why might hwsrv-205226.hostwindsdns.com not be hitting the (redundant, I think) entries here? bigsky:~ root# postmap -vs /etc/postfix/client_checks postmap: name_mask: ipv4 postmap: inet_addr_local: configured 5 IPv4 add

Re: Kerberos principal name mismatch

2017-11-28 Thread Viktor Dukhovni
On Wed, Nov 29, 2017 at 12:31:21AM +0100, Anvar Kuchkartaev wrote: >Hello I configured 2x postfix instances which uses shared disk as mail >storage and they act as MX server and smtp server at same time. First >server mx0.example.com and mx1.example.com and smtp.example.com points >

Re: What am I missing in this client check???

2017-11-28 Thread Viktor Dukhovni
On Tue, Nov 28, 2017 at 08:57:05PM -0500, Bill Cole wrote: > I fear that I've misunderstood something for a very long time... > > Why might hwsrv-205226.hostwindsdns.com not be hitting the (redundant, I > think) entries here? The postmap(1) command does not support any of the partial key lookups

Re: What am I missing in this client check???

2017-11-28 Thread Bill Cole
On 28 Nov 2017, at 21:09 (-0500), Viktor Dukhovni wrote: On Tue, Nov 28, 2017 at 08:57:05PM -0500, Bill Cole wrote: I fear that I've misunderstood something for a very long time... Why might hwsrv-205226.hostwindsdns.com not be hitting the (redundant, I think) entries here? The postmap(1)

Slow delivery of mails reg.

2017-11-28 Thread anant
Hi, We have a internal relay configured in our setup.  The relay host had stopped accepting mails as the system was hanging and we could resolve it only after about 8 hrs.  Meanwhile the queue built up and there were about 80,000 mails in queue to relay to the relay host.  Once the system was m

Re: Slow delivery of mails reg.

2017-11-28 Thread Viktor Dukhovni
On Wed, Nov 29, 2017 at 09:20:21AM +0530, an...@isac.gov.in wrote: > We have a internal relay configured in our setup.  The relay host hadstopped > accepting mails as the system was hanging and we could resolve > it only after about 8 hrs.  Meanwhile the queue built up and there > were about 80,00

Re: Slow delivery of mails reg.

2017-11-28 Thread anant
- Message from Viktor Dukhovni -     Date: Wed, 29 Nov 2017 04:47:35 +     From: Viktor Dukhovni Reply-To: postfix-users@postfix.org Subject: Re: Slow delivery of mails reg.       To: postfix-users@postfix.org On Wed, Nov 29, 2017 at 09:20:21AM +0530, an...@isac.gov.in wrote:

Re: Slow delivery of mails reg.

2017-11-28 Thread Viktor Dukhovni
On Wed, Nov 29, 2017 at 12:04:14PM +0530, an...@isac.gov.in wrote: > > To understand why delivery was slow you need to analyze your logs > > and examine the "delays=" log entries to see whether the delays > > in connecting to the relay host or waiting for deliveries to > > complete. > > > > --