----------------------------------------------------------------------------- MDaemon Server v3.0 Release Notes ----------------------------------------------------------------------------- --------------------------------- MDaemon v3.0.0.0 - Feb 29nd, 2000 --------------------------------- SPECIAL CONSIDERATIONS ---------------------- o MDaemon now comes in two versions - Standard and Pro. The only differences being that the Standard version does not include multiple domain or IMAP support. This decision was made so that we can maintain a lower price point for those customers who do not need these advanced features. Trial keys will enable MDaemon in Pro mode. o The registration key system has been changed. MDaemon 3.0 requires a new registration key. Registered users of previous versions of MDaemon only need to pay a small upgrade fee in order to acquire a new 3.0 registration key. Please contact sales@mdaemon.com for information on paying the upgrade and acquiring a new registration key. IMPORTANT: MDaemon Pro supports multiple domains on a single instance. As such, MDaemon 2.x's license policy of allowing multiple copies of MDaemon to run under the same key in order to support multiple domains DOES NOT apply to MDaemon 3.0. If multiple domains are required under MD 3.0 you must aquire and run the Pro version. In no case is anyone licensed to run multiple copies of MDaemon 3.0 using the same registration or trial key. In order to enforce this policy MDaemon will not allow multiple copies of itself to operate on the same computer. o MDaemon 3.0 handles customized POP and SMTP strings differently. As a result you will have to reenter any custom POP and SMTP strings into the new sections and using the new numerical values specified in the MDaemon User's Manual. The old 'Pop-Strings' and 'Smtp-Strings' sections have been replaced with 'Custom-POP' and 'Custom-SMTP' under MD 3.0. Also, all the string constants have been changed. Please refer to the manual for instructions on entering custom strings under MD 3.0. o Recent versions of Microsoft Internet Information Server (IIS) have shipped which take control over all the ports used for sending and receiving mail. This prevents competing mail software such as MDaemon from functioning. Fortunately, you can switch off this behavior or reconfigure it within IIS to circumvent the issue. If you are receiving errors from MDaemon stating that various ports are already in use you might be suffering from this problem. If you suspect this check http://kb.deerfield.com/index.cfm?k=2&a=1358 for a Knowledge Base article on how to disable this IIS feature. o The v3.x GUI requires v4.70 of the Windows Common Control library files. These files are already present on Win95b, 98, NT and 2000 computers but may need to be upgraded on older Win95a installation. If certain features of the GUI do not work correctly for you please download and install this Microsoft patch: http://www.microsoft.com/msdownload/ieplatform/ie/comctrl.asp This is a smart patch which will not install unless it's needed. o The v3.x series makes sweeping changes to the internal structure of MDaemon and many of its supporting DAT configuration files. As a result, the installation process has automatically migrated your old v2.x configuration files to the new v3.0 formats where appropriate. Your old v2.x files were backed up and placed in the OLDFILES directory during the installation process. o The multi-domain feature set new to the v3.x series has required changes to several supporting DAT file formats including the USERLIST.DAT file. As a result of these changes the v3.x series is completely incompatible with the discontinued WebPOP series of products from Alt-N Technologies. WebPOP is no longer supported and will not be updated. We are providing our customers with our new WorldClient technology which improves dramatically on the basic WebPOP idea. o There is no longer a POP logon field within the user database. Now, the mailbox value is also used as the POP logon. If you had accounts which maintained different values for their mailbox and POP logon, the conversion process which was invoked automatically during install has changed these account records to use the mailbox value. The conversion utility has created a file called TRACKPOP.TXT which will contain details about accounts which did not have matching POP logon and mailbox values. These accounts most likely will need to be reconfigured at the mail client level to use the mailbox value for the POP logon. In keeping with the removal of a stand alone POP logon field, the $POPNAME$ macro has been discontinued. The conversion utility has scanned the appropriate .DAT files and removed this macro. o There is no longer a separate field in the user database for a FILES directory. Now, an account's FILES directory will always be within the mail directory in a sub-dir called FILES. The conversion utility which was automatically invoked during install will add entries to a file called TRACKDIR.TXT which will detail any incompatibilities this might cause for any of your accounts. Additionally, there is no longer a separate FILES directory for gateway domains. The FILES directory will always be maintained as part of the overall mail directory. o The aliasing system has been completely redesigned. Your aliased accounts have been modified so check the 'Address Aliases' selection from the 'Setup' menu and carefully inspect your aliases ASAP. o WorldClient Standard 2.0, which ships free with this version of MDaemon, includes a new set of customized templates. WC Standard 2.0 depends heavily on the format of these templates and the tags contained therein. Therefore, major template customization with WorldClient Standard is not possible. To realize fully programmable, customizable templates, an upgrade to WorldClient Pro is required. o The documentation accompanying this installation is in Adobe Acrobat 4.0 format. Previously, documentation has been provided in MS Word format. You will need to download and install the Adobe Acrobat reader from http://www.adobe.com in order to access the documentation file. If you wish to download documentation in MS Word 2000 format you may do so via ftp://yoda.altn.com/MDaemon/md3000word2000.zip. o Added the following switch to the MDAEMON.INI file: [DomainPOP] DeleteOldMail=Yes (or No) - default is YES so read this carefully: When this switch is set to YES old mail will be deleted from all MultiPOP and DomainPOP hosts if the 'Leave mail on server' flag is switched OFF. So, unless an account is storing mail purposely on the server, old messages which may be present on the server for some reason will be deleted if this switch is set to YES. o Several places in the MDaemon GUI contain dropdown lists with all your account names and email addresses. Maintaining these lists consumes a huge amount of RAM and CPU power. Therefore, these listings have been restricted to display only the first 250 of your accounts. If you have more than 250 accounts you may have to manually enter addresses in certain locations throughout the GUI rather than select them from a lengthy (and costly) dropdown list. Also, the 'Edit Account' and 'Delete Account' menu options will not be present when account lists exceed 250 members. These functions are not needed since they duplicate functionality now present in the more powerful 'Account Manager' feature. Maintaining these functions when account lists exceed 250 members is very costly in terms of overall system performance and RAM usage therefore their continued existance, now that the Account Manager feature is available, can no longer be justified. If 250 as a limit is not to your liking you can configure the number you want to use by editing the following key in the MDaemon.ini file: [Special] MaxAccountsInListbox=250 o The HELP.DAT file has been updated by the installation process. Your old HELP.DAT has been renamed to HELP.OLD. MAJOR NEW FEATURES ------------------ * MULTIPLE DOMAIN SUPPORT WITH DEDICATED OR MULTI-HOMED IP'S * Full support for multiple domains has been completed. This introduces a wealth of new features and GUI changes. MDaemon's support for multiple domains is built around the concepts of a 'primary domain' and one or more 'secondary domains'. MDaemon maintains local mailbox directories for all accounts within the primary and all secondary domains. Therefore, it is no longer necessary to run multiple copies of MDaemon in order to service multiple domains in this fashion. When you create a mail account one of the things you will do is specify the domain that this new account belongs to. The same goes for mailing lists. Several key features, such as accounts, lists, and domain security settings, are on a PER DOMAIN basis. This means that features such as the IP Screen and IP Shield are tied to domains individually. However, several features such as the 'NT account importer' and the DomainPOP 'Real Name Matching' feature, are tied exclusively to the primary domain only. MDaemon allows you to associate an IP address with the primary and each secondary domain. MDaemon will automatically detect the IP address that an incoming connection is attempting to reach and will use the appropriate domain name accordingly. For example, suppose you have the following domains and accounts configured: altn.com, IP = 1.1.1.1 arvel@altn.com, POP logon = arvel, POP password = ALTN arvelh.com - 2.2.2.2 arvel@arvelh.com, POP logon = arvel, POP password = ARVELH If a connection is attempted to IP 1.1.1.1 then MDaemon will answer as 'altn.com'. If a connection is made to 2.2.2.2 then 'arvelh.com' will be used. Suppose arvel@altn.com connects to 1.1.1.1 to check his mailbox. In the POP logon field he would supply 'arvel' and use 'ALTN' for the password in order to gain access. This is normal. But suppose arvel@arvelh.com connected to 1.1.1.1 to check his mail. Since he is technically connecting to the wrong server (he should be connecting to 2.2.2.2) he will need to supply his POP logon AND domain name in the POP logon field to gain access. This is the only way MDaemon will know which 'arvel' is trying to access mail. Connections to 1.1.1.1 will assume that the 'arvel' making this connection is 'arvel@altn.com'. Of course, if 'arvel@arvelh.com' had connected to 2.2.2.2 he would need only supply his POP logon value. See? So, if an account connects to the IP address for his own domain he will need to specify only his POP logon value, otherwise he must specify his POP logon value and his domain name. In this way support for servicing multiple domains can be accomplish using a single multi-homed IP address. So, how is the POP logon and domain specified? That is a tricky question. You would expect that providing the accounts email address would work, like this: arvel@arvelh.com. However, it turns out that many email clients on the market today will not allow the '@' symbol to be used in the POP logon field. So, MDaemon's default delimiter character is '$' rather than '@'. So, you would use: 'arvel$arvelh.com' rather than 'arvel@arvelh.com'. However, the delimiter character that you want to use can be set to whatever value you like by editing the following key inside the MDaemon.ini file: [Special] POPDelimiterChar=XXXX This value can be up to 10 chars long making it possible to provide a string of characters that serve as the delimiter. For example, using .at. will let you make POP logon values of 'arvel.at.arvelh.com'. Support for multiple domains has required several internal changes including: o Completely new IP Screening and IP Shielding editors have been completed. These new editors allow configuration of these features on a per domain basis. o A $DOMAIN$ macro has been added to the list of macros. This macro will return the currently active domain - so it can vary. The $DOMAINNAME$ macro has been replace with $PRIMARYDOMAIN$. This macro always returned the domain name for the primary domain. You should use the $DOMAIN$ macro in your mail path template so when you create users their mail directories will be separated by domain. For example, use this template for your mail path: c:\mdaemon\users\$DOMAIN$\$MAILBOX$. o Messages which MDaemon must auto-generate from time to time will attempt to use the appropriate domain name. o The DomainPOP 'Real Name Matching' feature will only work with the primary domain. It does not work with a secondary domain. o Every DAT file that was formerly indexed on mailbox only have been converted to full email address indexing. o Several internal editors have been changed to present user selections using complete email address rather than just mailbox values only. o The format of the EDITUSER.SEM, ADDUSER.SEM, and DELUSER.SEM file has been changed. Please refer to the MDaemon manual for complete details. o As part of the multi-domain process, when you create a secondary domain the following aliases will be setup to automatically: MDaemon@secondarydomain.com = MDameon@primarydomain.com listserv@secondarydomain.com = MDaemon@primarydomain.com listserver@secondarydomain.com = MDaemon@primarydomain.com list-serv@secondarydomain.com = MDaemon@primarydomain.com These aliases will be automatically removed if the secondary domain is deleted. * IMAP ENGINE * MDaemon now supports the IMAP protocol. Now you can take advantage of this more modern mail access protocol using mail clients which support it. The IMAP engine includes a special option in the Timeouts dialog. The option is 'IMAP NOOP Commands Trigger 1 Minute Inactivity Timeout'. When active, this setting reduces IMAP timeouts to 1 minute if a NOOP command is encountered. This is to prevent what a lot of IMAP clients are doing - issuing NOOP commands simply to keep sessions alive unnecessarily. Use of this switch will greatly reduce the resources consumed by a widely deployed IMAP based mail site. * IMPROVED CONTENT FILTER SYSTEM * Content filter system now supports AND/OR logic for making more complex rules. Macro support has also been added which will allow you to use MDaemon's macros (such as $HEADER:FROM$ or $BODY$) to create rules that use dynamic data from the message itself rather than fixed data constants. See the MDaemon manual for a complete listing of the macros available to the content filter. * SPAM BLOCKER - ORBS/MAPS-RBL SUPPORT * Added new security feature called "Spam Blocker". This feature allows you to specify several ORBS/RBL type hosts. MDaemon will check each of these hosts each time someone tries to send you mail. If the connecting IP has been blacklisted by any one of these hosts their mail will be refused. IMPORTANT NOTE: Use of this feature can almost completely eliminate spam from being sent to your users. However, some sites are blacklisted by mistake. Use of this feature could cause the postmaster some grief but overall it is well worth it if you are worried about controlling spam. Also, use of this feature will slow the overall performance of MDaemon significantly. Performing multiple lookups on each and every inbound message delivery can be a costly performance drain. Future versions of MDaemon will reduce the performance costs of utilizing this feature. Additionally, the lookups are performed using your internal Windows DNS server - not the one in Setup->Primary Domain->DNS. We tested this feature using our own local DNS server which we run on our network. Performance is acceptable for us at around a 1-3 second delay per mail session when compared to the same mail session with the feature off. The extra few seconds are consumed by the lookup process. The amount of time your lookups will add depends on where your DNS server is and how fast your connection is to it. If you are willing to accept these tradeoffs you can use this feature to become spam free. The feature includes an 'exception' database. The first thing you should do after switching this feature on is add your local IP address range to the exception list. IP's in the exception list are not subject to Spam Blocker lookups. For information on spam and how to control and eliminate it using ORBS visit http://www.orbs.org. Visit http://www.mail-abuse.com/rbl/ for information on the MAPS-RBL. ORBS and MAPS-RBL are trademarks of their respective organizations. Alt-N is proud to be associated and make use of their services on behalf of our customers. * NEW 'POP BEFORE SEND' OPTION * A new editor in the Security menu has been added which allows you to configure a POP check before sending any SMTP email. A lot of ISP's are requiring their customers to perform a POP check before they are allowed to send mail through the ISP's mail server. If this is the case with your ISP then this feature will solve the problem. * PROGRAMMABLE USER MANAGEMENT AND MESSAGE SENDING API * MDaemon.exe, MDConfig.exe, WCStandard.exe, and WebConfig.exe all use MDUSER.DLL to access MDaemon's user management system - you can too. See the MDaemon manual for complete information. * BETTER INTEGRATION WITH WORLDCLIENT PRO * Phase one of our plan to incorporate our products into a seamless whole has been completed. A new dialog screen exists off the Setup menu which contains the setting you need in order to enable integration support between MDaemon and WorldClient (especially WorldClient Pro). o WorldClient Std/Pro sessions will appear in MDaemon's session window list. You can right click and terminate them if you need to. o If you elect to have MDaemon integrate with WorldClient Pro rather than Standard you can set the 'Synchronize accounts' switch setting within MDaemon. When this switch is set, creating/editing/deleting an account via MDaemon, MDConfig, or WebConfig will instantly propagate such to WC Pro. The reverse is also true. In this way complete account synchron- ization between MDaemon and WorldClient Pro is possible. NOTE: This requires WorldClient Pro v2.0.3.0 or higher. IMPORTANT: Added the following switch setting for MDaemon.ini: [Special] AlwaysAllowPOPFromIP=xxx.xxx.xxx.xxx In the account editor you can flag accounts to NOT be able to check mail with POP/IMAP clients. However, WorldClient Pro must use POP to access an account's mailbox. The following switch will allow POP checks to occur if they are made from the IP specified here. So, you could put the IP address of the computer running WorldClient Pro (most often it would be 127.0.0.1) and that computer will be able to access all accounts even if they are set to disallow POP/IMAP access. * NEW, MORE POWERFUL, ALIASING SUB-SYSTEM * The aliasing system has been redesigned completely. Rather than using a separate "alias the domain, then alias the account" method which required two separate editors, MD now uses a single editor which aliases complete email addresses. With this new system you can set an alias like this: 'postmaster@mydomain.com = arvel@otherdomain.com' You can also use wildcards like this: '*@spammo.com = spamfolder@mydomain.com' You can even do wildcards like this: '*@old-domain.com = *@new-domain.com' or '*@first.com = *.user@sub.*' This new system will even allow you to alias OUTSIDE your local system. This makes it possible for you to redirect mail without having to maintain a local account configured to forward messages somewhere. When wildcards are used, the aliasing system behaves in a special manner. Assume you have the following configuration: Account: arvel@arvelh.com Alias 1: arvel_hathcock@arvelh.com = arvel@arvelh.com Alias 2: *@backup.domain.com = *@arvelh.com In the past sending a message to 'arvel_hathcock@backup.domain.com' would not work because the address translation process would convert 'arvel_hathcock@backup.domain.com' to 'arvel_hathcock@arvelh.com' and stop at that point. 'arvel_hathcock@arvelh.com' is not a valid local account so the message would not be delivered. Now, when wildcards are found in the alias the expansion process will continue such that: 'arvel_hathcock@backup.domain.com' will become 'arvel_hathcock@arvelh.com' which in turn will then become 'arvel@arvelh.com'. * MESSAGE PRECEDENCE SYSTEM ADDED * You will notice that MD is using more digits when it computes its file names now. For example, a file name looks like this: MD75000002341.MSG The file name is composed of three parts, the 'MD' part indicates this is an MDaemon email message. If it were 'PD' rather than 'MD' this would indicate that the message has been processed through the content filter system. 'RD' means the message has been read using WorldClient Standard. The next two bytes are the PRECEDENCE (importance) value of the message, 0 to 99. This is the relative sort order of the message during the delivery process. When it's time to deliver the mail in a queue, messages with lower values are delivered FIRST. So, the lower the number the more important the message is. MDaemon has predefined the following PRECEDENCE values: PRECEDENCE_URGENT 10 - messages which match the priority mail settings get this level assigned to them. PRECEDENCE_HIGH 25 - some important system messages from MDaemon to 'Postmaster' might get this level assigned to them. PRECEDENCE_NORMAL 50 - normal email sent from one user to another. PRECEDENCE_LOW 75 - messages generated via the RAW system get this level assigned to them by default, however, RAW messages can have their precedence level assigned dynamically (see below). PRECEDENCE_BULK 80 - mailing list messages get this level assigned to them by default, however, each list can have a unique level assigned via the list editor GUI. PRECEDENCE_RETRY 90 - delivery of messages in the retry queue gets a very low PRECEDENCE rating. The last 9 bytes of the file name is the message number. 9 digits will allow up to 999,999,999 messages to be in the same queue at the same time. Previously, MD could only store up to 99,999 simultaneous messages per queue or mailbox. * NEW WORLDCLIENT STANDARD 2.0 INCLUDED * Bundled WorldClient Standard 2.0 includes several fixes and enhancements. MDaemon now includes a WorldClient configuration setup dialog that allows you to modify key settings for WorldClient Standard or WorldClient Pro if an upgrade has been performed. This more powerful version of WorldClient is now stored in the WCSTANDARD directory within the MDaemon directory structure. The old WC directory can be safely removed. * NEW ACCOUNT MANAGER FEATURE * To better manage the selection, addition, deletion or modification of your accounts, the Account Manager feature has been added. This new GUI will provide much better access to account information. You can use it to sort accounts by domain, name, or mail directory. * NEW HEADER TRANSLATION FEATURE * The 'Outbound Domain Conversion' feature has been destroyed. In place of this horrible coding a powerful 'Header Translations' feature has been inserted. This new feature will allow you to change ANY bit of text found within any header to a new value whenever a message is detected which must leave your domain and travel across the Internet. Your old 'Outbound Domain Conversion' settings have been migrated to this new 'Header Translations' feature. It works like this: You specify the text you want to search for and the corresponding replacement value. MD then zips thru all the headers in the message and makes the replacements. You can specify headers which MD should NOT make modifications to (such as Subject: or Received: headers) as well. This feature is much more powerful and versatile than the old 'Outbound Domain Conversion' feature while retaining the same basic functionality. * MORE MAILING LIST OPTIONS * The following additions were made to the mailing list system: o The membership screen was changed to make it work better. o New POST ONLY and READ ONLY membership types were created. o You can add POST ONLY members to mailing lists using this wildcard form: '*@domain.com'. Now, any poster from 'domain.com' will be allowed to POST to the list. o Added a button to allow you to set which mode new subscribers will utilize, 'NORMAL', 'DIGEST', 'READ ONLY', or 'POST ONLY'. * SPEED IMPROVEMENTS * We are always striving to optimize our code. For v3.0 the internal storage of account information has been optimized to use less RAM and provide faster data access. Also, MD's habit of previously blocking while moving a large message around has been fixed. Finally, several of MDaemon's editor screens have been converted to mode- less property sheets. This will allow screens to remain open for long periods without affecting server performance. The only screens not yet converted are the mailing list and account editor screens. ADDITIONAL CHANGES AND NEW FEATURES ----------------------------------- o The unregistered version now allows unlimited mailing lists. o When MD loads the USERLIST.DAT file it will perform some clean up and make sure to not include any bad records that might be there due to disk corruption or other problems. If corruption is detected MDaemon will rifle through the USERLIST.DAT file and remove any bad records to USERLIST.BAD. o During SMTP i/o, if the addresses used matches an MDaemon alias the router window will display something like this: , Recipient ok (alias for arvel@arvelh.com) For security reasons, the '(alias for xxx@xxx.com)' part is NOT trans- mitted to the mail client (it's only shown locally). o Added a switch to Relay Control and Address Aliases dialog whcih allows you to configure MD such that matches to aliases will NOT be subject to relay restrictions. In other words, addresses which match a known alias are always acceptable for relaying. o Added switches to Misc. Options screen to configure the state of MD's GUI when it starts. These are: start in tray, start maximized, or start in a default window. The old Misc. Options switch 'Start MDaemon in a Maximized State' has been removed. As a result, you may wonder why MD did/didn't start the way it was previously configured. Just reconfigure it using the new settings and all will be well from thence forth. MD will also remember if the router windows was maximized or not from the last shut down and will reinstate it accordingly. o When you change domain names all your accounts will be updated to reflect the new domain name. If the old domain name is used in the account's mail path it can be updated to the new domain name and all the account's mail can be moved to the new location. If you want this to occur set the following switch in the MDAEMON.INI file: [Special] RelocateMailDir=Yes (or No) Since moving mail directories around is a serious thing to do the switch is set to NO by default. o Added 'X-MDRemoteIP:' header which will contain the IP of the system that connected and delivered a message to MDaemon. This switch will not work if you have the 'Hide IP addresses when processing messages' switch on in Misc. Options screen. This is for security purposes. The reason for this header is to allow easy content filtering based on the IP of the remote connection. You can have your content filter rules pickup on this header if needed. o Added 'Send To SMS Gateway' action to the Content Filter section. This provides you a GUI to enter your SMS gateway's host name and your pager number. MD will handle the rest. o EVERYONE mailing lists will be created as private lists. o Added the following content filter macro expansions: $FILTERRULENAME$ $MESSAGEFILENAME$ $PRIMARYDOMAIN$ $PRIMARYIP$ $HEADER:XXX$ Where XXX is the header name. Ex: $HEADER:X-MDAEMON-DELIVER-TO$, $HEADER:TO$, etc... For the "send note" and "append standard disclaimer" actions only, $INCLUDE:XXX$ Where XXX is a text file that is inserted into the declared location. The text file is also run through the macro expansion process. o The summarized log file will now include information on POP and IMAP mail checks. o Added INI option to WorldClient.ini: [Special] ShowAddressLookup=No (or Yes) If set to No, the compose pages will not have links to the LDAP Address Lookup page. The default is No. o MDaemon's real time log files will start with the letters RT so that you can better distinguish them when looking in the logs directory. Also, these files will be deleted as part of the standard clean up procedure anytime MD is rebooted. o Added the following key to the MDAEMON.INI file: [Special] RawConversionLimit=0 MD will process only this many RAW files per queue run. This is to try and be more efficient - convert some, deliver some, convert some more, deliver some more, etc... 0 means no 'per queue run' limitation - MD will convert ALL the RAW files each queue run (as it always has). o The following X-FLAG has been added to the RAW system: x-flag=Precedence ## (where ## is a numeric from 0 to 99) If you put this line into the RAW file the corresponding precedence level will be assigned to the converted message (see above for discussion on precedence levels) o Added a 'Restore panes' option to the Windows menu so that if you move the panes around in the Router window and lose the ability to move them back you can reset all the panes to the default settings. o Many GUI fixes to status bar help and hot-key shortcuts. o The MDSTATS Log page now shows IMAP sessions. o The MDSTATS User page now shows if the account is being forwarded or not. o Added two new switches to MDStats.ini: [Special] OnlyOneInstance=No (or Yes) [QueueOptions] ShowDirectories=Yes (or No) If OnlyOneInstance is set to Yes, only one instance of MDStats will be able to run at a time. If ShowDirectories, from the Queue page you can follow subdirectories of the queue directories. Directories cannot be moved, deleted, or copied. o Messages with the header 'Precedence: bulk' will no longer trigger auto- responders or delivery confirmations. o The 'exit' option will be available in the system tray icon's context menu even when running MDaemon as a service. Previously, when running as a service the 'exit' option was not available. o The import from a text file feature has been changed to output only a single log file with details on successful and failed import attempts. o The import from a text file feature will prompt you for the domain you wish to import users into. o The NT account import feature will prompt you for the domain you wish to import users into. o MDConfig will return an error message during a server connection attempt if the content of its work directory (MDCFGWRK) could not be removed. This is to prevent the accidental overwrite of configuration data due to some older files being flagged 'read only' for some unknown reason. o List membership now supports recursion so it's possible to have other lists as members of mailing lists. o You can't subscribe to the internal EVERYONE list(s) via an email command message to MDaemon. Doing so could present a security issue. o You can no longer add/remove members to the EVERYONE mailing list. This never worked across a reboot of MDaemon and was causing a lot of con- fusion. The EVERYONE mailing lists are maintained by the system and should not be altered. o MDaemon will now send auto-generated system mail back to the triggering user's Reply-To: rather than always to the From: header value. o MDaemon will no longer send the complete path to a file in response to a GET command. Doing so could present a security issue. o Importing accounts now has a 'cancel' button. o Deleting accounts in mass has an 'apply to all items' button on the verification dialog. o The SET DIGEST command has been replaced with simply : DIGEST o The SET NONDIGEST command has been replaced with just: NORMAL o Added SUPPRESS command to add an address to a list's suppression file. See HELP.DAT or the manual for complete instructions on the use of this command. o Added UNSUPPRESS command to remove a suppressed address from a list's suppression file. See HELP.DAT or the manual for complete instructions on how to use this command. o Added a NOMAIL feature to the mailing list engine. Accounts configured as NOMAIL are temporarily suspended from receiving mail but are not removed from the list's membership. Users can set/unset their NOMAIL state by using the NOMAIL and MAIL commands. See the HELP.DAT or the manual for complete instructions on the use of this command. o Added a SIZE command to the MDConfig protocol. This will prevent errant transfers from being accepted as legitimate. o MDaemon's daily log file names will be prepended with 'MD' so that you know it's an MDaemon log file. o The F5 hotkey will refresh all the GUI stats rather than loading the Auto Responder editor - the Alt-F9 key should do that now. o Netscape and Pegasus have difficulty if the last three bytes of a message are '\n.\r'. A workaround has been put into MDaemon to accommodate this. o Passwords in MDaemon, WorldClient Standard, and WebConfig will be case sensitive if the following key is set in the MDaemon.ini file: [Special] CaseSensitivePasswords=Yes (default is Yes) o MDSTATS user list was changed to single column since the data it must display is much longer now (due to multiple domain support). o Added a new switch to WorldClient.ini for WorldClient Standard: [Special] UseLogonCookie=Yes (or No) If set to no, WorldClient Standard will not send or use an HTTP cookie to store the user name of the last logged on user. The default is Yes. o Added switch to Misc. Options to save the state of the POP/IMAP/SMTP servers across a reboot. o Added switch to Misc. Options screen to control use of the ESMTP VRFY command. If you don't want account information provided to other systems who issue a VRFY command uncheck this switch. o Added 'Authenticate List Posters Using FROM: Header' switch to Misc. Options. Usually posters to private lists are checked using the MAIL FROM value passed during the SMTP session. If you would rather have your system use the value of the FROM: header within the message itself you can enable this switch. o EVERYONE mailing lists cannot change the subscribe/unsubscribe settings. These lists are maintained by MDaemon itself. o The template editor no longer has entries for the discontinued POP logon and FILES directory fields. o Changed algorithm to update CPS rate more frequently (thanks go to Mike Smith for his help on this one). o The 'MAILBOX' command sent to MDaemon to retrieve an accounts mailbox format setting has been replaced with the 'MAILFORMAT' command. o The 'POP' section in the MDaemon.ini file has been renamed to 'DomainPOP'. o There is no more 'POP LOGON' command. o There is no more 'KILLFILE.SEM'. o Added 'ALIASES.SEM' which forces a reload of the 'Address Alias' settings. o Added 'TRANSLAT.SEM' which forces a reload of the 'Header Translation' settings. o The $POPACCESS$ macro has been changed to $ALLOWACCESS$. o The new $DOMAIN$ macro will return the domain name of the currently active domain rather than a fixed value. o The $DOMAINNAME$ macro has been replaced with the $PRIMARYDOMAIN$ macro. This macro always returns the domain name of the primary domain. o The new $DOMAINIP$ macro will return the IP address of the currently active domain rather than a fixed value. o The $PRIMARYIP$ macro will always return the IP address for the primary domain. o The 'PORTS' and 'DNS' tabs have been split up. o The 'DNS' allows you to edit the number of DNS retry attempts. o Added switch to 'DNS' tab to use the internal Windows controlled DNS server IP addresses. o Added a button to load and edit the MXCACHE.DAT file. o Added switch to 'DNS' tab for controlling the use of A records parsed from MX packet returns. o Several screens have had IMAP configuration settings inserted. o The 'REGISTER' tab has been removed from 'SETUP | PRIMARY DOMAIN'. The information in this tab was needlessly duplicating the 'Register MDaemon' menu selection. o The 'Misc. Options' screen has a new entry that allows you to specify a maximum size after which the transfer of a message will be unilaterally terminated by MDaemon. This acts as an emergency cutoff switch to help arm you against malicious mail bomb attacks. o The 'Misc. Options' screen has a new entry that allows you to select the application of 'Strict Quotas'. When selected, account quota calculations will include any hidden files found in the mail directory and also all the files found by a recursive search of the entire mailbox directory structure. o MDaemon and MDConfig will store the APP directory in the registry. This is useful for third party utility integration. o MDaemon will use 'company.mail' as a default primary domain name if none other is specified. o MDaemon will attempt to detect your IP address and use that rather than '127.0.0.1' for a default value. o You can have MD add a header to list messages by setting the following key in the MDAEMON.INI file by hand: [Special] BulkMailHeader=Precedence: bulk You can change this value if needed. Its purpose is to provide a value that will cause downstream autoresponders to not send back an auto- response. Please be aware that this value must be a complete RFC822 legal message header (in legal 'Header: Value' format) o Hitting ALT-F4 will not shut down the server. It will minimize it to the system tray. o MD will be more tolerant of improperly formatted MXCACHE.DAT files. o Move IP Cache menu selection out of the Security section and into the Setup main menu. o When you override the SMTP or POP initial greeting strings MDaemon will no longer append version information to the new value. o One misconfigured server we found on the net responded to the end of a message transmission with 220 rather than 250. 220 is the signal to start the message transaction process. This confused MD and resulted in strangeness. We've patched MD to handle delivery to these sorts of troublesome sites. o If a message arrived via an SMTP session which specified a NULL return path (i.e. MAIL From: <>), and the message didn't have a Reply-To: header, but the 'Force Reply-To' switch was set, MD would form the forced Reply-To header correctly, but in a way incompatible with certain MS mail client products. This has been corrected. o For the purpose of better integration between MDaemon and WorldClient the 'Passwords are case sensitive' option has been removed from the WorldClient settings dialog within MDaemon. The switch is now called 'POP/IMAP/WC passwords are case sensitive' and can be found in the Misc. Options screen. Since the setting applies to more than just WorldClient it was removed from the WorldClient specific editor and placed in the ever growing Misc. Options area. o MD will not auto-prune a list member on a 500 error if the message transmission has taken place. 5xx errors after the transmission begins will no longer trigger an autopruning event. o Messages created for the "Archival" feature will now be exempt from the content-filter system. This was causing some problems. o MD will strip 'R:' from the beginning of list message subject headers. o MD will warn you if a newly created account uses a mail directory that already exists. o Changed default full size log window font to MS Sans Serif unbolded from old ugly compiler default. You can control the font used by setting the following keys: [LogWindow] DefFontFace=MS Sans Serif (or Times Roman, or whatever you like) DefFontHeight=10 (or whatever, 10 is default) DefFontWidth=4 (or whatever, 4 is default) o The following key will reflect if MDaemon was started as an app or service: [Service] StartedAsService=Yes (or No) o The POP PASSWORD command is not properly named since the password is also used for IMAP and WorldClient. The command has been changed to simply PASSWORD. o The mailing list editor will allow you to specify separate files for the list's header and footer file entries. o The KILLFILE.SEM file has been renamed to SUPPRESS.SEM. o The related MX options will be disabled in the GUI when MX records are not being used. o MDaemon will not attempt to perform a RAS dialup if the profile is missing for some reason. FIXES ----- o Fix to potential crash when processing certain mal-formed headers. o Fix to potential buffer overrun when recipient's domain is 255 chars long. o Fix to DomainPOP parsing problem when addresses were presented like this: "'Thomas, Frank'" , "'Hathcock, Arvel'" , etc... o Fix to 100% CPU sometimes at the end of a message transfer. o Fix to forwarding messages sometimes leading to large .MSG files in one of the mail queues and also a 100% CPU situation. o Fix to EVERYONE mailing lists not being updated after an account import operation. o Fix to MDaemon not always honoring aliases pointing to a mailing list. o Fix to MDaemon losing the case of the mailing list name when a member unsubscribes. o Fix small bug that could result in orphaned .RTE files in the mail queue. o Fix small bug preventing accurate scrolling of the log window for some. o Fix to router window scrolling problems on sites with hi-rez monitors o Fix to potential crash when editing or adding a user (rare but possible) o Fix to rare problem wherein multiple RCPT TO command could be given in an SMTP session errantly. o Fix to messages forwarded using advanced forwarding options not working. o Fix to some forwarded messages not being properly locked while being constructed. o Fix to MDConfig not sending a list's autoprune setting back to MDaemon. o Fix to WorldClient Properties dialog not always saving/retrieving its settings to/from the right WorldClient.ini file. o Fix to RAS sub system sometimes displaying the wrong result string when a disconnection event occurs. o Fix to small memory leak when importing NT users from the SAM database. o Fix to real names not being imported from NT SAM unless MD was running on the PDC. o Fix to MD not cleanly exiting an SMTP session in the event of a serious problem which required a session termination. o Fix to a bug which caused MD to not properly byte-stuff a period on a line by itself in some cases. o Fix to accelerator conflict related to the Content Filter selection. o Fix to MD sometimes not cleaning up its work files from the SMTPIN queue when a session abnormally terminates. o Fix to list footer being applied to messages that are base64 encoded. List headers and footers are incompatible with this sort of mail. o Fix to bug wherein the Content-Type header would be mishandled when MD extracts attachments from messages. o Fix to MD not locking the message file as it moved it into the users directory. o Fix to MD using 100% CPU when filtering a message through an MBF and when shuffling messages into other queues (including user's mail dir). o Fix to autoprune feature not working correctly under some conditions. o Fix to a problem wherein subject text contained in { and } chars might be stripped from list messages needlessly. o Fix to content filter disclaimer always being added as a separate attachment. o Fix to crash when using the outbound domain conversion feature along with RAW messages that do not contain a domain name in the FROM header. The content filter feature generates such messages. o Fix to MD sometimes not sending notifications when auto-pruning removed a list member. o Fix to user's added via MDConfig not getting new user welcome message. o Fix to a bug wherein switching fonts on the router window would prevent it from properly scrolling. o Fix to permanent IP addresses being removed from the IP Cache if the 'Clear IP Cache at each queue run' switch was set. o Fix to blank catalogs not always being truly created. o Fix to modality problem with popup message boxes potentially leading to a system crash. o Fix to low disk space monitoring system sending a warning message and/or shutting off mail services even if configured not to do so. o Fix to several problems related to auto low disk cutoff system. o Fix to MDConfig putting ini file on the desktop at times. o Fix to being able to create a catalog using a name which already exists. o Fix to several errors related to the GUI tracking the runtime status of WorldClient and WebConfig. o Fix to several problems with starting/stopping WorldClient Pro via the MD GUI. o Fix to ReplyTo header not always working correctly in RAW mail. o Fix to bug preventing receipt notifications from working properly at times. -----------------------------------------------------------------------------