home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Media Share 9
/
MEDIASHARE_09.ISO
/
mailers
/
bnp420.zip
/
BNP.DOC
next >
Wrap
Text File
|
1993-03-13
|
10KB
|
252 lines
BinkleyTerm (Opus/Portal of Power) Netmail Packer
Version 4.20
Written by Nathan Moschkin
Copyright (C) 1992, 1993 by Nathan Moschkin
Copyright is for program and documentation
Please distribute freely
Special thanks to David Page and Joe Keenan for putting up with my
questions and bugs. Thanks to Mark Prado for giving me a computer
to work on.
Disclaimer and Copyright
------------------------
This program has no garantees, no warentees, no nothing. Use it
as is, and that's that. Do not copy this program in anything
other than the original ARJ archive created by Nathan Moschkin.
This material is copyright 1992, 1993 by Nathan Moschkin
Thank you very much for you attention.
What is BNP?
------------
BinkleyTerm netmail packer is a medium sized netmail handler.
Squish can get the job done, but it's 200k, oMMM is 80k but
doesn't do what this does, handle 4D point numbers. BNP will
automatically create and remove point directories.
Shareware vs. Freeware
----------------------
BinkleyTerm Netmail Packer (henceforth referred to as BNP) does
not REQUIRE registration. If you still wish to register by
donating money, see the file DONATE.FRM.
BinkleyTerm Netmail Packer is NOT PUBLIC DOMAIN. It is FREEWARE,
meaning product support, updates, and product itself is provided
free of charge upon request.
System Requirements
-------------------
BNP will run on any 80x86 machine with at least 256k of free
memory. A mailer and hard drive would be nice too.
BNP works with BinkleyTerm, OPUS-CBCS or Portal of Power.
Because of the nature of FrontDoor and D'Bridge, BNP will not
work with them, it's not in the design. BNP was compiled using
Borland C++ 3.1 and will work on any PC using IBM or Microsoft
DOS 3.30 or later.
Documentation
-------------
Everything is documented in the appropriate file, this is a
fairly self explanitory program.
BNP will automatically reroute/repack .FLO and .OUT files.
Inside the BNP ARJ you will find CONFIG.BNP which is your configuration
file. Here is a description of every configuration command.
ADDRESS zone:net/node[.point][@domain]
Your fidonet technology address. You must specify zone,
net and node. Point is optional. You may specify 10
logical addresses. No wildcard addresses allowed.
NETMAIL d:\path
You must specify a path to netmail. Just insert the drive
and path statements in the NETMAIL line.
OUTBOUND d:\path
Specifies path where outbound packets are stored. In the
case of zone and point differentiations, new outbound areas
may automatically be created.
MAXARCSIZE nnnn
Specifies the size, in kilobytes, for the maximum archive
size, BNP will not add to bundles exceeding this limit.
LOGFILE d:\path\filename.ext
Specifies what file to write log entries to. If this
parameter is omitted, BNP will make no attempts to write
to any sort of log file.
ROUTEFILE d:\path\filename.ext
Specifies where to look for a routing file. You must have
one, this is not an option. ROUTE.BNP is included as an
example.
KILLOLD nnnn
This directs BNP to kill mail older than [nnnn] days. This
is a very destructive feature and should only be used in
areas where space is limited.
GRUNGY [ignore/delete/exclude]
This parameter activates GRUNGY, the grunged message
processor. GRUNGY will produce a GRUNGY.RPT file notifying
you of the messages that were grunged.
This has three options.
delete: kills all grunded messages.
ignore: will keep all grunged messages in place, but will
still produce a GRUNGY.RPT
exclude: do not include grunged messages in the packet,
but do not delete from the message area.
QUIET
Specifies operations in supressed screen writes mode.
PKTTYPE [TYPE2/TYPE2+/TYPE2.2]
Specifies in which FTSC packet format to pack mail.
FTSC-0001 (type 2).
FTSC-0039 (type 2+).
FTSC-0045 (type 2.2).
FTSC-0001 is, for all intents and purposes, STONEAGED.
PACKER_DEF # commands
You must specify at least one archiver. Where '#' is any
character of the IBM ASCII character set. This can be only
ONE character in length, though, or BNP will report ERROR.
PACKUP # node1 [node2] [node3] [node4]
Specifies to pack mail to the specified nodes using the
specifies compressor.
KILL NONE/ALL
Specifies whether BNP should kill all sent messages or
not to kill any sent message, regardless of attribute
setting. If this option is omitted, killing is done
only when killsent status is enabled on the message
BSY_FLAG
This will instruct BNP to create .BSY flags so that
BinkleyTerm will not process mail for that node.
PKT_PASS zone:net/node[.point] password
This specifies that all nodes that are found under this
search specification will be password-protected with
this password. Wildcard addresses allowed.
You will also find ROUTE.BNP. Here is a run down of every routing
command.
SCHED # HH:MM HH:MM [Day1|Day2|Day3 etc...] or [All]
Specifies a schedule with a start and end time in military
24 time. The day specifiers can be any combination of the
abbreviated seven days of the week seperated by a PIPE, but
no spaces at all! Or, for all days of the week, use the
keyword ALL.
Ex: Sched A 16:00 22:19 Tue|Wed|Fri|Sun
POLLxxxx node1 [node2] etc...
Forces BinkleyTerm or OPUS-CBCS to call a system regardless
of whether there is mail waiting or not. Where 'xxxx' are
the following keywords:
CRASH - Send immediately or as soon as possible
DIRECT - Send as soon as non-CM nodes are processed.
NORM - Same as direct, but no garantees that the
bundle will end up going where it's supposed
to.
HOLD - Make other system pickup mail. This is
useless for POLLxxxx but is good for SEND and
ROUTE commands.
NOBUNDLE node1 [node2] etc...
This tells BNP NOT to bundle mail for the specified nodes,
instead mail is kept unbundled and is sent as .xUT packets.
If there is more mail, more is added to the packet.
Routing commands will work normally.
SENDxxxx node1 [node2] etc...
Sends mail directly to the specified nodes directly using
one of the above keywords.
NOTE: an '*' anywhere in place of a number in the fidonet
address specifies that BNP will treat it as GLOBAL.
Ex: SendCM 1:109/40 400 1:261/*
Sends direct Crash to 1:109/40, 1:109/400 and ALL of 261.
ROUTExxxx node [nodes] etc...
Routes mail addressed to [nodes] through [node]. You must
specify at least two entries, a destination and a final
destination.
Ex: RouteDIRECT 1:109/40 1:* 2:* 3:* 4:* 5:* 6:*
Routes all mail for ALL nodes in zones 1 through 6 via
1:109/40.
NOTE: BNP analyzes in decending order. This means that
overrides and ruled exceptions go BEFORE other entries.
ex:
SendCM 1:109/40 400 50 500 60 600 70 700 10 100 20 200
RouteCM 1:109/400 1:109/*
This will route all mail to any node in net 109 via
1:109/400 except the ones listed above that entry.
I hope this explains most of your questions. If you have other
questions, feel free to contact me at +1-301-649-3207 between 6PM and
10PM GMT-5 (EST), or netmail me at 1:109/427.
Acknowledgments
---------------
BinkleyTerm is by Vince Perriello, Bob Hartman and Bit Bucket
Software.
D'Bridge is written by Chris Irwin.
FrontDoor is written by Joaquim Homrighausen.
IBM is a trademark of International Business Machines
Borland C++ 3.1 by Borland International Inc.
Microsoft MS-DOS is by Microsoft Inc.
Opus-CBCS was originally written by Wynn Wagner III
ARJ is by Robert K. Jung