This file lists error messages for the EXTERNAL program. Messages are 
listed in alphabetical order. System messages for returned mail are 
documented in the Microsoft Mail Administrator's Guide under "System Log" 
in Appendix B, "Log Files."

For information on specifying the options correctly, see the option 
descriptions in Chapter 12, "Setting Up The External Mail Program" 
of the Microsoft Mail Administrator's Guide, or in Appendix A, 
"External Options" in the Microsoft Mail Multitasking MTA 
Administrator's Guide.


	     --------------------------------------


A connection to this server already exists.
   This is the second time the connection to this postoffice has been 
   requested. If you specified dynamic drive connections, check to see 
   if the connection was established prior to running the External program. 
   Also check to see that you did not specify the connection twice in the 
   INI file or on the command line.

A critical error has occurred. <filename>
   Check that there is still a connection to the server and that the server 
   is not full. If you are reading or writing to a floppy disk, check that 
   the disk is in the drive, that it is not write-protected, and that the 
   drive door is closed.

A critical error has occurred.
X.25 Diagnostic from <name> operation
<description>(<decimal code>)
   The X.25 call cannot be made because the operation <name> failed with 
   an X.25 description of <description> and a diagnostic code <decimal code>
   For more information about this problem, check your X.25 manual.

An unknown error code <error code> was returned.
   An error was returned from Novell Netware. For further information, 
   consult your Novell documentation.

<net/postoffice> Busy
   The specified postoffice is busy.  Try connecting later. 

Command line error: first drive greater than last drive.
   Check how you specified the drives with DrivesDirectPO (-D). The drives
   must be specified in ascending alphabetical order. For complete
   description of the option, see Chapter 12, "Setting Up The 
   External Mail Program" in the Administrator's Guide.

Connection end. Disconnection.
   The connection between your postoffice and the external postoffice ended. 
   This is due to a disconnection either at your postoffice or the other
   postoffice.

Connection end. Disk storage full.
   The connection between your postoffice and the external postoffice has 
   ended because the disk storage of your postoffice or of the external 
   postoffice is full and no further mail transfer can take place.

Connection end. Protocol violation.
   There has been an error in the file transfer protocol. This happens 
   if a disconnection occurs at a critical point in the protocol. Try 
   the operation again.

Connection end. Time out.
   The connection between your postoffice and the external postoffice (or 
   gateway or Remote client user) has ended because no response was detected 
   from the communication device within the allocated timeout period.

Could not find mail system data files on drive <drive letter:>.
   Make sure the current directory on the drive specified with the 
   DrivesDirectPO (-D), DrivesDynamic (-F) or DriveHomePO (-H) option 
   is the directory containing the Mail system data files for the postoffice. 
   
   For example, if the External Mail program is to dispatch 
   mail for three postoffices on drives M, N, and O, the -DMO
   option can be used. Drives M, N, and O must point to directories 
   containing Microsoft Mail data files. To check that the directories
   contain the data files, use the MS-DOS DIR command for a directory
   listing of each drive. A list of subdirectories should appear, 
   starting with the ATT directory.

Could not login to the server.
   External could not log into the server. Check the log_in name and
   password you specified on the DrivesUNC or DrivesNovell option.
   If the problem still occurs there may be a problem with the connection.

Datagram notification initialization failed.
   Ordinarily, a datagram notifies the External Mail program of urgent 
   mail. This error occurs when there are problems with memory allocation 
   or a problem due to NetBIOS. For LAN-Manager compatible networks, 
   ensure that the network has been started. For Novell networks, ensure 
   that NetBIOS is loaded.

Disk error encountered while inserting data into .MBG from <filename>
   The disk used to connect the postoffice had an error, or is full. 
   There may also be too many messages in the .MBG file.

Drive connection failure. Unable to prompt for external login ID. 
   An attempt to connect to another post office failed because the network 
   drive could not be connected.  

Drive in error: <drive letter>
   The External Mail program cannot link to the file server on the
   specified drive. Either the server is down or there is a hardware problem. 
   No mail will be transferred to and from this postoffice.

