

DEC MAILworks for DOS Version 1.2-1 Release Notes
=================================================

August 30, 1994


DEC MAILworks Server Requirements
=================================

o  The DEC MAILworks for DOS V1.2 release is only supported when
connecting to a DEC MAILworks Server for OpenVMS version V1.2 or
later.


Changes included in the Version 1.2-1 release
==============================================

o The crash which occurred when sending a message when there was no
disk space on a file server has been corrected.

o The folder counts on folders containing corrupted messages has
been fixed to the extent possible.  

o The temporary .BOD files which were not being deleted after
creating a message are now being removed.
             
o The crash which occurred when doing a show full header on a
message containing a non-receipt from a FAX gateway has been
corrected

o The ability to select a single entry after performing a multiple
select in the PAB has been restored.

o Forwarding multiple messages without header now results in the
headers of all the selected messages being removed.

o The crash which occurred when attempting to open a folder
containing a corrupted message has been fixed.

o An ALT V (View Full Header) while creating/editing a revisable
message will now display current header settings.  Previously
changes made to the header during edit session were not included in
the show header display.  

o When a DDS entry includes a middle initial, the initial will be
displayed in the DDS index list.

o Printing an unread message remotely will now set the unread
message to read.

o Printing an unread message remotely will now generate a read
receipt.

o The crash  (GPF)  which  occurred  when  selecting  (F5)  a message
for read then closing and reading another message immediately afterwards
has been fixed.

o The two extraneous .PRF files have been removed from the kit.

o The PRN_TEST.EXE file required for cleaning up after local printing
has been added to the kit.

o The missing file MNUUSS.CFG has been added to the kit.
 

Installation change since ALL-IN-1 MAIL for DOS V1.1A
======================================================

DEC MAILworks for DOS V1.2 and subsequent releases include an
upgraded local file cabinet.  If you have a version prior to DEC
MAILworks for DOS V1.2, you will be unable to access your local
file cabinet.  A conversion utility is included in the kit.  This
will be run as part of the installation procedure.  If for any
reason, one or more drawers are not converted at installation time,
the utility may be run separately from the installation procedure
in order to convert additional drawers. Prior to running this
utility, you should make sure you are connected to any file
services which contain a local drawer. You are limited to
converting no more than 100 local drawers per invocation of the
conversion utility.

This utility will:

o Create a backup copy of your drawer list which is contained in  
  the file X400DRAW.CAB.  The backup file will be named           
  X400DRAW.V26.

o Create a LOCALCAB.OLD subdirectory to hold backup copies of your 
  file cabinet index files.

o Back up your current index files into LOCALCAB.OLD. The previous 
  version files it copies are the index files associated with each 
  drawer.   They have the extensions: .DT, .ST, .MP, .NX0 and     
  .NX1.  Each drawer has a unique name for the associated set of  
  index files.

o Create new index files. The new index files have the extensions: 
  .DT, .ST, .MP and .NX.


When you run the utility you will be prompted to choose a local
drawer for conversion, for example:


    The following is a list of your local drawers:
                                       
    0  All drawers
    1  Sales
    2  Marketing
    .
    .
    .

    Enter the selection of the drawer to convert:


You then choose a drawer and press Enter.

You will be returned to the DOS prompt when the conversion is
completed.

If you need to run the conversion utility after installation in
order to convert additional drawers, type FCONVERT from the A1M$SYS
directory.


Known Problems and Limitations
==============================

This section outlines the known problems in DEC MAILworks for DOS
V1.2-1


 Installation Related
 --------------------

o If installing from VMS Media, please note that the kit name has
been changed to DMW$DOSV12.  This replaces references to
A1MAIL$DOS_V12 in the installation guide.


 Setup Related
 -------------

o Be sure to set the variables A1M$SYS and A1M$USER as directed in
the installation procedure. Do not set them equal to "path."

o While searching the directories specified by PATH, if DOS finds
any of the following file names ($RUN.OVL, IBM$RUN.OVL,
SYS$MSG.DAT, SYS$HELP.DAT or SYS$ERR.DAT) before the %A1M$SYS% path
entry, there will be a file conflict and the DOS client will not
run. If such a conflict should occur, add the correct path to the
start up .BAT file.   

