Also Can you let me know what can be done to resolve this? replace the 0000 with the FQDN?
just search for SMTP-IN logs
I cannot find this piece of text in the SMTP log.
Does your 465 port enabled?
Yes it is. Listening on 127.0.0.1
Hello,
Let’s check if your localhost listener you have configured with SSL on port 465 for SMTP-Incoming service is working well.
For this please provide the output of the following command (to be ran from the console of your Axigen server)
echo -e "ehlo this-is-a-test\nquit" | openssl s_client -connect localhost:10465 -crlf -ign_eof 2>&1| tee /tmp/this-is-a-test.tx
Note: the output should be saved in /tmp/this-is-a-test.txt file so you could just attach to your answer.
BR,
Ioan
Will these commands work for windows?
Hello,
Obviously not and its first time you’ve mention that your Axigen is running on Windows.
In this case just share here the axigen.cfg configuration file so we could check your configuration.
BR,
Ioan
was asking this because of “openssl” you mentioned in the command.
Please note i cannot run this command. I get following error.
openssl’ is not recognized as an internal or external command,
operable program or batch file.
as this is windows os
Hello,
1/ Checking 127.0.0.1:465 listener from axigen.cfg didn’t pop up any red lights.
2/ We see that SMTP-IN is saved in a separate log file (smtp.txt). Could you please share it as well?
BR,
Ioan
Hello,
Most probably it is empty because it was “rotated” by the server and no other tests were made in the mean time.
Could you please make a new test with your mail client and check if there are any new SMTP-IN lines in smtp.txt (or other *.txt file present into the log folder)?
BR,
Ioan
created by AXIGEN version 10.3.1.5 (Windows/x64)
2020-08-04 15:40:09 +0530 16 LAPTOP-RKEA2THQ SMTP-IN:00000000: << SSL: client hello, remote 127.0.0.1:56245, version TLS 1.3 (0304)
2020-08-04 15:40:09 +0530 16 LAPTOP-RKEA2THQ SMTP-IN:00000000: << SSL: client hello, remote 127.0.0.1:56245, 31 cipher suites: c024c028003d006b006ac00ac014003500390038c023c027003c00670040c009c013002f00330032c02cc02bc030009d009f00a3c02f009c009e00a200ff
2020-08-04 15:40:09 +0530 16 LAPTOP-RKEA2THQ SMTP-IN:00000000: >> SSL: server hello, remote 127.0.0.1:56245, version TLS 1.2 (0303)
2020-08-04 15:40:09 +0530 16 LAPTOP-RKEA2THQ SMTP-IN:00000000: >> SSL: server hello, remote 127.0.0.1:56245, cipher suite c02f
2020-08-04 15:40:09 +0530 16 LAPTOP-RKEA2THQ SMTP-IN:00000000: >> SSL: server write cert, remote 127.0.0.1:56245, version TLS 1.2 (0303)
2020-08-04 15:40:09 +0530 16 LAPTOP-RKEA2THQ SMTP-IN:00000000: >> SSL: server write cert, remote 127.0.0.1:56245, certificate 1: serial 01
2020-08-04 15:40:10 +0530 08 LAPTOP-RKEA2THQ SMTP-IN:000000BD: [127.0.0.1:465] connection accepted from [127.0.0.1:56245]
2020-08-04 15:40:10 +0530 16 LAPTOP-RKEA2THQ SMTP-IN:000000BD: >> 220 LAPTOP-RKEA2THQ Axigen ESMTP ready
2020-08-04 15:40:10 +0530 16 LAPTOP-RKEA2THQ SMTP-IN:000000BD: >> 421 LAPTOP-RKEA2THQ error reading data
2020-08-04 15:40:10 +0530 02 LAPTOP-RKEA2THQ SMTP-IN:000000BD: SSL_write error (An established connection was aborted by the software in your host machine.)
2020-08-04 15:40:10 +0530 08 LAPTOP-RKEA2THQ SMTP-IN:000000BD: closing session from [127.0.0.1]
This is the content generated
Hello,
So you could see that the server is sending the so called “banner” 220 LAPTOP-RKEA2THQ Axigen ESMTP ready but from there the session got aborted.
Please check on your mail client what is the problem.
BR,
Ioan
With same peice of code able to reach gmail. So not an issue with client code. This is something to do with SSL configuration only.
So, basically you are saying that your mail client is able to connect to Gmail on port 465 but not to Axigen on port 465.
Could you please increase the log level on your mail client so you could find what is not working well?
HTH,
Ioan
Generally if something goes wrong while mail is being send we would see an exception being thrown. But here in this case the client gets stuck which means that’s something wrong with the configuration of server rather than server side code(this I’m claiming based on previous experience with non-smtp setup when firewall was disabled I could recieve the mail).
Can you please confirm if I’m on correct line?