Email Notifications PRO version V2.3, issue?

[OPTIAIR]

I was testing and found similar behaviour as this
https://www.coreftp.com/forums/viewtopic.php?p=102228&hilit=notification#p102228


I was testing the 2.3 beta, seems that notifications do not work (for me) as it gives a timeout to Amazon SMTP
my results
FOR PORT 587

version 1993 with FORCE TLS = ON and AUTH LOG = ON

Attempting notification...
Connect socket #1508 to 3.11.252.235, port 587...
sftp keep-alive
sftp keep-alive
Connection timed out
Notification failed
Transfer time: 00:00:32
sftp keep-alive

telnet 3.11.252.235 587 works fine.


version 1993 with FORCE TLS = OFF and AUTH LOG = ON
Attempting notification...
Connect socket #1392 to 3.11.252.235, port 587...
HELLO command failed
Notification failed
Transfer time: 00:00:02
sftp keep-alive




version 1993 with FORCE TLS = OFF and AUTH LOG = OFF
Attempting notification...
Connect socket #1392 to 3.11.252.235, port 587...
HELLO command failed
Notification failed
Transfer time: 00:00:02
sftp keep-alive


so it looks like FORCE TLS = OFF gives always a HELLO command failed.
if it is ON, then I get the timeout.

I am sure the credentials entered are correct for my SMTP and that ports are open.
No proxy settings filled either.
latest V2.2 also does not work.


FOR PORT 465

-AUTH LOG = OFF
Attempting notification...
Connect socket #2080 to 35.178.252.162, port 465...
sftp keep-alive
Connection timed out
Notification failed
Transfer time: 00:00:11


- AUTH LOG = ON
test.txt - 20 bytes transferred in 0 seconds
Attempting notification...
Connect socket #2044 to 35.177.173.199, port 465...
sftp keep-alive
sftp keep-alive
sftp keep-alive
sftp keep-alive
sftp keep-alive
Connection timed out


CONCLUSION:
What do I do wrong with notifications as this is usefull PRO versions functionality.
I have port 465 and 587 open, do I need some other ports open to the Amazon server.
Is support TLS 1.2 broken somehow?

[ForumAdmin]

Try port 587, with the "TLS 1.2" option checked (no other options checked)

[OPTIAIR]

That suggestion gives me the error: HELLO command failed.:


Welcome to Core FTP, release ver 2.3, build 1995 (x64) -- © 2003-2025
WinSock 2.0
Started on Tuesday January 06, 2026 at 09:26:AM
Resolving xyz
xyz [22] connecting...
SSH-2.0-CrushFTPSSHD
diffie-hellman-group15-sha512,curve25519-sha256,diffie-hellman-group18-sha512,curve25519-sha256@libssh.org,diffie-hellman-group17-sha512,diffie-hellman-group16-sha512,diffie-hellman-group14-sha256,ecdh-sha2-nistp384,rsa2048-sha256,diffie-hellman-group-exchange-sha256,ecdh-sha2-nistp521,ecdh-sha2-nistp256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,rsa1024-sha1,ext-info-s,kex-strict-s-v00@openssh.com
diffie-hellman-group-exchange-sha256
ssh-rsa,rsa-sha2-256,rsa-sha2-512
rsa-sha2-256,rsa-sha2-512,ssh-rsa,ssh-dss,ecdsa-sha2-nistp521,ecdsa-sha2-nistp384,ecdsa-sha2-nistp256,ssh-ed25519
rsa-sha2-256
ciphers selected:
aes256-ctr,aes192-ctr,aes128-ctr,aes256-cbc,aes192-cbc,aes128-cbc,3des-cbc,blowfish-cbc,rijndael128-cbc,rijndael192-cbc,rijndael256-cbc,rijndael-cbc@lysator.liu.se,des-cbc,des-cbc@ssh.com,aes128-gcm@openssh.com,aes256-gcm@openssh.com
client->server cipher: aes256-ctr
client->server mac: hmac-sha2-256
server->client cipher: aes256-ctr
server->client mac: hmac-sha2-256
ssh-rsa ...........................................................
password,publickey,keyboard-interactive
sending password...
PWD
Current directory is '/'
Keep alive on...
CWD /ReleaseManagement
Transferred 1,710 bytes in 0.001 seconds
CWD /ReleaseManagement/
CWD /ReleaseManagement/
RETR /ReleaseManagement/abc.sql
abc.sql - 98196 bytes transferred in 1 seconds
Attempting notification...
Connect socket #1500 to 3.11.252.235, port 587...
HELLO command failed
Notification failed
Transfer time: 00:00:02
sftp keep-alive

I would imagine that in my initial tests I did already try with TLS1.2 on all the time... (see below/above)
Maybe Coreftp has an option where it can pass parameters to Powershell to send email that way.
Thanks