o If, after installing DEC MAILworks for DOS and while making an
ASYNC connection, you receive the error message:

   "Unable to connect to the server, Connection request refused"

check that the server is running and your server account has NETMBX
and TMPMBX privilege.  See your server's system manager for
assistance. 


 Read Related
 -------------

o  A Read Receipt is sent only if you are reading the message when
connected to the DEC MAILworks server.  Unread messages moved to a
local drawer and read while not connected to the server will not
generate a read receipt.
  
o  While using the PATHWORKS file redirector, a user will not be
able to read the content of a message that is stored in a drawer
with a directory specification of [username.A1MAIL$] unless the
device is the user's SYS$LOGIN directory.  The workaround for this
problem is to start mail with the /NM switch.

o Generally, the built-in viewer can handle files that are several
thousands of lines long.  The memory available to the mail client
may limit the size of file that the built-in viewer may display. 
If this problem is encountered, it is recommended that the user try
using an external viewer.

o If a user presses ALT/B (disconnect) while reading a message, the
client will disconnect from the server. However there is no
feedback to the user that this has completed successfully until the
user exits read at which time they will no longer be able to access
the server.

o When reading a text message with the built-in viewer that
contains no carriage returns or line feeds, a user may receive an
error of "Line too long."  It is suggested that the user try to
read the message with an external viewer.

o The help text for viewing a message incorrectly states that Ctrl-
End will move to the bottom of the file and Ctrl-Home will move to
the top of the file.  It should read Ctrl-PageDown will move to the
bottom of the file and Ctrl-PageUp will move to the top of the
file.


 Network Related
 ---------------

o Async Scripts: It may be necessary to customize the KERMIT  
GETIN.TAK and GETOUT.TAK scripts for proper operation in various  
environments. See the comment lines in these files for more  
information.

o  When using the ASYNC connection, the only version of KERMIT that
is supported is the one shipped with the kit.  Do not replace the
KERMIT in the A1M$SYS directory with another version.

o  The ability to change a mistyped password and to reset expired
passwords while making an ASYNC connection has been added.  When
using this new feature, the user will be receive an invalid
password when the client connects to the mail server and is
required to reenter the new password.  This is a limitation of this
new feature. 


 Windows Related
 ---------------

o Running 2 copies of DEC MAILworks for DOS in the Windows
environment will almost inevitably cause an access violation to
occur. 

o The A1MAIL.PIF and A1MAILE.PIF file specify c:\a1mail as the mail
directory.  If a user installs mail elsewhere, these .PIF files
will need to be modified by the user. 

o When running A1MAIL from Windows, the application may hang or
display a fatal error when starting.  If this occurs, run A1MAILE
instead.


 File cabinet Related
 -------------------

o You can set the message order of folders only for folders in
remote drawers.  The message order for local folders is first
in/first out. There is no sorting by date for local folders.
  
o If you delete a folder that contains messages, it will delete the
messages, but not the folder itself. You must do a second delete  
operation on the folder to remove the folder the from list. 

o You cannot delete a remote drawer using the "Delete the selected 
local drawers" command. 

o The delete drawer operation causes the fifth character in the
drawer name to no longer appear on the drawer list. 

o If you delete a local drawer, you cannot Undelete it. 

o A user may not undelete a folder.  Undeleting a message within a
deleted folder will undelete the folder.  If the folder is empty,
it must be recreated.

 Memory Related
 --------------

o There have been instances of memory problems, particularly in   
using Windows with the non-extended version.  If this should occur,
exit DEC MAILworks for DOS and then restart.  This will free up
memory.

o The Honeywell Bull 386 PC or the NEC 386 PC may not be able to  
use the DEC MAILworks for DOS built-in editor.  Use an external   
editor. 

o To use a memory-intensive, external editor such as WordPerfect,
with the extended versions of the DOS client (A1MAILE and
A1MAILAE), requires that at least 1 megabyte of Extended memory is
free. 

To check to see if you have sufficient Extended memory, run the   
PMINFO.EXE utility, which is included in the installation kit.  
Check the "Extended memory" column to see if 1024K bytes of
Extended memory is available.

