Mail@domain.com is a valid deliverable e-mail box address BUT does not send or receive

Support and Discussion
, ,
1

Hello everybody,

I do not know more what should I do.

I created one e-mail box using the maindomain, but I cannot send or receive any email.

Please see the logfile and configuration of the server below and I appreciate very much any help.

Jul 28 11:26:46 vmi1359256 postfix/smtpd[55065]: error: open database /etc/postfix/vmail_ssl.map.db: No such file or directory

Jul 28 11:26:47 vmi1359256 postfix/smtpd[55065]: connect from keeper-us-east-1d.mxtoolbox.com[18.209.86.113]

Jul 28 11:26:47 vmi1359256 postfix/smtpd[55065]: NOQUEUE: reject: RCPT from keeper-us-east-1d.mxtoolbox.com[18.209.86.113]: 554 5.7.1 <test@mxtoolboxsmtpdiag.com>: 
Relay access denied; from=<supertool@mxtoolboxsmtpdiag.com> to=<test@mxtoolboxsmtpdiag.com> proto=ESMTP helo=<keeper-us-east-1d.mxtoolbox.com>

Jul 28 11:26:47 vmi1359256 postfix/smtpd[55065]: disconnect from keeper-us-east-1d.mxtoolbox.com[18.209.86.113] ehlo=1 mail=1 rcpt=0/1 quit=1 commands=3/4

Jul 28 11:26:48 vmi1359256 postfix/smtpd[55065]: connect from keeper-us-east-1d.mxtoolbox.com[18.209.86.113]

Jul 28 11:26:49 vmi1359256 postfix/smtpd[55065]: NOQUEUE: reject: RCPT from keeper-us-east-1d.mxtoolbox.com[18.209.86.113]: 554 5.7.1 <test@mxtoolboxsmtpdiag.com>: 
Relay access denied; from=<supertool@mxtoolboxsmtpdiag.com> to=<test@mxtoolboxsmtpdiag.com> proto=ESMTP helo=<keeper-us-east-1d.mxtoolbox.com>

Jul 28 11:26:49 vmi1359256 postfix/smtpd[55065]: disconnect from keeper-us-east-1d.mxtoolbox.com[18.209.86.113] ehlo=1 mail=1 rcpt=0/1 quit=1 commands=3/4

Jul 28 11:28:28 vmi1359256 dovecot: imap-login: Login: user=<contato@domain.com>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=55081, TLS, session=<6tHu5IwBfrF/AAAB>

Jul 28 11:28:28 vmi1359256 dovecot: imap(contato@domain.com)<55081><6tHu5IwBfrF/AAAB>: Logged out in=327 out=1042 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0 body_count=0 body_bytes=0

Jul 28 11:28:28 vmi1359256 dovecot: imap-login: Login: user=<contato@domain.com>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=55082, TLS, session=<jQ/v5IwBhrF/AAAB>

Jul 28 11:28:28 vmi1359256 dovecot: imap(contato@domain.com)<55082><jQ/v5IwBhrF/AAAB>: Logged out in=105 out=931 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0 body_count=0 body_bytes=0

Jul 28 11:30:09 vmi1359256 postfix/anvil[55067]: statistics: max connection rate 2/60s for (smtp:18.209.86.113) at Jul 28 11:26:48

Jul 28 11:30:09 vmi1359256 postfix/anvil[55067]: statistics: max connection count 1 for (smtp:18.209.86.113) at Jul 28 11:26:47

Jul 28 11:30:09 vmi1359256 postfix/anvil[55067]: statistics: max cache size 1 at Jul 28 11:26:47

Jul 28 11:37:10 vmi1359256 dovecot: imap-login: Disconnected (no auth attempts in 0 secs): user=<>, rip=167.94.146.56, lip=144.126.140.222, TLS: Connection closed, session=<vXYOBI0BmsanXpI4>

Jul 28 11:43:28 vmi1359256 dovecot: imap-login: Login: user=<contato@domain.com>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=55508, TLS, session=<iliTGo0BJo9/AAAB>

Jul 28 11:43:28 vmi1359256 dovecot: imap(contato@domain.com)<55508><iliTGo0BJo9/AAAB>: Logged out in=91 out=605 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0 body_count=0 body_bytes=0

Jul 28 11:43:28 vmi1359256 dovecot: imap-login: Login: user=<contato@domain.com>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=55509, TLS, session=<sl+TGo0BLo9/AAAB>

Jul 28 11:43:28 vmi1359256 dovecot: imap(contato@domain.com)<55509><sl+TGo0BLo9/AAAB>: Logged out in=105 out=931 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0 body_count=0 body_bytes=0

Jul 28 11:51:00 vmi1359256 dovecot: imap-login: Login: user=<contato@domain.com>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=55533, TLS, session=<Sg9+NY0BYJl/AAAB>

Jul 28 11:51:00 vmi1359256 dovecot: imap(contato@domain.com)<55533><Sg9+NY0BYJl/AAAB>: Logged out in=11 out=462 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0 body_count=0 body_bytes=0

Jul 28 11:51:00 vmi1359256 dovecot: imap-login: Login: user=<contato@domain.com>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=55535, TLS, session=<LteFNY0BcJl/AAAB>

Jul 28 11:51:00 vmi1359256 dovecot: imap(contato@domain.com)<55535><LteFNY0BcJl/AAAB>: Logged out in=124 out=1334 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0 body_count=0 body_bytes=0

Jul 28 11:51:01 vmi1359256 dovecot: imap-login: Login: user=<contato@domain.com>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=55540, TLS, session=<OcuSNY0BgJl/AAAB>

Jul 28 11:51:01 vmi1359256 dovecot: imap(contato@domain.com)<55540><OcuSNY0BgJl/AAAB>: Logged out in=105 out=931 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0 body_count=0 body_bytes=0

Jul 28 11:51:51 vmi1359256 dovecot: imap-login: Login: user=<contato@domain.com>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=55542, TLS, session=<FVmJOI0BfrB/AAAB>

Jul 28 11:51:51 vmi1359256 postfix/submission/smtpd[55543]: error: open database /etc/postfix/vmail_ssl.map.db: No such file or directory

Jul 28 11:51:51 vmi1359256 postfix/submission/smtpd[55543]: connect from localhost[127.0.0.1]

Jul 28 11:51:51 vmi1359256 postfix/submission/smtpd[55543]: warning: hash:/etc/postfix/vmail_ssl.map is unavailable. open database /etc/postfix/vmail_ssl.map.db: No such file or directory

