December 13th, 2010· Stability fixes. In certain scenarios, hMailServer could stop processing incoming requests.
August 5th, 2010· Issue 312: In some cases, the POP3 server returned incorrect data which could lead to corrupt attachments. Changes have been made to prevent this error. The error was apparent when retrieving PDF files which had been sent using Outlook Express.
· Issue 313: If hMailServer was configured to download messages from a server which did not support UIDL, hMailServer timed out. hMailServer has been changed to disconnect immediately and report an error when this happens. The External account functionality in hMailServer does not work with POP3 servers not supporting UIDL.
· Issue 314: If DKIM was enabled and a user sent an email with no text in the body, hMailServer did not correctly sign the message.
· Issue 1879: OpenSSL has been upgraded to version 0.9.8o.
May 13th, 2010· Issue 288: The live log in hMailServer Administrator could stop work, and Administrator could hang, if there was a high throughput in hMailServer.
· Issue 306: If a DNS blacklist returned several DNS records, hMailServer only analyzed one of them.
January 27th, 2010· If hMailServer tries to report statistics to hMailServer.com, and hMailServer.com is not available, the SMTP delivery will stop. Messages will still be queued up so no email will be lost.
· When Spamhaus were used, false positive were sometimes reported (under high Spamhaus load?). In the DNS blacklist settings, it's now possible to specify ranges by using -, for example 127.0.0.1-5. It's also possible to specify more than one address by using |, for example 127.0.0.1|127.0.0.25. This makes it possible to specify more granular values than before.
· In some cases hMailServer extracts the senders IP address from the Received headers in email when doing anti-spam. If hMailServer was unable to do this extraction, the anti-spam tests were aborted. This has now been changed so that hMailServer still does the anti spam tests, but skips the ones which are dependent on the IP address (DNS black lists and SPF).
January 9th, 2010· Issue 284: If a message is sent to an alias, which forwards the message to a route, and that route only has the aliased address listed - not the original address, hMailServer will not accept the message delivery.
December 22nd, 2009· hMailServer sometimes reported an error about being unable to notify IMAP clients about mailbox changes. The problem occurred if the client had disconnected in an incorrect way.
September 14th, 2009· When an error occurs it's logged to the hMailServer error log and the standard log (if application logging is enabled). In the normal log file, the first column of the error line contained APPLICATION rather than ERROR. It now says ERROR which makes it easier to locate error-lines in the standard log file.
· If a DNS lookup fails, this was reported as an error before. DNS lookups may fail if the recipients DNS server is not properly configured, and this is not an error in the hMailServer installation. Due to this, this is no longer reported as an error to the hMailServer log, but rather mentioned in the bounce message.
· Issue 247: When a new message is added to a folder using an IMAP client, hMailServer now explicitly tells the same client that a new message has been added to the folder. This should solve problems with listing of Draft messages in Thunderbird.
· Issue 249: If spam protection was enabled, but header tagging was not, hMailServer would fail to download messages from external accounts containing spam messages.
· Issue 250: If SPF test passed, but another spam test failed and the message was rejected during the SMTP conversation, sometimes the rejection description sent to the client was empty.
· Issue 253: When clearing the delivery queue, orphaned rows were left behind in the hm_messagerecipients table.
September 14th, 2009· hMailServer now supports IPv6.
· It's now possible to bypass grey listing if a connection arrives from a MX or A record for the sending domain.
· In the SpamAssassin settings, there's now a Test button which allows you to easily confirm that the SpamAssassin connection information is correct.
· In the MX query, you can now right click on rows and copy to clipboard.
· There was some inconsistencies related to IMAP folder hierarchy delimiter. When creating rule actions, the only valid IMAP folder delimiter is the one specified in the IMAP settings. If you've selected that . is the delimiter, specifyinng the IMAP folder name FolderSubFolder will cause a folder with the name "FolderSubFolder" to be created, rather than one named Folder and a second named SubFolder.
· A new event has been added, OnExternalAccountDownload.
· Issue 238: IMAP: hMailServer sometimes produced a BODYSTRUCTURE response with a syntax error.
· Issue 240: If you tried to add route members prior to saving the route, an error was shown.
· Issue 244: IMAP: The Recent flag not removed properly, which made duplicate messages appear in RoundCube.
· Issue 245: The AD integration in hMailServer Administrator didn't always add correctly configured hMailServer accounts.
September 14th, 2009· Issue 243. When restoring a backup, addresses specified in a route were not restored.
August 15th, 2009· Issue 241. When IMAP clients requested body structure information for a message, hMailServer were in some cases unable to create this, which resulted in the message not being shown to the client. An error message related to PartStructure were logged when this error occurred.
July 15th, 2009· Message indexing for improved performance
· Improved SMTP authentication methods to reduce spam
· Built-in diagnostics tool to make troubleshooting easier
· IMAP UIDNEXT implemented
· New rule actions and criterias have been added
· It's now possible to skip greylisting if SPF passes
May 30th, 2009· Issue 216: SMTP connection sometimes dropped during DKIM verification. This problem occurs if a the DNS server publishing the publi key publishes a CNAME record which points at the TXT record which contains the actual public key.
January 6th, 2009· It wasn't possible to display messages having an attachment with file names containing specific character.
Find us on Google+
