

- #HMAILSERVER NEVER RECEIVES EMAIL UPDATE#
- #HMAILSERVER NEVER RECEIVES EMAIL UPGRADE#
- #HMAILSERVER NEVER RECEIVES EMAIL PASSWORD#
- #HMAILSERVER NEVER RECEIVES EMAIL WINDOWS#
#HMAILSERVER NEVER RECEIVES EMAIL PASSWORD#
Issue 77: Domain administrators should not be able to change server administrator password (security).Version 5.6.1 - Build 2208 () - Production Issue 86: Server did not restart after the delivery queue was manually cleared.To force the previous behavior, set RewriteEnvelopeFromWhenForwarding=1 under the section in hMailServer.ini. This change was made to reduce risk of message delivery failures. Issue 50: When performing forwarding, hMailServer now keeps the original From address rather than changing to that of the forwarding account.OpenSSL upgraded from 1.0.1k to 1.0.1l.Fixed file access issues introduced in earlier 5.6.2-builds.Version 5.6.2 - Build 2234 () - Production Issue 97: When TLS is used, elliptic crypto should be available.Issue 94: When upgrading hMailServer, the list of languages in hMailServer.ini is no longer over-written.This is useful when working with legacy systems with malfunctioning SMTP support. The new ini file setting DisableAUTHList allows you to specify a comma-separated list of SMTP ports which authentication should not be enabled for.Version 5.6.3 - Build 2249 () - Production Issue 99: If a TCP disconnect occurs during TLS handshake, the connection is not immediately released.If the log file was locked by an external processed, a crash dump file was created.Sometimes when stopping the server, an error regarding "abandoned wait" was reported.OpenSSL has been upgraded from 1.0.1m to 1.0.1o.This issue made it possible for an attacker with man-in-the-middle access to intercept traffic.

Issue 109: Fixed plaintext injection vulnerability when using STARTTLS.OpenSSL upgraded from 1.0.1o to 1.0.1p to solve a security issue related to certificate validation:.Version 5.6.4 - Build 2283 () - Production Unquoted service paths would allow a user with access to the server where hMailServer runs, but with less privileges than hMailServer, to gain the privileges of hMailServer by creating a new executable and placing it in C:\Program\Files\hMailServer\hMailserver.exe.
#HMAILSERVER NEVER RECEIVES EMAIL WINDOWS#


The error message when trying to create two IP ranges with the same name has been improved.Custom script files are no longer uininstalled when uninstalling hMailServer.Issue 149: When searching for messages using IMAP and a "Not Deleted" criteria, sometimes incorrect email messages were returned in the response.The installation program is now rendered properly on high-DPI screens.When installing the client tools for hMailServer, now all necessary dependencies are installed as well.Issue 166: When hMailServer is running, it should accept to OS-shutdown requests from Windows (this should reduce the number of errors logged when a server running hMailServer reboots).Issue 127: hMailServer should be able to accept email from and deliver email to quoted mailboxes containing spaces.Deleting an account with an empty account address deletes the data directory.Issue 173: Improved address syntax validation.Version 5.6.5 - Build 2367 () - Production Version 5.6.6 - Build 2383 () - Production This issue will be fixed in the next build. If your cipher list references ciphers which no longer exists, hMailServer will fail to start. OpenSSL 1.0.2 contains a lot of changes, for example removal of several weak ciphers. OpenSSL 1.0.1 is no longer supported by the OpenSSL team (starting ). OpenSSL upgraded from 1.0.1u to 1.0.2j.
#HMAILSERVER NEVER RECEIVES EMAIL UPGRADE#
This change will prevent hMailServer from stop working after an upgrade (which previously happened if the cipher list contained ciphers supported in the old but not in the new version) Issue 208: If the cipher list contains unsupported ciphers, hMailServer will now report an error but continue running.Various security-related improvements have been made to hMailServer WebAdmin, primarily to reduce the risk of attacks using XSS and CSRF.Issue 225: Fixes an issue where TLS would not be used if the sending server did not use the proper syntax for the STARTTLS command.Version 5.6.7 - Build 2425 () - Production Version 5.6.8 - Build 2574 () - Production Issue 453: Incorrectly formatted SPF record can lead to crash.
