Release Notes:  DynaComm i:mail
Release Number:  4.0.0.0 PATCH
Release Date: March 10, 2004
===========================================================================
PATCH HISTORY
1.1 Running a report produces a set of errors and no report. Seen in a 4.0
upgrade/install over of a 3.1 installation that includes application of
latest 3.1 patch file.
2.1 Fixed bug where SMTP server would unexpectedly terminate when handling
IPv6 "AAAA" record type.
2.2 Fixed - Some global options did not get saved properly in unchecked state.
2.3 Fixed - GPF occured When user selects text containing characters with
ASCII code above 128.
2.4 Fixed - UI crashes when Archive or Stamp rule dialog is active, none
of controls have focus and user presses 'b' key.
2.5 Fixed - UI or scheduled task crashes on exit if there was an unsuccessfull
attempt to compact a database.
2.6 Improved Message Folders performance.
2.7 Added safety checks in Bayesian training.
2.8 Added step to compact the database in Recalculate Probabilities task.
2.9 Stamping outbound messages is not performed when distributed training
is enabled.
2.10 Fixed - Bayesian statistics report displayed "0 Unique Spam Words" in
certain situations.
2.11 Fixed - Removed word "reverse" from description generated by the
"From domain does not have a DNS MX or A record".
2.12   is converted to space when stripping HTML.
2.13 Modified - Bayesian algorithm for final probability for keyword that is
present more than once.
2.14 Fixed - UI GPF when BlackList rejection message is more than 255 characters
long.
2.15 Fixed - New user added to a new report would not appear on reload.
2.16 Fixed - GPF when adding a new user and cancelling the dialog.
2.17 Fixed - Find function would not find Uncategorized messages
even if "Any Category" is checked.
2.18 Fixed - GPF when scrolling fast in a message folder display.
3.1 Fixed - IF "localhost" or "127.0.0.1" was used as a host name in the console,
established connection caused UI performance degradation.
3.2 Fixed - Bayesian training failed with "Unknown error" when connected from a
remote console or if either "localhost" or "127.0.0.1" was used as the host name.
3.3 Fixed - When Log or Folders database reached size limit (1GB),
logging/adding messages would not stop.
3.4 Fixed - SQL server version of the Folders database would not accept
new records.
3.5 Fixed - SMTP Server would stop when trying to send e-mail while being
blacklisted and message was over 256 bytes long.
3.6 Fixed - SMTP Server would stop when SQL server version of Folders
database failed to find any messages.
3.7 Fixed - SMTP Server would crash when trying to process certain messages.
3.8 Improved - Processing of messages attached to messages.
===========================================================================
Please review this document carefully before installing or running DynaComm
i:mail. These notes contain last-minute release information that may affect
your use of the product.

Contents
This document contains the following sections:
1.0 Upgrade/Install Over Warning!
2.0 System Requirements
3.0 Notes on DynaComm i:mail
4.0 Implemented or Fixed
5.0 Technical Support
=========================================================================
1.0 Upgrade/Install Over Warning! Read this BEFORE upgrading to
DynaComm i:mail 4.0

1.1 Upgrading from DynaComm i:mail 3.0
If you attempt to install DynaComm 4.0 over DynaComm i:mail 3.0, an error
message displays and the install over does not proceed. To upgrade from
DynaComm i:mail 3.0, you must first install-over with DynaComm i:mail 3.1.
A copy of DynaComm i:mail is stored on the installation media in the
DynaComm imail 31 folder.

DynaComm i:mail 3.1 File Type topic structures and handling are
significantly changed. In previous versions of DynaComm i:mail
(version 3.0 and earlier), file identification is based on file name
extension. In DynaComm i:mail 3.1, file identification has changed due to
implementation of two major changes:
a. A file type includes a file signature (where known) in addition to
file extension. File identification uses the file signature first and then
the file extension. This prevents bypass of a filtering rule by renaming
a file.
b. To accommodate the change described in "a" above, File Type definitions
are restructured to include additional file type groups which include over
180 file type definitions. This resulted in rearrangement of file type
extensions in file type groups such that file extensions in file type
groups are not the same as they were in the previous release(s).

Before starting the upgrade process, do the following:
a. Review and note any custom File Type Groups and file extensions
for each. These will have to be recreated.
b. Review DynaComm i:mail 3.1 default settings with your rules using
custom settings on the Attachment tab (Rule dialog) and reports using
custom settings on the File Type tab (Report dialog). These will have
to be reset.

