? From: hamdi201...@gmail.comSent: February 7, 2020 10:37 PMTo: postfix-users@postfix.orgSubject: warning: TLS library problem: routines:ssl_choose_client_version:unsupported protocol? Hi everyone
On Sat, Feb 08, 2020 at 09:36:41AM +0300, Andreas X wrote:
> Hi everyone. I have a php contact form, that reports the following postfix
> error (getting that in maillog file): https://hastepaste.com/view/jr41N
It is rude to post links to pastebins. If you want help, please paste
all the logs for
Hi everyone. I have a php contact form, that reports the following postfix
error (getting that in maillog file): https://hastepaste.com/view/jr41N
The same applies for, when I send an e-mail to that e-mail address by using
Outlook.
Obviously my mail server having troubles sending e-mails to some
> On Apr 29, 2018, at 12:06 PM, Dominic Raferd wrote:
>
>
> Thanks Viktor, I will bear this in mind for the future. But even if
> (with your help) I could determine exactly what the problem was for
> these two senders I think there is zero chance they would be
> interested in hearing from me a
On 29 April 2018 at 16:57, Viktor Dukhovni wrote:
>
>
>> On Apr 29, 2018, at 3:37 AM, Dominic Raferd wrote:
>>
>> This is a genuine and expected sender (VoIP provider). I am less sure
>> about atlas.net.tr, but it is probably genuine and expected by
>> recipient too. Unwanted ones I have not both
> On Apr 29, 2018, at 3:37 AM, Dominic Raferd wrote:
>
> This is a genuine and expected sender (VoIP provider). I am less sure
> about atlas.net.tr, but it is probably genuine and expected by
> recipient too. Unwanted ones I have not bothered to report here.
>
> I don't require encryption on p
On 29 April 2018 at 08:35, Viktor Dukhovni wrote:
>
>
>> On Apr 29, 2018, at 3:28 AM, @lbutlr wrote:
>>
>> It appears that Swiss domain uses Google for their email:
>>
>> finarea.ch. 21599 IN MX 20 alt2.aspmx.l.google.com.
>> finarea.ch. 21599 IN MX 30
> On Apr 29, 2018, at 3:28 AM, @lbutlr wrote:
>
> It appears that Swiss domain uses Google for their email:
>
> finarea.ch. 21599 IN MX 20 alt2.aspmx.l.google.com.
> finarea.ch. 21599 IN MX 30 aspmx2.googlemail.com.
> finarea.ch. 21599 IN
On 29 Apr 2018, at 01:18, Dominic Raferd wrote:
> I've now found similar fall-backs for atlas.net.tr (Turkish service
> provider) - same TLS problem 'error:1408A10B:SSL
> routines:ssl3_get_client_hello:wrong version number:s3_srvr.c:960:'. I
> guess that (in both cases) this is because the incomin
fix/smtpd[6043]: connect from
smtp1.finarea.ch[77.72.174.188]
2018-03-26 00:29:22 ourdomain postfix/smtpd[6043]: SSL_accept error
from smtp1.finarea.ch[77.72.174.188]: -1
2018-03-26 00:29:22 ourdomain postfix/smtpd[6043]: warning: TLS
library problem: error:1408A10B:SSL
routines:ssl3_get_client_hello:wro
> On Apr 28, 2018, at 3:40 AM, Dominic Raferd wrote:
>
> So far I have one genuine sender that is failing TLS, but upon
> checking I see that it falls back to cleartext.
It'd be interesting to know why that particular sender is having
trouble. Can you provide more detail?
Some senders have S
On 27 April 2018 at 17:17, Viktor Dukhovni wrote:
>
>
>> On Apr 27, 2018, at 2:22 AM, Dominic Raferd wrote:
>>
>> $ grep -a "warning: TLS library problem" /var/log/mail.log.1
>> /var/log/mail.log|grep -o "error:.*"|sort|uniq -c|sort -nr
>>
> On Apr 27, 2018, at 2:22 AM, Dominic Raferd wrote:
>
> $ grep -a "warning: TLS library problem" /var/log/mail.log.1
> /var/log/mail.log|grep -o "error:.*"|sort|uniq -c|sort -nr
> 12 error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version
&g
ils of the reported error messages over the recent period can
>> be summarised thus:
>>
>> $ grep -a "warning: TLS library problem" /var/log/mail.log.1
>> /var/log/mail.log|grep -o "error:.*"|sort|uniq -c|sort -nr
>> 12 error:1408F10B:SSL routines:SSL
could be read as
> implying an internal problem on my mailserver. Which is true?
>
> The details of the reported error messages over the recent period can
> be summarised thus:
>
> $ grep -a "warning: TLS library problem" /var/log/mail.log.1
> /var/log/mail.log|grep -o
/host, but the messages could be read as
implying an internal problem on my mailserver. Which is true?
The details of the reported error messages over the recent period can
be summarised thus:
$ grep -a "warning: TLS library problem" /var/log/mail.log.1
/var/log/mail.log|grep -o "er
On Jan 24, 2018, at 9:25 PM, li...@lazygranch.com wrote:
postfix/smtpd[14755]: warning: TLS library problem: error:140760FC:SSL
routines:SSL23_GET_CLIENT_HELLO:unknown protocol:s23_srvr.c:640:
Should I be blocking some encryption method? I thought openssl dropped
support for the hackable
> On Jan 24, 2018, at 9:25 PM, li...@lazygranch.com wrote:
>
> postfix/smtpd[14755]: warning: TLS library problem: error:140760FC:SSL
> routines:SSL23_GET_CLIENT_HELLO:unknown protocol:s23_srvr.c:640:
>
> Should I be blocking some encryption method? I thought openssl dropped
postfix/smtpd[14755]: warning: TLS library problem: error:140760FC:SSL
routines:SSL23_GET_CLIENT_HELLO:unknown protocol:s23_srvr.c:640:
Should I be blocking some encryption method? I thought openssl dropped
support for the hackable protocols.
On Behalf Of Thomas Glanzmann
>
> Has someone an idea what the problem is here and how I can get a
> workaround to
> not offer startssl to the hays mailservers?
smtpd_discard_ehlo_keyword_address_maps
Mit freundlichen Grüßen
Drießen
--
Software & Computer
Uwe Drießen
Lembergstraße 33
67824
20 13:15:04 infra postfix/smtpd[457]: warning: TLS library problem:
457:error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version
number:s3_pkt.c:293:
Sep 20 13:15:04 infra postfix/smtpd[457]: lost connection after STARTTLS from
mail2.hays.de[93.188.241.74]
Sep 20 13:15:04 infra postfix/smtpd
21 matches
Mail list logo