o If you are using WordPerfect as the external editor for the
product, you must be aware that WordPerfect needs a minimum of 394K
bytes of memory in order to run. After DEC MAILworks is loaded into
memory, there should be over 400K bytes of memory remaining, so
WordPerfect should be usable. If you are having a problem getting
WordPerfect to load within our product, then there is probably
other software being loaded into low memory. Check to see that DOS
is loaded into HIMEM and that there are no TSRs loaded except the
CTIxxx TSR used by DEC MAILworks.


 Built-in Editor Related
 -----------------------

o This editor supports only ASCII text files.  You should not   
attempt to edit, include, or view other file types with this   
editor.  If this is done the user may see what appears to be   
"garbage" in the edit window.  Simply press ESC to leave the   
editor.

o Editing is limited to ASCII text files of less than 2000 lines. 
To edit files greater than this limit, use an external editor.  
You cannot include files that cause the line count to exceed 2000 
lines during the edit session.  The editor does not impose this   
limit when viewing an ASCII text file.

o When using the built-in editor as a viewer, CTRL/Zs are
considered end of file.  This is an accepted end of file indicator
on MS-DOS.  It may be possible that messages originating outside of
DEC MAILworks contain a CTRL/Z in the text of the message.  Any
text following the CTRL/Z will not be viewed by the built-in text
viewer.

o When the first line of text word wraps and the user then up
arrows up to the first line, the last letter of the first line may
be lost.  

 PAB related
 ------------

o When searching the PAB from an address field, only single word
searches will work.  A search for "Van den" will not successfully
find all of the surnames that begin with "Van den".  The user must
limit the search to "Van" and select from the list.  

o When accessing the PAB, the entire content of the PAB is read
into memory.  Therefore, the number of entries in a user's PAB will
be limited to the amount of memory available to the mail client.  

o Various address functions will turn lowercase PAB entries into
uppercase.  In some instances these changes will be permanent.

o It is not possible to modify an entry in the PAB from all
capitals to mixed case.  The workaround is to delete the entry and
enter it into the PAB again.

o When a PAB entry has a nickname and surname of equal length, when
the surname is entered on an address field, the nickname will be
displayed instead.

o When doing a substring match search in the PAB, if the substring
matches exactly names in the PAB, other partial matches may not be
found.  For example, DON* will find DON Jones, Don Smith, but not
Donna Smithi.  Use of a less restrictive criteria will find all. 
DO* will find all three names in the example.


 Miscellaneous
 -------------

o If you need to reboot while you were creating a message, the text
of the created message MAY still be available in your user
directory as a text file with the extension of ".BOD". If this file
is present, it can be included when you recreate the message.

o The CTRL/PGUP and CTRL/PGDN keys will not work on some of the
form fields on the second form of the ASYNC script creation form. 
To use these keys, navigate to the first form on the field.

o When undeleting a list of messages, not all of the selection
marks will be cleared after the function has completed.

o If the distribution list utility is used to modify a nested
distribution list, the nested distribution list will be removed
from the list in which it is nested.  

o When transferring a message from the server to the client, the
size of message indicator displayed in the index may increase. 
This does not indicate that the content of the message has changed.

o When moving a message between drawers, a copy of the message is
placed in the Wastebasket of the source drawer.  This copy will not
be purged when the user exits the mail client unless another
message within the same drawer has been explicitly deleted.  These
messages can be purged if the user selects the drawer and purges
the wastebasket within that drawer.

o When messages containing non-text bodyparts are printed to remote
printers, all of the bodyparts will be printed as if they were
text. This may result in several pages of unreadable output.

o If a user has two folders within the same drawer with names that
differ only by case, the count that indicates the number of
messages in these folders may become inaccurate.  It is recommended
that users do not use folder names that differ only by case.

o When attaching a file to a revisable message, when the user is
prompted for a file name and only a drive letter and : is entered,
occasionally an error will be displayed.  To avoid this error a
user needs to enter a trailing \.  If the error occurs, the user
just needs to press ENTER a second time.

o When a user replies to a message using the option to include the
text from the original message, if they do not have sufficient disk
space the text will not be included.  The fact that the text is
missing is obvious to the user because the text will not be
displayed in the editor.  There is no error message telling the
user that there is insufficient disk space.

o If the DDS process on the server is hung for some reason, the
mail client will hang when attempting a DDS search.  The DDS
process on the server needs to be stopped or the PC rebooted to
correct this problem.

