Internet Exchange for cc:Mail Version 3.14
Release Notes
(5 May 2000)

This is the release notes for Version 3.14 of Internet Exchange for cc:Mail. In successive versions, this file will contain a log of bug fixes, enhancements and other changes. The new format of the release notes will date it chronologically, with the latest one coming first.

Thank you for using Internet Exchange for cc:Mail, Version 3.XX, IMA's industry-leading Gateway/MTA for Lotus cc:Mail. Among Internet Exchange 3’s many features are:

Complete 32-bit Architecture
Internet Exchange Version 3.XX is a complete 32-bit multi-threaded gateway/MTA. This not only improves the speed of performance, but also makes better use of Windows NT and the Windows 95 or Windows 98 operating systems.

Windows NT Service Application
Operating as a native Windows NT Service Application allows Internet Exchange to start in the background automatically without the need to manually log onto the system (this is a feature supported only in Windows NT mode). The advantages of operating as a Windows NT Service include added security and automatic startup, thereby allowing the system administrator to reboot the system remotely without having to worry about starting Internet Exchange again.

POP3 Server Support
Internet Exchange now supports remote access via POP3 into the cc:Mail post office. This feature is configured using the MTA control options.

Remote Web Based Administration
Internet Exchange now offers a browser-based remote control with diverse functions: a user can access the gateway-MTA securely via the World Wide Web to monitor the operation of Internet Exchange, to modify the gateway configuration, to view logfiles and system resources, to shut down or start up the gateway or some of its individual components, and to schedule shut-down or start-up.

The remote control is simple to use and explicit in functionality to the point that a new user could utilize it fully on the first attempt.

ESMTP Support
Version 3.1X adds support for ESMTP (SMTP Service Extensions). In addition to the ETRN extension for remote queue startup that has previously supported, Version 3.1X now supports the message size extension, allowing communicating ESMTP sessions to determine prior to a message transmission if the remote site will accept a message based upon size. This results in significant bandwidth savings for oversized messages.

Simple Mailing List Management
The new forwarding mechanism also allows for the creation of mail aliases, where messages can be automatically redirected to multiple recipients.

Anti-Spam Engine
The anti-SPAM category of options are designed to control the reception of unsolicited and unwanted SPAM mail messages; an administrator may decide to automatically reject mail coming from any number of definable users, domains or IP address ranges. Internet Exchange is capable of recognizing a spammer's address in different portions of the message headers, and once identified the offending message is handled by a SPAM mail processor in a manner previously chosen by the administrator. Version 3.1 also adds controls that allow for specifying what hosts or networks can relay mail through Internet Exchange, providing a means for preventing spamming organizations from using Internet Exchange as a relay for their junk mail.

Fail Safe Implementation
Fail safe implementation allows multiple copies of the Internet Exchange to be used by the same post office. There is no limit on the number of MTA's that can be run on a single cc:Mail post office. The usefulness of such a feature becomes apparent when one MTA is delivering mail very slowly or not at all: a second or third MTA will send mail instead of a terminated MTA or in simultaneous conjunction with one that is too impaired to operate efficiently on its own.

RAS Support
RAS is the Remote Access Server for Windows which is actively supported on all win32 platforms. This is a useful feature not just for dial-up issues, but for any Windows supported dial-up mechanism, be it a leased line that directly connects to a Windows system, a dial-up connection, an ISDN connection, possibly even a TAPI application that complies with the RAS API (such as video conferencing), or X.25. RAS is fully integrated into Internet Exchange, meaning that dial-up support is available in any language on Windows 95, NT 3.5x, and NT 4.0. Support for dial-up scripting is also included.

Dialup Scheduler
Internet Exchange's user friendliness is enhanced in Version 3.1 by the addition of the new Dialup Scheduler with embedded Active ETRN support, particularly in cases where it is impractical to have permanent Internet connections. The Dialup Scheduler provides the gateway administrator with a graphical user interface (GUI) for configuring dialup schedules and other RAS-related profiles.

Active ETRN Support
The new Active ETRN support, which is integrated into the Dialup Scheduler, allows the administrator to specify multiple remote mail servers that may be holding mail for the site. Upon the establishment of a dialup connection, Internet Exchange will send ETRN requests to each of these remote servers indicating its ability to receive email, regardless of if there is email to send to those sites. This new Active ETRN capability significantly enhances Internet Exchange's ability to efficiently receive email from one or more remote servers as compared with other more traditional non-active implementations.

