


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


                  (C) Copyright Microsoft Corporation, 1991-93


This document (README.TXT) contains important information that supplements 
the Microsoft Mail version 3.2 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.

This document covers the following topics:

   A. How to print these notes
   B. Information for Microsoft Mail administrators
   C. External Mail program features not described in the Administrator's 
      Guide
   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


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. 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
   4. Modem Script return codes and external retries
   5. Multiple modem messages in a script response buffer
   6. Setting up Eicon Gateway software
   7. Moving a user already defined in the Destination 
      Postoffice Address List
   8. Import Utility example correction 
   9. Unencrypted password option no longer required for Novell
   10. MS-DOS External and LAN MAN opportunistic locking


B.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.

B.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.

B.3. Directory of Text Files Installed by Setup
-----------------------------------------------
The Microsoft Mail Setup programs install the following text files in the 
server programs directory you specified.

  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
  OS2MTA.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

B.4. Modem Script Return Codes and External Retries
---------------------------------------------------
Processing of certain return codes from modem script files differs from 
versions of Microsoft Mail prior to version 3.2. When the Call script returns 
a result code of NoCarrier (4), NoDialTone (6), Busy (7), or NoAnswer (8), 
the External program now increases the retries count on all mail that was 
queued to be sent. If the retry count exceeds the number for the routing, the 
mail is returned to the sender. 

If a script you customized for a previous version of Mail is to be used with 
the External Mail program version 3.2, check to see if the retry count on 
script return codes 4, 6, 7, and 8 was used. If the script was designed so 
that return code was not expected to increase the retries count, recompile 
the script using return code 9--External does not increase the retry count if 
encounters a script return code 9.

For more information about writing script files, see Appendix E, "Script 
Files," in the Microsoft Mail Administrator's Guide.

B.5. Multiple Modem Messages in a Script Response Buffer
--------------------------------------------------------
When the External Mail program receives a message from a connected modem, 
multiple messages can be put into the response buffer. If you are writing a 
custom script or using a script from the Supplementary Scripts disk that was 
written for modems manufactured outside of North America, use the ISIN 
operator to check the response buffer. This is especially important for 
incoming call messages.

Change the search for response return codes from:
         if (response = "2^M") 
to:
         if ("2^M" isin response)

For more information about writing script files, see Appendix E, "Script 
Files," in the Microsoft Mail Administrator's Guide.

B.6. Setting up the Eicon Gateway Software
------------------------------------------
For information about installing the Eicon Gateway software, see the Eicon 
documentation and Appendix F, "X.25 Settings for Mail," in the Microsoft Mail 
Administrator's Guide. Your Eicon setup must match the configuration of the 
line leased from your X.25 carrier. Values vary by carrier and installation--
confirm all values set by the ECCFG program with your carrier.

The Microsoft Mail Administrator's Guide provides information about 
parameters that are critical when setting up the Eicon board and software. 
For the configuration option Number Of TVCs, a value of 004 is suggested. The 
correct value depends on the line installed--a different value could be 
appropriate for your configuration.

B.7. Moving a User Already Defined in the Destination Postoffice Address List
-----------------------------------------------------------------------------
You can use the Move User utility to move locally defined users between 
postoffices. If you attempt to move User X from Postoffice A to Postoffice B, 
and there is already an external address for User X in Postoffice B's 
Postoffice Address List (POL), you are asked for another alias for user X 
before you can move the user.

To avoid this situation, be sure that the external address for a user is 
deleted on the destination postoffice before you move the user.

B.8. Import Utility Example Correction 
--------------------------------------
On page 322 in the Microsoft Mail Administrator's Guide, in the section 
"Examples of Running Import," the third example is incorrect.

The example should be: 

import admin -ppassword -gsnads -x -fh:\snads.txt

B.9. Unencrypted Password Option No Longer Required for Novell
--------------------------------------------------------------
If you are running Microsoft Mail on a Novell network, and you are upgrading 
your postoffice from a version of Microsoft Mail prior to 3.0, remove the SET 
UNENCRIPTED PASSWORDS=ON option from the AUTOEXEC.NCF files. This setting was 
previously required to properly configure dynamic drives for the External 
Mail program.

B.10. MS-DOS External and LAN MAN opportunistic locking
-------------------------------------------------------
If External is running on a MS-DOS LAN MAN workstation with opportunistic 
locks enabled, External may hang the workstation when trying to recover from 
critical errors. When this occurs, External stops delivering mail and the 
workstation must be restarted. 

To avoid manually restarting the workstation, take one of these two 
preventative measures:

1. In your LANMAN.INI file Workstation Section [workstation] turn off 
opportunistic locking of files by turning off bit 0 in the wrkheuristics 
entry. See appendix B of the Microsoft LAN Manager Administrator's Reference.

2. Use the External option RebootOnCE to automatically restart the 
workstation on critical errors. See section C.2 in this document for more 
details.

C. EXTERNAL MAIL PROGRAM FEATURES NOT DESCRIBED IN THE ADMINISTRATORS GUIDE
===========================================================================

This section covers the following topics:

   1. Generic script file included with the Server
   2. Automatically rebooting MS-DOS External on critical errors
   3. Specifying X.25 facilities and user data


C.1. Generic Script File Included with the Server
-----------------------------------------------------
A new generic script file for Hayes-compatible modems is included with the 
Microsoft Mail for PC Networks MS-DOS server version 3.2. The script file, 
USGNERIC.MDM, is designed to operate with any modem compatible with the Hayes 
AT command set. The generic script does not set the baud rate--the baud rate 
is set using the Config Serial Baud-rate command in the Administrator 
program.

The generic script is installed in the GLB directory of the postoffice 
directory you specify when running the Setup program (SETUP.EXE). To use this 
script, specify the option CommScript=USGNERIC in the External Mail program. 
For more information about specifying scripts in the External Mail program, 
see Chapter 12, "Setting Up the External Mail Program," in the Microsoft Mail 
Administrator's Guide.

C.2. Automatically Rebooting MS-DOS External on Critical Errors
---------------------------------------------------------------
A critical error is generated by MS-DOS when an unrecoverable situation 
occurs in an application. When this happens, the message "Abort, Retry, 
Fail?" is displayed--to continue using the application, the user must 
respond. If, when MS-DOS External is running, a network connection fails due 
to a problem at the file server, this type of critical error occurs. The MS-
DOS External Mail program traps the error and stops moving mail on the failed 
connection, but continues to move mail on other connections. External tries 
to re-establish the failed connection and MS-DOS successfully reconnects if 
the condition that caused the critical error has been corrected.

In some environments, network redirectors become unstable following a 
critical error. There is a possibility that the MS-DOS External Mail program 
will not be able to re-establish the postoffice connection and will hang. If 
this occurs, the computer on which the External Mail program is running must 
be rebooted. Instead of manually rebooting the computer, you can specify an 
External Mail program option to reboot automatically. 

To specify automatic rebooting when critical errors occur, specify RebootOnCE 
in the EXTERNAL.INI file. For example:

[External]
RebootOnCE

C.3. Specifying X.25 Facilities and User Data
---------------------------------------------
This section describes how to specify X.25 facilities and user data for mail 
exchanged with other postoffices or mail received from Remote client users 
through an X.25 public carrier. To set up X.25 communications for Microsoft 
Mail, see Appendix F, "X.25 Settings for Mail," in the Microsoft Mail 
Administrator's Guide.

By adding the following entries to an External .INI file, you can indicate 
which facilities to initiate for an X.25 communication session. For 
information about creating an External .INI file, see Chapter 12, "Setting Up 
the External Program," in the Microsoft Mail Administrator's Guide.

You can specify one or more of these options to apply to all instances or for 
a specific instance. You can also specify the call user options for each 
postoffice being called. 

If you specify the same option as a shared instance and as a specific 
instance, External only initiates the specific instance. If, for call user 
data, you specify only a specific postoffice, the last call user data entry 
in the shared or specific instance is used. If you enter conflicting options 
or if options are missing, the External program uses the option it finds 
last. 

X25CallFacilities option

  Syntax: X25CallFacilities=[network/postoffice:]$value[$value]...

  Use X25CallFacilities to specify which X25 call facility to initiate. 
  For a list of call facility codes, see your X.25 manual.

  Specify the facility code in hexadecimal notation. Each hexadecimal value 
  must be prefixed by a dollar sign ($) and be a value from 0 to 9 and A to 
  F. You can specify up to 128 hexadecimal values. The maximum length cannot 
  exceed 401 characters.

  For example, to reverse the charges when communicating with the SERVER1 
  postoffice on LAN1, where the facility code is hexadecimal 01 and its 
  parameter is hexadecimal 01, you would specify 
  X25CallFacilities=LAN1/SERVER1:$01$01


