On Mon, Mar 29, 2021 at 04:06:51PM -0400, Viktor Dukhovni wrote:
> > On Mar 29, 2021, at 3:45 PM, Tomas Habarta wrote:
> >
> > 6663]: recvmsg(128, {msg_name=NULL, msg_namelen=0, msg_iov=[{iov_base="\0",
> > iov_len=1}], msg_iovlen=1, msg_controllen=0, msg_flags=MSG_CTRUNC}, 0) = 1
> > [7141]:
> On Mar 29, 2021, at 3:45 PM, Tomas Habarta wrote:
>
> 6663]: recvmsg(128, {msg_name=NULL, msg_namelen=0, msg_iov=[{iov_base="\0",
> iov_len=1}], msg_iovlen=1, msg_controllen=0, msg_flags=MSG_CTRUNC}, 0) = 1
> [7141]: recvmsg(128, {msg_name=NULL, msg_namelen=0, msg_iov=[{iov_base="\0",
>
On Mon, Mar 29, 2021 at 01:22:38PM -0400, Wietse Venema wrote:
> Tomas Habarta:
> > Hello,
> >
> > I would like to ask about the following encountered during selinux testing:
> > * currently running 3.5.8 self-compiled (no vendor packaging), centos8
> > (selinux disabled)
> > * target platform
Tomas Habarta:
> Hello,
>
> I would like to ask about the following encountered during selinux testing:
> * currently running 3.5.8 self-compiled (no vendor packaging), centos8
> (selinux disabled)
> * target platform centos8 (same configuration but selinux enabled)
Best bet is to strace the
On Mon, Mar 29, 2021 at 06:36:10PM +0200, Tomas Habarta wrote:
> selinux enabled:
> transaction fails with:
>
> tlsproxy[23256]: warning: tlsp_get_fd_event: receive remote SMTP peer file
> descriptor: Success
> tlsproxy[23256]: TLS handshake failed for service=smtp pee
ransaction fails with:
tlsproxy[23256]: warning: tlsp_get_fd_event: receive remote SMTP peer file
descriptor: Success
tlsproxy[23256]: TLS handshake failed for service=smtp peer=[10.25.41.35]:25
tlsproxy[23256]: connection closed fd 128
tlsproxy[23256]: DISCONNECT [10.25.41.35]:25
The "w
message was received at Mon, 6 Jul 2009 15:30:05 +0200
from myserver.mydomain.tld [xxx.yyy.www.zzz]
- Transcript of session follows -
recipie...@recipdomain.tld,recipie...@recipdomain.tld...
Deferred: 403 4.7.0 TLS handshake failed.
Warning: message still undelivered after 4 hours
On 7/9/2009, Rocco Scappatura (rocco.scappat...@infracom.it) wrote:
# postconf -d | grep tls
? This shows defaults... please use postconf -n output - and no need to
filter it, it won't (shouldn't) be all that long...
--
Best regards,
Charles
Rocco Scappatura:
# postconf -d | grep tls
What web page is telling you to use postconf -d for
trouble shooting? It should say postconf -n instead.
Wietse
Thanks,
-Original Message-
From: owner-postfix-us...@postfix.org [mailto:owner-postfix-
us...@postfix.org] On Behalf Of Charles Marcus
Sent: Thursday, July 09, 2009 12:43 PM
To: postfix-users@postfix.org
Subject: Re: TLS handshake failed
On 7/9/2009, Rocco Scappatura
Hello,
-Original Message-
From: owner-postfix-us...@postfix.org [mailto:owner-postfix-
us...@postfix.org] On Behalf Of Wietse Venema
Sent: Thursday, July 09, 2009 12:47 PM
To: Postfix users
Subject: Re: TLS handshake failed
Rocco Scappatura:
# postconf -d | grep tls
What web
...
Deferred: 403 4.7.0 TLS handshake failed.
Warning: message still undelivered after 4 hours
Will keep trying until message is 4 days old
This problem is downstream of your server. The server that received
the mail from you is unable to deliver it further, because it cannot
establish a TLS connection
Thanks Victor,
-Original Message-
From: owner-postfix-us...@postfix.org [mailto:owner-postfix-
us...@postfix.org] On Behalf Of Victor Duchovni
Sent: Thursday, July 09, 2009 2:11 PM
To: postfix-users@postfix.org
Subject: Re: TLS handshake failed
On Thu, Jul 09, 2009 at 10:11:26AM
13 matches
Mail list logo
