> On Feb 19, 2019, at 7:35 AM, A. Schulze <s...@andreasschulze.de> wrote:
>
> Feb 19 13:25:53 spider postfix/master[2282]: warning: process
> /usr/lib/postfix/tlsproxy pid 996 killed by signal 11
> Feb 19 13:25:53 spider postfix/master[2282]: warning:
> /usr/lib/postfix/tlsproxy: bad command startup -- throttling
> Feb 19 13:26:53 spider postfix/tlsproxy[1021]: warning: No server certs
> available. TLS can't be enabled
> Feb 19 13:26:53 spider postfix/master[2282]: warning: process
> /usr/lib/postfix/tlsproxy pid 1021 killed by signal 11
> Feb 19 13:26:53 spider postfix/master[2282]: warning:
> /usr/lib/postfix/tlsproxy: bad command startup -- throttling
> Feb 19 13:27:53 spider postfix/tlsproxy[1046]: warning: No server certs
> available. TLS can't be enabled
> Feb 19 13:27:53 spider postfix/master[2282]: warning: process
> /usr/lib/postfix/tlsproxy pid 1046 killed by signal 11
> Feb 19 13:27:53 spider postfix/master[2282]: warning:
> /usr/lib/postfix/tlsproxy: bad command startup -- throttling
> Feb 19 13:28:53 spider postfix/tlsproxy[1061]: warning: No server certs
> available. TLS can't be enabled
> Feb 19 13:28:53 spider postfix/master[2282]: warning: process
> /usr/lib/postfix/tlsproxy pid 1061 killed by signal 11
> Feb 19 13:28:53 spider postfix/master[2282]: warning:
> /usr/lib/postfix/tlsproxy: bad command startup -- throttling
>
> The discussion between Wietse and Viktor addresses exactly that point.
> I only want to show/agree, Viktors Patch isn't ready to release.
Is that *with* my patch applied? For me, applying the patch
made the segfaults in a certificateless proxy configuration
go away. I see the same segfaults with 3.4.0-RC2 unpatched,
but not with the patch...
--
Viktor.