Drive is either local, used or greater than LASTDRIVE.
   The specified drive has already been assigned or comes later in the 
   alphabet than the drive specified with the LASTDRIVE setting in the 
   CONFIG.SYS file. Select another drive or update the LASTDRIVE setting.

Error: Duplicate postoffice serial numbers found: [<serial number>]
Postoffices:
<network1>/<po1>
<network2>/<po2>
   The External Mail program has detected the presence of two postoffices 
   with the same serial number. Make sure you do not have two drives 
   pointing to the same postoffice. If your postoffices are on permanent 
   drives, make sure you do not accidentally also define one of those 
   permanent drives as a dynamic drive.

Error: dynamic drive letter same as permanent.
   The dynamic drives that were specified are the same as the permanent 
   drives. You must specify two dynamic drives that are not permanent drives.

Error: External requires search rights.
   For information about assigning rights, see Chapter 2, "Preparing to Use 
   Mail on the Network" in the Administrator's Guide.

Error: File not found. TRANSFIL.GLB
   This is the transparency array file used for character conversions.  
   Run Update to restore this file.

ERROR: Insufficient memory to run External.
   The workstation must have at least 640K of conventional memory and 
   350K of extended or expanded memory. Additional memory will be required 
   to handle additional postoffice connections, heavy message traffic, and 
   high speed transmission.
  
   Free some memory and try the operation again.

Error: invalid dynamic drive specified.
   Check that the two drives that you specify with the DrivesDynamic (-F) 
   option are valid MS-DOS drives on the workstation.

Error: invalid password or network name is used.
   Check that the postoffice with which you are attempting to establish 
   communications requires a password. Ask the administrator of the external 
   postoffice for the password, and enter it into the Administrator 
   program External-Admin Setup screen for this postoffice. Then try again 
   to establish a communication session.

   For LAN-Manager compatible networks, also check that you have correctly 
   specified the server name and share name when setting up your network 
   environment.

Error: invalid permanent drive specified.
   Check that the drives specified with the DrivesDirectPO (-D) option 
   are valid MS-DOS drives.

Error: Mailbox file close error.
   There was an error when External was closing the .MBG file. 
   There may possibly be database corruption.

Error: Memory problem.
   The program requires more memory. Free some memory and try the operation 
   again.

Error: on log file open.
   The External Mail program cannot open the log file. Check that the file 
   is not being edited and that the DirectDrivesPO (-D) and DriveHome PO (-H)
   options correctly specify the home postoffice.

Error opening LOG\SYSTEM.LOG on <path network po>
   Couldn't open the system log on another postoffice. Check that 
   network connection to that post office is valid and try again.

Error: Network Operating System not supported.
   Microsoft Mail supports LAN Manager compatible networks and Novell 
   networks. If your network is not one of these types, you will not 
   be able to operate Microsoft Mail.

Error: PC postoffice version.
   External attempted to connect to a postoffice with an incompatible 
   Mail database. You can fix the problem by upgrading the postoffice 
   with a more recent version of Mail.

Error: Script file not found.
   The External Mail program cannot find the script file that you specified. 
   If you used the CommScript (-T) option to specify the script file, 
   make sure that the filename is correct. Also make sure that the script file
   is in the home postoffice GLB subdirectory on the drive where the data 
   files are located. 

   If you do not use the CommScript (-T) option to specify the script file, 
   make sure that the DEFAULT.SCR script file is present in the home 
   postoffice .GLB subdirectory on the drive where the data files are located.

Error: single postoffice version.
   External attempted to connect to a postoffice without the ability
   to make multiple connections. You can fix the problem by upgrading
   the postoffice with a version of Mail which offers multiple connections.
   
Error: the dynamic drive letters cannot be the same.
   The two drive letters that you specified in the DrivesDynamic (-F) option
   are the same drives. You must specify two different drives for dynamic
   connections.