Due to the changes described above and the unlimited variations of the use
of file types in rules and reports, special procedures exist for an
upgrade installation from DynaComm 3.0 to version 3.1. These install
procedures include:
* Active rules using custom selections for File Types are preserved
but made inactive.
* Reports with custom selections for File Types are changed to use the 
efault setting of "All" file types.
* A text file, "imail30rules.txt", is created and stored in the
DynaComm i:mail install directory. This file details all active rules and
reports using customized File Types.
* The "imail30rules.txt" file displays at the end of the upgrade to inform
you of existing rules and reports using custom file type settings that
must be adjusted before starting DynaComm i:mail 3.1. This file does not
appear if no rules or reports using custom file type settings are found.

To adjust affected rules and reports, do the following before starting
DynaComm i:mail 3.1:
1. Recreate custom File Type groups and include the file types that were
in use in DynaComm i:mail 3.0.
2. For each affected rule, open the Rule dialog, click the Attachment tab
and reapply file type settings. At the top of the dialog, select "Active"
to reactivate the rule.
3. For each affected report, open the Report dialog, click the File Type
tab an reapply file type settings.
4. Save the updates.
5. Start DynaComm i:mail SMTP server.

In some cases, your upgrade procedures may be as simple as reselecting
the File Type group and reactivating the rule. Check to verify that the
file types in the new group match the old group. In other cases you may
have to select multiple File Type groups to achieve the same results
produced in DynaComm i:mail 3.0.


1.2 Upgrading from DynaComm i:mail 3.1
1.2.1 To ensure successful implementation of the Bayesian Analyzer,
refer to the DynaComm i:mail Online Reference (Help) and the DynaComm
i:mail Administrator Guide for complete information on the requirements
for installing, enabling, training and using the Analyzer.

1.2.2 If you have archived files, you must run the Rebuild folders function
immediately after installation to be able to see the files through
the Message Folders topic window. Rebuild is initiated with the Rebuild
button in the Message Folders topic window. Depending on the number of
archived messages, Rebuild can be a resource intensive process. Removal
of selected or all messages may be considered to reduce resource requirements.

1.3 Administrative Database Upgrade (FilterAdmin)
If the FilterAdmin.mdb database has been moved from the default
installation location, special procedures are required for upgrading.
These include:
a. Before performing the upgrade installation, copy the database to the
default location (Program Files\FutureSoft\DynaComm imail\) and change the
System DSN pointer for the database through the Control Panel.
b. Perform the installation.
c. After installation, the database can be moved/copied to the custom
location and the System DSN pointer modified to point to the new location.

=========================================================================
2.0 System Requirements

2.1 All Components on One System 
2.1.1 With no Bayesian Distributed Trainer installed
Software:
* Microsoft Windows NT 4.0 (SP6 or higher), or
Microsoft Windows 2000 (SP2 or higher), or
Microsoft Windows XP Pro (SP1 or higher), or
Microsoft Windows 2003 Server

* Microsoft Internet Explorer 5.01 (or higher)

Hardware:
* 500 users
- 1.0 GHZ or faster processor
- 512 MB total RAM for system with 1 CPU
- 256 MB RAM for each additional CPU
- 1 GB free hard drive space
- CD-ROM drive

* 5000 users
- 1.0 GHZ or faster processor
- 512 MB total RAM for system with 1 CPU
- 256 MB RAM for each additional CPU
- 2 GB free hard drive space
- CD-ROM drive

2.1.2 With the Bayesian Distributed Trainer installed
Software:
* Microsoft Windows 2000 (SP2 or higher) with IIS 5.0, or
Microsoft Windows XP Pro (SP1 or higher) with IIS 5.1, or
Microsoft Windows 2003 Server with IIS 6.0

* Microsoft Internet Explorer 5.01 (or higher)

* Microsoft .NET Framework 1.1 (included on installation media or from
the Microsoft web site)

Hardware:
* 500 users
- 1.0 GHZ or faster processor
- 512 MB total RAM for system with 1 CPU
- 256 MB RAM for each additional CPU
- 1 GB free hard drive space
- CD-ROM drive