Jul 28 11:51:51 vmi1359256 postfix/submission/smtpd[55543]: warning: hash:/etc/postfix/vmail_ssl.map lookup error for "localhost"

Jul 28 11:51:51 vmi1359256 postfix/submission/smtpd[55543]: warning: tls_server_sni_maps: localhost map lookup problem

Jul 28 11:51:51 vmi1359256 postfix/submission/smtpd[55543]: SSL_accept error from localhost[127.0.0.1]: -1

Jul 28 11:51:51 vmi1359256 postfix/submission/smtpd[55543]: warning: TLS library problem: error:1422E0EA:SSL routines:final_server_name:callback failed:../ssl/statem/extensions.c:1006:

Jul 28 11:51:51 vmi1359256 postfix/submission/smtpd[55543]: lost connection after STARTTLS from localhost[127.0.0.1]

Jul 28 11:51:51 vmi1359256 postfix/submission/smtpd[55543]: disconnect from localhost[127.0.0.1] ehlo=1 starttls=0/1 commands=1/2

Jul 28 11:51:51 vmi1359256 dovecot: imap(contato@domain.com)<55542><FVmJOI0BfrB/AAAB>: Logged out in=11 out=462 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0 body_count=0 body_bytes=0

Jul 28 11:51:51 vmi1359256 dovecot: imap-login: Login: user=<contato@domain.com>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=55546, TLS, session=<OISSOI0BhLB/AAAB>

Jul 28 11:51:51 vmi1359256 dovecot: imap(contato@domain.com)<55546><OISSOI0BhLB/AAAB>: Logged out in=119 out=948 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0 body_count=0 body_bytes=0

Here is the test made through ip-tracker.org

MXTOOLMAIL-01
MXTOOLMAIL-011009×615 21.7 KB

Here is the test made through mxtoolbox.com

MXTOOL-01
MXTOOL-011336×535 31.5 KB

Please I appreciate any help. I am since two days trying to solve this issue.

2

More settings:

Server: Ubuntu 20.04

CyberPanel

Current Version: 2.3
Build: 4Current Commit: 63cd467b5a7882ad2b4a207ce748e8446838c376
Latest Version: 2.3
Latest Build: 4Latest Commit: a2a2bd93a3957bcae0af42e8c5fbf1184cf847cc

root@vmi13:~# journalctl -f | grep postfix
Jul 28 13:02:09 vmi1359256.contaboserver.net postfix/anvil[58784]: statistics: max connection rate 2/60s for (smtp:142.93.73.156) at Jul 28 12:58:48

Jul 28 13:02:09 vmi1359256.contaboserver.net postfix/anvil[58784]: statistics: max connection count 1 for (smtp:142.93.73.156) at Jul 28 12:58:41

Jul 28 13:02:09 vmi1359256.contaboserver.net postfix/anvil[58784]: statistics: max cache size 1 at Jul 28 12:58:41

Here is the test made through //email/testTo:

Checking contato@domain.com from www12-do.checktls.com(V03.71.00) at 2023-07-28T15:58:32Z:

