New in MDaemon 13.6 |
  
|
New in MDaemon 13.6 |
|
MDaemon Pro now has a simple message recall system that can be enabled and configured on the new Message Recall screen, located on the Server Settings dialog. Using this system you can choose to delay incoming messages sent by authenticated local users for 1 to 15 minutes. During that delay period the messages are simply left in the inbound mail queue. This provides a short period during which a user can attempt to stop a message from being delivered. Once the delay period expires the message is delivered normally. The message recall feature is disabled by default. When the feature is enabled, the default delay period is 1 minute.
To recall a message a user can simply log in to WorldClient and click the Recall button that will be displayed when viewing a recently sent message in the Sent Items folder. If clicked before the recall time limit expires, WorldClient will send a RECALL message to MDaemon. Alternatively, the user can go the the Sent Items folder in his mail client, locate the message he wishes to recall, and then "Forward as Attachment" the message to the mdaemon@example.com system account, using "RECALL" as the message's Subject. Another alternative is to view the message's headers, copy the Message-ID header value (the part to the right of the "Message-ID:" string), create a new message and place "RECALL" plus the message ID value in the subject. If both alternatives are used within the same recall message, only the message ID option will be used.
Regardless of the chosen recall method, MDaemon will send an email back to the user, saying whether or not the recall was successful. When a message is successfully recalled, MDaemon deletes the message from the inbound queue as if it had never been sent. All recall processing is logged to MDeamon's Routing log.
A Statistics Log screen was added to the Logging dialog, with options for controlling the statistics log file and a new SQLite database file used for logging statistical information about MDaemon's activity. This database is used by WebAdmin's new Reports feature and contains data on MDaemon's bandwidth usage, number of inbound and outbound messages, spam statistics, and the like. By default this database is stored in the "MDaemon\StatsDB" folder and 30 days worth of data is saved, but you can adjust how long to keep the data if you wish to retain more or less than the default 30 days. Data older than the designated limit will be removed during the nightly maintenance process. You can also specify how often MDaemon will compact the database to conserve space.
The Reports page in WebAdmin uses this database to generate a variety of reports available to Global administrators. For each report, data may be generated for several predefined date ranges, or the admin may specify a custom date range. Administrators can choose from the following reports:
●Enhanced bandwidth reporting
●Inbound vs. Outbound messages
●Good messages vs. Junk messages (percentage of email that is spam or a virus)
●Inbound messages processed
●Top recipients by number of messages
●Top recipients by message size
●Outbound messages processed
●Top spam sources (domains)
●Top recipients of spam
●Viruses blocked, by time
●Viruses blocked, by name
ActiveSync Services for MDaemon now support MDaemon's public folders in addition to mailbox folders. The behavior of any client accessing public folders via the ActiveSync protocol can vary. While MDaemon's ActiveSync implementation supports Email, Events, Contacts, Tasks and Notes, not all device clients are capable of handling this data. Public folder access can be controlled at the user, domain, and server levels.
There is a new global option on the Public & Shared Folders screen (and mirrored on the Mobile Device Management » Options screen) for controlling whether or not ActiveSync users will be able to access their public folders from their devices. There are corresponding options on the Domain Manager and Account Editor that can be used to override the global setting for specific domains and users, respectively.
MDaemon 13.6 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.
The ActiveSync server now supports additional ActiveSync protocol versions: 12.1, 14.0, and 14.1. This provides ActiveSync support for a wider variety of devices and applications, including Outlook 2013. This change provides new ActiveSync policy capabilities and improves overall device management. ActiveSync for MDaemon is a separately licensed product with a free trial period, and it can be purchased from www.altn.com or your local distributor/reseller.
Additional ActiveSync changes include:
●The Policies screen has been redesigned and supports many new ActiveSync policy options.
●Options has a new control to specify the number of days that an ActiveSync device can go without connecting to MDaemon before it will be forgotten. When MDaemon forgets a device, its configuration and access settings are discarded. If the device ever connects again, MDaemon will respond as if it is a new device that has never been used on the server. It will be forced to reprovision if a policy is in place for the domain, perform an initial folder sync, and re-sync all subscribed folders. This option can help keep your server free from maintaining information for old and unused devices. The option is set to 31 days by default.
●The Integrated Accounts screen was redesigned and renamed to "Devices".
●There is now a White List and Black List for ActiveSync. The White List is used to exempt specific devices or device operating systems from provisioning, or policy restrictions. The Black List is used to restrict devices or device operating systems from accessing MDaemon's ActiveSync server. For both lists you can create entries based on Device ID, Device Type, and Device OS.
●The new Restrictions screen allows you to specify User Agent and Device Type values and restrict devices matching those values to specific versions of ActiveSync.
●For accounts configured to use the Attachment Linking feature, it can now be used for outbound messages as well, with a new option on the Account Editor's Attachments screen for enabling the new feature on a per-user basis. When the user sends an email, Attachment Linking will extract the file, store it, and replace it with a URL to the file.
●You can now specify the maximum number of days that any attachment will be stored. As part of the daily cleanup event, MDaemon will remove from the root attachment folder and its subfolders any file found to be older than the specified number of days. This only works when you are using the default root attachment folder: <MDaemonRoot>\Attachments\. It does not work if you customize the attachment folder to point elsewhere.
●You can now specify a minimum size below which attachments are not extracted. Using this option you can configure MDaemon to ignore small attachments, extracting only larger ones.
●Attachment Linking will try to use the file name provided in the MIME headers, if one is present. If the file name is longer than 50 characters then only the last 50 characters will be used. If the file name is missing an extension, ".att" will be appended.
MDaemon now has a Public Folder Manager under the Setup menu, to help you administer your Public Folders more efficiently. The Public & Shared Folders screen, however, is still located on the Server Settings dialog for managing your global settings.
●The Domain Manager has been redesigned. It now displays several screens for each domain instead of having everything on a single screen, and there are better options for creating, deleting, and renaming domains. Further, many domain specific functions have been moved there and consolidated from other places in the UI. As a result of this you will no longer find default domain related settings on the Server Settings dialog. You can still designate a Default Domain via a button on the Domain Manager, but that designation is only needed in a few circumstances, such as any time the server engines cannot determine a more appropriate domain to use in a given processing context (which should be almost never).
●Domain Signatures (both plain text and html) were combined onto a single screen called Signatures and moved to the Domain Manager. The Server Settings dialog contains a similar screen called Default Signatures, used for Domains without a designated Domain Signature.
●When you have configured MDaemon's Delivery options to send some messages to a Smart Host, you can now specify different Smart Host settings on a per-domain basis using the Domain Manager's Smart Host screen. When no Smart Host has been specifically designated for a domain, the default Smart Host will be used.
MDaemon now contains both Group and Template Managers. The Group Manager helps you more easily manage groups. It is used to create account Groups and manage which accounts belong to them. Groups have a number of different uses and functions. For example, using the Group Properties screen you can assign an account template to a Group, allowing you to control a variety of account settings for group members. You can also control whether or not group members have access to ComAgent and instant messaging. Further, the Content Filter supports groups, allowing you to create rule conditions based on whether or not a message sender or recipient is a member of a specific Group. Finally, for Shared Folders you can assign Access Control List rights to specific Groups, meaning all members of that Group will share those access rights. You can add accounts to a Group from both the Group Manager and from each user's Mail Folder & Groups screen.
With the Template Manager you can create and manage Account Templates, which are named sets of account settings that can be assigned to specific Groups. Any account belonging to one or more of those groups will have the designated account settings locked, being controlled only by the assigned templates rather than by the Account Editor. The categories of account settings that a template will control are designated on each template's properties screen, which is reached by double-clicking the template's name. Further, there is a special template called "New Accounts" that replaces the old New Account Defaults screen. This special template is applied to all new accounts when they are created. Rather than locking and controlling certain account settings like other templates, New Accounts is used simply to designate the initial settings for new accounts. Those initial settings can then be changed normally by using the Account Editor to edit individual accounts.
On MDaemon's user interface, the tabs that display Routing, SMTP-in, SMTP-out, IMAP, POP, MultiPOP, and DomainPOP activity can now be colorized to help visually separate events during a session. This features is disabled by default, but can be enabled via the "Use colors when displaying mail session logs" option located at: Logging » Options and Preferences » UI. The default text colors can be changed by editing the [Colors] section of the LogColors.dat file. See the Logging Options page for more information and a list of the default colors.
Active Directory monitoring has been improved to periodically query Active Directory and keep all public contact records updated with the most recent information stored. Common fields like an account's postal address, phone numbers, business contact information, and so on will be populated into their public contact record, and this data will be updated any time it is changed in Active Directory. Numerous contact record fields will be monitored in this way. For a complete list of which public contact record fields can be mapped to Active Directory attributes, see the contents of the ActiveDS.dat file in MDaemon's \app\ folder. Also, you do not need to enable full Active Directory account monitoring to take advantage of this. A new option on the Active Directory Monitoring screen allows you to enable this feature separately from full Active Directory account monitoring.
This feature will create contact records on the fly if they don't already exist, and it will update contact records that do exist. Further, please note that it will overwrite any changes you make outside of Active Directory. Contact record fields that are not mapped are left unaltered. Therefore any existing data that is not subject to this process will not be altered or lost. Finally, MDaemon accounts that are set to private are not subject to having their contact records created or updated.
Windows Performance Counters have been implemented to allow monitoring software to track MDaemon's status in real time. There are counters for the number of active sessions for the various protocols, number of messages in the queues, server active / inactive states, MDaemon up time, and session and message statistics.
To use the performance counters, start System Monitor by going to Control Panel | Administrative Tools | Performance, or by running "perfmon". These are 32-bit counters so on 64-bit machines you must run "mmc /32 perfmon.msc". Click on Add Counters, select the MDaemon performance object, then select and Add the counters that you want to see. To see the performance counters from MDaemon running on another machine you must have the "Remote Registry" service enabled and access through any firewalls.
ActiveSync Device Policy Support
MDaemon is now equipped with support for basic ActiveSync device policy. You can view predefined policies and create your own policies from a new screen at: Mobile Device Management » ActiveSync » Policies. Policies can be created to require devices to use a password, force passwords to use both letters and numbers, lock devices after a designated number of minutes, and cause the device to be wiped after ten failed password attempts.
A default policy can be assigned per domain from the ActiveSync » Domains screen. Policies can also be assigned per device, from the Account Editor's ActiveSync screen.
|
Not all ActiveSync devices recognize or apply policies consistently. Some may ignore policies altogether and others may require a device reboot before changes take effect. Further, no policy is applied until the next time the device connects on its own to the ActiveSync server. |
Detect and Stop Hijacked Accounts
Dynamic Screening has been improved by adding an option to disable local accounts that try to send more than a specified number of messages in a designated number of minutes. Accounts disabled by this process can still accept incoming mail but they cannot log in to web mail or web administration and they can not collect or send mail. The intent is to try and recognize and stop a hijacked account so that the postmaster can review the situation and take action. Consequently, when an account is disabled a notification email is sent to the postmaster. The postmaster can simply reply to the message to re-enable the account.
The WorldClient themes now support document sharing using document folders. Document folders have full Access Control List (ACL) support like other shared folders, which can be used to set permissions and sharing rules, and any types of files can be shared through the system. WorldClient users can upload files to their document folders using the built-in tools. When using the LookOut theme, browsers that support the HTML5 Drag and Drop API, such as Chrome and Firefox, can also upload files by dragging them from the desktop into the browser window. Filenames can be searched and renamed, and files can be attached to new messages that are being composed.
IMAP "COMPRESS" and "BINARY" Support
The IMAP server now supports the COMPRESS extension (RFC 4978), which compresses all data sent to and from the client. This does require extra memory and CPU usage per IMAP session. You can disable COMPRESS support via a new option at: Server Settings » Servers.
The IMAP server also now supports the BINARY extension (RFC 3516), which lets clients download message attachments in decoded form.
Simple Message Ticketing System
Public folders can now be configured as a message ticketing public folder through the "Assign a unique ticketing (or tracking) number to messages" option located on the Public Folder Manager. If this is enabled for a public folder MDaemon will add the public folder name and a unique identifier to the subject of messages sent to the submission address of the public folder. Any outbound messages having this specially formatted subject will have the From address changed to the submission address of the public folder and a copy of the outbound message will be placed into a child public folder named "Replied To". In addition, any inbound messages with this specially formatted subject will be automatically redirected to the public folder, regardless of the address the message was sent to.
ActiveSync Autodiscover Service
MDaemon now supports the ActiveSync Autodiscover Service, which allows users to set up an ActiveSync account with just their email address and password, without needing to know the host name of the ActiveSync server. Autodiscover requires HTTPS to be enabled, and for most systems it also requires that a new CNAME or A-record be added to DNS. "autodiscover.<your-MDaemon-server>.com" should resolve to the MDaemon server running ActiveSync (for example, autodiscover.example.com).
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.
●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 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.
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.
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.
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.
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.
New quota options are available on the Template Manager 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.
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.
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 » Mobile Device Management... » 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 » Mobile Device Management... » 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. After that, if you wish to continue using it you can acquire a license key from www.altn.com or your local distributor/reseller.
●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.
See:
Copyright © 1996-2013. All rights reserved. Alt-N Technologies, Ltd.