New Workgroup Edition Versions
Internet Exchange Version 3.1X introduces the Workgroup-250 and Workgroup-400 Editions; these are 250- and 400-user licensed versions of Internet Exchange. In addition, the Enterprise Edition and the three Workgroup Editions now share a common set of programs, and are licensed via the application of different software licenses, making upgrading from any of the Workgroup Editions as simple as applying for a new key.

Gateway/MTA Migration Strategy
There have been numerous requests to feature a migration tool that permits users on a cc:Mail platform with SMTP connectivity to gradually switch to Lotus Notes or to Microsoft Exchange (and vice versa) while retaining the same email addresses. This migration strategy allows mail to be sent and transferred among cc:Mail, Lotus Notes and Microsoft Exchange environments; the mail then appears to be of a format native to its destination.

The Migration Strategy has the following capabilities:

    • Change and modify outgoing mail headers automatically
    • Permit forwarding of individual user addresses to any Internet sub-domain
    • Permit forwarding of entire sub-domains to any other Internet sub-domain
    • Replicate email sent to any other MTA

Real Time Log Analyzer / Standard Logfile Format
The format of the Internet Exchange logfile has been standardized. A new API based upon this format is now documented and DLL's supplied for developers that wish easy access to logfile information. In addition, the new Real Time Log Analyzer keeps track of key gateway information, such as general gateway statistics, anti-spam statistics, and security and permission statistics for real-time display.

RFC-1522 Support
The added support for RFC-1522 allows for the inclusion of non-ASCII characters in Internet mail headers.

Ability to Set a Maximum Message Size Per Domain
This feature allows message size control on a domain basis vs. one global setting.

Configure Users Has Search Facility
A search facility allows a search to be conducted in a user database; this is particularly useful if the user database in the MTA is very large.

Dynamic RBA Rules Compilation
RBA Rules Compilation is a feature that enables users to compile an entire post office address database automatically. For performance reasons, RBA is launched as a separate utility to prevent it from blocking SYSMAN when it compiles large databases. The schedule of compilation runs on a minimum granularity of one hour; once a compilation has started, it will not be possible to start another until the first one has been completed.


Windows 95 Updates from Microsoft
It is necessary for the proper operation of Internet Exchange that the Service Pack 1 and Kernel Updates be applied. They can be obtained over the World Wide Web at:

Windows 95 Service Packs (Microsoft)

Windows 95 Kernel32 Update


Web Server Requirements

Remote Control and WEB Servers
Internet Exchange for cc:Mail V3.1X requires a WEB Server running on the same PC. Internet Exchange has been designed to work with a number of WEB servers. Support is limited to WEB Site Pro V2.0 as we have found it be a robust product that can provide all the security requirements that our users may need.

You may try WEB Site Pro V2.0 free of charge for 30 days. Should you decide to buy it please contact IMA directly. Purchasing from IMA will ensure that you receive Internet Exchange specific support on configuring WEB Site.

Please contact if you would like to purchase WEB Site Pro v2.0

Getting and Installing WEB Site V2.0 Pro - 30 day Evaluation
To get WEB Site Professional please visit URL:

Follow the registration and downloading procedures to download a 17MB compressed file, that contains various modules that make up WEB Site Pro. We only require the basic WEB Server functionality.

Once you have downloaded the 17MB file, extract the files by executing the self-extracting ZIP file. The basic web site functionality needed by Internet Exchange is found in the WEB Site Pro V2.0 4.1MB file called WS2PEVAL.EXE. Simply run this program and follow the installation procedure to install WEB Site.

Once you have WEB Site installed on your system, run Internet Exchanges' Remote Control Installer. This program will customize WEB Site Pro to work with Internet Exchange.

WEB Site Pro V2.0 has a full range of security features including SSL which can provide strong authentication, traffic integrity and confidentiality.

Note: The URL for the Gateway is:


Version 3.14 (5 May 2000)


