MDaemon Server v11.X Release Notes

Alt-N would like to recognize and celebrate the life and contributions of a unique and talented individual without whom our achievements would have been incomplete at best and a whole lot less fun.  Linda Cleminshaw 1964-2009 -- you will be greatly missed. 

MDaemon 11.0.0 - March 10, 2010

SPECIAL CONSIDERATIONS

1.  MDaemon's POP and IMAP servers now require use of the full email address as login by default.  If user's mail clients are configured to only use the mailbox value as login they will not be able to log into MDaemon with their POP/IMAP client until they change their mail client configuration to use full email address as login.  If you wish to continue to allow mailbox only logins then you can disable a switch in Ctrl+O | System "POP/IMAP servers require full email address for authentication" (strongly NOT recommended as mailbox only logins are ambiguous when MDaemon is serving multiple domains). 

2.  Attachment Linking has undergone a complete overhaul and its configuration has been reset to defaults as a result. See the section ATTACHMENT LINKING for details.  All accounts previously subject to Attachment Linking in previous versions will now be setup to extract attachments to the FILES folder. So, you may need to manually reconfigure accounts that you want using Attachment Linking. Sorry, this could not be helped.

3.  Updated WorldClient.dll to dynamically generate the robots.txt file in the WorldClient HTML directory to be explicit about which files should not be indexed unless the WorldClient.ini has the following in place: ModifyRobotsTxt=No under the [WebServer] section. Alternatively if the robots.txt file is read-only it will not be touched. Custom Logon.html files need to have the following meta tag inserted into their headers: <meta name="ROBOTS" content="NOINDEX, FOLLOW">

4.  The Globe and Redline themes within WorldClient have been discontinued and are no longer being supported.  Running MDaemon 11 for the first time will move the \Templates\ and \HTML\ folders for these two themes to \WorldClient\Old\.  They can be safely deleted if you decide not to manually maintain these themes yourself.

5.  DKIM-record-check at http://dkimcore.org/tools/dkimrecordcheck.html is a tool for checking your DKIM DNS setup for compliance with the DKIM specification as published in RFC 4871.  Given a selector and a domain this tool will retrieve the DKIM key record from DNS, parse it using the BNF from the DKIM specification, and then sanity check the various fields.  In the end you'll get a good / bad result letting you know whether your DKIM DNS setup is "to spec" or not.  Note, this site is a work in progress and is not hosted or created by Alt-N.

6.  The default options for quota calculations have been reset.  Check Ctrl+U|Quotas to make sure they are as you desire.  The default for including Inbox sub-folders when calculating quotas has been changed from FALSE to TRUE.

7.  As part of it's BlackBerry Internet Service integration (see below) MDaemon now requires all IMAP/POP sessions from BlackBerry users to use a full email address as IMAP and/or POP login when configuring their BlackBerry device to collect mail.  This is necessary in order to achieve the level of integration we are shooting for.  This might mean that some of your existing users will no longer be able to collect mail on their BlackBerry.  This problem is solved by deleting and recreating the email profile on the BlackBerry device (see "How to get your MDaemon account setup for BlackBerry push mail" below) and being certain to use full email address when configuring the username/login parameter.

8.  MDaemon's installation process now performs a one-time collection of basic customer information.

MAJOR NEW FEATURES

[4274] BLACKBERRY INTERNET SERVICE (BIS) INTEGRATION (MDaemon PRO only)

Users of BlackBerry's BIS service can integrate their MDaemon mail account with their BlackBerry device allowing for BlackBerry push mail as well as improved email handling when using a BlackBerry with MDaemon. BIS integration options can be configured via a new selection from the Setup menu (Alt+B).  Any BlackBerry device setup to pull mail via IMAP from MDaemon can be setup for push mail and (very cool) will also have messages composed on the device sent to your MDaemon for delivery rather than having the BIS servers deliver the mail themselves.  This allows your BlackBerry composed emails to comply with your own security policies, content-filter rules, DKIM, archiving, etc. 

