┌─────────────────────────────────────────────────────┐
│ ██████ ▄▄ ██ ██████ ██████ ██████ │ Version: 1.2
│ ██ ██ ██ ██ ██ ██ ██ │ Release: 01.06.1992
│ ████ ██ ██████ ██████ ██████ ██ █████ │ Author : Matjaz Koce
│ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ │
│ ██ ██ ██████ ██████ ██ ██████ ██████ │ (c) MicroArt d.o.o
├─────────────────────────────────────────────────────┤ 1991-92
│ FidoPCB - FidoNet to PCBoard 14.x mail interface │
└─────────────────────────────────────────────────────┘
Lazy Sysop's rule:
"Long manuals are never printed and read completely"
FidoPCB 1.2 Page i
-----=- Table of contents -=---------------------------------------
Naming Conventions -=-------------------------------- ii
Distribution File -=--------------------------------- ii
Distribution Rules -=-------------------------------- ii
Contacting the Author -=----------------------------- iii
Shareware -=----------------------------------------- iii
Unregistered Shareware version -=-------------------- iii
Overview -=------------------------------------------ 1
Limitations -=--------------------------------------- 2
Installation and Setup -=---------------------------- 3
Command line parameters -=--------------------------- 5
Configuration file -=-------------------------------- 7
Lost Mail -=----------------------------------------- 13
Handling NetMail -=---------------------------------- 14
Running FidoPCB as a DOOR -=------------------------- 16
Areafix -=------------------------------------------- 17
Support and distribution nodes -=-------------------- 18
Copyrights, Trademarks and Warranty -=--------------- 19
Credits -=------------------------------------------- 20
FidoPCB 1.2 Page ii
-----=- Naming Conventions -=----------------------------------------------
FidoPCB is distributed using the file naming convention of: FPvvb.aaa,
where 'vv' stands for the version number (ie. 13 for version 1.3, 50 for
version 5.0). The 'b' refers to a letter code specifying (A)lpha, (B)eta
or (S)hareware release versions (ie. The shareware release is distributed
as FPvvS.aaa). The AAA suffix refers to the compression method used on the
distribution archive. This may be ARC, ZIP, ARJ, etc. When referring to
the distribution file in the documentation, it will usually be referred to
as the distribution archive.
-----=- Distribution File -=-----------------------------------------------
The following files should be present within the distribution archive:
File Description
============ ========================================================
FILE_ID.DIZ Archive description
MICROART.BBS MicroArt BBS Description and Phone Numbers
ORDER.FRM FidoPCB Order Form
HISTORY.DOC File describing changes from version to version
FIDOPCB.DOC The FidoPCB User's Manual
FIDOPCB.EXE The executable program
FIDOPCB.CFG Sample (self describing) configuration file
FIDOPCB Sample DOOR file
LOST. PCBoard message base for lost mail
LOST.NDX Index file for LOST.
MATRIX. PCBoard message base for NetMail
MATRIX.NDX Index file for MATRIX.
RUNFD.BAT Sample Batch used to run FrontDoor, PCBoard and FidoPCB
============ ========================================================
Alpha/Beta versions usually do not include the User's Manual. The revision
history file, HISTORY.DOC, is included however, and should be consulted to
see brief descriptions of changes and fixes. Please be sure to read this
file if you are working with an alpha or beta version of FidoPCB!
-----=- Distribution Rules -=----------------------------------------------
Sysops MAY place 'ZIP Comments' in the FidoPCB distribution archive file if
they normally do so with all their download files. Sysops MAY place
additional files (such as 'README.1ST' or 'BBS_AD') ONLY if file names
don't conflict with the files already in the distribution archive (see
previous sentence).
Distribution of the alpha and beta versions is restricted to those systems
with specific permission to distribute them. Do not distribute any version
of FidoPCB except the unregistered shareware (FPvvS.aaa) version!
FidoPCB 1.2 Page iii
-----=- Contacting the Author -=-------------------------------------------
Problems, questions, and suggestions should be directed to Matjaz Koce:
Modem: MicroArt BBS
Node 1: +38 66 34 986 [1200-9600]
Node 2: +38 66 33 816 [1200-2400]
Node 3: +38 66 37 536 [1200-2400]
Mail: MicroArt d.o.o Phone: +38 66 24977
Matjaz Koce Fax: +38 66 21275
Marusiceva 5
66000 Koper
Slovenija
EchoMail: AdriaNet: Sysops, Shareware, HomeMadeSW Conferences
FidoNet: FidoPCB, Enet.sysop Conferences
SaltAir BBS: Sysop Chat, Net_mail, Utility
NetMail: 2:380/100@FidoNet.org
2:333/606@FidoNet.org
-----=- Shareware -=-------------------------------------------------------
Since you've most likely read statements under the heading "Shareware"
before, I won't bother going into the idea again. Simply be aware that
FidoPCB is Shareware (US$ 39, or 62 DEM for the 256 area version). The
registered version has some additional features. The ORDER.FRM file
contains the registration form and price information. You can also send me
NET_MAIL, or leave a comment to the sysop on MicroArt BBS.
Any and all registered users may operate any current and future releases of
FidoPCB v1.x (both registered and beta versions). Both registered and beta
versions are always available from MicroArt BBS and other support BBS's,
and may be downloaded from MicroArt BBS as desired.
Registration will also give you access to the BBS support conference
called FidoPCB, to share your experiences with other registered users.
In this conference you can also make suggestions, report bugs (I hope
this won't happen), and so on.
-----=- Unregistered Shareware version -=----------------------------------
Running FidoPCB will indicate whether you are using the shareware [NR]
or registered [Serial#] version. The unregistered version will accept a
maximum of 20 configured areas. The Tearline will also indicate that
you're using '---FidoPCB [NR]'. There are no other limitations in the
unregistered versions of FidoPCB.
FidoPCB 1.2 Page 1
-----=- Overview -=--------------------------------------------------------
FidoPCB is a utility used to import/export FidoNet type messages into
PCBoard message bases. Messages are transferred between many different
BBS's in, so called, Fido FTS-2 type packets. FidoPCB's features include:
- Unpacking of compressed packets (ZIP, ARC, ARJ, LHA formats)
- Importing of PKT files containing messages for various AREAS (without
conversion into MSG format) into PCBoard message bases
- Exporting of new messages from PCBoard message bases
- Packing of exported messages
- Create the necessary MSG files for FrontDoor (send file, hold file)
- Create the necessary OUT file for BinkleyTerm
- Support for up to 10 AKA Aliases
- Bi-directional NetMail (private FidoNet mail) handling.
- Recognition of CRASH, DIRECT, INTL and other FidoNet message flags
- Handling of AreaFix commands (if you are a host, new areas can be
connected or removed automatically) with connection security levels
and passwords
- Support for networks and multinode PCBoard systems with file sharing
- Configurable as a DOOR (requires a Fossil driver)
- Duplicate Message checking
- Recognition of ^aINLT and ^aFMPT flags for imported NetMail messages
- Recognition and support of PCBoard's "Private" message flag
All of these, and other features can be used with multiple aliases (AKAs).
FidoPCB 1.2 Page 2
-----=- Limitations -=-----------------------------------------------------
As mentioned, the unregistered version will handle only 20 configured
areas. Registered versions of FidoPCB can handle 256, 512, 1024 or more
message areas, depending on your needs.
By setting FILES=65 or higher in CONFIG.SYS, FidoPCB will be able to
process mail for 30 configured nodes (if you are working as HUB or HOST).
Future versions will have limitations dependent on the FILES setting, and
available memory only.
FidoPCB doesn't check how much disk space is available, so be sure that
there is at least 1Mb or more free space available (depending on your
packet size, and the number of configured Nodes and areas). Your system
should have at least 350K of free RAM available, mainly to run archivers
like PKUNZIP, etc. For exact memory requirements, please
check the manual for the appropriate archiver(s) for details.
FidoPCB can handle messages of up to 64Kb. Future versions will be able to
accomodate messages of unlimited size.
FidoPCB 1.2 Page 3
-----=- Installation and Setup -=------------------------------------------
Included in the distribution archive, is a sample configuration
file. I advise you to use it as an example. You should also have
experience using PCBSETUP, as you'll have to install two additional
conferences (Matrix and Lost Mail). This will be discussed later in this
Manual. Also be sure you placed the directory containing the various
archivers (PKUNZIP, PKZIP, ARJ...) in your search PATH. Alternately, you
can define their locations in the FIDOPCB.CFG file.
Throughout this manual, the directory where FidoPCB resides in, is
referred to as FIDOPCB. You may change this if you wish. The
Installation is divided into four steps (#3 is the longest :->):
1) Create the FIDOPCB directory, and change to it with the CD command
2) Extract FPvvb.aaa: FIDOPCB.EXE - executable code
FIDOPCB.CFG - sample configuration file
FIDOPCB.DOC - The User's Manual
RUNFD.BAT - sample BAT file for FrontDoor
MATRIX.* - message base and its index
LOST.* - message base and its index
3.1) Using a text editor, edit the FIDOPCB.CFG configuration file.
Lines should end with LF/CR. DON'T use tabs: CHR(9)!
The configuration file is 'self describing'. All of the commands
and parameters are discussed in the Manual. Don't forget to set
up all of the conferences you entered in the configuration file
under the AREA parameter, with PCBSetup. You must also go into
PCBoard and join them, in order to create the respective MSGS and
MSGS.NDX files if they don't already exist.
3.2) Create an area with PCBSetup, where lost mail should be placed.
Use the directory you specified with the LOST_MAIL command in
FIDOPCB.CFG. Copy the LOST.* files to that directory.
3.3) Create an area with PCBSetup, where NetMail should be placed. Use
the directory you specified with the NET_MAIL command in
FIDOPCB.CFG. Copy the MATRIX.* files to that directory.
3.4) Run FIDOPCB with the SET ALL TOP commands to both check for errors
in the configuration (they will be reported), and to set all of the
Last Message Read (LMR) pointers. If an error is reported, repeat
step 3.1
3.5) Select one area as a 'test area', and enter some (at least two)
messages via PCBoard (do not use messages with *Origin lines, unless
you're using the FORCE parameter on the FidoPCB command line!)
3.6) Run FIDOPCB with the EXPORT parameter to export the test messages
3.7) Check the results by looking in the directories specified with the
PACKET and MAIL commands in FIDOPCB.CFG, and examining FIDOPCB.STA.
If nothing is there, repeat step 3.
FidoPCB 1.2 Page 4
-----=- Installation and Setup -=------------------------------------------
4) Include FIDOPCB in your BAT files for events (see sample RUNFD.BAT)
5) Install FidoPCB as DOOR (Optional)
If you are unable to set up FidoPCB, mail me at my BBS. I'll be there
to help you.
FidoPCB 1.2 Page 5
-----=- Command line parameters -=-----------------------------------------
Running FIDOPCB.EXE without parameters or with the /? switch will display
all of the available command line parameters on the screen. FidoPCB needs
only simple information on the command line in order to run. Most of the
information is read from FIDOPCB.CFG.
Syntax: FIDOPCB [/?] [command] [areaname] [areanumber] [switch]
/? Displays a short description of all commands and switches
Valid commands are: EXPORT, IMPORT, TOSS, SET, LIST, STAT
Valid switches are: FORCE, RESET, STRIP
Commands:
EXPORT - Exports all new messages (since the last execution of FIDOPCB),
and updates the Last Message Read (LMR) pointers
IMPORT - Looks for new Mail Packet files in the FILES directory, and
imports them into the apropriate PCBoard message bases. It
also updates the LMR pointers, regardless of there being any
messages to export
TOSS - Combines the functions of the IMPORT and EXPORT commands by
exporting all new messages, and looking for new Mail Packet
files, importing them if found, and then updating the LMR
pointers
SET - The syntax for the SET command is:
SET <areaname>/ALL <number>/TOP
It sets the LMR pointer for <areaname>, or for all areas if you
specify the ALL parameter. Using the TOP parameter instead of
a number will set LMR pointer to the highest message. You may
use negative numbers to roll back the LMR pointer(s) from the
current value, by the number indicated (the number is subtracted
from the high message number). If the number is above the
highest message, the highest message number will be used.
LIST - The syntax for the LIST command is:
LIST <areaname>/ALL
It lists the LMR pointer(s) and area types. Using the ALL
parameter instead of <areaname> lists all areas.
STAT - Displays statistics for all inbound/outbound mail
Switches:
DOOR - Works only with a Fossil driver installed, and requires
access to PCBOARD.SYS. It can be used with all of the
other commands and switches.
RESET - used with the STAT command to reset statistics to 0
STRIP - Converts all characters above CHR(128) into asterisks (*).
Used with the EXPORT and TOSS commands.
FORCE - Overrides checking for "Origin:" lines. The purpose of
checking for these lines is to avoid sending out received
messages. Used with the EXPORT and TOSS commands.
FidoPCB 1.2 Page 6
-----=- Command line parameters -=-----------------------------------------
Examples:
FIDOPCB LIST ALL - Lists all areas (name, LMR pointer, type)
FIDOPCB STAT - Shows import/export statistics
FIDOPCB STAT RESET - Resets statistics for all areas to 0
FIDOPCB SET Net_Mail TOP - Sets LMR pointer in MATRIX to the
highest message
FIDOPCB SET ALL -10 - Sets LMR pointer to <current>-10 in all areas
FIDOPCB SET FIDOTEST 1 - Sets LMR pointer in the FIDOTEST area to 1
FIDOPCB TOSS STRIP - Looks for MO?, TH?, etc., and imports them
into PCBoard. Routes messages in PKT files
to other nodes as defined in FIDOPCB.CFG.
Exports all new messages from PCBoard into
PKT files, converting all characters with a
value above CHR(128) (Ç) to asterisks (*).
FIDOPCB EXPORT FORCE - Exports all new messages from PCBoard into
PKT files, including messages with
"* Origin:" lines in the body text, which
are not exported by default.
FIDOPCB IMPORT - Scans for MO?, TH?, etc. files, and imports
them into PCBoard.
FIDOPCB TOSS DOOR - Imports/Exports all messages. Output is
sent to the modem instead of a file.
FidoPCB 1.2 Page 7
-----=- Configuration file -=----------------------------------------------
FIDOPCB.CFG contains the configuration for FidoPCB. The configuration file
can, and should be created with a standard text editor such as QEdit,
PCWrite, or EDLIN. Never use Word Processors such as Word, WordStar or
WordPerfect, since they may put additional, unwanted characters into what
should be a standard ASCII text file. Maximum line length is 1024
characters.
Lines starting with a semi-colon (;) are ignored. Each command should be
specified on a separate line, and no TAB characters (CHR(9)) should be
imbedded on the line. The sample FIDOPCB.CFG included in the distribution
archive should be used as a point of reference.
Do NOT leave any blank lines between commands. Because blank lines are
ignored, FidoPCB will point to the wrong line number if an error should
occur. If you place a semi-colon on otherwise blank lines, then FidoPCB
will be able to point to the correct line.
Future versions of FidoPCB will include a configuration program in order to
ease the configuration process.
Valid commands are: ORIGIN, TAG, SYSOP, NODE, AREA, AREA_MSGS, MAIL,
IGNORE_ECHO, PACKET, WORK, FILE, COMPRESS, FLOW_TYPE,
AKA, USE_AKA, AKA_TAG, INTERFACE, NET_TOSS, NETWORK,
LOST_MAIL, NET_MAIL, PCBOARD, FRONTDOOR, ZIP,
UNZIP, ARC, UNARC, ARJ, UNARJ, LZH, UNLZH, MAX_MSGS,
DUPE_CHECK, DOMAIN, BAD, NO_BELL, AREA_LEVEL,
NODE_LEVEL, PASSWORD, AKA_DOMAIN
Most of the commands have default values so it isn't necessary to use them
in your configuration file.
Commands are separated into six groups: Directory Descriptions, Archiver
Definitions, Area Descriptions, Node Descriptions, Strings, and Switches.
Some are strictly connected. For instance:
AREA_MSGS, AREA_LEVEL follow the AREA command
NODE_LEVEL, SYSOP, COMPRESS, FLOW_TYPE, USE_AKA follow the NODE
command
AKA_TAG,AKA_DOMAIN follow the AKA command
SYSOP follows the ORIGIN and NODE command
DIRECTORY DESCRIPTIONS: Limited to 64 characters per description, and
the described directory must exist when FidoPCB is run.
Command Description
─────────── ─────────────────────────────────────────────────────────────
FILE path to inbound packets (where received files are placed)
PACKET path to outbound packets (where outgoing packets are placed)
MAIL path to *.MSG (where FrontDoor finds .MSG files)
BAD path to bad packets (used for packets that contain errors)
FidoPCB 1.2 Page 8
-----=- Configuration file -=----------------------------------------------
Command Description
─────────── ─────────────────────────────────────────────────────────────
WORK path to FidoPCB's work directory (a RAM disk if possible)
LOST_MAIL path to LOST.* (PCBoard area where lost mail is imported)
NET_MAIL path to MATRIX.* (PCBoard area where NetMail is imported)
** Remember: The recipient's Net address goes on the
first line of a message
PCBOARD path to PCBOARD.SYS (created by PCBoard for running Doors)
FRONTDOOR path to FrontDoor files (used to generate semaphore files)
Examples: MAIL c:\front\mail
PACKET f:\microart\pcb\fidopcb\packet
PCBOARD m:\pcb
SWITCHES: Enable or disable certain functions and features. Defaults are
the first listed settings listed in the table.
Command Switches Description
─────────── ────────── ─────────────────────────────────────────────────
INTERFACE NONE FidoNet interface program you are using.
BINKLEY
FRONTDOOR
NET_TOSS PCBOARD System to which NetMail is sent. Setting this to
FRONTDOOR 'Both' places mail in both PCBoard and FrontDoor.
BOTH
NETWORK OFF When enabled, allows File Locking. For use with
ON Multitasking and multiple Node environments.
NO_BELL OFF When enabled, FidoPCB will beep when an error is
ON encountered while packets are being processed.
If you use LANTastic or NOS 4.0, this feature
should be disabled.
IGNORE_ECHO ON Exports only those messages with PCBoard's Echo
OFF flag set. If disabled, all messages are exported.
MAX_MSGS 9999 Specifies the number of messages to export at one
time. The valid range is 1-9999.
DUPE_CHECK 200 Specifies the number of messages that are checked
for duplication in areas specified with the DUPE
switch in the AREA declarations. FidoPCB checks
the From, To, Subj, Date, Time and ^aMSGID fields.
Also checked, are the first ten characters of
messages. Any duplicates will be copied into
the LOST mail conference. The valid range
is 1-9999.
FidoPCB 1.2 Page 9
-----=- Configuration file -=----------------------------------------------
Command Switches Description
─────────── ────────── ─────────────────────────────────────────────────
COMPRESS ZIP Compression method to be used on Outbound, as well
ARC as inbound echomail packets.
ARJ
LZH
Examples: INTERFACE frontdoor
NETWORK off
NET_TOSS both
STRINGS: These definitions are used to identify your system and messages
that originate from it.
Command Description
─────────── ─────────────────────────────────────────────────────────────
ORIGIN Your node's main address. Format: Z:NNN/SSS (Zone:Net/Node)
DOMAIN The UUCP organization identifier that is appended to the
^aMSGID flag of messages originating on your system. It can
be up to 20 characters long. The default is "fidonet.org".
SYSOP Name of the SysOp whose system is specified by the ORIGIN
and NODE commands.
TAG The string that will be appended to all messages originating
at your main Net Address.
AKA Alias addresses by which your system is known. Up to 10 AKA
aliases may be defined. Strictly connected to the AKA_TAG
command.
AKA_TAG The string that will be appended to all messages originating
at your AKA Address.
AKA_DOMAIN The UUCP organization identifier that is appended to the
^aMSGID flag of messages originating on your system. It can
be up to 20 characters long. The default is "fidonet.org".
Examples: ORIGIN 2:380/100
DOMAIN fidonet.org
SYSOP Gregor Rudolf
AKA 1 2:333/606
AKA_TAG We are the best in Koper, Slovenija (2:333/606)
AKA DOMAIN fidonet.org
FidoPCB 1.2 Page 10
-----=- Configuration file -=----------------------------------------------
ARCHIVER DEFINITIONS: These definitions are used to identify the location
and names of your archiving utilities. If you already have
that location listed in your PATH statement, then use of these
definitions is not required. If you need to use them, it
isn't necessary to include commandline switches, as they are
already coded into FidoPCB. The proper syntax for using these
definitions is: <drive>:\[path]<utility name>
Command Purpose Requires Embedded Switches
─────────── ────────────────────────────── ───────── ──────────────────
ZIP Generate ZIP format archives PKZIP -M
UNZIP Extract ZIP format archives PKUNZIP -O
ARC Generate ARC format archives PKARC -R
UNARC Extract ARC format archives PKXARC -M
ARJ Generate ARJ format archives ARJ M
UNARJ Extract ARJ format archives ARJ E -U
LZH Generate LZH format archives LHA M
UNLZH Extract LZH format archives LHA E
Examples: ZIP c:\utility\pkunzip.exe
UNARC m:\archiver\pkxarc.exe
ARJ c:\arj.exe
UNARJ c:\arj.exe
UNLZH d:\lharc\lha.exe
AREA DESCRIPTION: Definitions for message area routing. These commands
require multiple parameters in one line, and are strictly
connected to additional commands.
Command Parameters Description Connected to
─────────── ────────── ────────────────────────────────── ─────────────
AREA number Area identifier for connection to AREA_MSGS
the NODE parameter. (Range: 1-127)
name FidoNET's name for the area, as
listed in the comprehensive Areas
directory (ELISTvvv.aaa).
path Path to the PCBoard Message file.
NOMSGS If used, declares the area to be
a pass-through area.
DUPE Enables duplicate checking in the DUPE_CHECK
the area. A control file using 4
bytes/checked message is created.
AREA_LEVEL number Sets a security level for use by NODE_LEVEL
AreaFix to forward the area. The
valid range is 1-9999. Default: 0
FidoPCB 1.2 Page 11
-----=- Configuration file -=----------------------------------------------
Command Parameters Description Connected to
─────────── ────────── ────────────────────────────────── ─────────────
AREA_MSGS filename The PCBoard message file name. If
not defined, the default is MSGS
Example: AREA 1 Clipper d:\pcb\clipper DUPE
AREA_MSGS Clip
AREA 99 For_node_603 d:\pcb NOMSGS
NODE DESCRIPTION: Descriptors for message packet routing. These commands
require multiple parameters in one line, and are strictly
connected to additional commands.
Command Parameters Description Connected to
─────────── ────────── ───────────────────────────────── ──────────────
NODE address Host Node's address (Z:NNN/SSS) SYSOP,
areas The area number(s) tied to this COMPRESS,
Node. Area numbers must be FLOW_TYPE,
defined with the AREA command! USE_AKA
Individual areas can be separated
by commas, and consecutive areas,
ranged with hyphens. If no areas
are defined, packets are created
containing all areas.
NODE_LEVEL number Sets a security level for use by AREA_LEVEL
AreaFix to forward areas with an
equal or lower security level to
the node. Valid range is 1-9999.
Default: 0
PASSWORD string The AreaFix password used by this
node. Limit: 20 characters.
SYSOP Name of the SysOp whose system is
specified by the NODE command.
COMPRESS mode Compression method to used on
packets to/from this node. The
default is ZIP. Valid parameters
are ZIP, ARC, ARJ, LHA.
FLOW_TYPE flag Outbound packet status flag. The
default is NORMAL. Flags are:
NORMAL, HOLD, IMMEDIATE, CRASH.
FidoPCB 1.2 Page 12
-----=- Configuration file -=----------------------------------------------
Command Parameters Description Connected to
─────────── ────────── ───────────────────────────────── ──────────────
USE_AKA number Predefined AKA to be used on
packets sent to this node. AKA's
are defined with the AKA Command!
Example: NODE 2:333/600 1-3,7,15
NODE_LEVEL 3
PASSWORD fidopcb
SYSOP Maurizio Biondi
COMPRESS ZIP
FidoPCB 1.2 Page 13
-----=- Lost Mail -=-------------------------------------------------------
LOST, and the index LOST.NDX, make up the PCBoard compatible message base
that contains mail from any areas not defined in FIDOPCB.CFG. Look at it
occasionally, or set up it in PCBSETUP, since it is one of the indicators
of your system being set up correctly on your end.
Area names defined in FIDOPCB.CFG with the AREA parameter, are compared
with the names found inside the packets. If FidoPCB finds messages
directed to an area that wasn't defined, it puts those messages into the
LOST message base.
The first line of all messages placed in LOST, are saved with the
statement, AREA: <areaname> in the first line. That way, you will be
able to locate problem.
Duplicate messages are also placed in LOST, and are saved with the
statement, DUPLICATE, on the first line, and AREA: <areaname> on the
second line. This permits you to to check the messages, and move or
kill them.
FidoPCB 1.2 Page 14
-----=- Handling NetMail -=------------------------------------------------
MATRIX, and the index MATRIX.NDX, make up the PCBoard compatible message
base file containing NetMail messages (private FidoNet messages). If you
are using FrontDoor, FidoPCB scans for new .MSG files and imports them to
the MATRIX conference in PCBoard. Compressed NetMail messages are imported
automatically without using .MSG files.
When you enter NetMail messages, you must enter the recipient's network
address at the start of the first line using the format: (Z:NNN/SSS.PPP)
Z = Zone number (Default = 2)
N = Net number
S = Site (Node) number
P = Point number (optional)
Don't forget to enclose the address in parenthesis "()", as FidoPCB only
checks for this format! MATRIX messages are then converted to the .MSG
format used by FrontDoor, so you can review them. Exported messages are
placed in the directory you specified with the MAIL command in FIDOPCB.CFG,
from where they are routed by FrontDoor.
To add special flags to a message, add one of the following commands,
enclosed in parenthesis "()", at the start of the second line: HOLD, IMM,
CRASH, INTL. Multiple flags can be entered by separating them with a comma
(,) and no trailing spaces.
Flag Description
───── ───────────────────────────────────────────────────────────────────
HOLD Causes FrontDoor to put this message on hold.
IMM Causes the message to be forwarded immediately.
CRASH Forces FrontDoor to forward this message directly to the recipient.
INTL Forces the message to be routed via the Zone Gate, to recipients
outside your zone. Do not use this flag in conjunction with the
CRASH flag.
Example:
===================================================
To: ALL Date: 10.10.91
From: Gregor Rudolf Time: 12:13:11
Subj: Just sampling... Read: NO
Conf: MATRIX (54)
(2:380/101) <- recipient's address
(IMM,CRASH) <- special flags
This is only a sample message.
=====================================================
If you have NET_TOSS set to BOTH in the configuration file, DO NOT use FM
to read messages, as this will generate duplicates in the MATRIX conference
in PCBoard.
FidoPCB 1.2 Page 15
-----=- Handling NetMail -=------------------------------------------------
The first line of all received messages will contain the sender's address,
in the format: FROM:(Z:NNN/SSS.PPP). This allows you to see the sender's
address and facilitate your replies. Messages in this conference will also
include all additional lines extracted from the message header, including
the ^aMSGID, ^aINLT and ^aFMPT lines.
FidoPCB 1.2 Page 16
-----=- Running FidoPCB as a DOOR -=---------------------------------------
FidoPCB can be configured to run as a DOOR. This mode will allow you and
you users to process mail independently from FrontDoor and other events.
Two things are needed to set FidoPCB up as a DOOR: First, you must have a
Fossil Driver such as BNU or X00 installed on your computer. Second, the
PCBOARD.SYS file generated by PCBoard should be in the directory defined by
the PCBOARD command in FIDOPCB.CFG.
Create a batch file using the sample FIDOPCB file as an example. Then,
using PCBSetup's Main Conference (and/or a conference specific) Door Paths
editor, create an entry for the door. You may set the Password, Security
and Shell options as you desire. The LOGIN, USER.SYS and DOOR.SYS options
must be set to NO.
FidoPCB obtains all the necessary information from PCBOARD.SYS. The
program also generates the two semaphore files used by FrontDoor, a
function that is of particular help in the case of multinode systems.
You may want to restrict access to the FidoPCB door on your system, to
prevent abuse, and to keep dummy NetMail and duplicate messages from
circulating around the world. On my system, for instance, only a few users
have a security level high enough to run the FidoPCB door.
FidoPCB 1.2 Page 17
-----=- Areafix -=---------------------------------------------------------
Areafix is active when you're operating as a HOST or HUB and Access to it
is allowed only for configured nodes. It allows all of your configured
nodes to list, select and deselect available areas on your node, with a
simple NetMail message. Areafix messages should be addressed to Areafix.
The subject of the message should include your AreaFix password, and the
optional "-q" switch in order to generate a list of selected areas.
Areas are activated by entering their name in the body text. To turn off
active areas, this name should be preceded with a hyphen (-).
Example: From: Matjaz Potrc, MojsteR BBS (2:380/101)
To: Areafix, MicroArt BBS (2:380/100)
Subj: fidopcb -q
-------------------------------------------
Clipper
-C_Echo
FidoPCB 1.2 Page 18
-----=- Support and distribution nodes -=----------------------------------
All FidoPCB support BBS's carry the FidoPCB echo conference. You can find
the most recent releases of the Beta and Shareware versions of FidoPCB, on
both the support and distribution sites. If you have any problems with the
program, simply join the support conference. My partners and I will answer
your questions. We only ask that you be patient in waiting for your
answers.
The following, is a list of FidoPCB support boards around the world:
Country Board Name FidoNET Phone Protocols
──────── ────────────────────── ───────── ─────────────── ────────────
Slovenia MicroArt BBS 2:380/100 +38 66 349-86 V.32
MojsteR BBS 2:380/101 +38 68 237-31 V.32bis
Italy Fido_TS_1 2:333/603 +39 40 378-3111 V.32bis/HST
USA The Sweet Life PCBoard 1:102/815 1 818 882-9058 V.32bis/HST
NETRef BBS 1:273/214 1 215 736-1889 V.32bis/HST
Canada Innovatron 1:240/333 1 819 893-9682 V.32bis/HST
FidoPCB 1.2 Page 19
-----=- Copyrights, Trademarks and Warranty -=-----------------------------
All of the programs mentioned are copyrighted and/or trademarked by their
respective authors. Please refer to each program in order to determine the
actual copyright/trademark owner(s) as appropriate or needed.
IN NO EVENT SHALL THE AUTHOR, MATJAZ KOCE, BE HELD RESPONSIBLE IN
ANY WAY, FOR THE BEHAVIOR OF ANY VERSION OF FIDOPCB. NEITHER THE
AUTHOR, OR ANY OTHER PARTY AUTHORIZED BY THE AUTHOR TO MODIFY AND
DISTRIBUTE FIDOPCB, SHALL BE HELD LIABLE FOR DAMAGES INCURRED,
INCLUDING ANY LOST INCOME, AND/OR OTHER SPECIAL, INCIDENTAL, OR
CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE, OR INABILITY TO USE
FIDOPCB. THIS INCLUDES, BUT IS NOT LIMITED TO LOSS OF DATA, DATA
BEING RENDERED INACCURATE, LOSSES SUSTAINED BY THIRD PARTIES, OR
A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS. THE
ABOVE TERMS APPLY IN ALL CASES AND SITUATIONS, EVEN IF THE AUTHOR
HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES, OR FOR ANY
CLAIM BY ANY OTHER PARTY.
FidoPCB 1.2 Page 20
-----=- Credits -=---------------------------------------------------------
Thanks to:
- All beta testers
- Gregor Rudolf, who helped me with advice.
- Damjan Pavlovec, Matjaz Potrc, George Silberstern and Mike Waldron,
for their help with the documentation.
- George Silberstern, for being providing user support in the USA
- Mosaic v1.0 and other PCBoard mailer/tossers, as their bugs, slow
processing, inabillities made me feel bad. So much so, that
I decided to write a tosser of my own
Revision history can be found in the file, HISTORY.DOC, which is included
in the FidoPCB distribution archive.
PLEASE, SUPPORT SHAREWARE!
Thank you.