Beijing Paradise BBS Backup/PARADISE.ISO/software/BBSDOORW/UCPCK104.ZIP/UUCPCHK.DOC

Text File | 1995-12-06 | 7.9 KB | 166 lines

UUCPCHK.EXE Version 1.04 Copyright (c) 1995 by James J. Murphy

This program is Freeware.  If you have any suggestions, complaints,
or bug reports, then I may be contacted via Internet E-Mail.

My address is: [e-mail]
   - or -      [e-mail]

STANDARD DISCLAIMER

Run this program at your own risk.  My Fido Net here in the Republic
of Panama is presently using this program to check UUCP addressed
Internet E-Mail for people subscribing to LISTs or attempting to FTP,
or download WWW pages.  I take no responsiblity for any damage done
to your computer hardware, software, or message bases, by your use
of this program.

WHAT THIS PROGRAM DOES

This program will check all messages in your Netmail (.MSG)
directory addressed to UUCP (or an optional additional name),
that do not have the HOLD or SENT flag set, against a list of BAD
addresses, or address fragments (ftp, www, etc.).  If it finds any,
it will set a flag in the message of either HOLD or SENT.  This
stops the message from being sent and allows you to manually check
the message, or you can use a utility like NETMGR to BOUNCE these
messages back to the sender.  It also checks for the presence of an
'@' symbol (or additionally, AND optionally a BANG '!' symbol) in
the address, and if missing, flags the message as bad.  It checks
for a comma ',' in the address (not allowed), and will flag that
also.  If there is no address after the TO: line in the text of the
message, or more than one space after the TO:, or no TO: at all,
then it will also flag the message.

While running you will see the word 'Working' appear, and for each
message processed you will see a Dash (-) appear.  If a message is
found that has improper addressing you will see a Plus-Sign (+)
appear, and if a possible corrupted message is found, then you will
see an Asterisk (*) appear.  A report is then shown showing the
total messages processed, and the number of BAD (Improperly
Addressed) messages, and the number of corrupt messages.  If you
have the LOG feature turned on then BAD and CORRUPT messages will be
described in the log file.

Either put the contents of the archive in its own directory, or put
it into the same directory as NETMGR.  All the files begin with the
name UUCP, so they are easy to sort out from NETMGR files.

Enclosed are the following files:

        UUCPCHK.EXE     The main program that does the work.
        UUCPCHK.CFG     A sample config file that must be edited
                        to match your system.
        UUCPCHK.BAD     A sample BAD address file.  Edit it to
                        suit your needs.
        UUCPCHK.DOC     This file you are reading.
        UUCPCHK.LOG     An example of the LOG file.
        UUCPCHK.NAM     An example of the NAM file.
        UPGRADE.TXT     Important Info if Upgrading from an older
                        version.

The first thing you should do is edit UUCPCHK.CFG with a text
editor, and make sure you have your name in there, and the path to
your Netmail (.MSG) directory.  I would use the LOG function, at
least at first, to see which messages are flagged as BAD.  The log
can be accumulated until it fills up your hard disk, or you can have
it sent to you as a netmail message using Xrobot or some other
message making program, and then delete the log.  The log is NOT
created unless a BAD message is detected.  The config file is
commented, to assist you in changing it.  Blank lines or lines
preceeded by a semicolon are ignored.

The UUCPCHK.BAD file contains bad Internet addresses or segments of
addresses, that are checked against the TO: line in the text of UUCP
messages, and if they match, that message is flagged either with a
HOLD flag or SENT flag (see UUCPCHK.CFG).  Edit this file to suit
your needs.

After you run the program and the bad messages are flagged, you can
either check them out manually, or use a program like NETMGR to
check for these flagged messages, and 'bounce' them back to the
sender.

UUCPCHK.EXE should be run with either one or two parameters.

Examples:

UUCPCHK.EXE  D:\FD\NETMGR
UUCPCHK.EXE  D:\RA\FD\UUCPCHK UUCPCFG2.CFG
UUCPCHK.EXE

The first parameter is necessary, and it tells the program where the
config file and  bad address file is located, and where to put the log
file.  The second parameter is optional.  The name of the config file
defaults to UUCPCHK.CFG, but you can make it use a config file with
a different name by placing the name as the second parameter.  If
you run the program with NO parameters, you will be shown a help
screen.

If you have 2 or more Gateway Names other than UUCP, then you could
run UUCPCHK a number of times, specifying a different CONFIG file
with each invocation of the program.  Each CONFIG file would specify
a different additional Gateway Name.  It runs very quickly, so the
running time should not be a major factor.

When entering the paths in the config file or on the command line,
DO NOT put a trailing backslash at the end of the paths.

You may optionally create a file called UUCPCHK.NAM which should
contain names, first and last, one full name to a line.  These names
are NOT checked against the UUCPCHK.BAD file for bad internet
addresses.  These are privileged people that you trust not to
subscribe to lists, or whatever you are trying to prevent the others
from doing. This file is NOT necessary to use UUCPCHK.  If it is
present in the UUCPCHK directory (where the Config file is located),
it will automatically be used.

The files UUCPCHK.CFG, UUCPCHK.BAD, and UUCPCHK.NAM can have blank
lines and lines starting with a semicolon ';' which will be ignored,
this allows the commenting of the file(s) if necessary.

You can have the flagged (as BAD) messages identified, for
processing by NETMGR.  Line 9 in the CONFIG file allows you to have
an error number placed into the Subject line of the message header.
The error will be shown by the following string: #ERR1# to #ERR8#,
and can be searched for by NETMGR to send a customized (for the
particular error) message identifying each type of error.  A list of
the number and types of errors is shown below.

  #ERR1# - Error 1: Incorrect Gateway Name
  #ERR2# - Error 2: Disallowed Address in To: line
  #ERR3# - Error 3: Address not on To: line
  #ERR4# - Error 4: Two or more Spaces between To: and Address
  #ERR5# - Error 5: No To: Line
  #ERR6# - Error 6: No @ Symbol in To: line
  #ERR7# - Error 7: Comma in To: line
  #ERR8# - Error 8: No @ Symbol or ! Symbol in To: line

I will explain some of the Errors here.  #ERR1# means that a Gateway
name such as 'UUCP [1:135/292.1]' was entered on the To: line of the
message header (I saw this on my BBS).  Only 'UUCP' should have been
entered.  #ERR2# means the To: line in the message Text had an
address that matched a BAD address in the UUCPCHK.BAD file.  This
user may have tried to subscribe to a LIST or FTP a file. #ERR3#
means the To: was present, but did not have an address after it.
#ERR8# will only be shown if you specify in the CONFIG file that the
BANG Symbol '!' will ALSO qualify a message as a GOOD Internet
address.

Note: UUCPCHK will always NOT check a message with the HOLD or SENT
flag set, but WILL check a message with #ERR as the first four
characters in the subject line, if you do not have ERROR as the
parameter in Line 9 of the config file.  In other words, if you have
the config file Line 9 set to ERROR to add an error identifier to
the subject line of bad messages, then UUCPCHK looks for #ERR on the
subject line, and if found, will not check the message again.  If
you have NONE for Line 9, then it DOES NOT check the subject line
for the string #ERR.

This program does not utilize SHARE, or any kind of file or record
locking in a multitasking environment, so care should be taken to
make sure there are no conflicts with another program editing or
writing a .MSG file at the same time this program is checking your
message base.