


                  -------------------------------------------
                  Microsoft Mail for PC Networks version 3.5
                                README File
                  -------------------------------------------


                  (C) Copyright Microsoft Corporation, 1991-95


This document (README.TXT) contains important information that supplements 
the Microsoft Mail version 3.5 manuals and online help provided in this 
package. The manuals include the Microsoft Mail Administrator's Guide, the 
Technical Reference manual, and the User's Guides for the MS-DOS client, 
Windows-based and Presentation Manager clients, and Macintosh client.

README.TXT also contains information about fixes made to components of
Microsoft Mail for PC Networks since version 3.2a.

This document covers the following topics:

   A. How to print these notes
   B. How to get help from Microsoft online
   C. Information for Microsoft Mail administrators
   D. Information for users of the MS-DOS client software
   E. Information for users of the Windows-based client software
   F. Information for users of the Presentation Manager client software
   G. Information for users of the Macintosh client software
   H. Fixes made to components of Microsoft Mail for PC Networks since
      version 3.2a
   I. Special 3.5 upgrading information for PC-NFS network administrators


A. HOW TO PRINT THESE NOTES
===========================

To print these notes:
---------------------
1. Type: copy readme.txt printer:
   Replace "printer:" with the port to which your printer is connected,
   such as lpt1.
2. Press ENTER.

To print these notes from Microsoft Windows:
--------------------------------------------
To print README, open README.TXT in Windows Write, Microsoft Word, or another 
word processor. Then select the entire document and format the text in 10-
point Courier before printing.


B. HOW TO GET HELP FROM MICROSOFT ONLINE
========================================

Microsoft provides the following sources of online support and utilities
for Microsoft Mail administrators:

1. CompuServe, GEnie, and Microsoft OnLine provide Application Notes located
   in the Microsoft Software Library (MSL). KnowledgeBase articles can be
   accessed on CompuServe via GO MSKB.
2. Microsoft Download Service (MSDL) provides Application Notes and can be
   accessed via modem at 206-936-6735 (in Canada, 903-507-3022).
3. Application Notes can be retrieved over the Internet using the Microsoft
   anonymous FTP server. This can be reached by typing "ftp ftp.microsoft.com"
   at the ">" prompt.
4. Microsoft FastTips Technical Library provides KnowledgeBase articles and 
   can be accessed inside the United States at 800-936-4400.
5. For a Microsoft Technet CD subscription, call Corporate Support Sales and
   Service at 800-227-6735 or 800-344-2121, extension 035, inside the United
   States.
6. Outside the United States, contact the Microsoft subsidiary in your area 
   for regional online services. To locate your subsidiary, see the
   "Introduction" section in the "Microsoft Mail Administrator's Guide."


C. INFORMATION FOR MICROSOFT MAIL ADMINISTRATORS
================================================

This section covers the following topics:
  
    1. Microsoft Mail Technical Reference
    2. Supplementary modem scripts
    3. Directory of text files installed by Setup


C.1. Microsoft Mail Technical Reference
---------------------------------------
The Microsoft Mail Technical Reference manual describes features that 
administrators and programmers can use to extend and customize Mail in the 
Windows environment. For information not included in the Technical Reference, 
see the README.TXT file on the Technical Reference Server Programs disk.

C.2. Supplementary Modem Scripts
--------------------------------
Modem scripts used with the External Mail program are installed in the 
postoffice directory when you run the Setup program (SETUP.EXE). The 
Supplementary Modem Scripts disk contains additional modem scripts. For a 
list of modem script files and installation instructions, see the README.TXT 
file on the Supplementary Modem Scripts disk.