seconds		lookup	result
[000.000]	    	DNS LOOKUPS
[000.050]	    	SEARCHLIST	104.131.108.216,134.209.169.224,1.1.1.1,8.8.8.8,67.207.67.3
[000.079]	    	MX	(0) inbound-smtp.us-east-1.amazonaws.com
[000.080]	    	MX	(0) mail.domain.com
[000.080]	    	MX	(1) inbound-smtp.us-east-1.amazonaws.com
[000.080]	    	MX	(10) mail.domain.com
[000.134]	    	MX:A-->inbound-smtp.us-east-1.amazonaws.com	3.211.210.226
[000.135]	    	MX:A-->inbound-smtp.us-east-1.amazonaws.com	44.206.9.87
[000.135]	    	MX:A-->inbound-smtp.us-east-1.amazonaws.com	44.210.166.32
[000.135]	    	MX:A-->inbound-smtp.us-east-1.amazonaws.com	54.164.173.191
[000.135]	    	MX:A-->inbound-smtp.us-east-1.amazonaws.com	54.197.5.236
[000.142]	    	MX:A-->mail.domain.com	144.126.140.222
[000.145]	    	MX:A-->inbound-smtp.us-east-1.amazonaws.com	3.211.210.226
[000.145]	    	MX:A-->inbound-smtp.us-east-1.amazonaws.com	44.206.9.87
[000.145]	    	MX:A-->inbound-smtp.us-east-1.amazonaws.com	44.210.166.32
[000.145]	    	MX:A-->inbound-smtp.us-east-1.amazonaws.com	54.164.173.191
[000.146]	    	MX:A-->inbound-smtp.us-east-1.amazonaws.com	54.197.5.236
[000.158]	    	MX:A-->mail.domain.com	144.126.140.222
seconds		test stage and result
[000.000]		Trying TLS on inbound-smtp.us-east-1.amazonaws.com[3.211.210.226:25] (0)
[000.019]		Server answered
[000.019]	<‑‑	220 inbound-smtp.us-east-1.amazonaws.com ESMTP Amazon SES yLzNjcrlfgwVkYgyzoV5
[000.019]		We are allowed to connect
[000.019]	‑‑>	EHLO www12-do.checktls.com
[000.030]	<‑‑	250-inbound-smtp.us-east-1.amazonaws.com
250-8BITMIME
250-STARTTLS
250 Ok
[000.030]		We can use this server
[000.031]		TLS is an option on this server
[000.031]	‑‑>	STARTTLS
[000.041]	<‑‑	220 Ready to start TLS
[000.041]		STARTTLS command works on this server
[000.125]		Connection converted to SSL
SSLVersion in use: TLSv1_3
Cipher in use: TLS_AES_256_GCM_SHA384
Perfect Forward Secrecy: yes
Session Algorithm in use: Curve P-256 DHE(256 bits)
Certificate #1 of 5 (sent by MX):
Cert VALIDATED: ok
Cert Hostname VERIFIED (inbound-smtp.us-east-1.amazonaws.com = inbound-smtp.us-east-1.amazonaws.com | DNS:inbound-smtp.us-east-1.amazonaws.com)
Not Valid Before: Mar 16 00:00:00 2023 GMT
Not Valid After: Dec 22 23:59:59 2023 GMT
subject: /CN=inbound-smtp.us-east-1.amazonaws.com
issuer: /C=US/O=Amazon/CN=Amazon RSA 2048 M01
Certificate #2 of 5 (sent by MX):
Cert VALIDATED: ok
Not Valid Before: Aug 23 22:21:28 2022 GMT
Not Valid After: Aug 23 22:21:28 2030 GMT
subject: /C=US/O=Amazon/CN=Amazon RSA 2048 M01
issuer: /C=US/O=Amazon/CN=Amazon Root CA 1
Certificate #3 of 5 (added from CA Root Store):
Cert VALIDATED: ok
Not Valid Before: May 26 00:00:00 2015 GMT
Not Valid After: Jan 17 00:00:00 2038 GMT
subject: /C=US/O=Amazon/CN=Amazon Root CA 1
issuer: /C=US/O=Amazon/CN=Amazon Root CA 1
Certificate #4 of 5 (sent by MX):
Cert VALIDATED:
Not Valid Before: May 25 12:00:00 2015 GMT
Not Valid After: Dec 31 01:00:00 2037 GMT
subject: /C=US/O=Amazon/CN=Amazon Root CA 1
issuer: /C=US/ST=Arizona/L=Scottsdale/O=Starfield Technologies, Inc./CN=Starfield Services Root Certificate Authority - G2
Certificate #5 of 5 (sent by MX):
Cert VALIDATED:
Not Valid Before: Sep  2 00:00:00 2009 GMT
Not Valid After: Jun 28 17:39:16 2034 GMT
subject: /C=US/ST=Arizona/L=Scottsdale/O=Starfield Technologies, Inc./CN=Starfield Services Root Certificate Authority - G2
issuer: /C=US/O=Starfield Technologies, Inc./OU=Starfield Class 2 Certification Authority
[000.793]	~~>	EHLO www12-do.checktls.com
[000.828]	<~~	250-inbound-smtp.us-east-1.amazonaws.com
250-8BITMIME
250-STARTTLS
250 Ok
[000.828]		TLS successfully started on this server
[000.829]		warning: STARTTLS after second EHLO (see RFC3207 #4.2)
[000.829]	~~>	MAIL FROM:<test@checktls.com>
[000.840]	<~~	250 Ok
[000.840]		Sender is OK
[000.841]	~~>	QUIT
[000.852]	<~~	221 Bye 
seconds		test stage and result
[000.000]		Trying TLS on inbound-smtp.us-east-1.amazonaws.com[44.206.9.87:25] (0)
[000.012]		Server answered
[000.023]	<‑‑	220 inbound-smtp.us-east-1.amazonaws.com ESMTP Amazon SES YmMIcAq5UYejqeb3lmmV
[000.023]		We are allowed to connect
[000.023]	‑‑>	EHLO www12-do.checktls.com
[000.034]	<‑‑	250-inbound-smtp.us-east-1.amazonaws.com
250-8BITMIME
250-STARTTLS
250 Ok
[000.034]		We can use this server
[000.034]		TLS is an option on this server
[000.035]	‑‑>	STARTTLS
[000.055]	<‑‑	220 Ready to start TLS
[000.055]		STARTTLS command works on this server
[000.125]		Connection converted to SSL
SSLVersion in use: TLSv1_3
Cipher in use: TLS_AES_256_GCM_SHA384
Perfect Forward Secrecy: yes
Session Algorithm in use: Curve P-256 DHE(256 bits)
Certificate #1 of 5 (sent by MX):
Cert VALIDATED: ok
Cert Hostname VERIFIED (inbound-smtp.us-east-1.amazonaws.com = inbound-smtp.us-east-1.amazonaws.com | DNS:inbound-smtp.us-east-1.amazonaws.com)
Not Valid Before: Mar 16 00:00:00 2023 GMT
Not Valid After: Dec 22 23:59:59 2023 GMT
subject: /CN=inbound-smtp.us-east-1.amazonaws.com
issuer: /C=US/O=Amazon/CN=Amazon RSA 2048 M01
Certificate #2 of 5 (sent by MX):
Cert VALIDATED: ok
Not Valid Before: Aug 23 22:21:28 2022 GMT
Not Valid After: Aug 23 22:21:28 2030 GMT
subject: /C=US/O=Amazon/CN=Amazon RSA 2048 M01
issuer: /C=US/O=Amazon/CN=Amazon Root CA 1
Certificate #3 of 5 (added from CA Root Store):
Cert VALIDATED: ok
Not Valid Before: May 26 00:00:00 2015 GMT
Not Valid After: Jan 17 00:00:00 2038 GMT
subject: /C=US/O=Amazon/CN=Amazon Root CA 1
issuer: /C=US/O=Amazon/CN=Amazon Root CA 1
Certificate #4 of 5 (sent by MX):
Cert VALIDATED:
Not Valid Before: May 25 12:00:00 2015 GMT
Not Valid After: Dec 31 01:00:00 2037 GMT
subject: /C=US/O=Amazon/CN=Amazon Root CA 1
issuer: /C=US/ST=Arizona/L=Scottsdale/O=Starfield Technologies, Inc./CN=Starfield Services Root Certificate Authority - G2
Certificate #5 of 5 (sent by MX):
Cert VALIDATED:
Not Valid Before: Sep  2 00:00:00 2009 GMT
Not Valid After: Jun 28 17:39:16 2034 GMT
subject: /C=US/ST=Arizona/L=Scottsdale/O=Starfield Technologies, Inc./CN=Starfield Services Root Certificate Authority - G2
issuer: /C=US/O=Starfield Technologies, Inc./OU=Starfield Class 2 Certification Authority
[006.728]	~~>	EHLO www12-do.checktls.com
[006.736]	<~~	250-inbound-smtp.us-east-1.amazonaws.com
250-8BITMIME
250-STARTTLS
250 Ok
[006.736]		TLS successfully started on this server
[006.736]		warning: STARTTLS after second EHLO (see RFC3207 #4.2)
[006.736]	~~>	MAIL FROM:<test@checktls.com>
[006.745]	<~~	250 Ok
[006.745]		Sender is OK
[006.745]	~~>	QUIT
[006.754]	<~~	221 Bye 
seconds		test stage and result
[000.000]		Trying TLS on inbound-smtp.us-east-1.amazonaws.com[44.210.166.32:25] (0)
[000.013]		Server answered
[000.017]	<‑‑	220 inbound-smtp.us-east-1.amazonaws.com ESMTP Amazon SES Ortoz7Rt2jLJ9XFdpRE1
[000.017]		We are allowed to connect
[000.017]	‑‑>	EHLO www12-do.checktls.com
[000.025]	<‑‑	250-inbound-smtp.us-east-1.amazonaws.com
250-8BITMIME
250-STARTTLS
250 Ok
[000.025]		We can use this server
[000.025]		TLS is an option on this server
[000.025]	‑‑>	STARTTLS
[000.033]	<‑‑	220 Ready to start TLS
[000.033]		STARTTLS command works on this server
[000.074]		Connection converted to SSL
SSLVersion in use: TLSv1_3
Cipher in use: TLS_AES_256_GCM_SHA384
Perfect Forward Secrecy: yes
Session Algorithm in use: Curve P-256 DHE(256 bits)
Certificate #1 of 5 (sent by MX):
Cert VALIDATED: ok
Cert Hostname VERIFIED (inbound-smtp.us-east-1.amazonaws.com = inbound-smtp.us-east-1.amazonaws.com | DNS:inbound-smtp.us-east-1.amazonaws.com)
Not Valid Before: Mar 16 00:00:00 2023 GMT
Not Valid After: Dec 22 23:59:59 2023 GMT
subject: /CN=inbound-smtp.us-east-1.amazonaws.com
issuer: /C=US/O=Amazon/CN=Amazon RSA 2048 M01
Certificate #2 of 5 (sent by MX):
Cert VALIDATED: ok
Not Valid Before: Aug 23 22:21:28 2022 GMT
Not Valid After: Aug 23 22:21:28 2030 GMT
subject: /C=US/O=Amazon/CN=Amazon RSA 2048 M01
issuer: /C=US/O=Amazon/CN=Amazon Root CA 1
Certificate #3 of 5 (added from CA Root Store):
Cert VALIDATED: ok
Not Valid Before: May 26 00:00:00 2015 GMT
Not Valid After: Jan 17 00:00:00 2038 GMT
subject: /C=US/O=Amazon/CN=Amazon Root CA 1
issuer: /C=US/O=Amazon/CN=Amazon Root CA 1
Certificate #4 of 5 (sent by MX):
Cert VALIDATED:
Not Valid Before: May 25 12:00:00 2015 GMT
Not Valid After: Dec 31 01:00:00 2037 GMT
subject: /C=US/O=Amazon/CN=Amazon Root CA 1
issuer: /C=US/ST=Arizona/L=Scottsdale/O=Starfield Technologies, Inc./CN=Starfield Services Root Certificate Authority - G2
Certificate #5 of 5 (sent by MX):
Cert VALIDATED:
Not Valid Before: Sep  2 00:00:00 2009 GMT
Not Valid After: Jun 28 17:39:16 2034 GMT
subject: /C=US/ST=Arizona/L=Scottsdale/O=Starfield Technologies, Inc./CN=Starfield Services Root Certificate Authority - G2
issuer: /C=US/O=Starfield Technologies, Inc./OU=Starfield Class 2 Certification Authority
[000.457]	~~>	EHLO www12-do.checktls.com
[000.466]	<~~	250-inbound-smtp.us-east-1.amazonaws.com
250-8BITMIME
250-STARTTLS
250 Ok
[000.466]		TLS successfully started on this server
[000.466]		warning: STARTTLS after second EHLO (see RFC3207 #4.2)
[000.466]	~~>	MAIL FROM:<test@checktls.com>
[000.474]	<~~	250 Ok
[000.474]		Sender is OK
[000.475]	~~>	QUIT
[000.483]	<~~	221 Bye 
seconds		test stage and result
[000.000]		Trying TLS on inbound-smtp.us-east-1.amazonaws.com[54.164.173.191:25] (0)
[000.009]		Server answered
[000.016]	<‑‑	220 inbound-smtp.us-east-1.amazonaws.com ESMTP Amazon SES ua0CtoTgC4qz1MW1Zcs3
[000.016]		We are allowed to connect
[000.017]	‑‑>	EHLO www12-do.checktls.com
[000.024]	<‑‑	250-inbound-smtp.us-east-1.amazonaws.com
250-8BITMIME
250-STARTTLS
250 Ok
[000.024]		We can use this server
[000.025]		TLS is an option on this server
[000.025]	‑‑>	STARTTLS
[000.032]	<‑‑	220 Ready to start TLS
[000.032]		STARTTLS command works on this server
[000.109]		Connection converted to SSL
SSLVersion in use: TLSv1_3
Cipher in use: TLS_AES_256_GCM_SHA384
Perfect Forward Secrecy: yes
Session Algorithm in use: Curve P-256 DHE(256 bits)
Certificate #1 of 5 (sent by MX):
Cert VALIDATED: ok
Cert Hostname VERIFIED (inbound-smtp.us-east-1.amazonaws.com = inbound-smtp.us-east-1.amazonaws.com | DNS:inbound-smtp.us-east-1.amazonaws.com)
Not Valid Before: Mar 16 00:00:00 2023 GMT
Not Valid After: Dec 22 23:59:59 2023 GMT
subject: /CN=inbound-smtp.us-east-1.amazonaws.com
issuer: /C=US/O=Amazon/CN=Amazon RSA 2048 M01
Certificate #2 of 5 (sent by MX):
Cert VALIDATED: ok
Not Valid Before: Aug 23 22:21:28 2022 GMT
Not Valid After: Aug 23 22:21:28 2030 GMT
subject: /C=US/O=Amazon/CN=Amazon RSA 2048 M01
issuer: /C=US/O=Amazon/CN=Amazon Root CA 1
Certificate #3 of 5 (added from CA Root Store):
Cert VALIDATED: ok
Not Valid Before: May 26 00:00:00 2015 GMT
Not Valid After: Jan 17 00:00:00 2038 GMT
subject: /C=US/O=Amazon/CN=Amazon Root CA 1
issuer: /C=US/O=Amazon/CN=Amazon Root CA 1
Certificate #4 of 5 (sent by MX):
Cert VALIDATED:
Not Valid Before: May 25 12:00:00 2015 GMT
Not Valid After: Dec 31 01:00:00 2037 GMT
subject: /C=US/O=Amazon/CN=Amazon Root CA 1
issuer: /C=US/ST=Arizona/L=Scottsdale/O=Starfield Technologies, Inc./CN=Starfield Services Root Certificate Authority - G2
Certificate #5 of 5 (sent by MX):
Cert VALIDATED:
Not Valid Before: Sep  2 00:00:00 2009 GMT
Not Valid After: Jun 28 17:39:16 2034 GMT
subject: /C=US/ST=Arizona/L=Scottsdale/O=Starfield Technologies, Inc./CN=Starfield Services Root Certificate Authority - G2
issuer: /C=US/O=Starfield Technologies, Inc./OU=Starfield Class 2 Certification Authority
[000.553]	~~>	EHLO www12-do.checktls.com
[000.561]	<~~	250-inbound-smtp.us-east-1.amazonaws.com
250-8BITMIME
250-STARTTLS
250 Ok
[000.561]		TLS successfully started on this server
[000.561]		warning: STARTTLS after second EHLO (see RFC3207 #4.2)
[000.561]	~~>	MAIL FROM:<test@checktls.com>
[000.569]	<~~	250 Ok
[000.570]		Sender is OK
[000.570]	~~>	QUIT
[000.578]	<~~	221 Bye 
seconds		test stage and result
[000.000]		Trying TLS on inbound-smtp.us-east-1.amazonaws.com[54.197.5.236:25] (0)
[000.009]		Server answered
[000.017]	<‑‑	220 inbound-smtp.us-east-1.amazonaws.com ESMTP Amazon SES roB7CgXKdaBQ9oZOdA6o
[000.017]		We are allowed to connect
[000.017]	‑‑>	EHLO www12-do.checktls.com
[000.025]	<‑‑	250-inbound-smtp.us-east-1.amazonaws.com
250-8BITMIME
250-STARTTLS
250 Ok
[000.025]		We can use this server
[000.025]		TLS is an option on this server
[000.026]	‑‑>	STARTTLS
[000.033]	<‑‑	220 Ready to start TLS
[000.034]		STARTTLS command works on this server
[000.071]		Connection converted to SSL
SSLVersion in use: TLSv1_3
Cipher in use: TLS_AES_256_GCM_SHA384
Perfect Forward Secrecy: yes
Session Algorithm in use: Curve P-256 DHE(256 bits)
Certificate #1 of 5 (sent by MX):
Cert VALIDATED: ok
Cert Hostname VERIFIED (inbound-smtp.us-east-1.amazonaws.com = inbound-smtp.us-east-1.amazonaws.com | DNS:inbound-smtp.us-east-1.amazonaws.com)
Not Valid Before: Mar 16 00:00:00 2023 GMT
Not Valid After: Dec 22 23:59:59 2023 GMT
subject: /CN=inbound-smtp.us-east-1.amazonaws.com
issuer: /C=US/O=Amazon/CN=Amazon RSA 2048 M01
Certificate #2 of 5 (sent by MX):
Cert VALIDATED: ok
Not Valid Before: Aug 23 22:21:28 2022 GMT
Not Valid After: Aug 23 22:21:28 2030 GMT
subject: /C=US/O=Amazon/CN=Amazon RSA 2048 M01
issuer: /C=US/O=Amazon/CN=Amazon Root CA 1
Certificate #3 of 5 (added from CA Root Store):
Cert VALIDATED: ok
Not Valid Before: May 26 00:00:00 2015 GMT
Not Valid After: Jan 17 00:00:00 2038 GMT
subject: /C=US/O=Amazon/CN=Amazon Root CA 1
issuer: /C=US/O=Amazon/CN=Amazon Root CA 1
Certificate #4 of 5 (sent by MX):
Cert VALIDATED:
Not Valid Before: May 25 12:00:00 2015 GMT
Not Valid After: Dec 31 01:00:00 2037 GMT
subject: /C=US/O=Amazon/CN=Amazon Root CA 1
issuer: /C=US/ST=Arizona/L=Scottsdale/O=Starfield Technologies, Inc./CN=Starfield Services Root Certificate Authority - G2
Certificate #5 of 5 (sent by MX):
Cert VALIDATED:
Not Valid Before: Sep  2 00:00:00 2009 GMT
Not Valid After: Jun 28 17:39:16 2034 GMT
subject: /C=US/ST=Arizona/L=Scottsdale/O=Starfield Technologies, Inc./CN=Starfield Services Root Certificate Authority - G2
issuer: /C=US/O=Starfield Technologies, Inc./OU=Starfield Class 2 Certification Authority
[000.614]	~~>	EHLO www12-do.checktls.com
[000.623]	<~~	250-inbound-smtp.us-east-1.amazonaws.com
250-8BITMIME
250-STARTTLS
250 Ok
[000.623]		TLS successfully started on this server
[000.623]		warning: STARTTLS after second EHLO (see RFC3207 #4.2)
[000.623]	~~>	MAIL FROM:<test@checktls.com>
[000.633]	<~~	250 Ok
[000.633]		Sender is OK
[000.633]	~~>	QUIT
[000.641]	<~~	221 Bye 
seconds		test stage and result
[000.000]		Trying TLS on mail.domain.com[144.126.140.222:25] (0)
[000.036]		Server answered
[000.272]	<‑‑	220 domain.com ESMTP Postfix
[000.273]		We are allowed to connect
[000.273]	‑‑>	EHLO www12-do.checktls.com
[000.305]	<‑‑	250-domain.com
250-PIPELINING
250-SIZE 30720000
250-ETRN
250-STARTTLS
250-AUTH PLAIN
250-AUTH=PLAIN
250-ENHANCEDSTATUSCODES
250-8BITMIME
250-DSN
250 CHUNKING
[000.305]		We can use this server
[000.305]		TLS is an option on this server
[000.306]	‑‑>	STARTTLS
[000.338]	<‑‑	220 2.0.0 Ready to start TLS
[000.338]		STARTTLS command works on this server
[001.388]		Cannot convert to SSL (reason: SSL connect attempt failed error:14094438:SSL routines:ssl3_read_bytes:tlsv1 alert internal error)
[001.389]		Note: This same test with Format set to "Debug" may show more
[001.389]	‑‑>	MAIL FROM:<test@checktls.com>
[001.389]		Read failed (reason: did not read)
[001.389]	‑‑>	QUIT
[001.389]		Read failed (reason: did not read) 
seconds		test stage and result
[000.000]		Trying TLS on inbound-smtp.us-east-1.amazonaws.com[3.211.210.226:25] (1)
[000.010]		Server answered
[000.018]	<‑‑	220 inbound-smtp.us-east-1.amazonaws.com ESMTP Amazon SES 2mPLtKK4Dy0IxmRXZnxq
[000.018]		We are allowed to connect
[000.019]	‑‑>	EHLO www12-do.checktls.com
[000.027]	<‑‑	250-inbound-smtp.us-east-1.amazonaws.com
250-8BITMIME
250-STARTTLS
250 Ok
[000.027]		We can use this server
[000.028]		TLS is an option on this server
[000.028]	‑‑>	STARTTLS
[000.036]	<‑‑	220 Ready to start TLS
[000.036]		STARTTLS command works on this server
[000.076]		Connection converted to SSL
SSLVersion in use: TLSv1_3
Cipher in use: TLS_AES_256_GCM_SHA384
Perfect Forward Secrecy: yes
Session Algorithm in use: Curve P-256 DHE(256 bits)
Certificate #1 of 5 (sent by MX):
Cert VALIDATED: ok
Cert Hostname VERIFIED (inbound-smtp.us-east-1.amazonaws.com = inbound-smtp.us-east-1.amazonaws.com | DNS:inbound-smtp.us-east-1.amazonaws.com)
Not Valid Before: Mar 16 00:00:00 2023 GMT
Not Valid After: Dec 22 23:59:59 2023 GMT
subject: /CN=inbound-smtp.us-east-1.amazonaws.com
issuer: /C=US/O=Amazon/CN=Amazon RSA 2048 M01
Certificate #2 of 5 (sent by MX):
Cert VALIDATED: ok
Not Valid Before: Aug 23 22:21:28 2022 GMT
Not Valid After: Aug 23 22:21:28 2030 GMT
subject: /C=US/O=Amazon/CN=Amazon RSA 2048 M01
issuer: /C=US/O=Amazon/CN=Amazon Root CA 1
Certificate #3 of 5 (added from CA Root Store):
Cert VALIDATED: ok
Not Valid Before: May 26 00:00:00 2015 GMT
Not Valid After: Jan 17 00:00:00 2038 GMT
subject: /C=US/O=Amazon/CN=Amazon Root CA 1
issuer: /C=US/O=Amazon/CN=Amazon Root CA 1
Certificate #4 of 5 (sent by MX):
Cert VALIDATED:
Not Valid Before: May 25 12:00:00 2015 GMT
Not Valid After: Dec 31 01:00:00 2037 GMT
subject: /C=US/O=Amazon/CN=Amazon Root CA 1
issuer: /C=US/ST=Arizona/L=Scottsdale/O=Starfield Technologies, Inc./CN=Starfield Services Root Certificate Authority - G2
Certificate #5 of 5 (sent by MX):
Cert VALIDATED:
Not Valid Before: Sep  2 00:00:00 2009 GMT
Not Valid After: Jun 28 17:39:16 2034 GMT
subject: /C=US/ST=Arizona/L=Scottsdale/O=Starfield Technologies, Inc./CN=Starfield Services Root Certificate Authority - G2
issuer: /C=US/O=Starfield Technologies, Inc./OU=Starfield Class 2 Certification Authority
[000.684]	~~>	EHLO www12-do.checktls.com
[000.693]	<~~	250-inbound-smtp.us-east-1.amazonaws.com
250-8BITMIME
250-STARTTLS
250 Ok
[000.693]		TLS successfully started on this server
[000.694]		warning: STARTTLS after second EHLO (see RFC3207 #4.2)
[000.694]	~~>	MAIL FROM:<test@checktls.com>
[000.703]	<~~	250 Ok
[000.703]		Sender is OK
[000.704]	~~>	QUIT
[000.713]	<~~	221 Bye 
seconds		test stage and result
[000.000]		Trying TLS on inbound-smtp.us-east-1.amazonaws.com[44.206.9.87:25] (1)
[000.009]		Server answered
[000.016]	<‑‑	220 inbound-smtp.us-east-1.amazonaws.com ESMTP Amazon SES DuUv0astwNBAWYCjawyq
[000.017]		We are allowed to connect
[000.017]	‑‑>	EHLO www12-do.checktls.com
[000.024]	<‑‑	250-inbound-smtp.us-east-1.amazonaws.com
250-8BITMIME
250-STARTTLS
250 Ok
[000.025]		We can use this server
[000.025]		TLS is an option on this server
[000.025]	‑‑>	STARTTLS
[000.033]	<‑‑	220 Ready to start TLS
[000.033]		STARTTLS command works on this server
[000.072]		Connection converted to SSL
SSLVersion in use: TLSv1_3
Cipher in use: TLS_AES_256_GCM_SHA384
Perfect Forward Secrecy: yes
Session Algorithm in use: Curve P-256 DHE(256 bits)
Certificate #1 of 5 (sent by MX):
Cert VALIDATED: ok
Cert Hostname VERIFIED (inbound-smtp.us-east-1.amazonaws.com = inbound-smtp.us-east-1.amazonaws.com | DNS:inbound-smtp.us-east-1.amazonaws.com)
Not Valid Before: Mar 16 00:00:00 2023 GMT
Not Valid After: Dec 22 23:59:59 2023 GMT
subject: /CN=inbound-smtp.us-east-1.amazonaws.com
issuer: /C=US/O=Amazon/CN=Amazon RSA 2048 M01
Certificate #2 of 5 (sent by MX):
Cert VALIDATED: ok
Not Valid Before: Aug 23 22:21:28 2022 GMT
Not Valid After: Aug 23 22:21:28 2030 GMT
subject: /C=US/O=Amazon/CN=Amazon RSA 2048 M01
issuer: /C=US/O=Amazon/CN=Amazon Root CA 1
Certificate #3 of 5 (added from CA Root Store):
Cert VALIDATED: ok
Not Valid Before: May 26 00:00:00 2015 GMT
Not Valid After: Jan 17 00:00:00 2038 GMT
subject: /C=US/O=Amazon/CN=Amazon Root CA 1
issuer: /C=US/O=Amazon/CN=Amazon Root CA 1
Certificate #4 of 5 (sent by MX):
Cert VALIDATED:
Not Valid Before: May 25 12:00:00 2015 GMT
Not Valid After: Dec 31 01:00:00 2037 GMT
subject: /C=US/O=Amazon/CN=Amazon Root CA 1
issuer: /C=US/ST=Arizona/L=Scottsdale/O=Starfield Technologies, Inc./CN=Starfield Services Root Certificate Authority - G2
Certificate #5 of 5 (sent by MX):
Cert VALIDATED:
Not Valid Before: Sep  2 00:00:00 2009 GMT
Not Valid After: Jun 28 17:39:16 2034 GMT
subject: /C=US/ST=Arizona/L=Scottsdale/O=Starfield Technologies, Inc./CN=Starfield Services Root Certificate Authority - G2
issuer: /C=US/O=Starfield Technologies, Inc./OU=Starfield Class 2 Certification Authority
[000.568]	~~>	EHLO www12-do.checktls.com
[000.577]	<~~	250-inbound-smtp.us-east-1.amazonaws.com
250-8BITMIME
250-STARTTLS
250 Ok
[000.577]		TLS successfully started on this server
[000.577]		warning: STARTTLS after second EHLO (see RFC3207 #4.2)
[000.577]	~~>	MAIL FROM:<test@checktls.com>
[000.585]	<~~	250 Ok
[000.585]		Sender is OK
[000.586]	~~>	QUIT
[000.594]	<~~	221 Bye 
seconds		test stage and result
[000.000]		Trying TLS on inbound-smtp.us-east-1.amazonaws.com[44.210.166.32:25] (1)
[000.009]		Server answered
[000.016]	<‑‑	220 inbound-smtp.us-east-1.amazonaws.com ESMTP Amazon SES cr2j3coUSQhx6reYpOYG
[000.017]		We are allowed to connect
[000.017]	‑‑>	EHLO www12-do.checktls.com
[000.024]	<‑‑	250-inbound-smtp.us-east-1.amazonaws.com
250-8BITMIME
250-STARTTLS
250 Ok
[000.024]		We can use this server
[000.025]		TLS is an option on this server
[000.025]	‑‑>	STARTTLS
[000.032]	<‑‑	220 Ready to start TLS
[000.032]		STARTTLS command works on this server
[000.095]		Connection converted to SSL
SSLVersion in use: TLSv1_3
Cipher in use: TLS_AES_256_GCM_SHA384
Perfect Forward Secrecy: yes
Session Algorithm in use: Curve P-256 DHE(256 bits)
Certificate #1 of 5 (sent by MX):
Cert VALIDATED: ok
Cert Hostname VERIFIED (inbound-smtp.us-east-1.amazonaws.com = inbound-smtp.us-east-1.amazonaws.com | DNS:inbound-smtp.us-east-1.amazonaws.com)
Not Valid Before: Mar 16 00:00:00 2023 GMT
Not Valid After: Dec 22 23:59:59 2023 GMT
subject: /CN=inbound-smtp.us-east-1.amazonaws.com
issuer: /C=US/O=Amazon/CN=Amazon RSA 2048 M01
Certificate #2 of 5 (sent by MX):
Cert VALIDATED: ok
Not Valid Before: Aug 23 22:21:28 2022 GMT
Not Valid After: Aug 23 22:21:28 2030 GMT
subject: /C=US/O=Amazon/CN=Amazon RSA 2048 M01
issuer: /C=US/O=Amazon/CN=Amazon Root CA 1
Certificate #3 of 5 (added from CA Root Store):
Cert VALIDATED: ok
Not Valid Before: May 26 00:00:00 2015 GMT
Not Valid After: Jan 17 00:00:00 2038 GMT
subject: /C=US/O=Amazon/CN=Amazon Root CA 1
issuer: /C=US/O=Amazon/CN=Amazon Root CA 1
Certificate #4 of 5 (sent by MX):
Cert VALIDATED:
Not Valid Before: May 25 12:00:00 2015 GMT
Not Valid After: Dec 31 01:00:00 2037 GMT
subject: /C=US/O=Amazon/CN=Amazon Root CA 1
issuer: /C=US/ST=Arizona/L=Scottsdale/O=Starfield Technologies, Inc./CN=Starfield Services Root Certificate Authority - G2
Certificate #5 of 5 (sent by MX):
Cert VALIDATED:
Not Valid Before: Sep  2 00:00:00 2009 GMT
Not Valid After: Jun 28 17:39:16 2034 GMT
subject: /C=US/ST=Arizona/L=Scottsdale/O=Starfield Technologies, Inc./CN=Starfield Services Root Certificate Authority - G2
issuer: /C=US/O=Starfield Technologies, Inc./OU=Starfield Class 2 Certification Authority
[000.658]	~~>	EHLO www12-do.checktls.com
[000.667]	<~~	250-inbound-smtp.us-east-1.amazonaws.com
250-8BITMIME
250-STARTTLS
250 Ok
[000.667]		TLS successfully started on this server
[000.667]		warning: STARTTLS after second EHLO (see RFC3207 #4.2)
[000.667]	~~>	MAIL FROM:<test@checktls.com>
[000.675]	<~~	250 Ok
[000.675]		Sender is OK
[000.676]	~~>	QUIT
[000.684]	<~~	221 Bye 
seconds		test stage and result
[000.000]		Trying TLS on inbound-smtp.us-east-1.amazonaws.com[54.164.173.191:25] (1)
[000.009]		Server answered
[000.016]	<‑‑	220 inbound-smtp.us-east-1.amazonaws.com ESMTP Amazon SES yp1a9qkcHCR55WzTTLw2
[000.016]		We are allowed to connect
[000.017]	‑‑>	EHLO www12-do.checktls.com
[000.024]	<‑‑	250-inbound-smtp.us-east-1.amazonaws.com
250-8BITMIME
250-STARTTLS
250 Ok
[000.024]		We can use this server
[000.024]		TLS is an option on this server
[000.024]	‑‑>	STARTTLS
[000.032]	<‑‑	220 Ready to start TLS
[000.032]		STARTTLS command works on this server
[000.114]		Connection converted to SSL
SSLVersion in use: TLSv1_3
Cipher in use: TLS_AES_256_GCM_SHA384
Perfect Forward Secrecy: yes
Session Algorithm in use: Curve P-256 DHE(256 bits)
Certificate #1 of 5 (sent by MX):
Cert VALIDATED: ok
Cert Hostname VERIFIED (inbound-smtp.us-east-1.amazonaws.com = inbound-smtp.us-east-1.amazonaws.com | DNS:inbound-smtp.us-east-1.amazonaws.com)
Not Valid Before: Mar 16 00:00:00 2023 GMT
Not Valid After: Dec 22 23:59:59 2023 GMT
subject: /CN=inbound-smtp.us-east-1.amazonaws.com
issuer: /C=US/O=Amazon/CN=Amazon RSA 2048 M01
Certificate #2 of 5 (sent by MX):
Cert VALIDATED: ok
Not Valid Before: Aug 23 22:21:28 2022 GMT
Not Valid After: Aug 23 22:21:28 2030 GMT
subject: /C=US/O=Amazon/CN=Amazon RSA 2048 M01
issuer: /C=US/O=Amazon/CN=Amazon Root CA 1
Certificate #3 of 5 (added from CA Root Store):
Cert VALIDATED: ok
Not Valid Before: May 26 00:00:00 2015 GMT
Not Valid After: Jan 17 00:00:00 2038 GMT
subject: /C=US/O=Amazon/CN=Amazon Root CA 1
issuer: /C=US/O=Amazon/CN=Amazon Root CA 1
Certificate #4 of 5 (sent by MX):
Cert VALIDATED:
Not Valid Before: May 25 12:00:00 2015 GMT
Not Valid After: Dec 31 01:00:00 2037 GMT
subject: /C=US/O=Amazon/CN=Amazon Root CA 1
issuer: /C=US/ST=Arizona/L=Scottsdale/O=Starfield Technologies, Inc./CN=Starfield Services Root Certificate Authority - G2
Certificate #5 of 5 (sent by MX):
Cert VALIDATED:
Not Valid Before: Sep  2 00:00:00 2009 GMT
Not Valid After: Jun 28 17:39:16 2034 GMT
subject: /C=US/ST=Arizona/L=Scottsdale/O=Starfield Technologies, Inc./CN=Starfield Services Root Certificate Authority - G2
issuer: /C=US/O=Starfield Technologies, Inc./OU=Starfield Class 2 Certification Authority
[000.693]	~~>	EHLO www12-do.checktls.com
[000.701]	<~~	250-inbound-smtp.us-east-1.amazonaws.com
250-8BITMIME
250-STARTTLS
250 Ok
[000.702]		TLS successfully started on this server
[000.702]		warning: STARTTLS after second EHLO (see RFC3207 #4.2)
[000.702]	~~>	MAIL FROM:<test@checktls.com>
[000.710]	<~~	250 Ok
[000.710]		Sender is OK
[000.710]	~~>	QUIT
[000.718]	<~~	221 Bye 
seconds		test stage and result
[000.000]		Trying TLS on inbound-smtp.us-east-1.amazonaws.com[54.197.5.236:25] (1)
[000.009]		Server answered
[000.017]	<‑‑	220 inbound-smtp.us-east-1.amazonaws.com ESMTP Amazon SES AHjXfkcqTewLfAIySdqO
[000.017]		We are allowed to connect
[000.017]	‑‑>	EHLO www12-do.checktls.com
[000.025]	<‑‑	250-inbound-smtp.us-east-1.amazonaws.com
250-8BITMIME
250-STARTTLS
250 Ok
[000.025]		We can use this server
[000.026]		TLS is an option on this server
[000.026]	‑‑>	STARTTLS
[000.033]	<‑‑	220 Ready to start TLS
[000.034]		STARTTLS command works on this server
[000.120]		Connection converted to SSL
SSLVersion in use: TLSv1_3
Cipher in use: TLS_AES_256_GCM_SHA384
Perfect Forward Secrecy: yes
Session Algorithm in use: Curve P-256 DHE(256 bits)
Certificate #1 of 5 (sent by MX):
Cert VALIDATED: ok
Cert Hostname VERIFIED (inbound-smtp.us-east-1.amazonaws.com = inbound-smtp.us-east-1.amazonaws.com | DNS:inbound-smtp.us-east-1.amazonaws.com)
Not Valid Before: Mar 16 00:00:00 2023 GMT
Not Valid After: Dec 22 23:59:59 2023 GMT
subject: /CN=inbound-smtp.us-east-1.amazonaws.com
issuer: /C=US/O=Amazon/CN=Amazon RSA 2048 M01
Certificate #2 of 5 (sent by MX):
Cert VALIDATED: ok
Not Valid Before: Aug 23 22:21:28 2022 GMT
Not Valid After: Aug 23 22:21:28 2030 GMT
subject: /C=US/O=Amazon/CN=Amazon RSA 2048 M01
issuer: /C=US/O=Amazon/CN=Amazon Root CA 1
Certificate #3 of 5 (added from CA Root Store):
Cert VALIDATED: ok
Not Valid Before: May 26 00:00:00 2015 GMT
Not Valid After: Jan 17 00:00:00 2038 GMT
subject: /C=US/O=Amazon/CN=Amazon Root CA 1
issuer: /C=US/O=Amazon/CN=Amazon Root CA 1
Certificate #4 of 5 (sent by MX):
Cert VALIDATED:
Not Valid Before: May 25 12:00:00 2015 GMT
Not Valid After: Dec 31 01:00:00 2037 GMT
subject: /C=US/O=Amazon/CN=Amazon Root CA 1
issuer: /C=US/ST=Arizona/L=Scottsdale/O=Starfield Technologies, Inc./CN=Starfield Services Root Certificate Authority - G2
Certificate #5 of 5 (sent by MX):
Cert VALIDATED:
Not Valid Before: Sep  2 00:00:00 2009 GMT
Not Valid After: Jun 28 17:39:16 2034 GMT
subject: /C=US/ST=Arizona/L=Scottsdale/O=Starfield Technologies, Inc./CN=Starfield Services Root Certificate Authority - G2
issuer: /C=US/O=Starfield Technologies, Inc./OU=Starfield Class 2 Certification Authority
[002.634]	~~>	EHLO www12-do.checktls.com
[002.643]	<~~	250-inbound-smtp.us-east-1.amazonaws.com
250-8BITMIME
250-STARTTLS
250 Ok
[002.643]		TLS successfully started on this server
[002.643]		warning: STARTTLS after second EHLO (see RFC3207 #4.2)
[002.643]	~~>	MAIL FROM:<test@checktls.com>
[002.651]	<~~	250 Ok
[002.652]		Sender is OK
[002.652]	~~>	QUIT
[002.660]	<~~	221 Bye 
seconds		test stage and result
[000.000]		Trying TLS on mail.domain.com[144.126.140.222:25] (10)
[000.041]		Server answered
[000.214]	<‑‑	220 domain.com ESMTP Postfix
[000.215]		We are allowed to connect
[000.215]	‑‑>	EHLO www12-do.checktls.com
[000.244]	<‑‑	250-domain.com
250-PIPELINING
250-SIZE 30720000
250-ETRN
250-STARTTLS
250-AUTH PLAIN
250-AUTH=PLAIN
250-ENHANCEDSTATUSCODES
250-8BITMIME
250-DSN
250 CHUNKING
[000.245]		We can use this server
[000.245]		TLS is an option on this server
[000.245]	‑‑>	STARTTLS
[000.274]	<‑‑	220 2.0.0 Ready to start TLS
[000.274]		STARTTLS command works on this server
[001.324]		Cannot convert to SSL (reason: SSL connect attempt failed error:14094438:SSL routines:ssl3_read_bytes:tlsv1 alert internal error)
[001.324]		Note: This same test with Format set to "Debug" may show more
[001.324]	‑‑>	MAIL FROM:<test@checktls.com>
[001.325]		Read failed (reason: did not read)
[001.325]	‑‑>	QUIT
[001.325]		Read failed (reason: did not read)
3

Your SPF is not valid.

4

@webshanks , Thanks for the advice, but the problem about send and receive emails it is not with it connected.

5

Have you properly setup your SPF, DKIM and DMARC?

6

Yes I did! everyting. I have Amazon SES configured as the service that sends emails. Now I do not know how can I send and receive emails through cyberpanel email server.

7

Please send a screenshot of your MX, SPF, DKIM and DMARC. Are you using cloudflare?