MIME Text Body Handling
Currently, if the MIME body is TEXT/XXXX, it is always inserted as a NOTE_PART by CCIN. Starting with the new Internet Exchange 3.14, if any TEXT/XXXX is declared as an "attachment" in the content-disposition header, the MIME body-part will be inserted as a file attachment.

Bug Fixes

Date/Time Pattern and Y2K issues.
Using Internet Exchange 3.13, the date time filter can only accept a 2 or 4 digit year field in the date/time pattern filter, for example: hh:mm hh:mm

During the start of the year 2000, some ccMail users have been encountering problems when a single '0' would appear as the year 2000 in their filename attachment. This issue has been fixed starting from version 3.14 onwards by allowing the user to define a date/time pattern filter such as: hh:mm
to solve this case.

IPv6 Support
Prior to Internet Exchange 3.14, the DNS resolver cannot handle IPv6 DNS records and would result in being unable to resolve domains containing IPv6 information. This problem is now fixed in version 3.14.

Some Messages Causes the SMTPD Process to Crash
Prior to Internet Exchange 3.14, if the incoming message contains a line with more than 1,024 characters, this would cause the SMTPD module to crash. This is now fixed in version 3.14.

POP3D Exception Error
Prior to Internet Exchange 3.14, the POP3D would crash under some racing condition. This problem has also been fixed in version 3.14.

Mime-Version Header Being Added in Re-routed Message
When CCIN processes a non-local message, the mail will be re-routed to the output queue. If the message is a non-MIME, a Mime-version header is inappropriately inserted in the message. If the message contains a UUEncode file, the mail agent will fail to handle the attachment. This issue is now fixed in version 3.14.


Version 3.13 (13 August 1999)


Dial-up Scheduler now connects to NT RAS server without RAS scripting
To automatically launch the Dial-up Scheduler in Internet Exchange 3.12, RAS scripts are required to replace the manual procedure of entering connectivity and access information, such as username and password. In Version 3.13, connectivity and access information is obtained from the pre-configured RAS profile so it can be used during the authentication session, enabling the Dial-up Scheduler to connect to a RAS server running on a Windows NT machine even without RAS scripts. However, for other types of RAS servers, RAS scripts are still required.

Support for dot "." as a date separator in the attachments processed by CCOUT
In Internet Exchange 3.12, if CCOUT encounters a date/time stamp, it adds this date/time stamp to the attachment name, e.g.

    Progress report.doc 12/12/99 13:03

The CCOUT module shipped with Internet Exchange 3.12 and older versions applied the following logic to remove the date/time stamp:

    scan for the last dot "." from right to left, if dot "." is found, remove all characters until the last space before the dot.

Using the above mentioned logic, the filename would then be truncated as:

    Progress report.doc

Once a file name has been derived, CCOUT then maps the extension with the correct MIME type.

The above mentioned logic works perfectly okay except when the date/time stamp is separated by a dot "." e.g.

    Progress report.doc 12.12.99 13:03

If the same logic is applied to the above mentioned file name, CCOUT will truncate the file name as:

    Progress report.doc 12.12.99

In this case, only the time field is removed. Thus, CCOUT is unable to map the correct MIME headers and problems may be encontered in opening the attachment. Starting from Internet Exchange 3.13, appropriate filters have been implemented to solve this problem. These filters are classified as options which must be added to the IMA.INI file.

In order to activate the filtering capability of Internet Exchange 3.13 and truncate the filenames of attachments correctly, the following line needs to be added under the [option] section in the IMA.INI file.


Now, under the [DateTimePattern] section, the filters are defined as follows:

    Pattern1=dd.m.yy h:m AM
    Pattern2=dd.m.yy h:m PM

In case of a 12-hour notation, i.e. considering AM and PM, at least two filters must be defined in the time field, while in the case of a 24-hour notation, only one date pattern filter is needed. Once these filters are applied, the date/time stamp will be removed from the attachments.

Following are the keywords that can be used to define the filters.

Time filter:

    'd', 'dd', 'm', 'mm', 'mmm', 'yy', 'yyyy'

    'd': 1-31
    'dd': 01-31
    'm': 1-12
    'mm': 01-12
    'mmm': Jan,..Dec
    'yy': 00-99
    'yyyy': 4-digit year field.

