home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
DP Tool Club 17
/
CD_ASCQ_17_101194.iso
/
vrac_os2
/
ntmgr98p.zip
/
WHATSNEW.098
< prev
Wrap
Text File
|
1994-09-05
|
6KB
|
240 lines
========================================================================
WARNING! You *must* make changes to your old configuration files if you
want to upgrade to this version from NetMgr 0.97 or an earlier version!
------------------------------------------------------------------------
In short:
* The format for EchoCopy, EchoMove and Bounce actions has changed: you
need to add an origiantion adress for this now.
* NetMgr will not keep on scanning for more masks that match anymore. As
soon as a matching mask is found, scanning for matching masks stops. So
you must specify *all* actions you want to perform on a message with the
*first* mask that would match the message! Put the most 'specific' mask
first, and specify more generic, 'catch all' Masks at the end of the
config!
Performing more than one action for a certain mask is very easy now,
read the rest of this whatsnew file to find out how!
========================================================================
Changes and fixes since NetMgr 0.97:
* Squish code updated to Squish v1.10 standards (unlimited number of
messages in an area etc).
* New command line switch: -q will make NetMgr run in 'quiet' mode, where
hardly anything will be written to the screen.
* Kludges (VIA lines) are now invalidated when a message is bounced.
* EchoCopy and EchoMove can now use any address as their origination
address, not just 'Home'.
The format for those commands have changed to:
Action EchoCopy <address> <area> [seen-by]
Example:
Action EchoCopy 60:100/1.0 $c:\local\mvdmsgs 2:281/527
This will copy a message to the area 'local\msdmsgs', will use 60:100/1.0
as the origination address (origin line and MSGID) and will add the string
'2:281/527' to the SEEN-BY.
* Similar change for 'bounce'.
Format now:
Action Bounce 81:431/23 c:\txt\bounce.txt
Bounce messages and use 81:431/23 as origination address.
In addition, 'bounce' will now also show the original message header of
the message that was bounced. This information is shown below the
bouncetext, but (of course :-) before the message body.
* Bounce also has a few brothers now, in the same style:
■ Action EmptyBounce <address> <bounce textfile>
Will send a message back, with only the bouncetext as the body.
■ Action HdrBounce <address> <bounce textfile>
Will send the message back, with the bouncetext and the header of the
original message. The body of the original messag is not shown.
* New action: Forward.
Format:
Action Forward <mask>
Example:
Action Forward Gerard, 2:281/527.0, Kasper Kwant, 2:500/144.0, Test!, +l+c
This action will forward the message (shwoing both header and body, like
'bounce' does) to someone else.
The header of the message will be constructed using the mask you specify.
In this case, it will look like this:
From: Gerard, 2:281/527
To : Kasper Kwant, 2:500/144
Subj: Test!
Attr: Loc, Crash
----------------------------------
* Forwarded by NetMgr+ 0.98
Original message:
From:
To : <--- header of original message.
Subj:
----------------
Bla, bla <--- body of original message.
* New action: HdrFile
Format:
Action HdrFile <file to write to>
Example:
Action HdrFile c:\temp\headers.txt
This action will write a message HEADER to file. It is just like the
action 'FILE' but only writes out the header, not the message body.
* You can now specify several actions for one mask, and several masks
followed by one action.
Like this:
Mask *, *, Gerard van Essen, *, *, *
Mask *, *, Gerard van.Essen, *, *, *
Action Copy $c:\mail\persnet
When either of the two Masks is matched, the 'Copy' action will be
performed.
Another example:
Mask *, *, Gerard van.Essen, *, *, *
Action Copy $c:\mail\persnet
Action Copy !c:\mail\persjam
When the above mask is matched, BOTH actions will be performed on the
message, so two copies will be made.
==> !! Please note:
NetMgr will not keep on scanning for more masks that match anymore. As
soon as a mask is found, scanning for matching masks stops. So you must
specify all actions you want to perform on a message with that mask.
* Certain Mask/Action combinations will now be tied to a certain ScanDir.
When a ScanDir statement is found in NetMgr.cfg, all Mask/Action
combinations following that ScanDir up to the next ScanDir statement will
(only) be valid for that particular ScanDir.
ScanDir c:\fd\netmail
Mask A
Action ..
Action ..
Mask B
Action
Mask C
Action
ScanDir c:\fd\usenet
Mask D
Action
In the above example, c:\fd\netmail will be scanned for Mask A, B and C,
but not for Mask D.
c:\fd\usenet will (only) be scanned for Mask D.
You can also specify more than one ScanDir, followed by one or more Masks.
All ScanDirs will be scanned for those masks.
ScanDir c:\fd\usenet
ScanDir $c:\fd\netmail
Mask E
Action
In the above example, both c:\fd\usenet and $c:\fd\netmail will be scanned
for mask E.
* New ACTION: MakeMsg.
Format:
Action MakeMsg <file for body> <mask>
Example:
Action MakeMsg c:\txt\body.txt Art, 2:281/527.0, SysOp, 1:138/211.0, Poll me!, +l
This will generate a message to SysOp on 1:138/211, with body.txt as the
body of the message.
* New Action: ChangePath
Format:
Action ChangePath <new path>
Example:
Action ChangePath c:\frodo\infiles
This action replaces the path of files found in the subject line. It makes
sense to only use this for file attach messages, as you will get a
terribly screwed up subject line otherwise :-)
In the above example, the subject line:
Subj: c:\tmp\myfile.txt d:\outfiles\test.txt
will be rewritten to:
Subj: c:\frodo\infiles\myfile.txt c:\frodo\infiles\test.txt
If a file does not have a path at all, the defined path will be added:
Subj: test.txt
will get:
Subj: c:\frodo\infiles\test.txt
If the defined change will lead to a subject line that is too long (the
new path is longer than the old one, and the subject would get longer than
71 chars) the message will not be changed.
* Several other minor fixes and enhancements.