It looks like hMailServer is looking for an SSL Handshake and being given the wrong Encryption Version from the client.īut in any event your client is not able to negotiate the Security connection probably due to some mismatch with your Port security designation in TCP/IP ports section of hMailAdmin.Ĭode: Select all "TCPIP"ē176 " 00:05:26.796" "TCP - 77.238.178.200 connected to 145.239.116.225:25." By chance if you specified StartTLS for your Port 995 or 110, this could be causing you problem. At least based on what you have showed me so far, I would look here but I don't have a complete picture of what hMailServer is complaining about. I am guessing you are having some kind of conflict with the Encryption version and what you have specified in the TCP/IP ports. I am guessing your Log Entries and what you have told me in your Posts are indicating you are trying to Receive your email and getting this error. Then note your Settings>Advanced>TCP/IP Entries. I don't debug these kinds of entries much myself so I'm guessing here but I would check your Settings>Advanced>SSL/TLS in hMailAdmin and note which boxes are checked.
But it looks like something is not being entirely read and probably your Certificate entries since it is the SSL Handshake entry which is showing the failure. For instance your missing the HELO or EHLO entries and any other associated Entries. Still you aren't showing all your log entries. There are also Diagnostics utilities available for you to use. You should usually provide more documentation of your error such as your log files. I also don't know if you must use RSA Keys but I generated my certificate with Let's Encrypt and it included RSA Keys and that just happened to work with hMailServer. I'm not sure which formats hMailServer will accept but it does accept. You should also verify your SSL Certificate is in the correct format.
DISABLE ENCRYPTION VISUALSVN PASSWORD
hMailServer will not be able to read a password protected Certificate File. You also need to make sure your certificate files do not have a password associated with them. The file start and end should look exactly as I indicate above. You must make sure all the dashes displayed are present in your prikey.pem file. This is the end of my privkey.pem file for the Private key Certificate File: This is the start of my privkey.pem file for the Private Key Certificate File: