hMailServer changelog for 5.2

Version 5.2 - Build 356 (2009-07-21) - Production

  • Performance improvements have been made to the MySQL upgrade scripts. Upgrading larger installations to v5.2. should now be at least twice as fast.
  • When restoring a backup, restored messages received new UID's, which made them impossible to download.

Version 5.2 - Build 355 (2009-07-16)

  • If invalid folders had been created in 5.1, the upgrade to 5.2 would fail. The upgrade scripts have been modified so that if an invalid folder is found, it will be renamed to foldername-folderid.

Version 5.2 - Build 354 (2009-07-05)

  • If an email is being sent to a multihomed host with no MX records, hMailServer will bounce the delivery saying that there are no email servers. (Issue 229)

Version 5.2 - Build 353 (2009-07-02)

  • If one test resulted in PASS and another one FAIL, an empty X-hMailServer-Reason line was added to the MIME headers.
  • If two clients was auto-banned at the exact same time (millisecond), hMailServer could fail to auto-ban one of them if they were connecting from different IP addresses.
  • When connecting to a new server using Administrator, the server name in the title was not updated.

Version 5.2 - Build 352 (2009-06-21)

  • The default retry ccount for routes was set to zero.
  • If a DNS query fails, the bounce message now says that rather than "No mail servers appear to exists for the recipients address."
  • If the max number of recipients in every batch was set to zero, deliveries didn't work. Now "0" means unlimited.

Version 5.2 - Build 351 (2009-06-21)

  • The message "The password is weak. are you sure you want to use it?" was always displayed in english.
  • Data directory synchronizer failed to import messages from disk.

Version 5.2 - Build 350 (2009-06-17)

  • Another problem related to showing attachments with едц in RoundCube. Problem occured if file name was short.

Version 5.2 - Build 349 (2009-06-12)

  • A new option has been added to routes which allows you to specify whether messages arriving from route addresses should be considered local or not.

Version 5.2 - Build 348 (2009-06-07)

  • In hMailServer Administrator, under Utilities, a new basic diagnostic tool is now available. This tool helps you troubleshoot basic set up issues.
  • If a client sends a message from a local domain, the sener is now considered local. The same applies if his address matches a route. The previous behavior was that a sender was only considered local if his address matched an local account. This means that if you send from an alias address, you are now considered local. Please note that it's still not possible to authenticate using an alias though.
  • In the grey listing options you can now choose to bypass greylisting if SPF passes.
  • In the grey listing options you can now choose to bypass greylisting if SPF passes.
  • A new rule action has been added; Create Copy. This can be used for example to deliver copies of the same message to different destination servers.
  • A new rule criteria has been added; Delivery attempts. This can be used for example to deliver messages to different routes, depending on the current number of delivery attempts.
  • If hMailServer tries to deliver the same message multiple times, global rules will now be executed every time.
  • When you delete domains in hMailServer, you now need to confirm the deletion before the domain is removed.
  • The database upgrade is now done in a transaction (assuming the underlying database supports it).
  • In the database setup wizard, the creation log on the second last page is now cleared when the page is shown. Previously, the log could contain data from previous creation attempts, which could cause confusion.
  • Issue 145: IMAP UIDNEXT is now implemented.
  • Issue 201: It's now possible to index messages in folders, which increase disk usage but speeds up IMAP sort.
  • Issue 207: Incomplete upgrade of WebAdmin may result in bad error message.
  • Issue 209: If a Date header contained the timezone "GMT" (with quotes, obsolete syntax) the message was not displayed if Outlook Express was used.
  • Issue 213: If MySQL with InnoDB was used, message ID's could sometimes repeat themselves, which could lead to lost messages (client dependant).
  • Issue 215: If a message is downloaded from an external account, the message was not delivered to recipients on routes. There is now a new option in the external account settings which allows you to enable this behavior.
  • Issue 218: Attachment names containing non-latin characters didn't always show up properly.
  • Full change log