openssl s_client -connect mail.example.fr:465
CONNECTED(00000003)
406766E2C4700000:error:0A00010B:SSL routines:ssl3_get_record:wrong version number:../ssl/record/ssl3_record.c:354:
---
no peer certificate available
---
No client certificate CA names sent
---
SSL handshake has read 5 bytes and written 316 bytes
Verification: OK
---
New, (NONE), Cipher is (NONE)
Secure Renegotiation IS NOT supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
Early data was not sent
Verify return code: 0 (ok)
---
i don't understand anything at this time, may you can help me?
@nigihayami I assume you know that be filtered or closed you will not have access to the service on the port. Thus checking the certificate remotely is difficult at best and likely impossible.
Your IPv4 address looks from Telenor (Nordic countries and Asia)
Yet, your IPv6 address looks from Orange (France)
Does that seem right to you? My tool might be wrong but usually is right
Some of the tests above are only checking IPv4 address. I can't reach your domain on port 443 or port 465 on IPv4 or IPv6 right now but should check both once you have the right IP and the ports open.
I'm not sure what you're trying to achieve. These are some TLS directives for the OUTGOING SMTP CLIENT of Postfix. It does NOT enable TLS for INCOMING connections to your SMTP daemon.
The openssl s_client command you're running suggests you're testing the incoming SMTP daemon TLS setting, which is not congruent with your configuration in Postfix. At least, not what you've shown.
I do see you've gotten a certificate for your hostname: crt.sh | 13992600793. But did you also configure it in Postfix?
yes i did it, but now i have to recover my system, one backup of 50GB to be deployed. I must not edit any cert whereas it's a big mistake, 2 days lost.
I have finished to configure my server and everything is all right;
Linux Apache Mysql Php Postfix Dovecot Opendkim through this link: https://www.kohaku.fr
Now i am less stupid i have learn a lot, thanks to letsencrypt i'm secured.