* 5000 users
- 1.0 GHZ or faster processor
- 512 MB total RAM for system with 1 CPU
- 256 MB RAM for each additional CPU
- 2 GB free hard drive space
- CD-ROM drive

2.2 Console Only 
Software:
* Microsoft Windows 98, or
Microsoft Windows NT 4.0 (SP6 or higher), or
Microsoft Windows 2000 (SP2 or higher), or
Microsoft Windows XP Pro (SP1 or higher), or
Microsoft Windows 2003 Server

* Microsoft Internet Explorer 5.01 (or higher)

Hardware:
* PII 300 or faster processor
* 1 GB free hard drive space
* 128 MB total RAM 
* CD-ROM drive

2.3 SMTP Server Only
2.3.1 With no Bayesian Distributed Trainer installed
Software:
* Microsoft Windows NT 4.0 (SP6 or higher), or
Microsoft Windows 2000 (SP2 or higher), or
Microsoft Windows XP Pro (SP1 or higher), or
Microsoft Windows 2003 Server

* Microsoft Internet Explorer 5.01 (or higher)

Hardware
* 500 users
- 1.0 GHZ or faster processor
- 512 MB total RAM
- 1 GB free hard drive space
- CD-ROM drive

* 5000 users
- 1.0 GHZ or faster processor
- 512 MB total RAM
- 2 GB free hard drive space
- CD-ROM drive

2.3.2 With the Bayesian Distributed Trainer installed
Software:
* Microsoft Windows 2000 (SP2 or higher) with IIS 5.0, or
Microsoft Windows XP Pro (SP1 or higher) with IIS 5.1, or
Microsoft Windows 2003 Server with IIS 6.0

* Microsoft Internet Explorer 5.01 (or higher)

* Microsoft .NET Framework 1.1 (included on installation media or from
the Microsoft web site)

Hardware
* 500 users
- 1.0 GHZ or faster processor
- 512 MB total RAM for system with 1 CPU
- 256 MB RAM for each additional CPU
- 1 GB free hard drive space
- CD-ROM drive

* 5000 users
- 1.0 GHZ or faster processor
- 512 MB total RAM for system with 1 CPU
- 256 MB RAM for each additional CPU
- 2 GB free hard drive space
- CD-ROM drive

NOTE: DynaComm i:mail Scheduling requires mstask.exe which is available
with Internet Explorer 5.01 (or higher), Windows 2000 or Windows XP
Professional.

=========================================================================
3.0 Notes on DynaComm i:mail
3.1 What's New in DynaComm i:mail 4.0.0.0
* Implementation of Bayesian filtering
- New topic provides access to options to enable use of Bayesian filter,
options to perform actions on messages identified through filtering
processes, Statistics report, options to enable training of Bayesian
Analyzer with user input.
- New scheduled task allows for recalculation of Bayesian keyword
probabilities.

* Implementation of Microsoft Active Directory support
- Import user mail addresses and organization unit structure from Active
Directory.
- Provides for immediate processing of requests by user name.

* Implementation of function to reset File Type & Keyword Database values
to defaults.

* Enhanced User management
- User address can be added from Message Viewer dialog.
- Users can be removed from individual or all user groups with one command.

* Enhanced File Type management
- All file types within each group are displayed in descending alpha order.

* Expanded Configuration capabilities
- ESMTP authentication available for outbound mail connection
- SMTP session logging

* Expanded Known Spam Techniques options
- FROM domain does not have a DNS, MX or A record
- Number of HTML comments exceeds: "x" number
- Number of HTML-Encoded Characters exceeds: "x" number
- Sending server does not have Reverse DNS
- Reverse DNS domain does not match FROM domain
- Message has no hops
- Missing X-Mailer Header (machine generated message)

* Keyword processing enhancements (Categories topic)
- Allow complex expressions with keyword functions and operators
- Keyword processing with zero (0) weight
- Additional special character processing (UNICODE and Hexidecimal)
- Nested FOLLOWBY operator function implemented
- New operator: SET

* Rule processing enhancements (Block/Allow and Archive rules)
- Attachments can include wildcard characters in the file name
- HTML stripping preserves line breaks
- Improved handling of HTML message through decoding special HTML characters

* Message Folders management enhancements
- Folders pane: Rebuild Folders function, scrolling refresh improvements
- Messages pane: Filter messages by date, Bayesian Value field added, Train function for Bayesian Analyzer
- Find dialog: Bayesian Range selection, Extended Message Attributes (6 selectable options), Found Messages list includes message Bayesian Value

