I've been putting together a patch that fixes the TLS error reporting so
that it respects the incoming_interface log selector. This is so that the
postmaster can find out if a client is connecting to port 25 or 465 or
587, which is useful for M$ MUAs that have stupid TLS implementations.
I think the OpenSSL version works OK. I'd be grateful if someone can check
out the GnuTLS version.
Tony.
--
<fanf@exim.org> <dot@dotat.at> http://dotat.at/ ${sg{\N${sg{\
N\}{([^N]*)(.)(.)(.*)}{\$1\$3\$2\$1\$3\n\$2\$3\$4\$3\n\$3\$2\$4}}\
\N}{([^N]*)(.)(.)(.*)}{\$1\$3\$2\$1\$3\n\$2\$3\$4\$3\n\$3\$2\$4}}
that it respects the incoming_interface log selector. This is so that the
postmaster can find out if a client is connecting to port 25 or 465 or
587, which is useful for M$ MUAs that have stupid TLS implementations.
I think the OpenSSL version works OK. I'd be grateful if someone can check
out the GnuTLS version.
Tony.
--
<fanf@exim.org> <dot@dotat.at> http://dotat.at/ ${sg{\N${sg{\
N\}{([^N]*)(.)(.)(.*)}{\$1\$3\$2\$1\$3\n\$2\$3\$4\$3\n\$3\$2\$4}}\
\N}{([^N]*)(.)(.)(.*)}{\$1\$3\$2\$1\$3\n\$2\$3\$4\$3\n\$3\$2\$4}}
Attached Files:
-
tls.patch (20.5 KB)