Also, a new UI screen within the account editor and WorldClient will allow users to select one or more mail folders. When the BIS service connects to MDaemon to collect Inbox mail MDaemon will serve up the content of these selected folders as well (root inbox folder content is always sent and so doesn't need to be selected). All the messages from all the selected folders will appear within the single Inbox folder on the BlackBerry device. The messages are not actually moved into Inbox on MDaemon and folders are not created on the BlackBerry.  Rather, selected folder content is sent to the BlackBerry as if it were part of the Inbox folder.  

Finally, an internal folder aliasing scheme aliases your Sent and Deleted folders (no matter what they are actually called) to values which BIS recognizes.  This will help insure that sent and deleted messages are placed into the proper MDaemon folders.

How to get your MDaemon account setup for BlackBerry push mail:

  1. Go into the BIS configuration options (Alt+B).
  2. Enable the feature and make sure that the Subscribe URL is pointing to your WorldClient and the SMTP server value is pointing to your MDaemon SMTP server.   All these values should be setup and working with the defaults that you find there.  Remember that the Subscribe URL should point to your WorldClient server which needs to be accessible to the outside world.
  3. If your BlackBerry is already collecting mail from your MDaemon account this means that you have already configured your BlackBerry with an email profile for your MDaemon account.  This email profile must be deleted (recreating the email profile is necessary in order to trigger push mail setup within BIS).  Click here for instructions on how to setup an email profile on your BlackBerry.
  4. If your BlackBerry is not setup to collect mail from your MDaemon account use your BlackBerry device to create an email profile to do so.
  5. Some time after this the Subscribe URL associated with the domain the user belongs to will receive what's called a SUBSCRIBE request from the BIS service. This will be handled by WorldClient.  The process usually takes 5 minutes.
  6. Once the SUBSCRIBE request is properly received and processed the user's BlackBerry will be subscribed for push mail and the user will receive an email on his BlackBerrry telling him so.

Unsubscribing from push mail can be done by deleting the email profile using the BlackBerry device itself. BIS will then send MDaemon an UNSUBSCRIBE request and the account will be unlinked.  The UNSUBSCRIBE request may take some time to arrive and this poses no operational issues.

While waiting for the SUBSCRIBE request from BIS to arrive, any changes to email profile settings (such as signature text, advanced setup options, etc) will invalidate the request and you will not receive it.  So, make no further changes to the email profile settings until the SUBSCRIBE request arrives or you will have to start over with the SUBSCRIBE process.

BIS activity (connections from BIS IMAP clients as well as requests and notifications sent to/from MDaemon and the BIS network) are logged into a new tab and log file called "BIS" which you will find in the "Mail" section of the main UI.

When BIS integration is disabled globally or for particular domains any accounts already subscribed to BIS will continue to operate as before.  These switches will disable any additional BlackBerry device integration, however existing integrations are unaffected. 

This level of integration is not possible using POP.  Any of your BlackBerry users currently using POP to collect mail will need to delete their email profile and recreate it using IMAP (not POP) which may require accessing advanced setup options on the BlackBerry (see "How to get your MDaemon account setup for BlackBerry push mail" above).  MDaemon's IMAP server must be running for this feature to work.  It does not (and can not) work with POP.

MDaemon now requires all IMAP/POP sessions from BlackBerry BIS users to use a full email address as IMAP and/or POP login when configuring their BlackBerry device to collect mail.  This is necessary in order to achieve the level of integration we are shooting for.  This might mean that some of your existing users will no longer be able to collect mail on their BlackBerry until they delete and recreate their email profile on the BlackBerry device (see "How to get your MDaemon account setup for BlackBerry push mail" above) or at least update their BlacKBerry mail configuration settings to use full email address as login.

BIS and SSL

The BIS SMTP client does not currently support SSL/STARTTLS with self-signed certificates.  So, if you use STARTTLS or check the "Use SSL port" next to the SMTP server in the new BIS UI and you are using self-signed certificates then all SMTP sessions from BIS will either error out or get "stuck" until the inactivity timeout is reached.  This is solved by purchase and use of a commercial SSL certificate. 

The BIS IMAP client does support SSL with self-signed certificates.  So, if you check the "Use SSL port" next to the "Domain name" in the new BIS UI you can get IMAP SSL using the dedicated IMAP SSL port with any certificate you have.  The BIS IMAP client does not currently support STARTTLS so it is not possible to get SSL except on the dedicated IMAP SSL port.

[4802] IMPROVED SYNC CLIENT SUPPORT

Added support for Funambol version 8.0 open source SyncML clients.  These clients are available at no cost, and are greatly improved from earlier versions.  In particular, the BlackBerry client shows promise over other solutions.

Over the air installation from the device's browser:

BlackBerry OS 4.7 or later: http://my.funambol.com/bb/sync2.jad
BlackBerry OS 4.6 or prior: http://my.funambol.com/bb/sync.jad
Windows Mobile smart phone: http://my.funambol.com/me/funambol-sph-sync-client.cab
Windows Mobile PocketPC: http://my.funambol.com/me/funambol-ppc-sync-client.cab

Other phones, Microsoft Outlook, and Mozilla Thunderbird:

http://www.forge.funambol.org/download/

[4473] SMARTER MESSAGE ROUTING

A new switch was added to MDaemon's F2->Delivery screen.  The switch enables smarter message routing and is enabled by default.  With this switch enabled MDaemon will maintain single copies of messages destined for multiple recipients and use multiple RCPT commands to deliver the message whenever possible.  This saves on your 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 delivery option which sends all your outbound mail to a single designated IP/domain/host, MDaemon will store a single copy of each message and will use multiple RCPT commands even when recipients belong to different domains. 

[4235] 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 attachment, MDaemon will insert a URL which the user can click on to retrieve the attachement(s) as needed. This saves bandwidth and storage space on the client machine and especially on mobile devices.

All existing Attachment Linking config settings are no good and have been reset to defaults (which is automatic mode -- see below --, with the system enabled, but with no accounts setup to use it).

The Attachment Linking feature has been completely overhauled in the hopes of making it more attractive and easier to use. First, the UI for it was moved from "Account Settings" to "Web, Sync, & IM" since WorldClient plays such a major role in Attachment Linking. Second, there are two modes now with Attachment Linking - automatic and manual. If you select automatic mode (the default) then the feature works using internal settings that users can not change. As long as WorldClient is running no config changes should be needed. Manual mode is for when you want to place attachments in custom locations. You can still use all the account macros (like $DOMAIN$ and $MAILBOX$ etc) to keep attachments segmented. In automatic mode MDaemon places attachments at \MDaemon\Attachments\$DOMAIN$\$MAILBOX$\. This can not be changed.

The Account editor UI has been updated and accounts can now be configured to:

  1. Leave attachments alone -- do nothing (the default).
  2. Pull attachments out and store them in the account's FILES folder. Note that this does not employ Attachment Linking so there are no URLs placed within messages when this option is used and MDaemon does not police the user's FILES folder. With this option attachments are simply extracted and the email receives a list of attachment names so that you can see what was pulled out but no URL links to them are provided.
  3. Pull out attachments, store them, and provide URL access to them according to Attachment Linking configuration.

If you enable Attachment Linking you must also configure accounts to use it by selecting option 3 above.

All accounts previously subject to Attachment Linking in previous versions will now be setup to extract attachments to the FILES folder. So, you may need to manually reconfigure accounts that you want using Attachment Linking. Sorry, this could not be helped.

Disabling Attachment Linking will no longer reset accounts configured to use Attachment Linking. They will remain configured to use Attachment Linking however with the system disabled this won't do anything anymore. The config settings are left alone in case you switch Attachment Linking back on (you won't have to reconfigure accounts this way).

