The following information originally appeared in the Net information from
for the MSI_SupportNET by Mustang Software HQ BBS and is passed along for
your information in the RailNET ZIP packet.

Sysops: Preventing duplicate messages is YOUR responsibility.
Re-exporting mail from crashed message bases puts a burden on the entire
network, and adds needlessly to other sysops' long distance telephone
bills.

Successful echomail sysops monitor their systems DAILY for potential
problems, and take measures to protect the network should a
configuration problem or system crash occur.

Here's a sample mailrun event batch file for WILDCAT sysops, that uses 
PostMaster from Dave Cody, and Dupmsg from Jim Metzler, along with, of 
course Robocomm and TNet.

This will keep sysops well informed about the progress of their mail
runs and will alert them to problems before the NetGods have to become
involved ... It should be all but impossible to be the source of a
problem if you follow these instructions. Substitute your own sysop
name, hub name and paths for the ones shown here, of course.

PCBoardies can use this too--there should be a set of utilities for
PCBoard which function in the same way as TNet (try RNet or QNet);
PostMaster, which takes text files and imports them to the message
base (TXT2MSG for instance); and Dupmsg, which purges duplicate
messages -- try PCBPack for this.

So, without further ado, here's a sample net mailrun batch file:
---- CUT HERE ----
C:
CD \WC30

:OK, let's clean out some dupes!
DUPMSG

:Now let's export some mail.
TNET EXPORT MUSTANG

:Mail's exported, let's send it to HQ
CD \ROBO

:Rename our old QWK packets before we start
IF EXIST MUSTANG.QW2 DEL MUSTANG.QW2
IF EXIST MUSTANG.QW1 RENAME MUSTANG.QW1 MUSTANG.QW2
IF EXIST MUSTANG.QWK RENAME MUSTANG.QWK MUSTANG.QW1

:Let's backup the Robocomm log file and pick up the mail using Robocomm
IF EXIST ROBOCOMM.LOG TYPE ROBOCOMM.LOG >>ROBOLOG.OLD
DEL ROBOCOMM.LOG
ROBOCOMM /R /A NIGHTLY

CD \WC30

:now that Robo's finished, let's mail ourselves the log. Set the
:log style in Robocomm to 'Normal'

POSTMSTR /I:C:\ROBO\ROBOCOMM.LOG /C:0 /T:GWEN BARNES /F:ROBO /S:ROBO LOG

:now we import the mail and backup the TNET log file
IF EXIST ROBO\MUSTANG.QWK TNET IMPORT MUSTANG
IF EXIST TNET.LOG TYPE TNET.LOG >>TNETLOG.OLD

:now we mail ourselves the TNET log to see what we imported
POSTMSTR /I:C:\WC30\TNET.LOG /C:0 /T:GWEN BARNES /F:TNET /S:TNET LOG
DEL TNET.LOG

:Now let's kill any dupe messages that might have come from HQ becase
:someone else forgot to check for dupes first!
CD \WC30
IF EXIST DUPMSG.LOG TYPE DUPMSG.LOG >>DUPLOG.OLD
DUPMSG

:And let's mail ourselves the DUPMSG log to see how it went
POSTMSTR /I:C:\WC30\DUPMSG.LOG /C:0 /T:GWEN BARNES /F:DUPMSG /S:DUPMSG
DEL DUPMSG.LOG

:And the Wildcat error log, just in case something went wrong that we
:need to fix (such as a trashed conference) with WCREPAIR
IF EXIST ERROR.LOG TYPE ERROR.LOG >>ERRORLOG.OLD
POSTMSTR /I:C:\WC30\ERROR.LOG /C:0 /T:GWEN BARNES /F:WILDCAT /S:ERRORLOG
DEL ERROR.LOG

:Likewise for TNET's error log
IF EXIST TNET.ERR TYPE TNET.ERR >>TNETERR.OLD
POSTMSTR /I:C:\WC30\TNET.ERR /C:0 /T:GWEN BARNES /F:TNET /S:TNET.ERR
DEL TNET.ERR

:And Tomcat's error log, just for good measure
IF EXIST TOMCAT.ERR TYPE TOMCAT.ERR >>TCERROR.OLD
POSTMSTR /I:C:\WC30\TOMCAT.ERR /C:0 /T:GWEN BARNES /F:TOMCAT /S:TCERROR

:Then we bring the BBS up again. EXIT if you shelled, CAT if you
terminated.

---CUT HERE---