o If a user is running using the "MCS mode" and prints a message to
an attached printer, the character set may not display properly. 
It is recommended that users using this mode print to printers
attached to the server or other VMS machines.

o There is no function for copying a revisable message to a DOS
file. It is suggested that a user send the message to their own
address and then copy it to DOS.

o When creating a drawer, characters are generally uppercase;
however, some eight bit characters may not be uppercase.

o If a user deletes a folder containing one or more messages and
then opens the wastebasket, undeletes one of the messages in the
deleted folder, the folder and message will not appear on the index
after closing the wastebasket.  The user must exit mail and reenter
in order to access the undeleted message.

o In some instances a function key Fn may be available for use even
if the key is grayed out.

o Messages deleted by the DEC MAILworks for DOS clients may not
show up in other MAILworks clients wastebaskets unless another
message is deleted by the other client.  Messages deleted by other
MAILworks clients will be visible in the DEC MAILworks for DOS
wastebasket, but may not be purged on exit unless another message
has been deleted by the DOS client.  

o When attaching files to a revisable message, a user is allowed to
specify any string for the attachment type even though the string
may be invalid.  This may cause a failure when posting the message.

o If a message that has been forwarded does not contain a cover
note and it is copied to a revisable, a user will not be able to
add a cover note.  A user may modify the header information and add
attachments, but an attempt to enter the editor in what appears to
be an empty cover note will generate a error message.

o While using FIND, if a user specifies a search criteria that does
not match a message in the currently open folder, after exiting
FIND any operations on messages within the current open folder will
generate an error "There is an Error Accessing the File Cabinet". 
The user must close and reopen the folder.

o If a message with greater than 100 recipients in either the To or
CC field is copied to a revisable message, an error will be
displayed when modifying the revisable message.  The user will be
able to modify the message, but not all of the recipients will be
displayed in the To or CC field.  The recipients not displayed will
still be included in the modified copy.  

o If a user creates a folder with the same name but different case
as one of the "special" folders (ie. INBOX), they will not be able
to delete either folder.  To delete the folder the user must modify
their profile and change the special folder to another folder, then
delete the folder in question and reset the profile to the desired
value.

o If non-text attachments are printed to server printers, the
resulting output is not predictable.

o FIND on the IP MESSAGE ID within the OUTBOX folder does not work.

o If a user starts to create a message with the editor of choice
set to external, and then during creation changes the profile to
use the built-in editor, the create form will not display properly. 
The message can be successfully created.

o The EXIT option on the file pull down will not work while using
the built-in editor to create a message.

o If an attachment of a revisable message that has been saved is
deleted, corrupted, or protected, when a user modifies the
revisable, no error message will be given and an empty attachment
will be displayed.

o When printing a message from the OUTBOX, no date will be printed.

o If the results of a find include revisable messages, the
revisable messages can not be modified from the find list.  These
messages must be selected from a message index list.

o If a SHIFT F5 is pressed on a FIND list that has more messages
than can be displayed on a screen and the user moves these
messages, the list will not be completely updated to reflect that
all messages have been moved.  All messages will actually be moved.

o There is currently no way for a user to modify a personal name
from within create.  If a user is creating messages on a PC shared
with another user, they should check the value in the personal name
field of the user profile before creating a message.

o If a user's password expires between the time they connect to the
server and send mail, the sending of the mail message may fail. 
The error will not indicate that it is an expired password.

o If a user invokes the PAB from the built-in editor (ALT/A) and
from the PAB listing presses F1 (help) three consecutive times,
they will receive a stack overflow and will have to restart the
mail client.

o A GPF may be observed if the following steps are followed.  F5 to
select a message, RETURN to read the selected message, exit from
read, RETURN to read any message on the display list.  

o When a folder containing a corrupted message is opened, the
corrupted message appears in the list of messages in the folder. 
In accessing this message, because the message could have been
corrupted in various places, it is possible there will be instances
where problems will occur.  

o If a folder contains a corrupt message, it is possible that the
folder counts will be incorrect.  This usually results in the
creation of a wastebasket folder as well, regardless of whether
there are actually any deleted messages.  Copying the messages in
the corrupt folder to a new folder and deleting the old folder
should correct both the folder count and the wastebasket folder.  
         
           