* Implementation of global options
- Process mail attachments
- Determine file types by extension

* Expanded Blacklist configuration 
- New action option: "Accept and categorize the message as"

* SMTP Real Time Monitor enhancement
- Displays blocked messages in red

* SoBig.F virus implementation through registry entry

* Reporting enhancements
- New report: Bayesian Classification
- Save report to file server or FTP site
- Top 10 reports show top 25 in data tables
- Full report type name shown on Type tab in Report dialog
- Default time changed to Week-to-Date
- "Blacklisted Traffic" changed to "Rejected Connection" in report titles

3.2 General
3.2.1 DynaComm i:mail SMTP Server in a De-militarized Zone (DMZ).
To connect a remote DynaComm i:mail Console to a DynaComm i:mail SMTP Server
in a DMZ follow the Microsoft configuration instructions found at:
http://www.microsoft.com/com/wpaper/dcomfw.asp
See the DynaComm i:mail Online Reference for a description and examples of DMZ 
configurations.
3.2.2 DynaComm i:mail on a Windows XP Professional system
When a Windows XP Professional Machine is not part of a domain, the simple
file sharing model is fundamentally different than other versions of windows.
This means that an incoming connection, even if a user name and password
is provided, is forced to use the Guest account and has only Guest level
access to the share.
To allow connection a DynaComm i:mail Remote Console to a DynaComm i:mail
SMTP Server running on a Windows XP Professional machine that is not
part of the domain, the following steps must be performed on the
Windows XP machine:
Step 1 Disable the "use simple file sharing" option by:
a On the taskbar, right-click Start and select Explore.
b On the Tools menu, select Folder Options.
c In the Folder Options dialog, click the View tab.
d Clear Use simple file sharing (Recommended).
e In the Folder Options dialog, click OK.
f Close Explorer.
Step 2 Disable the Internet Connection Firewall by:
a On the Start menu, select Control Panel.
b In Control Panel, double-click Network Connections.
c In Network Connections, select Local Area Connection.
d In the Local Area Connection Status dialog on the General tab, click Properties.
e In the Local Area Connection Properties dialog, select the Advanced tab.
f Clear Protect my computer and network by limiting or preventing access to this computer 
from the Internet.
g Click OK.
h Close Local Area Connection Status dialog.
i Close the Network Connections dialog.
j Close Explorer.
Step 3 Re-boot the machine.

3.3 Installation/Setup/Uninstall
3.3.1 Removing Scheduled Jobs.
After removing DynaComm i:mail, scheduled jobs must be removed from the
Windows SCHEDULED TASKS area. These jobs/tasks are identified by the
naming convention, ndynacomm imail, where the "n" is a numeric value
(i.e. 1dynacomm imail).
3.3.3 Upgrading Versions
When upgrading from DynaComm i:mail 3.0 to 3.1, do not perform an
Uninstall. An uninstall removes the FilterLog file and the Upgrade/Install
over fails. Rather, insert the DynaComm i:mail 3.1 CD and complete each
Setup Program screen prompts. You are prompted to confirm saving the
current FilterLog file. Respond "Yes" to allow the install program to
place current FilterLog data into the new database structures. If you
respond "No", the current FilterLog file is removed and a new, empty
database is put into place.

3.4 Remote console
3.4.1 Remote Console
If you logon to a remote console with an account that is not established on
the SMTP Server component system, the Message Find function (Message Folders
topic window) and the Real Time Monitor function (SMTP Service topic window)
are disabled.

3.5 Utilities
3.5.1 Database Maintenance Tool
When switching the FilterLog database to an SQL Server database, you have
the option of creating an empty SQL database or of using the existing data
in the FilterLog database. If you choose to use existing FilterLog data,
the SMTP Server is stopped during the copy process. Depending on the amount
of copied data, this may be a lengthy process resulting in a significant time
that e-mail filtering processes are not active. Therefore, switching the
database immediately after initial installation of the product will avoid
this situation.

3.6 Documentation Library
The DynaComm i:mail reference library consists of printed and electronic 
material, which includes:

DynaComm i:mail Administrator Guide (AGimail.pdf)
DynaComm i:mail Online Reference (imappshell.hlp and imappshell.cnt files)
DynaComm i:mail Database Tool (dbtool.hlp and dbtool.cnt files)
DynaComm i:series Quick-Start (QSiseries.pdf)
Readme (readme.txt file)