Error while resolving the script label.
   An undefined label was found in the script file. Edit the script file 
   to correct the error and re-compile it before trying again.

Error: Working Model Postoffice version.
   The postoffice you specified is a demonstration postoffice created
   by a demonstration copy of Microsoft Mail. External can connect 
   postoffices created or upgraded with a purchased copy of Microsoft Mail.
     
Failed to open NETWORK.GLB file.
   External failed to open the NETWORK.GLB file. Try the operation
   again. If the problem persists, check that there is still a 
   connection to the server. Also check to see if the server is
   not full.

Failure reading from <queue>
   External failed while reading from mail from this queue. Try
   the operation again. If the problem persists, check to see if
   there is still a connection to the server. Also check to see
   that the server is not full.

Failure sending control data during message exchange.
   External failed while sending control data during message exchange. 
   Try the operation again. If the problem persists, check to see if
   there is still a connection to the server. Also check to see
   that the server is not full.

Failure sending data during message exchange.
   External failed while sending data during message exchange. 
   Try the operation again. If the problem persists, check to see if
   there is still a connection to the server. Also check to see
   that the server is not full.
 
Failure to initialize connection.
   External was unable to start the asynchronous or X25 connection protocol.   
   For modem connections, make certain that the modem is properly connected and 
   that a valid script file is being used. For X.25 connections, make certain that 
   the re-directory gateway is functioning. Make sure the modem is turned on, 
   and that you have specified the correct options for the communication device. 

Failure to initialize modem session.
   The modem has not been successfully initialized. Check that the modem is 
   turned on and that the modem cable is not defective. Also, make sure that 
   the modem is plugged into the correct communication port.

Failure to initialize modem session.
Check modem and script file.
   Make sure the modem is plugged in and turned on. Also make sure you are 
   using a valid script file. If problems still persist, verify that the 
   communications port and baud rate settings are correct. If the 
   error occurs again, restart the External, with the Verbose (-V) 
   option to ensure the modem is responding correctly.

Failure to initialize X.25 session.
Check redirector gateway and INI parameters.
   The X.25 session couldn't be started. Verify that redirector gateway 
   is running. Also make sure you specified the CommType and 
   X25SubAddress correctly. Also verify the X25PortNumber option 
   if you used it.

Failure to open script file: <filename>
   External failed while opening this script file. Try the operation
   again. If the problem persists, check to see if there is still a 
   connection to the server. Also check to see that the server is not full.

Failure to properly increment BIOS date.
  This is a warning that the local real time clock did not advance 
  the date properly.  If this problem is detected, External advances 
  the date to compensate. 

File is possibly corrupted: <filename>
  An External overlay file has been corrupted. To fix the problem, re-install 
  the External program.   

<filename> was not found.
  During a mail or attachment transfer, a file wasn't found. This indicates a 
  corrupted Mail database. Contact PSS.

Get group list failed.
   Try the operation again. If the problem persists, check that there is 
   still a connection to the server. Also check that the machine running 
   the External Mail program has sufficient memory available. Make sure 
   that there are no memory-resident programs installed.

Get user list failed.
   Try the operation again. If the problem persists, check that there is 
   still a connection to the server. Also check that the machine running the 
   External Mail program has sufficient memory available. Make sure that 
   there are no memory-resident programs installed.

Home Postoffice not in permanent drive range.
   The drive you assigned as the connection to the home postoffice with 
   DriveHomePO (-H) is not one of the permanent drives you assigned with
   DrivesDirectPO (-D). You must assign a permanent drive to connect the 
   home postoffice.

Incorrect script version.
   This version of the External Mail program requires a new version of the 
   script file. Copy a new version of the script file from the GLB 
   subdirectory.

Initializing data structures. Could not connect to drive.
   During the enumeration of remote post offices, External could 
   not make a network connection. Verify that network connections 
   are valid and try again.

Instant notification will not be active.
   Check that NetBIOS is loaded onto the machine running the External 
   program so that users receive instant notification of their mail.

