MAILWORKS-OSF DUXDMWE20171 DEC MailWorks for UNIX V1.7A ECO Summary
Copyright (c) Digital Equipment Corporation 1996. All rights reserved.
PRODUCT: DEC MailWorks for UNIX, Version 1.7A
OP/SYS: Digital UNIX[R] V3.0 through V3.2D
SOURCE: Digital Equipment Corporation
ECO INFORMATION:
ECO Kit Name: DUXDMWE20171
ECO Kits Superseded by This ECO Kit: DUXDMWE10171
ECO Kit Approximate Size: DUXDMWE20171.TAR 55020 Blocks
or 28170240 Bytes
System Reboot Necessary: See Release Notes
ECO KIT SUMMARY:
An ECO kit exists for DEC MailWorks for UNIX, V1.7A on Digital UNIX,
V3.0 through V3.2D.
Problems addressed by the DUXDMWE20171 kit:
o The inc command line command would occasionally hang when the
-nointeractive option was used and a large collections of messages was
imported.
o When sending messages through X.400, when a user included a comma
in their personal name, this would cause the MailWorks server to
treat the name as a distribution list; this in turn had undesirable
consequences, including the fact that a reply could go to the
wrong recipient.
o When a message being transferred to the X.400 MTA fails, resulting in
an error in the log file, a stack trace will also be placed in the log
file, to assist the development team in narrowing down the cause of the
problem.
o On a noisy or congested network, sometimes the server would not retrieve
an entire packet of information in one read operation; it now retries
until the entire packet is read.
o After encountering certain kinds of corruption in a message store while
opening a message store through the mcs server, the message store would
not be properly closed, leading to additional corruption.
o mschk has been made more robust, so that it no longer needs to be run twice
to completely recover a corrupt message store.
o If an X.400 message could not be transferred to the MTA, and the clock of
the PC that submitted the message was set later than the clock of the
server, then the server would mistakenly decide that it had retried
sending the message, and generate a non-delivery report. Now, the
server will retry submission of the message. Note that if the PC clock
is ahead or behind of the server clock, the retry period will be
correspondingly shorter or longer than normal. You should attempt to
keep the PC clocks close the server time, and you may want to keep this
in mind when selecting the retry period. Also, the comparison of times
is done using local time as reported by the PC. If the PC and the
server are in different time zones, the DeliveryTimeOut parameter should
be increased accordingly.
o Requests for delivery and receipt notification were not being properly
saved in draft messages when some forms of X.400 addressing were used.
o The lsfd daemon is now being installed with the appropriate privileges
to be able to process all messages in its queue. In previous
releases, under some circumstances, the lsfd daemon would be unable
to process some messages, which would then become "stuck" in the queue.
o The mcs server now responds properly to lost network connections; this
fixes one problem that could cause the mcs server to "spin"
Problems addressed by the DUXDMWE10171 kit:
o A few functional improvements, including:
* The ability to set passwords from MAPI-based clients (this capability
will be available starting with release 1.2 of the MAPI Connector
product.)
* The ability to set most of user's preferences to the values of a
reference or template user's preferences; thus making it easier to
synchronize the preferences of a number of users.
* The default values for several configuration choices have been changed
to values that provide better performance or more appropriate functional
behavior.
Additional details for each of these changes is provided in the release
notes.
o Performance of X.400 mail has been improved by making the process
(x488gsend) that submits messages to MAILbus 400 multithreaded.
o A number of problems have been fixed, including:
* A memory corruption in the mcs server (typically resulting in a seg
fault) has been fixed; this corruption was triggered by a TeamLinks for
Macintosh user sending a message that was previously saved in the
outbox.
* X.121 addresses are now being handled properly for PC clients.
* ReplyRecipients (otherwise known as Reply-to-users) are now being
handled correctly in inbound X.400 messages.
* If the server receives an X.400 delivery or non-delivery report that
was not requested by the originator of the message, the delivery report
is now discarded, rather than being delivered to the originator.
* Fix a memory leak that occurred on the receipt of messages.
* Fix a problem that would cause the message store server to record seg
fault information in the log files when the server is shut down. (Note
that the seg fault occurred after the server was completed with its
message stores, so no damage was done, in spite of the ominous
appearance of the log file.)
* Empty temporary folders created by PC clients during a search
operation are now deleted.
* The inc command is now optionally less verbose when doing an import
of message files: it will no longer prompt for the creation of a new
folder. This will be useful if and when the command is used to import
a large number of messages into the MailWorks message store.
* mschk has been made more robust, so that it will no longer fail when
it encounters some specific unusual problems with a message store.
Note that in rare cases, mschk will finish before it has corrected all
of the problems with a message store. If mschk does not complete with
the messages "Compacting message store...." and "Completed.", then you
should run mschk a second time to correct the remaining problems.
* When a message with an expired date is read before the expiration
date, MailWorks used to send a message to the originator that the
message was deleted without being read - it no longer does.
INSTALLATION NOTES:
As a general precaution, we recommend that you install this ECO after
performing a suitable backup of your system.
Unpack the tar file in a suitable directory. After unpacking the tar
file, you will have a full installation kit for MailWorks for UNIX
including detailed release notes, in the files mailworks_relnot.ps and
mailworks_relnot.txt, located in the /docs directory, and the
Installation Guide in the files mailworks_install.ps and
mailworks_install.txt, also in the /docs directory. We strongly
recommend that you print and read the Release Notes. Pay particular
attention to section 1.6.9 that describes recommendations for tuning the
UNIX kernel - the recommendations in this version of the release notes
have been updated, and if followed will significantly improve the
stability of the MailWorks server.
After adjusting the tuning of the UNIX kernel (if that proves necessary),
you should install the MailWorks server, following the steps described
in the Installation Guide in the ECO kit. Note: the installation
procedure has not changed from release 1.7 or 1.7A, so if you still have
those instructions on paper, you do not need to re-print them.
Otherwise, print the installation guide, and follow the steps detailed
in the document.
[R] UNIX is a registered trademark in the United States and other
countries licensed exclusively through X/Open Company Limited
This patch can be found at any of these sites:
Colorado Site
Georgia Site
Files on this server are as follows:
duxdmwe10171.README
duxdmwe20171.CHKSUM
duxdmwe20171.CVRLET_TXT
duxdmwe20171.tar
|