C.3. Directory of Text Files Installed by Setup
-----------------------------------------------
The Microsoft Mail Setup program installs the following text files in the 
server programs directory you specify:

  FILE          CONTAINS
  ----          --------
  ADMIN.TXT     Administrator program error and status messages
  CLIENT.TXT    MS-DOS client and Macintosh client program error messages
  DIRSYNC.TXT   Directory Synchronization error and status messages
  DISPATCH.TXT  Dispatch program error messages for MS-DOS and OS/2
  DYNADMIN.TXT  Dynamic Drive Administrator program error messages
  EXTERNAL.TXT  External Mail program error messages for MS-DOS and OS/2
  IMPORT.TXT    Local User Import program error messages, LAN Manager and 
                Novell Extract Utility error messages
  MMTA.TXT      Readme file for the Microsoft Mail Multitasking MTA
  README.TXT    This file
  SETUP.TXT     Microsoft Mail Setup program error messages
  SWITCHER.TXT  Information about changing Mail system drivers using the 
                Microsoft Mail System Selector


D. INFORMATION FOR USERS OF THE MS-DOS CLIENT SOFTWARE
======================================================

This section covers the following topics:

   1. Connection time-out with Microsoft LAN Manager version 2.0
   2. Saving an attachment with a long filename
   3. Incompatible support files
   4. Micro should be run before the MS-DOS 5.0 DOSSHELL
   5. Micro should use the -F option with graphics applications


D.1. Connection Time-out with Microsoft LAN Manager version 2.0
---------------------------------------------------------------
Long spans of inactivity while the MS-DOS client is connected to a postoffice 
on a LAN Manager version 2.0 server may lead to misleading error messages 
such as "Disk Full" when the client is used again. This is caused by a 
connection time-out with LAN Manager version 2.0 and does not occur with LAN 
Manager version 2.1. If this occurs, change the KEEPCON line in the 
LANMAN.INI file to KEEPCON=0.

D.2. Saving an Attachment with a Long Filename
----------------------------------------------
To ensure that users encounter no problems accessing files from another 
program that were created or saved by Microsoft Mail, direct users to remove
any spaces in filenames when saving attachments in Microsoft Mail.

D.3. Incompatible Support Files 
-------------------------------
If a user receives the message "Error file is not accessible. Check server 
connection.", the message could be caused by a conflict between the user 
running the MS-DOS client version 2.1 and the MS-DOS client version 3.0 
installed on the postoffice. To solve this problem, either upgrade the user to 
the MS-DOS client version 3.0 or install MS-DOS client version 2.1 on the 
postoffice.

D.4. Micro Should be Run Before the MS-DOS 5.0 DOSSHELL
-------------------------------------------------------
The Micro mail-notification TSR does not operate correctly when invoked from 
an MS-DOS session started after starting DOSSHELL. To use Micro with the 
MS-DOS shell, start Micro and then start DOSSHELL.

D.5. Micro Should Use the -F Option with Graphics Applications
--------------------------------------------------------------
If applications that switch the video into graphics modes are used, including 
DOSSHELL in graphics mode, ask users to start Micro with the -F option. 
However, due to variances in VGA hardware, problems could still occur when 
using this option.


E. INFORMATION FOR USERS OF THE WINDOWS-BASED CLIENT SOFTWARE
=============================================================

This section covers the following topics:
  
   1. Exporting folders to a transport message file
   2. Mail and SHARE.EXE
   3. The MMF file
   4. Accessing Mail using more than one client
   5. Send and receive privileges
   6. Checking for new mail
   7. Sending a bitmap as an attachment
   8. Using Mail with Windows for pen computing
   9. Deleting message-file backups 


E.1. Exporting Folders to a Transport Message File
--------------------------------------------------
Do not use the Export Folders command on the File menu to copy folders into a 
primary message storage file, such as the MSMAIL.MMF or MS_ATT.MMF file. If 
users do, the Personal Address Book (PAB) in the destination primary message 
storage file is overwritten. To avoid this problem, have users export the 
folders to a temporary file (for example, FOLDER.MMF), and then use the 
Import Folder command on the File menu to copy the folders into the other 
primary transport message storage.