Time field:

    'h','hh', 'm', 'mm', 's', 'ss'

    'h': 0-23
    'hh': 00-23 (or 00-12 if it is not a 24-hour notation)
    'm': 0-59
    'mm': 00-59
    's': 0-59
    'ss': 00-59

Note: In the above the separator is not only limited to "." but all characters with the exception of "H", "M", "S", and "Y".


CCIN crashes due to "Begin" bug
In Internet Exchange 3.12, when a non-MIME message contains the word Begin (case insensitive) in the message body, it causes an exception error in CCIN. This has been fixed in Version 3.13.

CCIN crashes due to malformatted RFC-822 header address (parser problem)
In Internet Exchange 3.12, if the RFC-822 message header contains a malformatted header address, CCIN is likely to crash and the message will remain in the system without being delivered to its intended recipients. This has been fixed in Version 3.13.

Forwarding address lookup is now case insensitive
In Version 3.12, forwarding address lookup for CCIN is case sensitive. Thus, if an address is specified in the message header in lower case, and it is entered in upper case in the address book, Internet Exchange will be unable to find a match and the message will not be sent to the intended recipient. This has been fixed in version 3.13. In Internet Exchange 3.13, the DBUPDATE.exe program converts USERFWD.BTR from case sensitive to case insensitive. This conversion is carried out in the background during the installation process.

SMTPD exception error
In Version 3.12, SMTPD issues an exception error when the RCPT TO address is longer than 255 characters. This has been fixed in Internet Exchange 3.13, Now if SMTPD encounters an address whose length is longer than 255 characters SMTPD will respond with a permanent SMTP error "address too long".


Version 3.12 (05 February 1999)


RFC 1522 decoding in MIME headers support (Support for name and filename parameters in incoming attachments)
To address the problem of incoming attachments losing their content type and content disposition information, Internet Exchange 3.12 now supports RFC 1522 decoding of MIME headers. In case of an incoming attachment with RFC 1522 encoded file name, Internet Exchange is now capable of decoding content type and content disposition information for correct display in the cc:Mail client.

RFC 1522 encoding in MIME headers support (Support for name and filename parameters in outgoing attachments)
To ensure that outgoing attachments conform to RFC 1522 encoding, we have introduced RFC 1522 encoding of MIME headers in Internet Exchange 3.12. With Internet Exchange 3.12 deployed as the Internet gateway, if a file is sent as an attachment from the cc:Mail client to the Internet, the attachment will retain the name and filename parameters. For example, if an attachment with a name "My docum…nt.doc" is sent out to the Internet using Internet Exchange 3.12, it will retain the following name and file name parameters:


Content-type: application/ms-word; name="=US-ASCII?Q?My Document=C9.doc?="

Content-disposition: attachment; filename="=US-ASCII?Q?My Document=C9.doc?="

Support for Japanese characters in Recipient address
Internet Exchange 3.12 running on a Japanese environment now provides support for an address to contain characters such as double quotes in the JIS encoded portion. Following is an example:


Note: The above mentioned ESC denotes ASCII code 27

The double quotes used to give errors, resulting in the message being bounced by SMTPC because of an invalid address. This enhancement eliminates this problem and allows certain characters to be used in the address.

Added a new option [Options]QualifyRecipientHosts=YES/NO
In the previous versions of Internet Exchange 3, if a message was sent to "user@anyhost", it was always appended to the local domain name. In Internet Exchange 3.12, an extra option has been added, which if set to "NO" does not append the local gateway domain name to the address "user@anyhost". Following is the complete description:

If a message is sent to user@anyhost with "QualifyRecipientHosts=NO" in the IMA.INI file, the address of the message will remain as "user@anyhost". Similarly if a message is sent to user@anyhost with "QualifyRecipientHosts=YES" in the IMA.INI file, the message will be sent to "", where "" is your local domain name.

It should be noted, that the sending of non-qualified addresses in this manner, is a direct violation of the SMTP protocol, and its use is strongly discouraged. In addition, as a protocol violation, the receiving SMTP host may elect not to accept messages with non-qualified recipient addresses.

Added the capability to handle unescaped double quotes in Mime headers
CCIN treats incorrectly formatted MIME message as NON-MIME mail, preventing any attachments to the message from being decoded. For example, the following will not be decoded.