Insufficient network resources. (COMMANDS)
   This is a NetBIOS error message. The workstation on which you are trying 
   to load the External program is configured with insufficient 
   network commands as specified with the net start command. Restart the 
   workstation with a larger /cmd parameter.

Insufficient network resources. (NAMES)
   This is a NetBIOS error message. Too many network names are in use on 
   the workstation where the External Mail program is running.

Invalid option specified:<option>
   The option that you specified is not valid. Check the option.

Invalid option specified in .INI: <option>
   This option you specified in the .INI file is not valid. Check the 
   syntax. 

Invalid path.
   The path you specified to the postoffice is invalid. Check to see that
   you specified it correctly. 

Invalid postoffice serial number on drive:<drive letter>.
   The postoffice on the specified drive has an invalid serial number. No 
   mail will be sent to this postoffice during this session.

Invalid receive log filename specified with -MR option. Using LOG\RECV.LOG.
   An invalid log file was specified with the LogReceive (-MR) option, so
   External will use the LOG\RECV.LOG file as the log file to hold received 
   messages.

Invalid script file
   Check that you are using a valid script file. If necessary, make 
   corrections to the file and then compile it again.

Invalid sent log filename specified in -MS option. Using 
LOG\<log file name>.LOG. 
   An invalid log file was specified with the LogSent (-MS) option, so
   External will use the LOG\SENT.LOG file as the log file to hold sent 
   messages.

Invalid value specified for: <option>
   The value you specified for this option is not valid. Check the value.

Invalid value specified for MaxLanMailSize=
   The value you specified for this option is not between 0 and 999,999
   kilobytes. Correct the value and run the program again.

Lost carrier.
   The modem carrier has been lost.  This usually indicates that the 
   External servers have stopped.  Try connection later.


Time-out occurred while reading data at the serial layer.
   The serial connection between two postoffices was dropped 
   because no new data was received for a while. Check the modem,  
   and cabling connections. This error can also be caused by the other  
   server running too slowly, crashing, or being interrupted by another 
   process.

Time-out occurred while writing data at the serial layer.
   The serial connection between two postoffices was dropped because 
   no new data could be written for a while. Check that the modem, and 
   cabling connections are correct.  This error can also be caused by 
   the other server running slow, crashing or being interrupted by another 
   process for an inapproprate amount of time. 

Mail transfer failed.
   Try the operation again. If the problem persists, check that there is 
   still a connection to the server. Also check that the server is not full.
   If the problem continues, check for a critical error such as a disk 
   failure.

Message was not delivered due to missing routing file.
   There may have been an interruption in transmitting the message. Instruct
   the user to resend the message the message. If the problem persists, the
   file may be corrupted.
   
Network name not found.
   The network name you specified was not found. Check the exact 
   spelling of the network name and try the operation again.

<net\po>Sign-on ID or password incorrect.
   Check the ID and the password you used to signon to the file server. 
   Check the spelling and try the operation again.

<network>/<postoffice> No answer.
   The postoffice with which you have attempted to establish communications 
   is busy in a communication session or is not set up to communicate with 
   your postoffice. Try again later.

No dial tone.
   The modem could not detect a dial tone. Check the connections 
   between the modem and the telephone line. If problem persists, 
   contact your local phone company.

No file connections are available.
  ???

No mail.
  No mail was destined for the specified postoffice. This is a normal 
  occurrence.

No X.25 session.
The X.25 session was unable to commence.  
   Check redirector gateway and X.25 options.


Not enough memory to load: <filename>
   To run the External program, the workstation requires at least 640K of
   and 350K of extended or expanded memory. Additional memory is required 
   to handle more postoffice connections, heavy message traffic, and high 
   speed transmission.

   Free some memory and try the operation again.
   
Notice in LOG\SYSTEM.LOG on: <path network po>
   There is a notice pertaining to your postoffice in the SYSTEM.LOG file 
   located in the LOG subdirectory of the postoffice data files directory 
   for the specified postoffice. Read this notice to identify the problem.

