------------------------------------------------------------------------
Subject : Bug and flaws in MTA
Target : All users
Date : 02-22-93
Rev. : 1.00 / 02-22/93
------------------------------------------------------------------------
What to do if you have software problems with MTA. You should do the
following:
- Send a message to Rob van.hoeven (mind the point) on 2:512/100.5
which describes the problem as detailed as possible;
- After the initial contact, you are probably asked (by me) for the
following:
- MTA.CTL
- MTA-debug file (see later)
- Exact call to MTA (from any exit or the command-line options)
- You can speed up the process when you include these matters with the
initial message !
MTA can create a debug-file. If you do so, MTA will run VERY slow !!!!
The syntax to create such a debug-file is as follows:
- Add the /DEBUG command-line option to the call to MTA. You can,
optionally, add a drive/directory and filename to this option (for
example /DEBUGC:\TEST\MTA.DEB). This is the preferred option when you
run MTA over various directories, otherwise it is possible that MTA
will create debug-files in various directories. MTA will append data
to previous debug-files if possible;
The debug-file is very big when you convert MANY files. If the problem
has to do with ONE (or a few) files, try to create a debug-file for
only THIS (or these) files and not for a complete conversion with all
bells and whistles. MTA will run VERY slow when you create the debug
file (almost everything I want to know will be included in the debug
log).