hMailServer changelog for 5.3

Version 5.3 - Build 1617 (2009-10-03) - Production

  • Issue 261: When restoring a backup, the restore of accounts failed if messages were not restored.

Version 5.3 - Build 364 (2009-09-20)

  • hMailServer now reports results from DNS blacklists to the TCP/IP log. This makes it easier to figure out which DNS blacklists caused a message to be rejected.

Version 5.3 - Build 363 (2009-09-16)

  • To improve security, empty passwords are no longer permitted.
  • 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.

Version 5.3 - Build 362 (2009-08-28)

  • 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 Folder\SubFolder will cause a folder with the name "Folder\SubFolder" 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.
  • Full change log