Upgrading to MDaemon 13.6 |
  
|
Upgrading to MDaemon 13.6 |
|
Below is a list of special considerations and notes that you may need to be aware of when upgrading to MDaemon version 13.6 from a previous version.
●The default settings for two SMTP authentication related values have changed. The option to require SMTP authentication when mail is from local accounts and the option to require authentication credentials to match that of the email sender are both now enabled by default. If you wish to disable either of these options, they are located on the SMTP Authentication screen.
●An option was added to Preferences » Headers to hide MDaemon's software version and other identifying information when creating Received headers or responding to various protocol requests. The option is disabled by default. As part of this process, MDaemon's Received header construction was simplified and no longer includes extraneous data. Also, the following undocumented MDaemon.ini settings were removed: [Special] SecureReceivedHeaders=Yes/No and [Special] ReceivedHasAuthedUser=Yes/No.
●The STARTTLS Required List is now also applied to the MAIL FROM value during an SMTP session (in addition to the EHLO and IP). If MDaemon receives a MAIL command followed by an email address that is on the STARTTLS Required List during a session that has not been secured, then the MAIL command will get a "454 STARTTLS Required" response.
●MDaemon Standard has been renamed to MDaemon Lite.
●The trial period for MDaemon, SecurityPlus, Outlook Connector, and ActiveSync has been reduced from 60 days to 30 days.
●The way smart hosts are used has changed. In the past the smart host for a domain was only used when the Delivery routing option to send mail to domain smart hosts was enabled. This made it impossible to use smart hosts for only some domains while simultaneously using standard direct delivery for others. Now if a smart host is configured and enabled for a specific domain under the Domain Manager, then that domain's outbound mail will be routed to the smart host regardless MDaemon's main delivery setting. So, now it is possible to specify and use smart hosts for some (and not necessarily all) of your domains. Please note that use of smart hosts had to be reset to OFF for all domains due to this change. So, if you want to enable smart hosts for one or more domains use the domain manager to do so.
●The WebAdmin log rollover and storage options have changed. WebAdmin will now rollover its logs on the same schedule as MDaemon (F2 | Logging in the MDaemon GUI). Weekly and Monthly rollovers are no longer supported. Additionally, new installs starting with this release will have their WebAdmin logs stored in the same location as the MDaemon logs (\MDaemon\Logs by default). Lastly, the WebAdmin-specific logging options that remain have moved under the general Log Options menu in WebAdmin.
●Please note that MDaemon's BlackBerry Enterprise Server does not (and can not) work with BlackBerry OS 10 devices. BlackBerry OS 10 devices are managed through MDaemon's ActiveSync server or with different management tools obtained directly from BlackBerry. MDaemon's BlackBerry Enterprise Server management features are for devices running BlackBerry OS 7 or earlier.
●The operation of SSL & TLS » STARTTLS Required List has changed. Hosts and IP addresses listed here will now require TLS on both incoming and outgoing connections from any host or IP on the list. In the past, the list only applied to outgoing connections. Also, IPs listed here can now be specified in CIDR notation.
●Prior to 13.5.0, public folders could not be deleted automatically when a domain was deleted. Now there is a new option on the Public & Shared Folders screen to control this. Enable the "Delete domain public folders when domain is deleted" option if you wish to delete a domain's public folders as well. Enabling this option is recommended, but in order to preserve existing behavior it is disabled by default.
●When 13.5.0 is started for the first time it will perform a one-time migration of account settings from WEBACCES.DAT into the accounts' HIWATER.MRK file, which is a more appropriate place for these configuration settings. The WEBACCES.DAT file is no longer used and will be removed as part of this migration process. Further, the Web Services settings on the New Accounts template only apply to newly created accounts, not to existing accounts. A new "Apply installation defaults" button reverts all the settings on this page to installation defaults
●The content of the NoComd.dat file is obsolete. Depending on your configuration, this file was emailed like an autoresponder to anyone who submitted an MDaemon command email that failed to contain valid commands for MDaemon to process. The content of the file contained instructions on how to ask for help, which were also obsolete. A new NoCommand.dat file has been created which no longer contains this errant instructions. If you would like to provide instruction to non-local users on (for example) how to send a SUBSCRIBE or UNSUBSCRIBE command email you can easily modify the NoCommand.dat file to do so. If you have previously modified the NoComd.dat file you can move your modifications into NoCommand.dat from the backup of NoComd.dat which was created as part of the installation process or from a backup created by the nightly config file backup feature.
●MDaemon no longer supports extraction of attachments into an account's FILES folder. This folder was rarely accessible. Instead, this option extracts attachments into the account's Documents IMAP folder which is accessible via WorldClient. Each account's FILES folder will be left in place in case there are files there that should not be deleted. However, no further use of this folder is made by MDaemon. As part of this, the $FILEDIR$ macro was removed.
●The format of log file lines in colorized logs has changed to include a two-digit color code in each line immediately following the time-stamp.
●It is possible to accidentally configure a valid account to receive bounces from mailing lists in such a way as to cause the list pruning operation to delete the account's other (non-list) related mail. To help prevent this we have updated the documentation with warnings and have reversed the default settings for two existing options located at Preferences » Miscellaneous. "List pruner deletes messages that don't contain parsable addresses" is now disabled by default, and "List pruner saves messages which result in list member removal" is enabled by default. Please set these options to how you want your system to behave. For more information see: Enhanced List Pruning.
●MDaemon will no longer bounce messages on a 5XX error from your smart host if one or more of the MX hosts from the receiving domain returned a temporary error earlier in the delivery session. This is on the theory that maybe one of the receiving domain's servers will correct itself before the next queue run. However, it is an indication of a bad site configuration if you are using a smart host and that smart host refuses to accept mail from your MDaemon server. It is expected that this will not ordinarily be the case. A new option was added to Server Settings » Delivery called "Bounce message on 5XX error from smart host" which defeats this mechanism and causes the message to go ahead and immediately bounce. If the message is not bounced it becomes part of the standard retry queue mechanism. If all of the receiving domains MX hosts return 5XX errors and the smart host returns 5XX errors then the message has nowhere else to go and is bounced regardless of any other settings.
●MDaemon FREE is no longer supported and the FREE registration key will not work beginning with this version. The last MDaemon FREE version is MDaemon 12.5. The MDaemon installation process will offer to convert FREE installs to TRIAL installs.
●A new global on/off setting was added for SyncML and ActiveSync servers to enable/disable them globally for all domains. Please check to be sure the SyncML and ActiveSync servers are enabled/disabled per your liking. This global switch is now used for ActiveSync when enabling/disabling it via the FILE menu and "Servers" section of the main UI.
●MDaemon no longer checks messages for RFC compliance by default to avoid an issue with Outlook's test messages (which are missing the Date header). Check Default Domain & Servers » Servers to make sure the ...refuse messages which are not RFC compliant setting is how you like it.
●MDaemon no longer supports Windows XP older than Service Pack 2 or Windows Server 2003 older than Service Pack 1.
●The ActiveSync for MDaemon license key is now subject to product activation. Trial keys must be activated within 5 days and production keys within 30 days. For more information on product activation, see: Product Activation Frequently Asked Questions at altn.com.
●Incorporation of MDS-CS has required that your BlackBerry Enterprise Server logging value found at Setup » BlackBerry... » Options be reset to a default value of "Informational". If this is not your desired setting you can change it there.
●The Domain Sharing option Incoming Minger lookups trigger Domain Sharing processing has been removed. If you have multiple servers using Domain Sharing and you are careful to configure each node to use all the other nodes for Domain Sharing (if appropriate for your setup), then this option should not be needed.
●The Over quota accounts can accept mail but not send mail option (located at Accounts » Account Options » Quotas) has been removed and replaced with two separate options: Refuse incoming messages sent to over quota accounts (enabled by default) and Refuse outgoing messages sent from over quota accounts (disabled by default). These new defaults may not replicate previously configured behavior so check and change as needed.
●Windows 2000 is no longer a supported operating system. MDaemon 12.0 requires Windows 2008, 2003, 7, XP, or Vista.
●WorldClient has an updated version of the CKEditor WYSIWYG editor for message composition. If you do not have custom themes it is recommended that you remove the MDaemon\WorldClient\HTML\fckeditor\ directory. This directory is not removed by the installer because of template customization.
●MDaemon's new BlackBerry Enterprise Server (BES) feature could result in duplication of data when combined with other sync techniques like SyncML or BlackBerry Internet Service Integration. Care must be taken to avoid this (see BlackBerry Device Activation).
●Passwords must now be at least 4 characters long. Existing passwords are not forced to change, but the next time you do change one the new password must have at least 4 characters.
●See Relnotes.html located in MDaemon's \Docs\ sub-folder for a complete list of all new features, changes, and fixes to MDaemon from the previous version.
See:
Copyright © 1996-2013. All rights reserved. Alt-N Technologies, Ltd.