home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 2 BBS
/
02-BBS.zip
/
RAIDP100.LZH
/
STATUS.TXT
< prev
Wrap
Text File
|
1990-01-01
|
34KB
|
627 lines
00.31
- This is the LAST CHANCE beta. If no bugs are reported, v1.00
will be released via the SDS on January 1. The only change will
be to recompile the program with the v1.00 signon. So now's the
time to send in those cards and letters if something isn't right.
- Yet another offering for the "one zone isn't enough" crowd ;-).
This time an INTL line will be generated in Raid replies if
the requestor's zone doesn't match either the aka zone selected
or the primary (first address) zone.
- Corrected message body password length test in response mode
so 8 character password is allowed.
00.30
- Response mode execution (-r switch) now doesn't read tic.cfg
unless there's netmail to process.
- Added "TidyNodes" configuration directive. If present all
distribution lines within area blocks in tic.cfg will be
tidied up by lining the fields up vertically the same as
add always does on the line(s) added. Of course the tidied
data will only be output if there's an update. Still no sort.
- Correct test for A (aka) present in flag field. Will now
correctly insert A# in flag field for remote adds when an
aka value is given on address/aka directives:
Address 123:456/789 6
All remote adds addressed to 123:456/789 will have A6 added
to the flag field if an aka is not already defined in the
flag field for the requestor. The aka value is a single
hex digit that corresponds to the Tick control file "aka"
directive. (see Tick documentation)
- Reset "from a point" flags before processing each netmail msg.
- Point processing changed again. If the origin net address and
the destination net address are both configured as addresses or
akas and the message body contains a '^AFMPT #' kludge line (and
pointnet is defined) the message is processed as point traffic.
The reply will always be shipped to the originator's net address
(.point). That way, if I'm 1:270/101 and 123:456/789, point 1
can be 1:270/101.1 or 123:456/789.1 and address requests to me as
1:270/101 or 123:456/789. It's still necessary to have "access"
directives for the point in any zone it will be using. If you
want to restrict a point to only one zone just configure it that
way. If you or your point has an identity crisis (or 1:270/101.1
and 123:456/789.1 are different points) you can "make it so".
Flexible enough? Or just confusing?
00.29a
- Corrected test for message to raid already processed.
- Reset areas per line to configured value before processing each
new message.
00.29
- Beginning with this *test* distribution I'm using the full MC C
compiler rather than the QC compiler. It's time to start testing
in a form that approaches what will be released. Still no
optimizations; that's next.
- Added DIRECT to all NetMail behavior flag selections. Your
packer must support the direct mail flag.
- Corrected several coding errors in AKA and kludge line
(^AINTL and ^AMSGID:) processing to try to make the program
zone "smart" rather than only zone "aware".
Address matching has this flow (sort of)...
- Match destination net/node against net/node in address/aka
list ignoring zones. If any addresses match (and other
header data is validated) the message will be processed.
The zone from the matching address/aka item becomes the
default zone for sender and receiver but either can be
overridden...
- If ^AINTL is located anywhere in the message body both the
origin and destination addresses (full z:n/n) will be
replaced by ^AINTL values.
- If ^AMSGID: is located anywhere in the message body that
address (full z:n/n) will be used as the sender's address;
replacing the default zone and possibly the net/node from
the message header. This overrides the ^AINTL origin.
- A special case is when the NetMail is addressed from and to
the same address (found in the address/aka list) and ^AFMPT
is located anywhere in the message body (before blank or tear
lines. If "pointnet" is configured address conversion will
be performed.
- If ^AFMPT is located anywhere in the message body and the
address is not one of "your" points the message will be
processed as if it wasn't from a point and a matching ^ATOPT
will be added to the response message.
- A ^AINTL line will be put into the response message if the
requestor and receiving zones are different.
- NetMail message body scan terminates at a blank or tear line.
- Installed default notify prefix text that is displayed when
the "notifyprefix" file is not available.
- Added "AreasPerLine", "Available", and "NotifyAvailable"
configuration directives to control the available areas
display content and format in NetMail response messages.
See raid.cfg and raid.prn for info.
- Force net addresses to display in status displays when not
generating netmail. That will help explain some unusual find
output displays. Since exact match is required when netmail is
generated the address column is unconditionally turned off.
00.28
- Fixed a stupid (what else?) bug in netmail path processing that
caused memory trashing if there was no trailing slash on the
path. << This one is critical! If you cannot upgrade to 0.28
please be sure to add a trailing backslash to the netmail path
in raid.cfg >>
- Added errorlevel 10 exit to indicate out of memory processing
raid.cfg or tic.cfg. This should be a flag to either cut back
or to get a large data space version of raid (requestable as
RAIDBIG from 1:13/13).
- Debug variable list for raidnote and raidinfo was confused.
- Find was displaying garbage when flags field was blank.
- Don't malloc for netmail message body until the message looks
like it's addressed to raid.
- Netmail addressed to an aka wasn't processed if the zone didn't
match. Initial message header check now ignores zone but it's
still not right.
00.27
- Added experimental (maybe temporary) AKA logic. The idea is that
raid.cfg "aka" directives can define Tick AKA hex values...
Address 1:13/13 <no aka -- the primary net address
Aka 46:123/1 4 <aka #4 -- alternate address
Aka 47:123/456 C <aka #C -- alternate address
If a netmail request arrive addressed "to" one of the aka addresses
and that address has an aka defined, any ADD requests from the
requestor will have the "A#" added to the flags field on added
areas. This isn't the same as having A# in the flags field of
"access" directives. That method unconditionally forces all
adds for that address to use the same aka number until you or I
change raid.cfg. The new way puts the caller in charge of which
net aka used.
But then again, maybe it'll be better to use the AKA entries right
out of TIC.CFG with the same end result.
- Plugged a couple of holes and *rewrote* (watch out!) multiple
"address" logic so netmail can come in addressed to any configured
address. The first address line is the primary and will be used
on manual mode netmail. Multiple address and multiple zone logic
will continue to evolve.
- Dropped the net/node portion of the action display (16 characters)
except for manual finds where the search address is less than
6 characters (as in RAID FIND or RAID FIND 1:150)
- Added multiple address processing in response mode. Up to
50 "address z:net/node" directives can be used in raid.cfg. The
first is always the primary address and will be used for all manual
mode operations. In response mode netmail addressed to any of the
configured addresses will be processed. Replies will be sent from
the same address the caller addressed the request to.
- +areaname is now legal in netmail add requests.
- Increase stack space from 2k to 4k to see if Terry Rossi's problem
"moves". [it didn't but a workaround is to disable his cache?!?]
- The netmail directory isn't checked unless -m, -r, or notify is
in effect.
- If the netmail isn't defined and -m, -r, or notify is in effect
the program will not continue. (was writing messages in root)
- NotifyThreshold value of 0 resulted in no notify messages being
written. Corrected a bad test.
- Netmail behavior test in notify was allowing config file
NotifyBehavior C or H to override C or H on Access images. The
precedence is now such that -MC or -MH overrides everything;
NotifyBehavior C or H overrides Access line behavior of N but
not C or H.
- Local lines in area blocks were giving find trouble. Find doesn't
thing local lines terminate area blocks now.
- Fixed a random store processing access and area directives. Only
showed up with the full compiler.
00.26
- Wasn't actually truncating area descriptions longer than 60
characters. They're stored as long as they were when read
from the config file but only the first 60 characters will
be copied to netmail.
- Added "alias" configuration directive so some of us can change
the name remote requestors address messages to. With or without
"alias" directives (up to 100 allowed) "raid" is still allowed.
- Added tab to white space check in netmail body and raid.cfg
processing.
- Fix situation where available area display legend item was
displayed even if condition not met.
- Make area name all caps in find display.
00.25
- Yet another configuration directive. SYSOP identifies you to
the outside world. If specified, your name will be used as
the NetMail "from" field rather than the Raid release for all
manual mode operations. Response mode replies will still be
from Raid.
- Additional NOTIFY support for specific addresses. New command
line syntax is: RAID [switches] NOTIFY address1 ... addressn
If no addresses are provided notify operates as before. If
addresses are provided only listed addresses receive notification
messages. In that case, all configuration directives that
determine notify eligibility are ignored.
- NotifyThreshold is a new configuration directive to provide
further control over who receives notify messages. If the
number of active areas for the net address is less than this
value the address is skipped. Before this directive came along
a hard-coded value of 1 was used so that any address with no
active connections but with an ACCESS entry would never receive
a notify message. You can set this value to 0 to force notify
messages out to all configured addresses (that pass exclude and
security level tests).
- Additional control parameters are now available to response
node users. The parameters (action modifiers) follow the
password provided in the netmail message subject field.
The sample RaidNote.Txt file has been updated to reflect
these changes.
-I Information request. Causes the file defined by the
INFOFILE configuration directive to be file-attached
along with the response mode reply. If INFOFILE contains
wildcard characters (* ?) the first matching filename
will be used.
-Q Query request. Changes the format of the available area
display at the end of the response mode reply. Areas
are displayed one per line along with descriptions as
provided on Area configuration directives.
- Added area description capability on the AREA configuration
directive. Up to 60 characters following the area security
level will be displayed if a response mode request includes
the -Q modifier.
- Added some new stuff on the ACCESS configuration directive.
% net address password level flags mail sysop
% ----------- -------- ----- ----- ---- -----
Access z:net/node PassWord 50 *H N Sysop's Proper Name
Access z:net/node PassWord 2001
Access z:net/node PassWord 72 . H
The address, password, and level fields are required. The
rest of the fields are optional. Since the fields are
positional, all fields to the left of any you provide must
also be provided.
If you want flags to be blank just use a period (.). Raid
will convert that to blanks rather than using the DEF_FLAGS
value as happens when the field is not provided.
The mail field can be C, H, or N. It's must be specified
(along with the flags field) if the sysop name is provided.
Otherwise it will be filled according to the flags field.
The mail field is used for all netmail to that net address
unless overridden (as with password and flags) by command
line switches.
The maximum length for the sysop name is 36 characters (a
message header restriction). No restrictions on content
other than multiple spaces will be trimmed to singles.
Clear as mud, eh?
00.24
- Changed the "available areas" display at the end of every
netmail message generated to indicate both restricted and
active status. As before, the legend items are displayed
only if the flag is displayed. The flag characters are
all configurable in raid.cfg. Here's an example...
Areas available / active on 1:13/13
*NODEDIFF FIDONEWS < BETATICK> < RAIDBETA> < SIRBETA >
*SOFTDIST NEWSLETR ECHOLIST SDSOPUS *SDSBINK
*SDSQUICK *SDSFRONT SDSRBBS *SDSOTHER CEE
WINDOWS
Flagged areas '*' are active.
Bracketed areas '< >' are restricted or private.
- Fixed tic.cfg processing situation where an AREA line with no
nodes following was reported as found twice.
- Fixed find with no search argument (RAID FIND) to interpret
AREA lines with no nodes and no breaking comment correctly.
AREA d:\directory AREA1
1:1/1 password
AREA d:\directory AREA2
STOPDUP << was being reported as AREA2 find
- Made yet another change to log file tags. All are 1 word of
six characters or less. The goal is to be able to reduce the
data someday.
- Response mode add now uses password provided following area name
in message body:
SOFTDIST newpswd << adds overriding default if no -P switch
SOFTDIST << adds with default or -P
- Corrected coding errors (uncovered during compilation with MSC
5.10) in network address conversion routine and in network
address find routines.
- Add -T command line switch for TIC.CFG location override.
- "not found" responses now indicate add or delete operation.
00.23
- Added search for RAID environment variable to RAID.CFG search.
If defined (SET RAID=d:\path\file.ext) and the file is not
accessible the program will not continue. If not defined the
search continues in paths defined BBS, MAIL, and then PATH
environment variables. -C on command line overrides all other
checks.
- Added "NotifyBehavior" and "NetMailBehavior" configuration
directives. Unless overridden by the -M command line switch
these directives control Notify and other netmail behavior. So
now there are three levels of precedence for netmail and notify
C)rash and H)old message behavior.
1) Access definition flag field if not overridden by
2) NotifyBehavior and NetMailBefavior if not overrodden by
3) -Mx command line switch
Message Kill/sent control uses levels 2 and 3.
- The "KillReceived" configuration directive sets default incoming
message disposition (response mode requests) unless overridden by
the -K command line switch.
- Don't log "nofind delete <address> <wildcard>" if it's part of an
add/update operation.
- Installed config file edits to (try to) catch obvious errors...
- Security level max is 4095
- NotifyMinimum and NotifyMaximum cannot overlap but can be equal
- NetMail path must be accessible
- Duplicate area blocks in tic.cfg are reported as warnings
- Raid.cfg directives are checked for redefinition
- Commented out area connections are now recognized when the flag
field has an & and no *. Other characters are ignored.
00.22
- Allow for "domain" following address in ^AMSGID kludge lines. Also
allow for point number. If z:net/node match home address point is
processed as if it was on a ^AFMPT kludge line.
- Installed minimal point support. If a NetMail message is addressed
from the distribution system network address and the body contains
a ^AFMPT kludge line the private point address will be built from
the distribution system zone + the configured pointnet + the value
from the ^AFMPT line. If "pointnet" is not configured or zero
the ^AFMPT will be ignored. NetMail replies will include a ^ATOPT
line if the original message was from a point.
- Adjusted command line net address interpretation to make it less
likely to send netmail to a bad address. When -M is used the address
must be z:net/node.
- Corrected active area tally. It was showing high counts for nodes.
- If a connection for an area in TIC.CFG is commented out (flags = &)
that area isn't tallied. That way, if all connections for a node
are commented out, the notify for that node will be skipped.
- Installed NotifyMinimum and NotifyMaximum config directives. They
default to 0 and 4095 respectively and in that default condition
allow all addresses not explicitly excluded (NotifyExclude) or
skipped (no active areas) to receive status notification messages.
If NotifyMinimum is raised or NotifyMaximum is lowered any net
address whose security is outside the range they bracket will be
skipped.
00.21b
- Correct response mode setting node security to zero.
- Allow ^AINTL and ^AMSGID: lines to change address before testing
address against "access" list.
- Corrected bad search for RAID.CFG if not in default directory.
00.21a
- Took out the reference to no add/del in help message
- Fixed line wrap in NOTIFY display and garbage in notify log entry
00.21
- Well, here we go. RAID.CFG is now required. Please be sure to
"install" it before trying this version. The RAID_CFG block will
need to be "converted" to ACCESS format before you can do much
work. With this change, Raid no longer has any dependence on
TIC.CFG other than area blocks.
Now that the .CFG file is installed processing has changed a bit...
Notify now ships netmail to all listed addresses rather than only to
RAID_CFG listed addresses (except where overridden in RAID.CFG).
And the "flags" field C and H (H if both) values will be used for
add Raid-generated NetMail unless overridden by command line switch.
- Delete of last entry in an area block no longer deletes the blank
line following it.
- ADD now inserts new lines at the end of area blocks so it doesn't
interfere with "local" entries.
- Exact match is required on command line requests (add/delete etc)
- Got rid of some information on screen during manual ADD/DELETE. Not
sure which way I want it. Ideas are welcome (in the echo so we can
share 'em).
00.20
- Response mode international processing? ^AINTL: line is created if
destination zone and originating zone aren't the same.
Similarly, if an ^AINTL: or ^AMSGID: line exists in an inbound
NetMail message Raid will (try to) use the from address string for
processing. This hasn't been tested and certainly isn't installed
based on any practical experience. It's just a starting point for
discussion and design.
- The original TIC.CFG is renamed to TIC.OLD when updates are written.
- -O (override) switch is now exclusive of -M (message) and for use
only on manual delete. The -M modifier (o) is gone from FIND and
DELETE manual requests. -O allows partial match on net address...
RAID DELETE 1:999/ ALL -O
deletes all net 999 entries from the Tick control file.
- Don't open/close log file unless log entries are generated. (2nd try)
00.19
- Don't open/close log file unless log entries are generated.
- Don't log FINDs. That's implied in response mode.
- Shortened execution in NOTIFY by opening/closing RAIDNOTE.TXT once
rather than as many times as there are connections.
00.18
- Well, this test release includes the first cut of the doc (RAID.PRN).
It's for information rather than editing at this point since it's so
fresh.
- -L command line switch operation expanded. "-L" still disables log
generation. "-Lpath\file.ext" overrides the default ".\RAID.LOG" log
file destination. As before, if the log can't be opened log processing
is suspended rather than aborting the program.
- Available area display adjusted to flag protected areas if present.
- Installed 'shotgun security'. Any AREA block following a line starting
off with three dashes "---" will be secure. ADD requests in response
mode will be denied. Response mode DELETE and all manual operations
are allowed no matter the security status.
AREA C:\AREA1 AREA1 unrestricted
AREA C:\AREA2 AREA2 unrestricted
---
AREA C:\AREA3 AREA3 restricted
- Notify is now NOTIFY on the command line (was -Nx). Netmail attributes
default to normal/private. Now uses -Mx to set C|H|K (RAID NOTIFY -MK).
In addition, if RAIDNOTE.TXT is found in the default directory, it
will be inserted ahead of the connection list. The file length and
content is not restricted other than that your mailer (and the
recipient's) must be able to process it. The process is a dumb copy.
All that's edited out is ^Z (eof). A sample RAIDNOTE.TXT will be
included in the distribution.
- Don't allow wildcard (ALL) as an area name in NetMail response mode.
- Only display available areas list in netmail messages
00.17
- Fixed problem in ADD logic that was grunging the file when multiple
ADDs were requested in one NetMail message.
- Manual ADD now uses default password and flags from RAID_CFG area block
if available and not overridden by -P or -F. Otherwise use PASSWORD
as password and no flag.
- Netmail adds/deletes were never applied. The call to write the updated
config file got deleted! Maybe it works now. But PLEASE BE CAREFUL!
- Do path existence test on RAID_CFG directory same as MAIL directory.
- Well, in my haste to get the 00.16 out the door I only removed half of
the security risk. I forgot to totally disallow flag field override by
netmail requestors. What we have now is that add/delete requests via
netmail will be honored only if the RAID_CFG area block entry for that
node has a value in the flag field. The flag field will be used for
all add requests processed in response mode. In cases where you want to
allow a node to do remote updates but don't want any flags, raid
recognizes a single period as the permission switch. In that case
the flag field for adds will be blank. Clear as mud, right?
These will not allow remote updates but will default to remote query:
AREA C:\LOGS RAID_CFG
1:123/456 PASSWORD
1:456/789 WHY_NOT
And these will allow remote update and query:
AREA O:\ RAID_CFG
1:123/456 PASSWORD .
1:456/789 WHY_NOT *H
00.16
- Installed a stub routine for processing IFNA style kludge lines
- Added a check for path existence before processing. The routine
is generic in that things like A: (root) and X (subdirectory) are
allowed. Trailing backslash is optional.
- If you use the RAID_CFG area block and leave off the "flags" field
the program will not allow NetMail updates. That's clearly a
temporary situation as we get our collective stuff together to build
more practical security into the program. It also lets us all test the
latest version without compromising security. And it allows password
protected queries to continue from your downlinks.
- Added an errorlevel to signal a critical error occurred renaming the
temporary file to TIC.CFG (or whatever) just after successful return
from deleting that file. Though this shouldn't happen it's a critical
error to trap and report. I just scanned this file and see I appear to
have forgotten to let you folks know the specifics of the errorlevels.
0-4 are reserved for "normal" terminations. 5 and above are aborts.
NO_ACTION 0 No netmail and no updates
NETMAIL_GENERATED 1 -R or -M mode and at least 1 message
CFG_READ_ERROR 5 Error processing of old TIC.CFG
CFG_WRITE_ERROR 6 Error updating TIC.CFG after updates
RENAME_ERROR 7 Trouble renaming after delete of old TIC.CFG
NETMAIL_ERROR 8 Trouble accessing NetMail area or message(s)
GENERAL_ERROR 99 Non-specific error termination
00.15
- More clean-up of code and logfile.
- Don't display find info for notify (-n) operation. Only 1 line per.
- First try at allowing ADD/DELETE via netmail (response mode). Unlike
areafix, RAID allows only ONE add/delete per line. Up to three fields
are allowed: <->areaname <password> <flags>
Areaname is required. Everything else is optional. Lacking password
or flags, Raid will use the default password / flags from the RAID_CFG
area block in your TIC.CFG file. As a result, in order to override
flags you need to supply password.
A comment... I'm not entirely sure we want to allow flag fiddling
by any/everyone. A Long Distance caller could easily change flags to
*C and not only cost *you* money but could then feed something illegal
right past you. I'm leaning toward dropping flag support in the 1.00
release and installing a RAID.CFG file with flexible configuration
in the next release. But need comments from you folks. I'll watch
for your comments in RAIDBETA. I assume all of us are hooked up by now.
00.14
- Changed log file from binary to text and terminate it with with ^Z
- Don't display available areas list to screen when doing notify
- Fix a couple of log entries and add a couple more
- ADD is now "replace" when an entry already exists. A delete is done
before every add. Keeps the file clear of dupes and allows remote
"refresh" to be done. The log file reports the deletes but they won't
show up on the screen or in generated netmail.
- Do a find after add/delete if -M switch is set
00.13
- Zones other than "yours" are still not supported!
- Display add/delete tallies after all operations have completed
- Always do a find operation if in response mode
- Tighten up netmail check to require exact match on message "to" field.
That means netmail messages to raid must now be addressed only to "raid".
- Check for area names and passwords > 8 characters; stop if error.
- Allow a "special" AREA block to be used exclusively by RAID. The name is
RAID_CFG. The path name defines log location and net/node lines define
remote access privilege / remote access password / and ADD defaults for
password and flags values...
AREA H:\ RAID_CFG log is written as H:\RAID.LOG
1:13/13 XYZZY *C 1:13/13 can access RAID remotely if XYZZY is
used as the access password (netmail subject).
XYZZY and *C will be the default password and
flags on manual and remote ADDs lacking
overrides (manual or remote).
Only the AREA line is used in this test version. Access security and
defaults *are* installed but remote add/delete are *not*.
- Raid will *not* recognize RAID_CFG in either manual or response mode.
That AREA block must be edited manually.
- Install log file routines. The log file (RAID.LOG) is opened as soon as
the tick control file read is complete. Log file location defaults to
the current directory. If AREA block "RAID_CFG" is present the path for
that block is used for the log. If the log can't be opened the program
continues without log. Log file output is disabled by the -L command
line switch.
- Added NOTIFY function. It's activated by the -Nx command line switch.
x is the same as for -M or -R. This is tied to addresses listed in
the RAID_CFG area block.
00.12
- Process all netmail addresed to raid individually rather than in a lump
- Disable find override if processing netmail in response mode
- Don't process messages generated by raid
- MAIL directory ending with \ won't give error anymore
- Debug and error messages can now all be redirected
00.11
- Changed output layout for find/add/delete for a consistent output
layout and to pave the way for combined add/delete/change requests
made via netmail. No, change isn't installed yet.
- First cut at inbound NetMail processing. Messages addressed to "RAID"
will result in a FIND operation. Feature is activated by the -R
(Response mode) switch. Modifiers (CHK) are available to direct NetMail
as for -M switch. Response mode scans the entire netmail area. Any
message addressed to "RAID" (case insensitive -- only the first 4
characters are checked), to the net/node in your TIC.CFG file, and not
flagged as "received" will be processed by Raid. The from net/node, along
with your zone (yeah, I know that needs work) are used to generate a
"FIND" request. Then the message is either marked received or is deleted
as indicated by absence/presence of -K.
- Added -K switch. See above.
Can be used like AreaFix in your mail processing BATch file as "RAID -R".
- Lots of code changes to tighten things up.
- Looks like the practical limit for a TIC.CFG file is around 100 areas.
The one Barry provided for test has 85 areas and works fine so far. I've
processed a .cfg file with 125 areas but think that's not conservative
enough.
- "O" modifier added to -M switch. That allows the sliding address match
for FIND requests. It's a security liability that should be used with
caution. Doing a RAID FIND 1:150/2 -MO will find all 1:150/2xxx nodes
and send the resulting message to 1:150/2.
00.10
- Reorganized program to make NetMail requests easier later.
- Sliding address match on FIND is disabled if -M switch is set. That
forces exact match for netmail messages.
00.09
- Add FIND count to -M output
- Rework output to funnel screen and message writes through a common
procedure
- Display available areas on screen.
00.08
- Changed available area display to list 6 areas per line
- Dropped -K switch
- Changed -M to allow C, H, and K modifiers (ie -MCK or -MH)
- Made sure case of arguments is retained
- Display warning if unrecognized switch/command is entered
- Require exact (rather than partial) match for DELETE operation. Only
FIND allows partial match.
- Fix FIND to recognize and bypass LOCAL lines and to properly detect
the end of an AREA block.
- Allow switches to follow FIND when no target is given: RAID FIND -D
- Change ZONE definition to use the first ZONE statement found. Was
looking for any ZONE statement without a period (.) for a match.
- Change areaname and password to 8+1 characters.
- Up max AREA blocks to 75.
00.07
- Fixed -M output for ADD operation
- Started expanding return message by listing all area names. That's
going to change along with the entire message layout.
00.06
- Corrected reversed -K test
- Corrected output file WRITE routine to do line output rather than
binary output.
- Changed error reporting to be more general
- Message body in -M output now has CR/LF at end-of-line rather than LF.
00.05
- Added -M logic.
- Added -K switch to mark NetMail kill/sent.
00.04
- Corrected situation where "RAID FIND\n" found matches on blank lines
between AREA blocks. RAID should now properly bypass blank lines.
- If -M or NOTIFY is used and a NetMail directory isn't defined RAID won't
continue.
- "FIND -M" now recognizes the -M (or any option) rather than searching
for it. Similarly, ADD and DELETE will see the option but will exit.
- Now checking for > 64 areanames on ADD, DELETE, and FIND. Of course
FIND only uses the first address right now.
- "FIND net/node -m" was giving strange results. Fixed file read code.
- Fixed DELETE so the first address in all area blocks can be deleted
rather than only in every other area block.
- Only rewrite file if ADD/DELETE change something