X25CallUserData option 

  Syntax: X25CallUserData=[network/postoffice:]$value[$value]...

  Use X25CallUserData to specify the information to be validated by 
  External at the destination postoffice, or for call routing. For a list of 
  valid entries for call user data, see your X.25 manual.

  Specify the data in hexadecimal. Each hexadecimal value must be prefixed by 
  a dollar sign ($) and be a value from 0 to 9 and A to F. You can specify up 
  to 128 hexadecimal values. The maximum length cannot exceed 406 characters.

  You can specify this option for each postoffice if you need to. If you 
  specify both the postoffice and the data, the data you specify will be used 
  for validation. If you specify only the postoffice, External uses the 
  X25CallUserData specified for the shared instance. 


X25ListenFacilities option 

  Syntax: X25ListenFacilities=$value[$value]...

  Use X25ListenFacilities to specify which X25 listen facility to 
  initiate in a specify External instance. For a list of listen facility 
  codes, see your X.25 manual.

  Specify the facility code in hexadecimal notation. Each hexadecimal value 
  must be prefixed by a dollar sign ($) and be a value from 0 to 9 and A to 
  F. You can specify up to 128 hexadecimal values. The maximum length cannot 
  exceed 384 characters.

  For example, if facility code is hexadecimal 01 and its parameter is 
  hexadecimal 01, you would specify X25ListenFacilities=$01$01


X25ListenUserData option

  Syntax: X25ListenUserData=$value[$value]...

  Use X25ListenUserData to specify the information that External uses to 
  check against the incoming X.25 communication. 

  Specify the data in hexadecimal. Each hexadecimal value must be prefixed by 
  a dollar sign ($) and be a value from 0 to 9 and A to F. You can specify up 
  to 128 hexadecimal values. The maximum length cannot exceed 401 characters.

  If this option is specified, the incoming call request packet must contain 
  identical user data; if it does not, the call is rejected.


Troubleshooting X.25 Facilities and User Data

If you use the LogVerbose option, all facility and user data is recorded in 
the SESSION.LOG file.

If you do not enter the syntax of the .INI entry correctly, External stops 
with the message "Invalid option specified in .INI: <option>." If the .INI 
entry is syntactically correct, but the values you specified are 
incorrect, a connection failure at the X.25 session layer could occur. 

Note: Postoffices not defined or correctly specified in the Administrator 
program, or incorrectly specified in the .INI file, cause External to stop.

If you use the LogVerbose option, a failure at the X.25 session level is 
recorded and displayed on the External Remote Postoffice screen. The logged 
information consists of the error type, such as a Call error or Read error, 
and three or more octets of data. The first octet is the cause code, the 
second octet is the diagnostic code, and the remaining octets are the Eicon 
or Atlantis internal error codes.

Note: An octet is a two digit hexadecimal value.

For example, using the Eicon board, if a call failed, the following error 
code could be displayed:

  Call error:
  00 42 12

The cause code of 00 and diagnostic code of 42 mean that a TD cleared the 
call due to an invalid facility code (such as rejecting a reverse charge call 
request). The third group of data, octet 12, specifies the Eicon or Atlantis 
specific internal error code. The Atlantis internal error code is two octets. 
The internal error code assists Microsoft Product Support Services (PSS) in 
solving your problem.

The Atlantis version displays 4 bytes of data instead of 3. The first 2 
bytes are the cause and diagnostic as per X.25 specifications. The last 2 
bytes describe the return code made by the Atlantis X.25 services. This code 
used by PSS. 


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

This section covers the following topic:

   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
----------------------------------------------
If a user has a problem accessing files from another program that were 
created or saved by Microsoft Mail, ask him or her to remove any spaces in 
the filename when saving the attachment in Microsoft Mail. 

D.3. Incompatible Support Files 
-------------------------------
If a user receives the message "Error file is not accessible. Check server 
connection", it 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 graphic 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
====================================================

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 their local hard disk, they 
must run SHARE.EXE before starting the Mail Windows-based client. Mail will 
not start if they have 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 your 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 Window's 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 their 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 above. 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 their 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 
their message file when they dial 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 check for new mail every 3 minutes, they 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 they are 
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 running the Setup 
program, where the user is not be 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
===========================================================

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 files 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 Presention Manager clients are on the 
disks labeled Windows-based Client, 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 their 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 
their message file when they dial 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 check for new mail every 3 minutes, they 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 they are 
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 Files 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 their 
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 carat (^), and the file extension. 

The carat 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 they minimize 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
================================================

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, they select the Save My Name And Password 
option button in the Preferences dialog box. 

If the server goes down while the user is using Mail, they can reconnect 
without leaving the Mail application. To do so, they 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 want 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.