Attachment Linking no longer inserts the full paths to any URL it generates and places into email messages. Instead a GUID is generated and this is used to map a URL to an actual file on disk. This GUID map is stored in the AttachmentLinking.dat file.

The Account Defaults UI has been updated to allow a default selection for how to handle attachments when creating new accounts.

[4502] DKIM ADSP - RFC 5617 SUPPORT

DKIM ADSP (Author Domain Signing Practices) was finalized and released to the world as RFC 5617 (see http://tools.ietf.org/html/rfc5617). 

DomainKeys Identified Mail (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 4+ years of effort in the IETF to get to this point.  Alt-N strongly supports the use of this protocol as widely as possible and MDaemon is fully capable to do so.  ADSP can be toggled using Ctrl+S->DKIM Options->"Unsigned/Improperly signed messages trigger ADSP processing."  You should also consider publishing your own ADSP record in your DNS server so that others can know what your signing practices are (see http://tools.ietf.org/html/rfc5617 for details).

[2051] STLS FOR DOMAINPOP/MULTIPOP

MDaemon's DomainPOP and MultiPOP servers support STLS. You can enable this via a global setting at Ctrl+S->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 which might cause you problems.

CHANGES AND ADDITIONAL NEW FEATURES

Fixes

MDaemon is a registered trademark of Alt-N Technologies, Ltd.
Copyright ©1996-2010 Alt-N Technologies, Ltd.