These items are provided on the installation CD-ROM in the /docs folder.
All are updated as various issues are reported and resolved. A copy of
Adobe Acrobat Reader is placed under /supporting applications/adobe for
access and use of the PDF file listed above. Or, access www.adobe.com to
download the Adobe Acrobat Reader to your system. The DynaComm i:mail
Online Reference is accessed through the Help Topics selection on the
Help menu. Dialog level context-sensitive help is accessed with the F1 key.

The most current copy of electronic media is available for download 24 hours
a day, 7 days a week from the FutureSoft web site at:
http://www.dciseries.com/products/imail/document.asp.

Printed documentation can be obtained by contacting your FutureSoft
Account Manager at 1.800.989.8908.

Send questions and comments about the documentation to: docs@futuresoft.com

=========================================================================
4.0 Updated or Fixed

#11822 - Implemented:  Ability to strip attachment from Administrative
Notification.
#11849 - Implemented:  Ability to RDNS connecting SMTP Servers in "Known
Spam Techniques".
#11853 - Implemented:  "HELO Domain" configuration option provides method
to use correct DNS name to avoid reverse DNS lookup problems.
#11883 - Implemented:  Ability to exclude scanning of attachments.
#12106 - Fixed:  Email w/Chinese character set is not being recognized.
#12110 - Implemented: Preserve message formatting when stripping HTML.
#12120 - Fixed:  Change to Port Number of existing Local Domain entry not
allowed.
#12122 - Fixed:  Reporting fails in DynaComm i:mail remote console.
#12320 - Fixed:  Block rule not blocking files with attachments identified
by wildcards.
#12395 - Fixed:  Unable to process Mail Bomb from legitimate SMTP Server.
#12401 - Fixed:  New Users added because of Mail re-Route to outside
Addresses.
#12432 - Implemented:  Ability to configure "From" Display Address of
Delivery Status Notifications; changed "From" address in bounce messages 
to the Administrator's e-mail address.
#12436 - Implemented:  Addition of a Total within "Standard Details Report".
#12442 - Fixed:  Scheduled jobs displayed incorrectly in console.
#12451 - Fixed:  Unable to delete domains within the Domain box in the 
rules.
#12452 - Fixed:  Message processing issue with malformed message from old
mail client.
#12468 - Fixed:  In some situations, sysadmin returns a "Host Not Found." 
essage when the host domain is valid.
#12471 - Fixed:  Un-optimized Log Processing causes CPU to run at 100%.
#12499 - Fixed:  Stripping HTML ignores capitalization and converts
message text to lower case.
#12560 - Fixed:  Console in "Read-Only" mode allows access to certain
functions in the (Message) Find dialog.
#12569 - Fixed:  Apostrophes are being stripped from e-mail addresses,
making the message undeliverable.
#12602 - Implemented:  Ability for DynaComm i:mail to perform a reverse
DNS lookup.

=========================================================================
5.0 Technical Support
For prompt and effective service, please be sure to include your company
name, address, any applicable phone (or fax) numbers, name and version number
of the product for which you need support. The following technical support 
ptions are available for DynaComm i:mail:

5.1 E-mail
North America, South America, Asia and Pacific Rim: support@futuresoft.com
United Kingdom, Europe, Africa and Middle East: support@futuresoftuk.com
Send files via FTP to ftp.futuresoft.com.

5.2 Telephone
North America, South America, Asia and Pacific Rim: Monday through Friday
between 08:00 and 17:00 Central Standard Time (CST) 1.281.588.6868
United Kingdom, Europe, Africa and Middle East: Monday through Friday
between 09:00 and 17:30 Greenwich Mean Time (GMT) +44 (0) 1260 292219

5.3 Fax
North America, South America, Asia and Pacific Rim: 1.281.496.1090.
United Kingdom, Europe, Africa and Middle East: +44 (0) 1260 292224

5.4 Ground Mail
We welcome your comments and suggestions about DynaComm i:mail.
Send them to us at:
FutureSoft, Inc.
12012 Wickchester Lane, Suite 600
Houston, Texas 77079

Copyright 2004 FutureSoft, Inc.
readme.txt DynaComm i:mail 4000 March 10 2004 sac