home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 2 BBS
/
02-BBS.zip
/
afp_130a.lzh
/
AFP.TXT
< prev
Wrap
Text File
|
1992-01-21
|
33KB
|
856 lines
The enclosed AREAFIX executable is a __TEST__ version that should be used
with caution!!! BACK UP YOUR AREAFIX.CTL AND AREAS.BBS BEFORE YOU TEST!!!
Bugs are expected!!!
If the last digit of an AreaFix version is non-zero (as in 1.21) it's a
test version requiring close attention to operation and output.
================================
AreaFix 1.29g *beta* 01/21/91
================================
v1.29g Change details:
- Showfeeds stopped working awhileback. This one seems to do better.
- Here's yet another eleventh hour Areafix.Ctl parameter with a
choice:
RescanListAddress List
RescanListAddress String
List is the default and generates the address as a list of space-
delimited values. String squashes them all together as z:n/n.p.
================================
AreaFix 1.29f *beta* 01/16/91
================================
v1.29f Change details:
- The new address mangler was hanging and doing other impolite
things when it tried to process a string with no addresses.
- Added more debug code ( -d and -d -d on command line ) to tell
a story in case we need to chase any more problems.
================================
AreaFix 1.29e *beta* 01/15/91
================================
v1.29e Change details:
*** This one has an entirely new 4D address decoder that's smaller,
faster, and [so far] more consistent than the old ones. HOWEVER
<comma> we all need to watch this carefully since a bug in this
routine will destroy Areas.Bbs files and address netmail replies
to the far reaches of the universe.
- Dropped the RESPONSE parameter from areafix.ctl and replaced it
with 2 others...
NO_RESPONSE_LIST
NO_NOTIFY_LIST
These 2 parameters tell the program whether to generate the list of
active areas at the tail of netmail reply and notify messages. They
will be active (no list generated) if uncommented. The command line
switch -L is provided as an execution-time reversal of the
areafix.ctl settings of both switches.
- Added yet another Password flag value. This one ( $ ) tells the
program to override No_Response_List and No_Notify_List for
individual addresses.
- Command line -n<filename> switch is added to override the
areafix.ctl file selection setting for the NOTIFY header file.
- Notify exclude list was only checked for zone:net/node. Added point.
- Purge never worked for SystemType QuickBBS folks. This one sees the
'P' (passthru) board number and flags the area as passthru.
================================
AreaFix 1.29d *beta* 01/10/91
================================
v1.29d Change details:
- If the requesting address is also the alert address areafix won't
send copies of replies.
- Replies with echolist were always missing ^AINTL lines. They should
be addressed correctly now.
- Reply messages now say "Unlinked" instead of "Deleted" when an area
is unlinked for a node. And of course UNLINK is now an aka for
DELETE on the areafix command line.
================================
AreaFix 1.29c *beta* 01/06/91
================================
v1.29c Change details:
- Fixed the control file sysop name problem. Sysop name no longer
includes the flag field as the first name.
- The initial message scan is changed to read only the first 2k
of each message rather than the entire message body. This should
fix the problem of areafix trashing memory when scanning large
messages not addressed to areafix and not a new area. It should
also speed up the program a bit. The assumption is that ^Amsgid,
^Aintl, and AREA: lines will all occur within the first 2k of the
message. Once a message is selected for processing the entire
body will be read.
- Response_Format is a new Areafix.Ctl parameter. This controls
whether active area information is included in replies to netmail
requests. It can be set to either LIST or NOLIST. NOLIST displays
only action responses. LIST (the default) adds a list of active
areas. LIST is the way previous versions operate.
================================
AreaFix 1.29b *beta* 01/02/91
================================
v1.29b Change details:
- This one fixes several problems related to area names being in
lower or mixed case in areas.bbs, areafix.ctl, and forward lists.
This could explain why some folks saw problems with forward lists
and area protect security levels while others saw none.
- Fixed Areafix.Ctl Password line processing so the optional sysop
name field can be more than 2 words.
- The KeyDefault settings were only being applied when there was a
period ( . ) on password entries. Now the defaults are applied
whenever there are *no* attributes listed on a password entry as
well as when period is used.
================================
AreaFix 1.29a *beta* 12/30/91
================================
v1.29a Change details:
- Added a little more feedback to forward list processing. If
running in debug mode ( -d ) additional information will be shown.
Anyone having or suspecting forward list problems should run with
-d on the command line ( areafix ec -d ) so more info can be
reported in case of failure.
- Fixed passthru code to stop flagging areas with only the '$'
format indicator as passthru. Now only '#' format areas are
processed as passthru.
- Changed "Area not found" to "Area not active" for area delete
response.
- Fixed an old memory thrashing problem that showed up when
"hundreds" of messages were processed and areafix began reporting
that it couldn't allocate memory.
- Installed a new 4d/5d areas.bbs address parser to fix some old
kludges in address processing.
- Area lists (find, notify) were wrong for addresses following a
non-zero point number. The new address parser fixes this by not
[incorrectly] 'sticking' points from one address to the next.
================================
AreaFix 1.29 *gamma* 12/04/91
================================
v1.29 Change details:
- This is a publicly available stress test. It is not tagged as a
public release so that everyone using the program can be urged
to exercise caution and care. Further updates leading up to the
1.30 release will be distributed only to beta testers.
- Troubles and comments should be shared in the QM_ECHO EchoMail
conference.
================================
AreaFix 1.28a *beta* 11/26/91
================================
v1.28a Change details:
- Netmail requests from a point were being processed as if from
the boss node.
- Netmail requests addressed to a point were being processed
incorrectly.
- Alert copy message addresses were getting confused. Fixed the
address display routine.
- All operations should now recognize .<point> shorthand notation.
- INTL/FMPT/TOPT/AREA kludge lines are accepted with or without ':'.
================================
AreaFix 1.28 *beta* 11/21/91
================================
v1.28 Change details:
- Attacked the stack overflow problem in notify processing.
- This one has a new address parser that tries not to get upset
about points (.), domains (@), and comments (;). It doesn't
seem to hang but things it doesn't know about are lost.
- This one has lots of changes toward support of 4-d addresses in
Areafix.Ctl and Areas.Bbs. Test carefully.
- Remote area delete operations make entries in Areafix.Del so
stray traffic for deleted areas will be treated like purges.
- Remote area delete removes downlink request entries from
Areafix.Que.
- A drop request (command line purge) removes forward que entries
from Areafix.Que.
- Successful requests for dropped/purged areas should now remove
traffic block entries from Areafix.Del.
- New areas are now created when traffic from an authorized feed
follows traffic from unauthorized feeds.
================================
AreaFix 1.27 *beta* 10/30/91
================================
v1.27 Change summary:
Control file changes:
Command line changes:
Netmail interface changes:
v1.27 Change details:
- Stack overflows and other strange errors in 1.26 seem to be the
result of the increase of internal buffer sizes. This one changes
the way areas.bbs processing is handled so line length can be
4096 without affecting the rest of the program.
- New area processing was still not exactly right. Tweaked it a bit
so echomail messages left over in a netmail area or scanpath will
be processed as new areas only if they really are. Also fixed it
so we can manually add new areas to areas.bbs and have areafix.que
processing done on the next areafix execution rather than waiting
for some other operation to force queue processing.
================================
AreaFix 1.26 *beta* 10/17/91
================================
v1.26 Change summary:
Control file changes:
- Add RescanList <filename> [command]
Command line changes:
- Temporary -V switch to turn on logging of new area create errors.
- Rescans for individual areas (-R) generate RescanList entries.
Netmail interface changes:
v1.26 Change details:
- The changes in 1.25 loosened up new area create logic a bit too
much. So much that areafix was imagining things. This one doesn't
try to create blank areanames.
- RescanList is a new control file directive. If found, it defines
the filename and optionally a command to insert when a rescan is
requested for area adds either via netmail or command line. The
special areaname "All" is excluded. This directive applies only
to non-QuickBBS installations. The format of RescanList is:
RescanList <Filename> [Command]
Filename is the required name of the file that will receive rescan
list entries. Command is optional and defines the command that will
precede area / address information in rescan list entries. If the
command parameter is not used the word "Rescan" is used. Up to 6
'arguments' will be written to rescan list entries:
Command <areaname> <zone> <net> <node> <point> <domain>
1 2 3 4 5 6
The first 5 arguments are always present and will always be
separated by spaces. This allows BATch file parameter substitution
with little difficulty. For example, considering the command line:
Areafix Add 2:243/47 INTERUSER FN_SYSOP -R
If Areafix.Ctl shows: RescanList C:\Files\Rescan.Bat ReScanMe
lines would be written to C:\Files\Rescan.Bat as:
ReScanMe INTERUSER 2 243 47 0
ReScanMe FN_SYSOP 2 243 47 0
If Areafix.Ctl shows: RescanList C:\Files\Rescan.Bat Call DoIt
lines would be written to C:\Files\Rescan.Bat as:
Call DoIt INTERUSER 2 243 47 0
Call DoIt FN_SYSOP 2 243 47 0
In this second example if DoIt is a BATch file it might look
like: MyProg ReScan %1 %2:%3/%4
and the resulting lines would resolve to:
MyProg ReScan INTERUSER 2:243/47
MyProg ReScan FN_SYSOP 2:243/47
- This one prints a line indicating that an area cannot be created
whenever security fails. The line indicates the address and area.
Until we see how badly we need the info and how much info is
generated the line will only be logged if you use -V (for verbose
logging) on the command lind as in 'AREAFIX EC -V'. -V is not
promised as a permanent fixture. It's just so we all have control
over logging of the new messages.
- Increased maximum allowed Areas.Bbs line length from 2048 to 4096
characters and maximum nodes per area from 256 to 1024.
================================
AreaFix 1.25 *beta* 10/08/91
================================
v1.25 Change summary:
Control file changes:
- KeyDefault values replace "." on Password entries
Command line changes:
- Drop now generates Areafix.Del entries for all nodes
Netmail interface changes:
- Remote add requests are no longer forwarded for protected areas
- Remote delete requests are now rejected if they fail security
v1.25 Change details:
- If a period ( . ) is used in the key/flag field on Password
entries the string assigned to the KeyDefault entry is added
to the key/flag data for that Password. This action can be
overridden by using minus ( - ) in the Password entry key/flag
field. In that case the defaults are not added.
KeyDefault *?
Password 13/13 Happy 99 . Sysop Name [ *? ]
Password 13/13 Happy 99 abc Sysop Name [ abc ]
Password 13/13 Happy 99 .abc Sysop Name [ abc*? ]
Password 13/13 Happy 99 abd- Sysop Name [ abc ]
Password 13/13 Happy 99 .abd- Sysop Name [ abc ]
- An add request for a missing area with security protection higher
than the requestor wasn't stopped in time to avoid forwarding the
request.
- Remove requests for areas with security protection higher than the
requestor were not being rejected.
- The debug log of security flags and levels for failed requests is
now gone.
- Command line purge operations (Drop) now generate Areafix.Del
entries for every node in every dropped area.
- New area creation tests were not consistent. Changed to always
check password entry '&' flag and skip ^Amsgid address overrides
if message body begins with AREA:
- Fixed a problem in address/aka matching.
- Address matching between headers on .msgs in netmail or scanpath
directories and new area create lists and Areafix.Del (purged
address/area) must be limited to only net/node. There is no way
to identify the zone number a .msg was actually received from so
the test will just have to ignore zones.
This hilites another fact of life in FidoNet -- the "new
wave" of echomail processors that leave the originating system
address intact. This of course throws areafix' area create and
purge check routines way off base since they assume the .msg
header address is correct.
================================
AreaFix 1.24 *beta* 09/18/91
================================
v1.24 Change summary:
Control file changes:
Command line changes:
- Notify allows command line switches again
Netmail interface changes:
- Forwarded requests don't use an address in the from text field
v1.24 Change details:
- Addresses not purged during purge processing are noted in the log.
- Point and domain information in areas.bbs is ignored rather than
choking areafix.
- Delete requests now check areafix.que and delete queue entries
for the address/area combination. This works for netmail as well
as manual delete requests.
- Forward request messages were addressed from "(...) Areafix at n/n".
The length of the string was not checked before being stuffed into
the 36 byte message header field. Short addresses like 13/13 worked
fine. Longer ones like 2220/200 or 124/4115 had problems. The fix
is to drop the "at n/n" from the field.
- If any switches were used on the command line along with notify
areafix thought there was a list of addresses to notify. It should
be fixed now so switches and addresses can be used separately or
together without confusing notify.
================================
AreaFix 1.23 *beta* 09/06/91
================================
v1.23 Change summary:
Control file changes:
- Assume Zone and Assume Net trigger zone: or zone:net assumption
- Password key/privilege mask includes new values (& #)
- Address and Aka are interchangeable
- Maximum address/aka entries expanded from 10 to 256
Command line changes:
- Notify can include a list of addresses to notify
Netmail interface changes:
v1.23 Change details:
- Added the Areafix.Ctl ASSUME directive. This one activates either
ZONE assumption or ZONE:NET address assumption. This feature tries
to be smart about multi-zone operations. When address assumption is
active areafix uses the netmail "to" address only until the request
is validated against your configured addresses. At that point your
system identity is changed to match the caller's.
If ZONE assumption is active Areafix locates the first matching
ZONE in your address list. NET assumption locates the first matching
ZONE:NET. From this point on all mail Areafix generates will ASSUME
the full ZONE:NET/NODE identity of the matching address for all
further operations. If no matching address is located Areafix uses
the first Address configured.
- Command line NOTIFY operation is changed to support address
assumption.
- Request forward logic is changed to support address assumption.
If the optional from address is not included on the forward list
line the assumption rules will be applied to the forward to address.
- Reworked initial message search to standardize message processing
logic and to catch messages previously missed.
- ADDRESS and AKA Areafix.Ctl directives can be interchanged. The
first ADDRESS or AKA defined is the main address used by areafix.
- As many as 256 Address or Aka entries can be defined in Areafix.Ctl.
- The Password key/privilege field can include an ampersand ( & )
to allow the address to create new areas or a pound sign ( # )
to add the address to new areas. These are alternatives to
listing the address on the NewAreasCreate and NewAreasNodes
directives.
- If a new area is created from one of the configured addresses that
address will no longer be inserted in the Areas.Bbs scan list.
- Dropped a memory clear call following newarea directory create.
- Multiple forward entries for the same area and address combination
in Areafix.Que will no longer generate multiple netmails. The
previous version generated one netmail for each Areafix.Que entry
without checking for repeats.
- A command line Notify operation is now either global (all
addresses) as it has always been or selective. Any arguments
that follow NOTIFY on the command line will be used to generate
notify messages.
- Query output is fixed so it lines up vertically again.
================================
AreaFix 1.21a-02 *beta* 09/03/91
================================
v1.21a-02 Change summary:
Control file changes:
- Forward_List allows optional from address definition
- Password key/privilege mask includes new values
- Password allows optional sysop name
- Squish documentation is removed
Command line changes:
- remove has been deleted since it caused trouble.
- drop is a simple delete-my-connections request for areas.
- -mk does the same thing as -m -k
Netmail interface changes:
- intl, msgid, and point address override only apply to netmail
v1.21a-02 Change details:
- Reduce data logged when directory remove fails.
- Command line REMOVE is gone.
- Command line DROP performs a single level deletion of echos
rather than addressing destructive remote deletion (autodelete)
requests to links. AreaFix sends normal area delete requests
(-areaname) to each address with a password configured and text
requests to others. This operation uses the Areafix.Ctl
parameter PurgeRemove to decide what do do with orphaned messages
and directories.
- Command line REMOTEDELETEAREA issues destructive remote deletion
(autodelete) requests to all links configured so. This means
that if links have the 'right' privileges set the request will
follow the distribution tree. The Areafix.Ctl RemoteDeletion
parameters are used.
- Forward_List definitions have an optional fifth field. If present
it will be used as the "from" zone:net/node for forward request
netmail messages.
- The Password key/privilege field can be a period ( . ) to indicate
that KeyDefault values are to be assigned or dash ( - ) to indicate
that no key or privilege values are assigned to the address.
- The password key/privilege field can include a plus ( + ) to
signal that the privilege settings are to be included whenever a
list of areas is sent to the address. The list option defaults
to off.
- Password definitions allow a one or two word sysop name following
key/privilege values. If the sysop name is provided all preceding
fields must also be present. Underline characters in the name will
be translated to spaces.
- Address overrides (^AINTL, ^AMSGID, ^AFMPT) are only done on
messages in the netmail area. This allows the message header
origin address to be used for new area creation logic.
- Area purge was not consistently updating areafix.del.
- Reference to squish format areas.bbs is removed.
- The command line -m (generate netmail message) switch can include
a trailing k (-mk) to set the kill/sent flag on generated netmail.
This has the same effect as -m -k.
================================
AreaFix 1.21a-01 *beta* 08/27/91
================================
v1.21a-01 Change summary:
Control file changes:
Command line changes:
- command line add operation now bypasses security lock/key checks.
- query now displays 1 copy of privilege flag status.
Netmail interface changes:
v1.21a-01 Change details:
- Fixed netmail message generation to put 2 spaces between year and
time per FTS-0001.
- Request forward date checking was wrong and incorrectly thought
any previously requested area was already forwarded 'today'.
Fixed to compare the correct dates.
- Command line ADD operations were being validated for lock/key
security. Change to override level/lock/key checks unless
processing netmail requests.
- Installed log of level/lock/key data when security fails for
add request.
- Fixed QUERY security check. Was coded such that if level OR
KEY was ok security passed. Should have been coded as AND.
- Command line QUERY was displaying the privilege flag status
summary twice. Deleted extra code.
- QUERY was displaying forward information. Deleted since FIND
is more appropriate for displaying that information.
- NewAreasNodes addresses are now sorted before adding to Areas.Bbs
if SortNodes is configured.
- New area creation checks to see if the from address in the new
traffic is from any of your configured addresses. If yes, your
address is not added to Areas.Bbs and is not logged as added.
=============================
AreaFix 1.21a *beta* 06/14/91
=============================
v1.21a Change summary:
Control file changes:
Command line changes:
Netmail interface changes:
-areaname code fell through to ~areaname -- CRITICAL fix
-areaname caused purgeremove operation
v1.21a Change details:
- -areaname was being processed as if it was ~areaname. The netmail
area delete code was dropping through to the new ~areaname code
so once an area was deleted by a node with the ~ privilege flag
set the area was being dropped from circulation.
- -areaname when PurgeAreas and PurgeRemove enabled removed the
message directory even when the area entry was not purged from
areas.bbs. The PurgeRremove code missed the fact that a node with
no purge me (*) privilege flag would not be purged. As a result
no notifications were made, The PurgeFile and log were not written
because no purge operation was performed. But the purgeremove was
done [silently] anyway.
- Subdirectory Remove operations are now logged.
=============================
AreaFix 1.21 *beta* 06/11/91
=============================
I urge you to install this areafix using sample.ctl as your areafix.ctl
file. There are several new and changed options we all need to try out.
v1.21 Change summary:
Control file changes:
Add: SystemType Squish affects passthru create
Delete: ShortForm replaced
Delete: LongForm replaced
Add: Format Short abbreviated node entries in areas.bbs
Add: Format Long full node entries in areas.bbs
Add: Format Zone first node entry in areas.bbs has zone
Add: FileShare open all files with share support
Add: NewAreasNoDir don't create new area subdirectories
Add: PurgeAreas kill dead-end passthru areas
Add: PurgeFile record of purged areas
Add: PurgeRemove delete purged directory
Add: KeyDefault default password key & privilege flags
Change: Password add security key and privilege flags
Add: ProtectDefault assigns level to areas without protect
Add: LockDefault default protect key & privilege flags
Change: Protect add security lock and privilege flags
Add: ForceIntl add ^AINTL line to every netmail
Add: RemoteDeletionForward forward remove requests to downlinks
Add: RemoteDeletionRemove delete removed directories
Command line changes:
Add: Create command line area create
Add: Remove command line area remove
Netmail interface changes:
Change: from name all messages are from sysop name
Change: re: messages with re: in subject are skipped
Add: ~areaname remote area deletion (if enabled)
Add: forward summary lists forwarded requests on response
v1.21 Change details:
- Added NewAreasNoDir to tell areafix to skip the subdirectory name
edit and creation steps during new area create operations. The
default condition is to create directories for all SystemType
formats except QuickBBS and Squish.
- When enabled via the ~ Password privilege flag netmail areafix
requests now have 3 flavors; add, delete, and remove. ~areaname will
remove an area the same as if the remove was requested by a
netmail to autodelete. Notification and forwarding are the same as
for requests directly to autodelete.
- Remove is accepted in command line mode.
areafix remove all put yourself out of business!
areafix remove area1 area2 ... drop areas from distribution
Notification and forwarding are the same as for requests directly
to autodelete.
- Create is accepted in command line mode.
areafix create area1 area2 ...
Manual create operations use the control file NewAreas directives
the same as if the new area arrived as unknown traffic except that
the requesting address (the configured primary address) is not
automatically added to the new area distribution list.
- Dropped 1 of the 2 places where requests are rejected for security.
Needs to be checked carefully to be sure things aren't getting thru.
- The forward que (areafix.que) file is no longer limited to 255
entries.
- Password and Protect entries are now limited only by available
memory.
- Pulled file open calls together for a general interface with Share
support. All files are opened in DENY NONE mode when control file
switch FileShare is flipped on. I don't use Share. Maybe it works.
- New area processing now adds entries from the queue file during the
creation execution rather than forcing an additional areafix execution.
- Purge operations installed. Any area delete request that leaves only
one address connected will be processed. Areafix.Ctl directives
PurgeAreas, PurgeRemove, and PurgeFile are added. Additional traffic
from a purged feed address in a purged area will be deleted until
any address turns the echo back on (request or traffic).
Purge operations are performed only when the area is passthru.
PurgeAreas activates area purge
PurgeRemove removes purged subdir
PurgeFile <filename to save purge data> names data file
- Leading + is ignored for netmail add requests.
- Leading + or - is ignored for remotedeletion requests.
- Reply and notification messages are from the configured SysOp name
rather than Areafix so bouncers occur less frequently.
- Messages with subject lines beginning with Re: are not bounced.
- Find/Query output includes queued (forwarded) request information.
- Added lock/key area security. Protect directives have an optional
LOCK field following the area security level. Password directives
have an optional KEY field following the address security level.
The lock/key uses 32 bits -- A-Z and 0-5.
Lock/key security operates in conjunction with security levels. Both
must pass validation tests before a remote ADD request is allowed.
The lock/key (as well as security level) mechanism is disabled for
command line ADD operations.
A KEY must have at least the same letter/number combination as a LOCK
to pass security validation.
Here's an example to get things rolling...
Password 1:13/13 MyPass 100 ACTXYZ01235
Protect AREA1 100
Protect AREA2 101
Protect AREA3 100 ACT123
Protect AREA4 100 ACT1234
1:13/13 can ADD AREA1 and AREA3. AREA2 is protected by a higher
security level. AREA4 is protected by a non-overlapping LOCK.
The 1:13/13 KEY does not "fit" the required 7 character LOCK. 4
is missing from the KEY.
Additional privilege bits are available on the Password Key string.
Besides the 32 key values (A-Z and 0-5) these additional indicators
can be used:
~ Allow remote deletion requests from this address
@ Allow remote deletion forwarding to this address
? Forward area add requests for this address
* Purge idle passthru areas when this address is the feed
- LockDefault (Protect) and KeyDefault (Password) strings are
used for all areas and nodes that do not have lock or key
values explicitly assigned in areafix.ctl.
- Added ForceIntl control file directive to force AreaFix to add an
^AINTL line to all output messages generated.
- Missing password (empty subject field) on incoming requests wasn't
being trapped soon enough.
- If an error occurs while processing an areafix request the offending
message and reply will not be deleted even if configured to delete.
- Replaced SHORTFORM, LONGFORM, and ZONEFORM (new) with FORMAT xxxx
(xxxx can be SHORT, LONG, or ZONE. The old config parameters will
still work.
SHORT Abbreviate to n/n or n wherever possible
LONG Use full z:n/n format for every entry in areas.bbs
ZONE Add zone to first entry on each line in areas.bbs
- Added RemoteDeletionForward configuration directive as a global
switch to enable auto-forward operations. When enabled (uncommented)
remote deletion requests can be "forwarded" to all nodes listed
for the affected area. Actual forwarding is controlled on a node-by-
node basis with the @ privilege flag on Password entries. If the
@ privilege is not enabled and RemoteDeletion Notify is active a
text notification message will be sent to the affected susop.
The end result is that each system in the distribution chain can
configure whether to accept AutoDeletion traffic and whether to
forward the messages farther along the distribution chain.
- Added RemoteDeletionRemove to remove deleted directories.
- RemoteDeletionNotify and RemoteDeletionForward messages are not sent
to the originator of the remote deletion request. The originator
only needs the action reply.
- Added ProtectDefault configuration directive to set a default Protect
value for all areas not named on Protect directives. Default is 0.
Affects netmail add and all query operations.
- Merged OS/2 changes provided by Bill Andrus.
- Recompiled with upgraded MSC 6.00A
----- George Peace 1:13/13 -----