E.2. Mail and SHARE.EXE
-----------------------
If the user's message file (.MMF) is located on the user's local hard disk, he or she must run SHARE.EXE before starting the Mail Windows-based client. Mail 
will not start if the user has not run SHARE.EXE.

SHARE.EXE is needed because the file that contains messages could be accessed 
by other mail-related applications. It is important that each program 
accessing your messages is able to lock portions of the file and protect 
other mail-related applications from overwriting information in the file.

If the message file is located on the postoffice, SHARE.EXE is not needed.

*****************************************************************************
IMPORTANT:  When running Mail in Windows for Workgroups version 3.1 in 386 
enhanced mode, VSHARE.386 is loaded automatically, so SHARE.EXE is not 
needed.
*****************************************************************************

E.3. The MMF File
-----------------
The Mail Windows-based client has many features, such as the message finder, 
offline composition, and an API that allows software developers to write new 
applications that help manage messages. These features require a new file 
format for storing messages. With the new format, all messages are stored 
in one file, with the extension MMF. Using one file makes backing up and 
moving messages very easy. The MS-DOS and Macintosh clients cannot read 
the new file format.

To convert messages from the old format to the new MMF format, Mail includes 
a utility called CONVERT.EXE. For information about running CONVERT.EXE, see 
the User's Guide for the Windows-based client.

This message file can be kept on the postoffice server or on a local disk. If 
it is kept on the postoffice, and the network connection to the postoffice is 
broken, the message file is inaccessible to Mail. If the user runs Mail 
offline in this case, Mail creates a temporary message file for use offline. 
When Mail is run online again, it uses the message file on the postoffice, and 
messages created while offline are not in this file.

A user can create message files other than the primary message file. These 
are created when using the Backup command on the Mail menu, the Export 
Folders command on the File menu, or by creating a temporary offline file as 
mentioned previously. To access these message files, the user specifies the 
name of the file in the command line when starting Mail, as follows:

msmail.exe /f <filename>

Mail opens the specified message file instead of the user's primary message 
file and starts offline. To revert to the user's primary message file, run 
Mail without the /f parameter.

E.4. Accessing Mail Using More Than One Client
----------------------------------------------
If a user stores his or her primary message file locally but also dials in 
to the Mail system with a modem, or uses a client in addition to the Windows 
client, the user should select the Copy Inbox On Postoffice check box in the 
Server dialog box. 

To display the Server dialog box, choose the Options command from the Mail 
menu, and then choose the Server button. A copy of the message file is 
retained on the postoffice, providing the user with an up-to-date version of 
the message file when he or she dials in.

E.5. Send and Receive Privileges
--------------------------------
The Presentation Manager client does not notify the user if he or she has no 
send or receive privileges. For example, if a user with no receive privileges 
checks for new mail, the user is informed that there are no new messages--not 
that he or she has no receive privileges.

E.6. Checking for New Mail
--------------------------
The setting in the Options dialog box that controls how often Mail checks for 
new mail also controls how often Mail checks the Outbox for messages to 
submit to the postoffice. If it seems that messages are taking too long to 
appear, remember that a message first waits in the Outbox and then waits 
again until Mail checks for new messages. For example, if a user specifies 
that Mail should check for new mail every 3 minutes, the user could wait up to 6 minutes before receiving the new mail.

E.7. Sending a Bitmap as an Attachment
--------------------------------------
If a user sends a bitmap created in Paintbrush or another graphics 
application, the recipient may not be able to view the bitmap if he or she 
is using a monitor with a different resolution.

E.8. Using Mail with Windows for Pen Computing
----------------------------------------------
Although Mail is pen aware, there are some cases, such as when running the Setup program, where the user is not able to write directly into a Mail edit 
control. To use pen for input in these cases, run the pen palette in the 
background.