Content-type: Application/ms-word; name=""floor plan.doc""

In order for it to be decoded, the second and third double quotes must be escaped by '\' as per RFC822, i.e.

Content-type: Application/ms-word; name="\"floor plan.doc\""

To solve this problem, a new option


has been added. This option's default value is set to YES. When set to NO, CCIN will accept unescaped special character such as double quotes.


Bug Fixes

Long File name with spaces not being recognized in non-Mime uuencoded messages
In Internet Exchange 3, long file names with spaces were not being preserved in non-MIME messages. This problem has been fixed in Internet Exchange 3.12 so that long file names with spaces are correctly preserved in non-MIME messages.

Bug in RFC 1522 encoding routine
In the previous versions of Internet Exchange 3, there was an encoding problem, where an address, say "JO… Wong" <>, became:

=ISO-8859-1?Q?=22JO=C9?= Wong" <>

This essentially converts the first double quote before the 8bit character as part of the encoded string. In Internet Exchange 3.12, the special characters are encoded in compliance with RFC 1522. The correct encoding is:

"=US-ASCII?Q?JO=C9?= Wong" <> (=US-ASCII?Q?JO=C9?= Wong)

Dial-up scheduler bug
In Internet Exchange 3.11 and earlier versions, the following problems occur within the dialup scheduler.

  • Unexpected shutdown
  • Corrupt weekend schedules
  • "OnlyIfMailQueued" bug in the weekend schedules

All of these problems have been fixed in Internet Exchange 3.12.

Problem with carriage return in the address field
Some mail clients split the address in the TO: field into two lines. In the previous versions of Internet Exchange 3, CCIN was not able to process addresses that are broken into two lines. In Internet Exchange 3.12, if CCIN finds an address split into two lines, it will combine them to come up with a single line of standard address, hence making it possible for the address to be displayed in cc:Mail.

Version 3.1 (10 August 1998)


Mail Relay Filtering
The new Mail Filtering controls enable the gateway administrator to stop spammers or any other undesirable source from using the Internet Exchange MTA as a mail relay. By using this tool, the administrator can deny external sources from using using the gateway to propogate spam or junk mail, while at the same time allowing well known hosts (such as local POP3 clients) to relay email.

Version 3.1 adds support for the ESMTP SIZE service extension. By using the Peer Configuration capabilities, the Internet Exchange administrator can specify a global maximum inbound message size to accept, as well as maximum sizes on a peer by peer basis. When communicating with remote ESMTP servers, Internet Exchange will use this information in order to determine when to send or receive large messages.

New Licensing System
Internet Exchange versions prior to 3.1 had two separate distributions - the Workgroup Edition (100 user) and Enterprise Edition (unlimited usage). Version 3.1 combines these two distributions into a single code base, and in addition to the Workgroup-100 Edition adds two new tiers - the Workgroup-250 and Workgroup-400 Editions (250 and 400 user versions). Upgrades from any Workgroup Edition to another Workgroup or Enterprise edition is now handled entirely through license keys.

Improved Y2K Date Handling
To address the millennium bug issue, Internet Exchange 3.1 features improved Y2K compliance. While versions since 2.11 have featured Y2K compliance, Version 3.1 adds to this the ability to detect and compensate for improper date information provided in message headers received from external systems.

Standard Logfile Formatting With API and DLL Support
The format for logfile entries starting with Version 3.1 has been standardized, and a new IMA Logfile API is provided with the corresponding parser DLL's being made available.

Real Time Log Analyzer
A new Log Console application is provided with Version 3.1 which allows administrators to view key gateway statistics in real time.

Dialup Scheduler
Versions of Internet Exchange prior to 3.1 in order to facilitate the establishment of dialup connections had to shut the gateway down and then restart, using external schedulers such as IMACRON. Version 3.1 has incorporated dialup scheduling internal to Internet Exchange, removing the need to employ external schedulers and to stop/restart the gateway. The Dialup Scheduler works in conjunction with RAS.

Active ETRN Support
This option allows the administrator to enable sending ETRN requests, which specify the FQDN of the gateway, to all remote SMTP servers that may be holding queued email during the dialup connection establishment. The sending of these requests can be to multiple remote servers, and regardless of wether outbound mail is destined for the remote server.