Out of file handles loading: <filename>
   Try increasing the FILES= parameter in the DOS CONFIG.SYS file.

Out of memory parsing command line.
   To run the External program, the workstation requires at least 640K of
   and 350K of extended or expanded memory. Additional memory is required 
   to handle more postoffice connections, heavy message traffic, and 
   high speed transmission.

   Free some memory and try the operation again.

Postoffice modem connection attempted with an unknown serial number: 
<serial number>.
   A postoffice with a serial number that is not recognized by your 
   postoffice has attempted to establish communications with your postoffice. 
   Check the serial number in the message with any serial numbers in the 
   Administrator program External-Admin Setup screens. You may have 
   entered the serial number incorrectly.

Postoffice record retrieval failed, File: <file name>.
   Try the operation again. If the problem persists, check that there is 
   still a connection to the server. Also check that the machine running 
   the External Mail program has sufficient memory available. Be sure that 
   there are no memory-resident programs installed.

   If the problem continues, the specified file is either corrupted or 
   does not exist. Restore a backup of the file to the server. Make sure 
   that it is copied to the correct subdirectory.

Releasing dynamic drive <drive>:
Failed. Error code is <error number>
   A Novell Netware error occurred releasing dynamic drive. Consult the Novell
   documentation.

Script generation: out of memory.
   The workstation must have at least 640K of conventional memory and 350K of
   extended or expanded memory. Additional memory will be required to handle
   additional postoffice connections, heavy message traffic, and high speed 
   transmission.

   Free some memory and try the operation again.

Server busy. Will try later.
   The server that you are trying to access is busy. Another communication 
   attempt will be made later.

SERVER.GLB file not found on home postoffice.
   You create the SERVER.GLB file with the Dynamic Drive Administrator 
   program. You must run this program first if you want to use dynamic 
   drives assigned by this program in External. The SERVER.GLB file must 
   be on the home postoffice drive. Check that you have correctly
   specified that with DrivesDynamic (-F) option when you start External. 
   
Server <server name> not accessible.
   The specified server cannot be accessed. Either the server is down or 
   there is a connection problem. Try again later when server is up and 
   connection is re-established.

Sharing violation loading file <filename>
   An overlay file cannot be used because it was locked by another process.  
   Verify that no other process are accessing the External executables 
   and try again.

Sharing violation opening file <filename>
   An attachment or mail file can not be transferred between postoffices 
   because the file was locked. Check that another process or client is not 
   using the file and try again.

<sign-on id>: Sign-on ID or password incorrect.
   The sign-on ID or the password of the postoffice for which you are 
   attempting to establish a communication session is incorrect. Ask 
   the postoffice administrator for the correct password and sign-on ID, 
   and type these when prompted in the Administrator program External-Admin 
   Setup screen for this postoffice.

Signon failed.
   A remote user was unable to sign on.

Statistics update failed.
   Try the operation again. If the problem persists, check that there 
   is still a connection to the server. Also check that the server is 
   not full. If the problem continues, check for a critical error such 
   as a disk failure.

The address type [<address type>] is not supported.
   During the transmission of the mail, an address type was encountered 
   that isn't supported.   

The break relative option (-BR) cannot be used in conjunction with the 
break date (-BD) or break time (-BT) options.
   When you start the External again, be sure to only use the BreakRelative
   (-BR) option. Do not use the BreakRelative (-BR) option with the 
   BreakDate (-BD) or the BreakTime (-BT) options.

The connection ID table is full.
   You have exceeded the maximum of connections allowed from a workstation 
   to a server (the maximum is 8 connections to the same server). 
   Solve this problem by releasing one or more connections.

The desired file server is not found.
   The file server you specified cannot be located. Check to see that
   you specified the name correctly. Also check to see that the server 
   is connected; if it is not, try again later.

The string size is invalid.
   A string in a script file is too long. Edit the script file to correct
   the problem, then re-compile it before trying again.