E.9. Deleting Message-File Backups
----------------------------------
In some circumstances, when Mail encounters problems in the message file 
(.MMF), the user is asked if Mail should repair the file. Each time the 
message file is repaired, Mail makes a backup copy of the file in the 
directory containing the message file. The first backup file is named 
<file>.BAK, where <file> is the name of the original message file. Subsequent 
backup files are named <file>.001, <file>.002, and so on. For message files 
stored on the postoffice, the <file> name is a number defined for the user 
(for example, 00000021). For message files stored locally on the user's 
computer, the <file> name is defined by the user. These backup files can be 
deleted by the user or administrator.


F. INFORMATION FOR USERS OF THE PRESENTATION MANAGER CLIENT SOFTWARE
====================================================================

This section covers the following topics:

   1. Installing and running the Presentation Manager client
   2. About dialog box statistics
   3. The MMF file
   4. Accessing Mail using more than one client
   5. Send and receive privileges
   6. Checking for new mail
   7. Sending a bitmap as an attachment
   8. Saving messages as files 
   9. Associating applications and file extensions
  10. Copying file attachments to the Clipboard
  11. Security setting in the MSMAIL.INI file


F.1. Installing and Running the Presentation Manager Client
-----------------------------------------------------------
The programs for the Windows-based and Presentation Manager clients are on the 
disks labeled Windows-based Client and Windows-based and OS/2 Presentation 
Manager Workstation Software. To install the clients on the network, follow 
the instructions in the Microsoft Mail Administrator's Guide. 

On OS/2 version 2.0, users can run the Windows-based client. To set up the 
Windows-based client, run the Setup program. 

On OS/2 version 1.x, users must run the PM client. To set up the PM client, 
run the PMSETUP program from an OS/2 window by typing PMSETUP at the OS/2 
prompt.

F.2. About Dialog Box Statistics
--------------------------------
In the Presentation Manager client, the values for Memory and Disk Space in 
the About dialog box may not be accurate.

F.3. The MMF File
-----------------
In Presentation Manager client version 3.2, all messages are stored in one 
file, with the extension MMF--one file makes backing up and moving your 
messages very easy. The MS-DOS and Macintosh clients cannot read the new file 
format. 

To convert messages from the old format used prior to version 3.0 to the new 
.MMF format, use the Mail utility called CONVERT.EXE. For information about 
running CONVERT.EXE, see the Microsoft Mail User's Guide for the Windows-
based client.

F.4. Accessing Mail Using More Than One Client
----------------------------------------------
If a user stores his or her primary message file locally but also dials in to 
the Mail system with a modem, or uses a client in addition to the Windows 
client, the user should select the Copy Inbox On Postoffice check box in the 
Server dialog box. 

To display the Server dialog box, choose the Options command from the Mail 
menu, and then choose the Server button. A copy of the message file is 
retained on the postoffice, providing the user with an up-to-date version of 
the message file when the user dials in.

F.5. Send and Receive Privileges
--------------------------------
The Presentation Manager client does not notify the user if he or she has no 
send or receive privileges. For example, if a user with no receive privileges 
checks for new mail, the user is informed that there are no new messages--not 
that he or she has no receive privileges.

F.6. Checking for New Mail
--------------------------
The setting in the Options dialog box controlling how often Mail checks for 
new mail also controls how often Mail checks the Outbox for messages to 
submit to the postoffice. If it seems that messages are taking too long to 
appear, remember that a message first waits in the Outbox and then waits 
again until Mail checks for new messages. For example, if a user specifies 
that Mail should check for new mail every 3 minutes, he or she could wait up 
to 6 minutes before receiving the new mail.

F.7. Sending a Bitmap as an Attachment
--------------------------------------
If a user sends a bitmap created in Paintbrush or another graphics 
application, the recipient may not be able to view the bitmap if he or she 
is using a monitor with a different resolution.

F.8. Saving Messages as Files 
-----------------------------
If the user uses the Save As command on the File menu to save a message as a 
text file, the text is saved in the ANSI code page. Extended characters may 
not be preserved if the text file is opened in an application other than 
Microsoft Mail.

