╚═════════════════════════════════════════════════════════════════════════════╝ First you will need to know the number of your HUB's conference that matches
this conference. Under Host Conf # enter in this number. Answer Yes to
the Export/Import prompt. Select the appropriate Tag Line NUMBER (1-9).
NOTE: Unless you have the Export/Import set to Yes, the conference will not
be imported/exported during the process of the .REP/.QWK files.
The last four fields are up to you. The first three are options, the last
field is the pointer that keeps track of where mail should be exported from in
each conference.
Echo Msgs Only refers to echo messages to your HUB that only have an ECHO STATUS
in the MSGS file.
Duplicates refers to check for duplicates when importing messages. If you
wish to check for duplicate in ALL conferences that are imported you can
use the command line switch /DUPS (works with only IMPORT.EXE). This will be
discussed later in the documentation with the IMPORT.EXE program.
Echo Private Messages will echo any messages that have a status of PRIVATE.
This means that they are RECEIVER-ONLY messages in PCBoard and are addressed to
a specific person. Most QWK type networks do NOT support Private Mail. This
options should normally be set to NO.
Msg Pointer is the last read message pointer for the EXPORT.EXE program.
Once you run the EXPORT.EXE, all messages will be reset to the Highest
Message Pointer. The High/Low conference numbers are shown on the screen
for your convenience. You can modify the Msg Pointer if you need to for some
reason.
Repeat the following steps for any other conferences that you will be
setting up. A very simple procedure.
NOTE: When creating the conference information, All Last Message Pointers
are set to 9999999. This is a SAFE number to use so no messages
are exported on your first run. The Msg Pointers will then be
set to the Highest Message number in each conference.
After you have edited all of your conference information, select/create
another network definition if you are echoing through more than one BBS. Then
just edit the new conference information until you are finished with all
networks.
That's it for the NETSM.EXE program.
CAM-MAIL EXPORT.EXE
The EXPORT.EXE program can only be passed one parameter. This is the
network definition name (8 letters max). This will be the EXACT name that
you used in the D NetWork Definitions via NETSM.EXE.
First, make sure that your WORK directory that you specified in NETSM.EXE
exists. If it doesn't, create this directory. Otherwise the program will
not work.
At the DOS command line type:
EXPORT NetDefinition Options
The program will then process any new messages that need to be exported.
EXPORT.EXE will create your .REP file in your .REP directory that you
specified in the CMSetUp.EXE program (E Misc Paths).
If a previous .REP file exists, EXPORT will unzip this file and append
any new messages to this file.
OPTIONS
/LOG - This will let you know what was processed during Export. The name
of the LOG file will be the name of your Net ID plus .LOG. This is
the ONLY option that you should be using when you are officially
exporting mail.
/TOP - This will TOP the All of your conferences for the High Message
Number. Only use this when you are first intialization a particular
network. Meaning, after you have everything setup properly use this
option.
/BUILDREP - This allows the building of a REP file that only contains the
conferences you want to be echoing from your HUB. This will not
affect your Last Message Read pointers inside the door or in Export.
Be aware that this will NOT EXPORT any new messages, but merely
create a REP packet that contains a bunch of messages that say ADD
this conference for scanning. See below for an example of what
happens.
/MAILDOOR:name - This works in conjunction with the /BUILDREP switch. The
:name represents the name of the Mail Door your HUB SYSOP is using.
The Default setting is CAM-MAIL. Here's what happens when you use
the /BUILDREP and /MAILDOOR:QMAIL settings. One Message for each
conference you're echoing is created like this:
TO: QMAIL
FROM: CAM-MAIL
SUBJ: ADD
Basically, all you're doing is configuring your hubs door OFFLINE. CAM-MAIL IMPORT.EXE
When you have downloaded a .QWK file from your HUB and the .QWK file is in
your .QWK directory (Which you specified in the CMSM.EXE program) you will
want to run IMPORT.EXE to import the messages into the correct conferences.
IMPORT will automatically create a file called DUPS.LOG. This file contains the
percentage of duplicate messages that were found. IMPORT create a file called
CRC.DAT. If IMPORT starts hanging this indicates that the CRC.DAT file is
corrupted. DELETE IT IMMEDIATELY.
The IMPORT.EXE has one parameter passed to it along with 2 optional
parameters:
IMPORT NetDef Options
/SYSOP - Any mail that is address to your REAL name will be converted
to SYSOP.
/DUPS - Force duplicate checking in ALL conferences.
/MAILFLAGS - Turn on Mail Waiting Flags when importing messages.
If you use the /FLAGMAIL option, you will no longer
need to use PCBNET.EXE. Free up save HD space <grin>.
/KILLQWK - Will Kill your .QWK file after importing.
/LOG - This lets you know what was processed during Import. The
name of the LOG file will be the name of your Net
Definition plus .LOG.
Once you figure out which options you want to use (I suggest all of them)
use the IMPORT program as defined above.
That's it. Very simple and easy to use. Once you have it all configured
add the EXPORT/IMPORT programs to your EVENT.SYS file and let everything
be automated.
PRESCANNING MAIL PACKETS
CAM-MAIL PRESCAN.EXE
What exactly is the PRESCAN.EXE file? This file will enable you to
create .QWK packets for users during your Event. This is very useful if
you are a HUB for a particular Echo NetWork (U'NI-net, ILink, Intelec, etc.)
as you can PreScan Packets for all of your NODES that call you, which will save
them on-line time and reduce their phone bill.
The number one purpose of prescanning packets, as far as I can see, is to
save money for long distance callers and to free up on-line time.
How do I enable the PRESCAN.EXE? First, you need to go into the USERSM.EXE
program. Select A (Edit Users Flags). Use the ALT-F command to find a user
which you wish to prescan packets. Move the cursor to OffLine Packets and put
a 'Y' in there. Move down to the next line (Packet Name) and select a unique
packet name. I suggest the first 8 letters of the Users Last Name. Each user
needs to have a different packet name. Repeat these steps for each user you want
to prescan packets for.
The next step is to go into your PCB directory where you will be running the
PRESCAN.EXE file. Once in this PCB directory, copy from your CAM-MAIL
directory these files: CAMZIPx.BAT and CAMUZIPx.BAT files. If you are like me
you will only have the CAMZIPZ.BAT and CAMUZIPZ.BAT files.
You're probably wondering why you just can't run the PRESCAN.EXE from your
CAM-MAIL directory. The problem is that when PRESCAN calls the PCB145.EXE file,
PCBoard expects to find your PCBOARD.DAT and your PCBPROT.DAT files. That is
why the program runs in the PCB directory.
The last and final step is to modify your EVENT.SYS file and add these lines
to it:
CD \PCB
\CAM-MAIL\PRESCAN.EXE \CAM-MAIL
Notice that the \CAM-MAIL command line parameter is the path to my
CAM-MAIL directory (Where CAM-MAIL.EXE, CAM-MAIL.KEY, and CAMMAIL.CFG is
located).
One important note: Make sure that your OFFLINE directory exists, otherwise
no .QWK packets will be created. (This is defined in CMSetUp.EXE.)
PRESCAN.EXE creates a log file called PRESCAN.LOG in the current directory.
PRESCAN will create a new file if it doesn't exist, otherwise, it will append
any information to it.
CAM-MAIL LOCALCAM
The purpose of Localcam is to create a QWK packet or insert a REP file as
easily as possible during your event.
Command Line Parameters:
There are a total of 7 command line parameters that can be passed to the
program. You MUST use 6 of the 7. Here's a list and a description:
Required commands
PCB:xxx - This is the DRIVE/PATH to your PCBoard Directory that you
wish to use. You MUST include the DRIVE letter.
FNAME:xxx - This is the First Name of the user.
LNAME:xxx - This is the Last Name of the user.
PWRD:xxx - This is the Password of the user.
Optional commands (One of the two must be used or both)
REP - Tells the program that you want to get a QWK file.
QWK - Tells the program that you want to insert a REP file.
DOOR:xxx - Tells the program to override the default door name.
The default is MAIL (Which is the KEY name via PCBSM).
If you installed the door with a different name, then you
will need to use this command so PCBoard will create the
USERS.SYS file.
How is works:
The program will create your QWK packet in the directory defined in the
CMSetUp.EXE program ((E) Misc Paths Path to QWK files). The door will look
for your REP file defined in the CMSetUp.EXE ((E) Misc Paths Path to REP).
How to Use:
Be sure you run the LOCALCAM.EXE in your CAM-MAIL directory. The program
will automatically change to your PCB directory in order to create the
USERS.SYS and PCBOARD.SYS. Please note that the program requires that you
have a PCB145.EXE (Somewhere in a Path or in the PCB directory), and that
the name of the door is called MAIL (This is the command that is used to
open the door via PCBoard itself). If you are unsure of how you installed
the Cam-Mail Door, go into PCBSM ((D) Users Info File Maintenance). Then
Select ((B) List Installed Third Party Application). It then should have
something like:
TPA: CAM-MAIL Ver: 1 Static: 60 Dynamic: 1 Key: MAIL
^^^^^^^^ ^^^^
The KEY should be MAIL and the TPA should be CAM-MAIL.
