hMailServer changelog for 5.3.1

Version 5.3.1 - Build 1748 (2009-12-28) - Production

  • 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.

Version 5.3.1 - Build 1746 (2009-12-20)

  • 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.

Version 5.3.1 - Build 1739 (2009-12-16)

  • If a user was a part of two groups, and these two groups had conflicting permissions, it was not clear what permission was used. Now the first permission is used.
  • When setting up a rule, the Body criteria did not include the HTML body part of the email message. It does now.
  • Issue 242: Performance improvements have been done to the message indexer when Microsoft SQL Server or PostgreSQL is in use.
  • Issue 274: It was not possible to rename a folder from SomeName to SomeNameTest without first renaming it to something completely different. This issue was introduced in the previous build.
  • Issue 282: hMailServer did not work properly with Symbian N60. When the phone was notified about new messages, the sender name was not always shown.

Version 5.3.1 - Build 1720 (2009-11-30)

  • There was a memory leak when using PostgreSQL. Memory increased steadily over time.
  • hMailServer no longer caches the administrator password. Should solve problem with the Invalid password-message directly after install.
  • The log message TCPConnection - Posting AcceptEx on ip:port did not log the correct ip:port details.
  • If a client sends a POP3 command while hMailServer is delivering a message to it, that command will now be processed after hMailServer has sent the message.

Version 5.3.1 - Build 1712 (2009-11-27)

  • If the delete threshold was set to a lower value than the mark-threshold in the anti spam settings, hMailServer only executed a single anti spam test.
  • When doing DNS lookups, hMailServer no longer parses the services-file. The services file is a file included in Windows which contains a mapping between a service name (http, smtp, etc) and a port number (80, 25, etc).
  • The built-in diagnostic test always attempted to connect on port 25 when testing outgoing connections. If a SMTP relayer is in use, hMailServer now uses the TCP/IP port specified in the SMTP settings instead.
  • If a DNS reply takes more than 20 seconds to execute, hMailServer now reports an error to the error log. Slow DNS replies may be an indication of incorrect DNS configuration in Windows.
  • OpenSSL has been upgraded to version 0.9.8l.
  • Issue 268: If an IMAP client asked hMailServer to sort messages based on the Date, hMailServer did not always give the correct result.
  • Issue 274: Using Outlook, it was possible to corrupt the hMailServer folder structure by moving a folder into one of its own sub folders. For example, it was possible to execute a command which moves the folder Test\Sub to Test\Sub\Sub1. If a user did this, he could no longer access his mailbox.

Version 5.3.1 - Build 1680 (2009-11-04)

  • Issue 267: hMailServer sometimes generated invalid message UIDs. This could have the effect that new messages did not show up in folders. The problem occurred if a rule executed a script function which saved a message, and another rule moved the same message after that. This fix prevents the problem from occurring again. To repair the problem in the database, run the Reset folder UIDs maintenance script, located here:

Version 5.3.1 - Build 1653 (2009-10-26)

  • Issue 264: Searching for strings in UTF8 format did not work properly when using IMAP.
  • Issue 266: Sorting on Arrival doesn't work with some IMAP clients. Sorting on Date works fine.
  • Full change log