F.9. Associating Applications and File Extensions
--------------------------------------------------
The user can view an attachment by double-clicking it; however, to do this 
in Presentation Manger, a section must be added to the WIN.INI file in the 
user's OS2\DLL directory, in the following format: 

[Extensions]
ext=c:\extapp.exe ^.ext
xls=c:\excel\excel.exe ^.xls

Type the file extension, an equal sign, the path and name of the application 
to be to run, a space, a caret (^), and the file extension.

The caret is replaced with the name of the attachment. For example, if you 
double-click a file called NAME.EXT, Mail executes the command "c:\extapp.exe 
name.ext".

F.10. Copying File Attachments to the Clipboard
-----------------------------------------------
Users should not copy file attachments to the Clipboard--the Presentation 
Manager Clipboard cannot handle file attachments.

F.11. Security Setting in the MSMAIL.INI File
---------------------------------------------
When using the Presentation Manager client, do not set Security=1 in 
MSMAIL.INI. If Security=1 is set, the user cannot use the task switcher to 
restore the application when he or she minimizes Mail. The Security setting in 
MSMAIL.INI controls whether a password is required to restore Mail when it is 
minimized. If Security is set to 1, a password is required.


G. INFORMATION FOR USERS OF THE MACINTOSH CLIENT SOFTWARE
=========================================================

This section covers the following topics:

   1. Working offline with the Macintosh client
   2. Attaching an object to a forwarded message


G.1. Working Offline with the Macintosh Client
----------------------------------------------
Under System 7, the user can use the Macintosh client to compose mail or 
access private folders on a local drive even if the postoffice server is not 
available. To use this feature, the user selects the Save My Name And Password 
option button in the Preferences dialog box. 

If the server goes down while the user is using Mail, the user can reconnect 
without leaving the Mail application. To do so, the user should use the 
Chooser to connect to the server--Microsoft Mail will find the postoffice.

G.2. Attaching an Object to a Forwarded Message
-----------------------------------------------
If the user is forwarding a message and wants to send an attachment (OLE 
object), have the user send the attachment in a separate message. Messages 
attached to a forwarded message are not transmitted when the message is sent.


H. FIXES MADE TO COMPONENTS OF MICROSOFT MAIL FOR PC NETWORKS 
   SINCE VERSION 3.2a
=============================================================

The following sections list fixes that have been made to client and server 
components of Microsoft Mail for PC Networks between the release of Microsoft 
Mail 3.2a and this release, 3.5. 

H.1. Client Information
-----------------------
This section covers the following topics:

1. Macintosh client fixes
2. Windows and Presentation Manager client fixes

H.1.1. Macintosh Client Fixes
-----------------------------
- Template information over 64K distributed by Directory Synchronization would
  be displayed in a corrupt manner.
- When sending to an X.400 address using Domain Defined Attributes, an error 
  -1 would occur and messages were not able to be sent.
- Messages were not able to be forwarded if the original message had an
  attachment and the user chose not to include the attachment in the forwarded 
  message.
- When the option to automatically open the TO: list on composing a message 
  was set, and the Macintosh was running System 7.5, an error would occur when 
  attempting to forward a message.

H.1.2. Windows and Presentation Manager Client Fixes
----------------------------------------------------
- Templates with extended characters from other postoffices would not be 
  displayed with the extended characters.
- Template fields with 0 length would not be displayed.
- When Gateway-originated messages with an hour time stamp of 24 or higher 
  were received, the Windows client would stop reading all messages in the 
  Inbox and display the following message:
       The mailbag file required for accessing your messages is missing or
       invalid. Contact your administrator to get your account restored from
       a backup.
- Gateway or External postoffice users who had multiple definitions on the 
  postoffice with different friendly names were not displayed in the GAL.
- Adding the same alias with a different underlying address from the GAL to 
  the PAB did not work.
- If the file in the database that holds account validation information was 
  locked open and a user changed passwords, no error would be given.

