

            ------------------------------------------------------
                  Microsoft Mail Multitasking MTA version 3.3
                                README File
            ------------------------------------------------------


                  (C) Copyright Microsoft Corporation, 1991-94


This document (README.TXT) contains important information that supplements 
the Microsoft Mail Multitasking Message Transfer Agent Administrator's Guide.

This document covers the following topics:

   A. How to print these notes
   B. Information for Microsoft Mail 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. INFORMATION FOR MICROSOFT MAIL ADMINISTRATORS
================================================

This section covers the following topics:
  
   1. Directory of text files installed by Setup
   2. Setting up the Eicon Gateway software
   3. Specifying X.25 facilities and user data
   4. Running multiple External X.25 instances using
      the Eicon OSI LAN Gateway

B.1. 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
  ----          --------
  DISPATCH.TXT  Dispatch program error messages for MS-DOS and OS/2
  EXTERNAL.TXT  External Mail program messages for MS-DOS and OS/2
  OS2MTA.TXT    This file

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

B.4 Running Multiple External X.25 Instances Using the Eicon OSI LAN Gateway
 ---------------------------------------------------------------------------
If you run multiple instances of the OS/2 External Mail program that access 
X.25 services through Eicon's OSI LAN Gateway (CommType=X25Eicon), External 
could halt when making connections and display an OS/2 system TRAP D message.

If you have this problem, do one of the following:

A. Obtain version V3R1 or later of the Eicon OS/2 Redirector software.
B. Run two instances of OS/2 External to communicate through the Eicon
   OSI PC Gateway.
C. Run a single instance of External to communicate through the Eicon 
   OSI LAN Gateway.

