home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
The Pier Shareware 6
/
The_Pier_Shareware_Number_6_(The_Pier_Exchange)_(1995).iso
/
035
/
ntmgr99p.zip
/
WHATSNEW.099
< prev
Wrap
Text File
|
1994-10-22
|
9KB
|
246 lines
alpha 1
-------
* New keyword: 'FrodoLog'. If you add this to your NetMgr.cfg file, NetMgr
will create a logfile that looks like what Frodo generates.
* Nodelist lookup facilities. NetMgr can now check the nodelist to see if a
particular address is listed.
Supported are the Version 7 nodelist, FrontDoor format nodelists and the
GIGO nodelist.
This last one is the index used by (surprise :-) GIGO (a fine Internet <->
Usenet gating package by Jason Fesler).
Jason graciously donated sources for both generation and lookup for
GIGO's nodelist index. The nice things about it are it's small size (for
the current world nodelist [nearly 3 MB!] the index is about 70 kB) and
the compilation speed (on my 386/40 compiling the world nodelist takes 8
seconds).
The nodelist lookup can be activated by using one of two 'pseudo
attributes': '#' and '@'.
+@ means the destination address must be listed.
-@ means the destination address must NOT be listed.
+# means the origination address must be listed.
-# means the origination address must NOT be listed.
Example:
Mask *, *, *, *, *, -@
Action Bounce 2:281/527 c:\msgs\unlisted.txt
This will bounce all messages addressed to systems that can't be found
in the nodelist, placing 'unlisted.txt' at the top of the
bounce-messages.
--> A point of a listed node is assumed to be listed as well!
Keywords:
Nodelist <path> - gives the path to the Version7 nodelist.
FDnodelist <path> - gives the path to the Frodo nodelist.
GigoNodelist <path> - gives the path to the GIGO nodelist index.
* To speed up access to regularly checked nodes, there is a simple cache
system for the nodelist checking: the last xx nodes will be cached in a
small file that is saved to disk at exit. For a new run, NetMgr will read
this file and keep it in memory to check it before actually doing a
lookup in the nodelist on disk.
Two keywords to make it work:
NodelistCache <path> - where to keep the 'cache file' (always called
nodes.buf).
CacheSize <number> - Number of nodes to keep in the cache. If you
usually have mail to 100 different addresses in
your netmail area, set it to at least 100.
When you update/recompile your nodelist, erase the 'cache file', as the
data that is cached may be invalid after the nodelist update!
* In order to support the new lookup feature, another action is added:
AddNote <textfile>
This will add the text from <textfile> at the top of the message. You
could use this to send a message through with a note ('please do not
reply through this system, the originating system is unlisted'). You know
those annoying messages :-)
* Added limited mailpacking capability (Binkley style outbound). The new
Action to use for this is: 'PackMail'.
Format:
PackMail <origination address> <destination address>
The Addresses are used to build the packet itself (ie: the packetheader),
*not* the messages *inside* the packet (for those, NetMgr obviously uses
the addresses found in the message header itself).
The second one (destination address) can also be '*', to indicate NetMgr
should use the same address as is found in the 'destination address
field' in the message.
Some examples:
Mask *, 2:281/527.0, *, *, *, +f
Action Packmail 2:281/527.0 *
This takes all file request messages, generated by 2:281/527, and
properly generate a request out of it. The request will be addressed to
the system that is also found in the 'destination address' field of the
message (that makes sense) :-)
Mask *, 2:281/527.0, *, 1:*/*.*, *, +l
Action Packmail 2:281/527.0 1:138/211.0
This will take all messages from 281/527, addressed to any zone 1 system,
and pack them in a mailpacket addressed to 1:138/211 (No, Evin, I am not
really doing this :-))
Currently, NetMgr will (hopefully) properly:
- Request files (make a *.REQ file).
- Attach files (make an *.?LO file). FLAGS KFS & TFS are supported.
- Pack (bundle, not compress) messages (make *.?UT file).
- Strip paths from subject lines of 'file attach messages'.
- Handle update requests.
- Handle (update) requests with passwords.
- Generate and check busy flags.
The packing is 'crude' (sp?): it is dumb, really. Right now, NetMgr will
happily pack messages to yourself, for example. Or route files to an
overseas system, even if they are not coming from your system etc. Or
route file requests.
Like all other commands, NetMgr simply scans headers and does what it's
told, the logic of it's actions has to come from YOU.
The only 'intelligence' of the packmail function:
■ It will not pack messages that are 'sent' or 'locked'.
■ It will fully automatically set the 'sent' bit after sending.
■ If the message is 'kill/sent', it will even delete it! Wow!
I'm still working on this function. Please comment to make it work well.
Also, check if the packets are generated OK and if the generated packets
are OK, this is new for me :-)
The best use for this function is for Fastecho/GEcho users, I think.
Where those programs will not correctly pack/process crash, file request
and attach messages in Binkley environments, NetMgr can pick up what they
leave behind and put this stuff in the Binkley style outbound.
Once again, Jason Fesler gave me most of the code for this. I could do
quite some 'cut & paste' and learn from his code.
He was also the one who came with the idea to let NetMgr do this. I was
actually planning on writing a separate program, never thought of NetMgr!
* Similar, but not the same: MoveMail.
Format: Action MoveMail <orig> <dest> <dir>
<orig> : origination address to use (packet)
<dest> : destination address to use (packet)
<dir> : output directory for packet.
This will create a mailpacket, not in Binkley's outbound but in the <dir>
you specify. The packetname will be a unique name created by NetMgr. The
packet will be from <orig> to <dest>.
Using '*' for <dest> is not allowed here (I don't think it is useful - it
can be added though).
If a file is attached to the message, it will be copied to <dir> as well.
The FLAGS KFS & TFS are respected too.
The 'sent' bit is set, or the message is killed (kill/sent).
Sent/Locked messages will not be processed.
Possible uses: mail delivery through a LAN, maybe also sending mail to
gateways on your system, dunno. Whatever, as long as Jason is happy :-)
* A new keyword in NetMgr.cfg:
Outbound <base outbound directory>
This has to point to your Binkley style primary outbound directory.
NetMgr can create names for outbound directories other than the default
zone (names like: C:\BT\OUT.006) itself, so one 'OutBound' statement does
it all.
Domains are not supported.
* New Action: 'Ignore'.
This action does absolutely nothing, but is it a 'match', so scanning for
a matching mask will stop after this.
For example:
Mask *, !2:281/527.0, *, *, *, +a
Action Ignore
Mask *, *, *, *, *, *
Action Packmail 2:281/527.0 *
This will make sure the 'packmail' stuff is never reached for file
attaches not originating from 281/527.
In this example you could easily do that in one Mask, of course, but I'm
sure there are good uses for this (even though I can't think of a good
example right now :-).
alpha 2
-------
* AddNote action was not recognized by the config reader. Fixed.
* NetMgr now supports FSC-0035 (REPLYADDR/REPLYTO kludges) and will now
properly bounce messages with these kludges. (Back to the internet :-)
alpha 3
-------
* Fixed a bug where ^AFLAGS handling was messed up in a rewrite.
* ^AVIA lines format change to match 'modern style' (JoHo and his disciples :-).
* The PackMail action now handles the destination address for the packet
differently. First of all, NetMgr does NOT do any BossRouting for mail
addressed to points anymore. You have to do that yourself now.
PackMail <address> * : Send/Route messages to dest address found in
msgheader (even if it's a point!).
PackMail <address> <address b> : Send/Route messages to address b.
PackMail <address> *:*/*.0 : Send/Route messages to second address,
with the pointnumber always set to 0
(in other words: do Bossrouting for this
entry).
PackMail <address> *:*/0.0 : Send/Route messages to node 0 in the net
of the destination address found in the
header (HostRouting).
* Fixed a memory loss problem for 'PackMail'.
* There was a really nasty and hard to find bug deep down in the Squish
part of the MSGAPI, that would mess up areas in some specific situation
when doing a 'rewrite' (it actually concerned messing up the chain of
free frames, the chain would be 'broken').
I hope the fix goes without side effects..