New RFC-1522 Decoding Option
A new option has been added to force RFC-1522 decoding regardless of the character set specified in the encoding string:


The default value is NO.

Bug Fixes

Long Filename Handling in CCOUT
In Versions 3.0/3.01, any attachment picked up by CCOUT that contained a SPACE in the filename was truncated if the ForceDosFileName option was equal to YES. This bug has been fixed in Version 3.1.

The original usage of the above option was to truncate the date and time stamp in the attachment filename. It was found that with some VIM implementations, esepcially Japanese VIM, the attachment's filename returned by VIM usually contained a date/time stamp at the end. Versions 2.12, 3.0, and 3.01 used this option to remove the date/time stamp from the filename. The algorithm used was to truncate after the first space found. This algorithm has been modified for Version 3.1 and truncation will occur after the first space after the filename extension.

CCIN Incorrectly Counts Total Number of Attachments
For messages that are received that are a nested multipart/mixed and message/rfc822 type, and the Include MIME header option is enabled, CCIN can miscount the total number of attachments. If an attempt to insert the 21st attachment is made, a VIMSetMessageItem 1/65535 error is generated. This problem has been resolved with Version 3.1.

CCIN GPF After Bouncing Mail With More Than 20 Attachments
After bouncing a message with over 20 attachments, CCIN would free up some global variables, which need to be reused later. When accessed after the free, CCIN would generate a GPF.

CCIN Access Violation When Obtaining Attachment Filename
When dealing with MIME messages with empty bodies, CCIN would sometimes GPF due to improper pointer checking. This has been fixed in Version 3.1.

CCIN Access Violation When Calling The rfc2UTC Function
GPF conditions were generated when the rfc2UTC function call was performed with NULL date string data.

Synchronization of Processes Which Cause Dynamic Conversion Failure
Under heavy system load, various Versions 3.0/3.01 modules can get out of sync resulting in their not releasing control of the SMTPADR.BTR database files prior to Dynamic Conversion resulting in Dynamic Conversion failure. This has been fixed by reworking the underlying interprocess communication between the various Internet Exchange modules.

Synchronization of Processes Which Cause Scheduled RBA Compilation Failure
Under heavy system load, various Versions 3.0/3.01 modules can get out of sync resulting in their not releasing control of the RULEBADR.BTR database files prior to scheduled RBA compilation resulting in RBA compilation failure. This has been fixed by reworking the underlying interprocess communication between the various Internet Exchange modules.

RFC-1522 String Decoding (CCIN)
Under certain conditions, CCIN would add an extra byte when performing RFC-1522 decoding.

POP3D List Command
In Version 3.01, if the POP3D is presented with a LIST command without any parameters, it would return immediately with an "OK" response and no data. It now returns all message numbers and the corresponding message sizes.

VIM GPF Upon Loss Of Network Connection
GPF's that were triggered through the VIM interface due to a temporary loss of network connection have been fixed. While the problem actually resides in the cc:Mail VIM libraries, Internet Exchange now has added code to trap the exception and retry the connection at a later time.

Version 3.01 (1 April 1998)


Mail relay feature re-enabled (Workgroup edition only)
Internet Exchange for cc:Mail Version 3.0 Workgroup Edition cannot be run as a Mail relay host. This feature has now been re-enabled. SMTPD would check the permissions of receiving mail against all recipients including LOCAL and non-LOCAL recipient addresses during the RCPT TO command which could may cause more than 100 users being present even if there are less than that locally. In Version 3.01, the SMTPD module will only check the permissions of LOCAL addresses thus allowing a Workgroup Edition of Internet Exchange to be used a mail relay host.

If the Internet Exchange gateway is set up as a mail relay host, set the Reject remote recipient option to NO so that mail intended for a non-LOCAL recipient can be forwarded to another host.

Added a new option [Options]ForceMapccMailAddress=YES/[NO]
In version 3.0, CCOUT does not do any address tranlation if it detects that the sender's cc:Mail address is an Internet address, ie, containing the character "@". That causes inconviniences to some sites.

By default, the option is set to be "NO". When the option is set to "YES", all senders from any cc:Mail PO other than Internet PO will be forced to do the address mapping even if it is in Internet address format.

