hMailServer changelog for 5.3.3

Version 5.3.3 - Build 1879 (2010-06-06) - Production

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

Version 5.3.3 - Build 1846 (2010-05-02)

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

Version 5.3.3 - Build 1829 (2010-04-02)

  • If public folders are used and the logged on user does not have permission to modify folder contents, hMailServer now explicitly tells the client that the mail box is read only. Before, hMailServer only informed the user when he tried to perform an action he did not have permission for.
  • In DataDirectorySynchronizer, it's now possible to select from a list what domains should be synchronized.
  • The OpenSSL package included with hMailServer has been upgraded to version 0.9.8n.
  • Issue 294: If an IMAP client issued the SELECT or EXAMINE command, hMailServer did not produce a complete response - the UIDNEXT value was missing from the response. This is not known to cause any errors apart from being an incorrect behavior.
  • Issue 303: If a domain administrator had access to the API, it was possible for him to create new domains. Only server administrators should have permissions to do this.
  • Full change log