This program can only be used on a Working Model Postoffice.
   You are attempting to connect to a demonstration postoffice. External
   can only connect postoffices which are created or updated with a 
   purchase copy of Microsoft Mail.

This program is incompatible with the postoffice.
   This version of the External program is not compatible with your 
   postoffice. Upgrade the postoffice with a more recent release
   of Microsoft Mail.

To use dynamic drives, DYNADMIN.EXE must first be run.
   If you use the DrivesDynamic (-F) to start External program, 
   program, you must run the Dynamic Drive Administrator program, 
   or specify the connections with DrivesUNC or DrivesNovell. If
   you decide to use the Dynamic Administrator program to assign
   dynamic drives, you must run it before you run the External program.

Unable to access <filename>. Check access rights.
   Mail cannot be transferred to this postoffice, because its files are 
   designated as read-only. Change the access rights on the postoffice 
   file server to read/write and try again.

Unable to allocate memory.
   External is unable to allocate memory. Free some memory and try again. 

Unable to find file: <filename>
  An overlay file is missing.  Re-install the Server Agents to obtain
  a copy of the file. 
  
Unable to load all of the dynamic postoffices.
  Too many dynamic postoffices are specified. Reduce the number of 
  dynamic post offices and try again.

Unable to load stack: <stack name>
   The overlay file for the requested stack is corrupted or missing. 
   Re-install the Server agents to obtain a copy of the file.

Unable to pack mail headers for transmission to the remote user.
   This error indicates a corrupted Mail database. Contact PSS.

Unable to read mail contents.
   This error indicates a corrupted Mail database. Contact PSS.

Unable to read mail headers for mail items.
   This error indicates a corrupted Mail database. Follow the
   procedure in Appendix G "Troubleshooting" in the Microsoft Mail
   Administrator's Guide. If this fails, contact PSS.

Unable to resolve group address while delivering mail.
   A group was not found during the delivery of mail. This
   indicates a corrupted mail database. Contact PSS.

Unable to send message text.
   This error indicates a corrupted Mail database. Contact PSS.

Unable to start new thread.
   When running in OS/2, External has run out of memory or system resources.  
   If this occurs, increase the value of the THREADS= statement in your 
   CONFIG.SYS file.

Unable to update COPIES while delivering mail.
   Check that the .MAI files are not locked open by External or clients. 
   Then try again.
   
Unknown Command line option: <option>
   The option that you specified is not valid. Check the option. 
   For valid options, see the option descriptions in Chapter 12, 
   "Setting Up The External Mail Program" of the Administrator's Guide.

Unsupported driver specified.
   Either this is a post 3.2 script file or the script file is corrupt.
   Recompile the MDM file and try again.


User Instant Notification will not be active (NetBIOS loaded?).
   For a user to receive instant notification of priority 5 mail, 
   check that NetBIOS is running on the machine dedicated to the 
   External Mail program and on the user's workstation.


WARNING: ignoring Dynamic attachment information specified by Dynadmin.exe
    The drives you specified for postoffice connections in the 
    Dynamic Drive Administrator program, are being replaced by 
    those you specified with the DrivesDynamic (-F) option.
   

WARNING: Unable to find specified Instance INI section.
   External cannot find the instance you specified with the InstanceName 
   option. Check the name you assigned the instance; for example 
   [External-Modem]. The name you specified with InstanceName must 
   match exactly with how it is specified in the INI file.


WARNING: Unable to open EXTERNAL.INI, check INI directory
   External cannot read the INI file. The server connection may have failed, 
   the file may not be located in the path expected or specified, or the user 
   access rights may be insufficient.
   
   Check to see that there is still a connection to the server. Unless you 
   specified another filename with /IniFileName=, External expects the 
   EXTERNAL.INI file to be in the INI directory of the home postoffice. 
   Check that you specified the path correctly. For a Novell network, 
   check that the necessary rights to access the server have been assigned.

WARNING: Unable to open specified INI File.
   External could not find the .INI file you specified on the command line.  
   Check that the file exists and that you specified the /IniFileName
   option correctly.