Added a new option [Options]ReplaceCommaWith=;
In previous version of Internet Exchange, when CCIN imports a message with sender Internet address that includes the comma character (",") in the comment part, it would replace the comma (",") with a semicolin (";") so as to aviod causing problem in cc:Mail environment since comma (",") is being used a separator in cc:Mail.

However, semicolin (";") is also a separator in Microsoft Exchange and it has been reported that the behaviour of Internet Exchange causes the message unrepliable to the original Exchange user. This option allows the gateway administrator to specify what the character is to be replaced with. If the option is set to comma (","), the original comma character (",") will be retained. The default value for this option is semicolin (";").

Bug Fixes

POP3 for Workgroup Edition.
Under some rare situations, POP3D will try to open <X>:\smtpadr.btr for 100 users limit checking. Although the file is located in the QUEUE directory, the POP3 server will insist on checking the files from the ROOT directory. This has now been fixed so that the POP3 Server will always look in the /QUEUE/ directory.

CCIN Exception Error at EIP=0040B0C6, Access violation ( c0000005 )
In some situations, a value is assigned to a NULL pointer which will cause the access violation when the "Map Sender Address" option is enabled. This is now fixed in 3.01 so that the CCIN module always checks the value of the NULL pointer.

CCIN Exception Error at EIP=0042891A, Access violation ( c0000005 )
If a line contains more than 1022 characters, the TAB expansion routine will cause an Access violation. Now, the CCIN module allows lines of more than 1022 characters.

Fixed a bug in CCIN where the MIME decoder is case sensitive in scanning
In 3.0, the CCIN module scans the Content-Tranfer-Encoding field to determine the encoding of the attached message. If the meesage was MIME encoded it would check for UUEncoding only in it's lowercase format (uue) and if not found, the CCIN module would discard some uuencoded attachments. In 3.01, CCIN now checks for UUEncoding in both its uppercase (UUE) and lowercase (uue) values when embedded in MIME messages.

Version 3.0 (19 January 1998)


SYSMAN: cc:Mail to Internet Exchange address mapping
For a DB6 PO, if a cc:Mail message is sent via the cc:Mail user alias, Internet Exchange will use the alias name for address mapping. A new option has now been added to the IMA.INI file:


If this option is set to NO, Internet Exchange will use the original cc:Mail user name instead of the cc:Mail alias to do the address mapping.

Note: This is only for a DB6 PO, for a DB8 PO, Internet Exchange for cc:Mail always uses the original cc:Mail user name to do the mapping.

Bug Fixes

RULEBADR: Rules Based Addressing Compilation
Fixed a bug in Rule-based Address Compilation that causes GPF.

SYSMAN: Dynamic Conversion
Fixed a bug that stops gateway operation when dynamic conversion fails.

SMTPD: Logging errors looping
Fixed a bug in SMTPD that causes a loop of logging error messages when the line length exceeds 1000 characters.

POP3 Server: Year 2000 compliance
Fixed the bug for Year 2000 compliance for the POP3 Server.

Version 3.0 Beta2


SYSMAN: Regular screen updates and Display message queue button
Regular screen updates logic is modified to have faster responses. Also when the Display message queue is selected, the queue listing area is forced to update no matter if regular screen updates is on or off.

SYSMAN: Deined access to User / Domain setup page while corresponding conversion utility is running
Now, when convadr.exe is running, the user cannot select the 'User setup page'. This is to avoid user cause any interruption of the conversion process. This is true for domain conversions also.

SYSMAN: Options [Gateway]SendMessageSize / ReceiveMessageSize
This is now replaced by the "default" entry options, Max. inbound size and Max. outbound size under the Peers setup page.

POP Server: Refusing multiple sessions of the same user
This prevents the same user to log in more than one session to avoid potential sychronization problem which may be caused between simultaneous sessions of mail clients (including POP3 and cc:Mail clients).

POP Server: Limited password trials
The number of trials to enter password used to log in a VIM session is limited to three times per session. This serves to discourage hackers.

POP Server: Added Clear Log button
A Clear Log button has been created to clear current log file contents.

POP Server: SendOldLogFile and KeepOldLogFile options
These options determine if the old log files will be sent to the postmaster and also if the old log file will be deleted.