H.2. Server Information
-----------------------
This section covers changes related to ADMIN.EXE, EXTERNAL.EXE, IMPORT.EXE,
REBUILD.EXE, and SRVMAIN.EXE.

H.2.1. ADMIN.EXE
----------------
- When the Administrator ID was changed to a mailbox with greater than 8 
  characters in Config-Dirsync-Server-Options, the "keep updates (days)" 
  option would also change.
- When a user who had Remote privileges and a custom view was updated using 
  Local Admin-Modify, the view would be reset to the default view.
- No error was reported if a postoffice's .XTN file was locked open while 
  being modified.
- Admin was not able to add users or modify groups if the postoffice address 
  list was over 32768 users long.
- Groups with addresses that were 10 characters long were not deleted in 
  Dirsync. This was due to an extra character being placed at the end of the 
  address by Admin and Dirsync not being able to handle 11-character 
  addresses.

H.2.2. EXTERNAL.EXE
-------------------
- During two-way asynchronous or X.25 communication, External did not lock 
  mailbags or create .0LK files.
- Communication over X.25 networks would not reliably send large numbers of 
  attachments (more than 20 in a single message) in low-memory conditions.
- Two entries were recorded in a postoffice's Sent.Log for messages sent over 
  asynchronous connections.
- Messages to invalid addresses did not report the invalid address in the 
  Non-Delivery Reports sent to the message originator or in the postoffices'
  System.Log.
- When External connected to the MS-DOS Remote client, queued messages would 
  be sent, but messages were not being picked up.
- The Echo command did not work in modem scripts.
- Asynchronous communications could leave temporary files stranded in the 
  postoffices' P1 directory.
- Non-Delivery Reports over asynchronous connections would leave extra entries 
  in the postoffices' System.Log.
- An error "Circular Route Detected" would be reported if a postoffice with 
  a name 10 characters long received a message with the hop trace option set 
  to NULL.
- Delivering a message marked urgent to a postoffice defined with the 
  DrivesWAN option in combination with the Netbios option could put External 
  into an infinite loop.

H.2.3. IMPORT.EXE
-----------------
- Using Import to add a local user to a postoffice did not put template 
  information into REGTRANS.GLB for Dirsync to process.
- Templates created by Import did not end with the correct line terminator.
- When local users were added using a batch file, the TID value was reset to 0 
  for each new user.
- Creating local users with no address type would hang IMPORT.EXE.

H.2.4. REBUILD.EXE
------------------
- Rebuild would occasionally not include all available addresses into the GAL.
  This was caused by a logic error in the Index sort routine.
- Some file errors were not handled correctly. When a write would fail, the 
  return code would be overwritten by another function and would close the 
  file.
- Temporary file creation was not handled correctly and could delete the 
  existing GAL.

H.2.5 SRVMAIN.EXE
-----------------
The following problems related to SRVMAIN.EXE were corrected:
- SRVMAIN would read Template files 1 byte at a time when a full import was 
  requested. This would slow down the network performance of the Dirsync 
  Server.
- SRVMAIN would fail when duplicate message headers were in the system 
  mailbag.
- Requestor password checking would fail if one requestor was registered after 
  another with a name that was a subset of the first.
- Dirsync crashed when X.400 addresses were included in the Dirsync first 
  cycle.


I. SPECIAL 3.5 UPGRADING INFORMATION FOR PC-NFS NETWORK ADMINISTRATORS
======================================================================

The Microsoft Mail Setup program writes some files with the read-only 
attribute. This is done for network security and to stop database contention. 
When updating the database, SETUP.EXE will not be able to write over these 
read-only files, and the error "Unable to write ANSISORT.GLB" will appear. To 
stop this error from appearing, remove the read-only attribute from any file 
in the Mail database. You can do this at the MS-DOS prompt by using the 
following commands:

M:             (To change to the Maildata directory)
attrib -r /s   (This command removes the read-only attribute of any file in 
                the database).

Setup will then proceed correctly.

