|
New in MDaemon 12.5 |
  
|
|
New in MDaemon 12.5 |
|
Tablet Support and other WorldClient Improvements
WorldClient's flagship theme, LookOut, has undergone major architectural and design changes to accommodate tablet devices such as the BlackBerry PlayBook and the iPad. Users should not have to change any settings to take advantage of these changes. These changes include:
| • | Single finger scrolling. |
| • | Dragging and dropping between folders with one finger; use two fingers to copy to the destination folder. |
| • | No popup windows for message composition, item entry and item editing to help maintain context. |
| • | Inline message preview to help preserve the flow of the mail folder and maximize screen real estate. |
Other WorldClient improvements
| • | ComAgent chatting has been moved to a side panel instead of being in a 'floating' tab that may cover other parts of the interface (Lookout theme). |
| • | Calendars can now be viewed together to help see schedules for multiple users (Lookout theme). |
| • | Autoresponder settings moved to their own page under Option to help make management easier. |
| • | Various HTML5 & CSS3 features have been used to improve performance and loading time (Lookout theme). The Compose page now uses app-caching to help load the HTML editor more quickly (particularly over SSL connections) on browsers such as the PlayBook, Chrome and Firefox that support the manifest HTML attribute. |
| • | Advanced message searching has now been enhanced with a number of other new search parameters to help make finding messages easier. |
| • | WorldClient's LookOut theme now auto-saves draft messages every minute. |
ActiveSync for MDaemon Improvements
ActiveSync for MDaemon has been improved and is now capable of synchronizing email as well as personal information manager (PIM) data. For information on configuring your specific ActiveSync device see the documentation that accompanied your device. Some information on basic device configuration is available from the Alt-N Technologies website: Windows Mobile, iOS, and Android.
ActiveSync for MDaemon is a separately licensed product available from Alt-N Technologies. ActiveSync for MDaemon will not work beyond a one-time 30-day evaluation period unless a license is purchased.
Spam Filter Updated to Include SpamAssassin 3.3.2
MDaemon's Spam Filter has been updated and now includes SpamAssassin 3.3.2. A summary of changes and other documentation on SpamAssassin can be found at the SpamAssassin website.
The Spam Filter updates option: Run SA-UPDATE as part of update process has been removed. This will now always take place. The old and out-dated method based on UpdateSpamAssassin.exe has been removed and that file has been deleted. MDaemon now relies on sa-update to perform all necessary SpamAssassin updates. Also, the 80_MDaemon_updates.cf file is no longer used and has been deleted.
Finally, the installer was changed to no longer delete existing .cf rule content. The rule updating process will manage .cf files.
BlackBerry® Mobile Data System Connection Service (MDS-CS)
MDaemon's BlackBerry Enterprise Server (BES) now includes MDS-CS. MDS-CS permits behind-the-firewall access to files and web applications from BlackBerry devices. It receives and responds to web requests from the BlackBerry Browser and other BlackBerry Applications, and sends login requests so that users can view Internet and Intranet content on their BlackBerry devices. This will, for example, allow you to access your private Intranet without a VPN connection.
You can find more information about MDS-CS at BlackBerry.com, but please note that not all of the features and capabilities documented there are supported by MDaemon.
Global Recipient (RCPT) Blacklist
Located under Security » Security Settings... » Screening, the Address Blacklist screen has been renamed to Sender Blacklist and a new Recipient Blacklist feature has been added. The new Recipient Blacklist operates on SMTP envelope RCPT data only (not message headers). Also, the Blacklist.dat file has been renamed SenderBlacklist.dat and a new RecipientBlacklist.dat file has been created. The BLACKLIST.SEM Semaphore File reloads both files into memory.
Personal Sender (MAIL) Blacklist
Each account now has a personal Blacklist contact folder. Incoming messages from any SMTP mail sender listed in the Blacklist will be rejected with "550 recipient unknown." Messages that make it past SMTP and into the local queue but have a blacklisted address in the From: or Sender: header will be moved to the bad message folder. The Blacklist folder is automatically created the next time a message is received for the account. Users can manage their account's Blacklist folder via WorldClient just as with the Whitelist folder.
Outbound Message Sending Quotas
New quota options are available in the New Account Defaults and Account Editor which let you set a limit to the number of messages an account can send via SMTP per day. The counter automatically resets to zero for all accounts at midnight each night. Note that it is possible to exceed this limit slightly if messages come in faster than the cache can keep up.
When MDaemon is configured to use Windows DNS servers it will now use all servers found instead of just the first two. This required several internal changes including doing away with the old "max retry attempts" option for DNS lookups. MDaemon will now try each DNS server once per lookup operation and in sequence until it exhausts the complete list of DNS servers or finds the first one that works. Also, on startup, the System log will display each DNS server that MDaemon will use and an indicate where it came from (i.e. manually configured or taken from Windows). Further, the options for designating a primary and secondary DNS server have been removed. Now there is just a single edit box that lets you manually configure as many DNS servers as you want. Finally, the options to use Windows DNS servers or manually configured DNS servers are no longer mutually exclusive. If you configure both, MDaemon will use both.
Configuration Session Improvements
The Configuration Session interface has been improved in several ways. For example, the right-click menu now works properly and allows you to disconnect an active session and you can double-click or view Properties of one or more active sessions, which displays the session log. You can also submit the connecting IP address to the IP and/or Dynamic Screen features. Also, the Sessions Window will update individual line items more efficiently and handle a much larger amount of session data. Further, Configuration Sessions can now change the primary domain name. Finally, changes made to the IP Screen, Host Screen, and Address Blacklist via WebAdmin will now be picked up by configuration sessions.
There are several improvements to the IP Shield:
| • | The IP Shield now has a master on/off switch. It is enabled by default but will have no effect when there are not yet any configured domain/IP pairs. |
| • | It supports the $LOCALDOMAIN$ macro which expands to cover all local domains (including gateways). If you use this macro it is no longer necessary to keep the IP Shield up to date when local domains or gateways change. Existing installations will not have their existing IP Shield values altered in any way. However, there is a new Default button that can be used to convert existing IP Shield values to the new $LOCALDOMAIN$ system. By default, entries are added to the IP Shield associating all reserved IP address ranges with $LOCALDOMAIN$. |
| • | When the Don't apply IP Shield to authenticated sessions option is enabled, the IP Shield restrictions will not apply to authenticated users. Mail will be accepted from an authenticated user regardless of the IP address from which he or she connects. Further, when a user doesn't authenticate and access is refused, the message returned to the SMTP client will be "Authentication required" in order to give the user a clue that he can fix the problem by configuring the mail client to use authentication before sending a message. |
| • | Also, the IP Shield has a new option that is disabled by default: Check FROM header address against IP Shield. If you enable this option then the IP Shield will compare the address taken from the message's FROM header in addition to that taken from the SMTP MAIL value. Note that this option can lead to problems with incoming list messages and other types of messages. It should not be enabled unless you are sure you need it. |
| • | The IPShield.dat file is now cached in memory to increase access speed. Create an IPSHIELD.SEM to reload the file into memory. |
Additional Features and Changes
MDaemon 12.5 has many new features and changes. See RelNotes.html located in MDaemon's \Docs\ subfolder for a complete list of all new features, changes, and fixes to MDaemon from the previous version.
New in MDaemon 12
MDaemon Pro is equipped with a BlackBerry Enterprise Server, which makes it possible for your users to synchronize their MDaemon/WorldClient email, calendar, and other personal information management (PIM) data with their BlackBerry smartphones. BlackBerry platform support also makes it possible for you to set security polices for user devices and even erase a device should it be lost or stolen.
MDaemon's BlackBerry Enterprise Server features include:
| • | No need for third-party sync clients. Each user's data is synchronized using software already present on all BlackBerry devices. |
| • | MDaemon/WorldClient email (including mail folders) is synchronized with the device in both directions. Therefore whether mail is read, moved, deleted, etc. on the device or the server it will be synchronized on both. |
| • | Two-way Calendar synchronization. For example, if you create a new appointment, set a reminder, or modify an appointment on either the device or within WorldClient it will be synchronized in both places. |
| • | Two-way tasks and notes synchronization. |
| • | Global address book lookup. |
| • | Scheduling with free/busy. |
| • | Limited BlackBerry device policy support, so that you can set device policies such as: require passwords, expiring passwords, encrypt media files, and more. |
| • | Set different policies for individual domains or users. |
| • | Remotely change the device's password and lock it. |
| • | Erase all data from the device, for example if it is lost or stolen. |
| • | Backup and Restore options for your BlackBerry Enterprise Server database. |
MDaemon's main BlackBerry Enterprise Server options are located at: Setup » BlackBerry... » BlackBerry Enterprise Server, and the account specific options are located on the BlackBerry Enterprise Server screen of the Account Editor.
MDaemon includes support for "ActiveSync for MDaemon," which is a separately licensed OTA ActiveSync (AirSync) server. This server is capable of synchronizing a user's default calendar and default contact data between his MDaemon/WorldClient account and an ActiveSync capable device. MDaemon's ActiveSync options are located under: Setup » Web, Sync, & IM Services... » ActiveSync, and there is an option on the Account Editor's Options screen if you wish to disable it for certain users. The ActiveSync screen contains options for enabling or disabling it for individual domains, setting the session timeout value, and designating the level of detail for the ActiveSync logs. There are also links to instructions on how to configure devices to use ActiveSync.
When you enable ActiveSync for MDaemon the first time it will operate for 30 days on a trial basis so that you can see if you like it. After that there is a one-time license fee if you wish to continue using it. You can acquire a license key from www.altn.com or your local distributor/reseller.
WorldClient Improvements
| • | ComAgent chat is now included in the LookOut theme. When this feature is enabled from a new option on the Personalize page in WorldClient, a ComAgent bar will appear in the lower right corner of the browser. This allows users to view their buddy list and chat with their ComAgent buddies just as when using the ComAgent application. |
| • | Updated WYSIWYG editor. This should deliver improved performance for message compose load times, and it includes improvements and fixes in both message generation and composition. |
| • | The calendar views in WorldClient's LookOut theme were redesigned to allow for enhanced event rendering and to give a more desktop-like experience. |
| • | You can now edit a single occurrence of a recurring event within WorldClient's calendar. |
| • | The desktop themes can now have a To column. When enabled, this will cause the Sender column to always display the From field. Previously the From column would change between To and From depending on whether the user was in the Sent Items folder or not. Users can enable this column from Options » Columns in WorldClient. |
New in MDaemon 11
BlackBerry Internet Service (BIS) Integration (MDaemon PRO Only)
MDaemon is now equipped with direct support for the BlackBerry Internet Service (BIS). BlackBerry Internet Service users can integrate their MDaemon mail account with their BlackBerry smartphone, allowing for BlackBerry push mail as well as improved email handling when using a BlackBerry device with MDaemon. Any BlackBerry device set up to pull mail from MDaemon via IMAP or POP prior to MDaemon version 11.0 can now be set up for push mail instead. Further, messages that are composed on the device will be sent to your MDaemon for delivery rather than having the BlackBerry Internet Service servers deliver them. This allows emails composed on a BlackBerry device to comply with your server's security policies, content-filter rules, DKIM, archiving, and so on.
Since BlackBerry Internet Service only collects mail from a user's Inbox, this can cause problems for people who use IMAP Filters to sort their messages to specific folders automatically. To overcome this problem, the BlackBerry Internet Service screen of the Account Editor and the Folders page in WorldClient allow the administrators and users, respectively, to choose which folders' new messages will be delivered to the user's device. When the BlackBerry Internet Service connects to MDaemon to collect new messages from the user's Inbox, MDaemon will also push the new messages from the selected folders. All new messages from all the selected folders will be sent to the BlackBerry device's Inbox. This does not push the actual folders to the device, it pushes only the new messages that they contain.
Finally, an internal folder aliasing scheme allows each user's "Sent Items" and "Deleted Items" folders to appear as values that the BlackBerry Internet Service recognizes, no matter what those folders are actually called in the user's account. This helps ensure that sent and deleted messages are placed into the proper MDaemon folders.
A new option that enables smarter message routing was added to the Delivery screen under the Default Domain & Servers dialog. By default, whenever possible MDaemon will maintain a single copy of each message destined for multiple recipients and use multiple RCPT commands to deliver the message. This saves on disk space and bandwidth. For example, if enabled this option will always operate whenever there is a single message addressed to multiple recipients at the same domain. Also, if you are using the "Send all outbound email to the 'Server' specified below" delivery option, which sends all your outbound mail to a single designated host, MDaemon will store a single copy of each message and use multiple RCPT commands even when recipients belong to different domains.
Support for Funambol version 8.0 open source SyncML clients was added. These client are available at no cost, and are greatly improved from earlier versions. In particular, the BlackBerry client shows promise.
Attachment Linking (MDaemon PRO only)
Attachment Linking is a feature whereby attachments are removed from email messages and stored locally on the MDaemon server. In place of the actual attachments, MDaemon will insert URL links which the user can click to download them from the server. This saves bandwidth and storage space on the client machine and especially on mobile devices. In MDaemon 11.0 the Attachment Linking feature was completely overhauled to make it both easier to use and more secure. First, the Attachment Linking dialog was moved from Account Settings to "Setup » Web, Sync, & IM," since WorldClient plays such a major role in the feature. Second, there are two new modes for Attachment Linking: "Let WorldClient automatically manage Attachment Linking" and "Manually configure Attachment Linking." If you select the automatic mode, which is the default setting, the feature works using internal settings that users cannot change. This is the simplest solution, and as long as WorldClient is running no configuration changes should be needed. The manual mode is needed if you wish to place attachments in custom locations.
Attachment Linking has the following additional changes:
| • | All accounts that were configured to use Attachment Linking in previous versions will now be set to extract attachments to the account's FILES folder. Consequently, you may need to manually reconfigure accounts that you want using Attachment Linking. |
| • | Disabling Attachment Linking no longer resets accounts that are configured to use it. They remain configured to use Attachment Linking but simply operate as if they were not. If you reactivate the feature then those accounts immediately start using it again. |
| • | The links that MDaemon places in messages no longer contain direct file paths to the attachments. Instead they contain a unique identifier (GUID) that the server uses to map the file to the actual path. This GUID map is stored in the AttachmentLinking.dat file. |
| • | The New Account Defaults dialog now contains an option that allows you to choose the default attachment handling setting for new accounts. |
DomainKeys Identified Mail (DKIM) Author Domain Signing Practices (ADSP) was finalized and released to the world as RFC 5617. DKIM defines a domain-level authentication framework for email to permit verification of the source and contents of messages. ADSP specifies an adjunct mechanism to aid in assessing messages that do not contain a DKIM signature for the domain used in the author's address (the FROM: header). ADSP defines a record that can advertise whether a domain signs its outgoing mail as well as how other hosts can access that record.
MDaemon was updated to support the final version of this specification. No changes to any existing DKIM or ADSP records are required. This represents the close of over four years of effort in the IETF to get to this point. Alt-N Technologies strongly supports the use of this protocol as widely as possible and MDaemon is fully capable of doing so. You should consider publishing your own ADSP record on your DNS server so that others can know what your signing practices are. ADSP can be toggled using an option on the DKIM Options screen.
STLS For DomainPOP and MultiPOP
MDaemon's DomainPOP and MultiPOP servers now support STLS. You can enable this via a global setting at: Security » Security Settings » SSL & TLS » MDaemon. STLS will be attempted but if the other side of the connection doesn't support it then a regular connection will be initiated. This feature honors the NoSTARTTLS.DAT file for excluding sites that might cause you problems.
See:
Copyright © 1996-2011. All rights reserved. Alt-N Technologies, Ltd.