POP Server: Informative message when shutting down
When the POP3 server is told to quit and there are still client threads present, the server thread will wait for the threads to die before termination. In Beta 1, under this situation there is no indication for such situation except in the log file. This is now modified that the Windows text of the application will show a "Waiting for the client threads to terminate" message.

Bug Fixes

CCIN: 7-Bit JIS Header Processing
CCIN would not properly decode 7-bit JIS character in the From header field. This has been fixed.

SMTPC: GPF when receiving 552 after sending out the 'Dot' command
This is now fixed.

SMTPC: 552 Response Handling
SMTPC will now bounce the message immediately when a SMTP error 552 is received during the "DOT" session.

SMTPC: Startup Using RAS
If Automatic RAS Dailup is used, SMTPC will not be started by Sysman until RAS connection is established.

SYSMAN: Application Error when peer domain name starting with a numerical is entered
Entering a peer name with a numeric value, eg. 123.dom or IP addresss is now fixed.

SYSMAN: Log Console Button Distortion
Distortion of button on Log Console when using Large font bug has been fixed.

POP Server: Background deletion handling
In Beta 1 problems may occurr when the POP3 server tries to retrieve a mail which has just been deleted in the background. This is fixed in Beta 2; the server now returns an error upon such a request to retrieve a deleted message.

POP Server: Icon switches to indicate activity level under NT3.51
In Beta 1 the minimized icon doesn’t change corresponding to the connection activity under NT 3.51. It has been modified to reflect the connection activity (as the tray icon does under NT4.0 and Win95).

POP Server: Allows useHostName option
The POP Server now uses the useHostName option in the IMA.INI file when constructing the FQDN for Internet addresses.

POP Server: Improper Construction of Originator Address
The POP3 server in beta 1 would append host domain info to the Internet address mapped in the USER setup menu, no matter if it already contains this information or not. This is fixed so the host domain information will be added only when necessary.

POP Server: Try reverse separator
The POP3 server will try to match the input user name in the database during the USER authentication. The POP3 daemon will reverse the default mapping process when it tries to find a match among the cc:Mail user names. In Beta 1 it only checks for the separator defined in the INI file; now it will try the both possible separators if the TryReverseSeparator option in the IMA.INI file is enabled.

POPServer: TCP Connection close handling
When the client side closes the connection suddenly the server side will handle the close "gracefully".


Version 3.0 Beta1 - Known Problems

LOG CONSOLE - Distortion of buttons on Log console when using Large font
As described...

SYSMAN - Distortion of queue RUN button under Japanese Windows 95
The queue RUN button is distorted when run under Japanese Windows 95

SYSMAN - Loop Detection During Forwarding
Currently, no loop detection has been done when entering forwarding addresses. Any address which causes a mail loop will be trapped later on when reaching the Maximum Trips value defined in "Advanced gateway option".

POP3 Server - Connection Termination
Under certain situations, the POP3 server does not shut down the TCP connection properly and will make remote client unable to reconnect until the timeout period has been reached

POP3 Server - Multiple Logins
The current POP3 server allows multiple login to the same cc:Mail mailbox. This may cause problems when one user is deleting a message while the other try to read the same mail.

POP3 Server - Password Checking
Password checking allows infinite trials. This may be inviting to hackers. It should set a limit of trials per session.

POP3 Server - Unstable Operation During Reclaim (DB8 Only)
If the cc:Mail administrator performs a reclaim operation on the post office while the POP3 user is connected, the VIM reference numbers will change during the reclaim operation. This results in the POP3 server trying to retrieve messages with the old (wrong) VIM reference numbers.


To get a feeling for the power and capabilities of IEMS, simply connect to our public IEMS system to see how IEMS can best benefit your organization. No need to download and install to get a feel for the system. For a more thorough checkout, please download a fully functional copy of IEMS for evaluation on your network.

Customize Your Email Service With
IEMS Programmer Toolkits and Open APIs

IMA provides open interfaces for third party developers to build custom applications, such as gateways, filter modules, archiving agents, mail clients, and more. The Programmers Toolkit contains all the tools necessary. Programming environments supported include C/C++ and PHP.


Copyright © 1993 - 2003 IMA Services Limited