Category : BBS Programs+Doors
Archive   : MSGTOS2C.ZIP
Filename : MSGTOSS.BBS

 
Output of file : MSGTOSS.BBS contained in archive : MSGTOS2C.ZIP
Msgtoss Support System - Sumner, WA (MO) ! Mike Zakharoff
;
; KEYWORD LIST (see MSGBBS.DOC for full details on keyword use)
; ------------
; Logically 'Chain' to the next BBS file ---> NBBS:[path]Filename.ext
; No. of records in RBBS message base(s) ---> RECS:xxxx
; Re-number msg only if last exceed xxxx ---> RNIF:xxxx
; Re-number msg bases starting with xxxx ---> RNST:xxxx
; Security level tossed msgs set to xxxx ---> ESEC:xxxx
; The "home" NODE address for the echo -----> NODE:xxxx
; Max Lines before MsgToss auto-breaks msg -> MAXL:xxxx
; Minimum number of 'free' message slots ---> SLAK:xxxx
; Format right margin of RBBS messages to --> MRGN:xx (30 thru 79)
; Whether to honor PRIVATE echomail --------> PRIV:x (1=yes 0=no)
; Force Msgs to M.DEFs as Already Scanned --> FMAS:x (1=yes 0=no)
; Strip Echo Control Lines (Only FMAS:1) ---> SECL:x (1=yes 0=no)
; Hash USERS to keep msgs while purging ----> USRH:x (1=yes 0=no)
; Capture messages with special text -------> CAPT:x (1=yes 0=no)
; Enable Duplicate Checking for this AREA --> CDUP:x (1=yes 0=no)
; Set Mailwaiting Bits for new RBBS msgs ---> MWST:x (1=yes 0=no)
; Maintain HISTORY file of purged messages -> HIST:x (1=yes 0=no)
; Zone & Domain Separation (1=none 2=full) -> GATE:x (1 or 2)
; Origin: line to be used for scanning -----> ORGN:text (last entry)
;
; Default keyword entries
;
-RECS:1000 RNST:1 RNIF:1 ESEC:5 MAXL:100
-SLAK:10 MRGN:77 FMAS:1 SECL:1 USRH:1 HIST:0
-CAPT:0 NODE:1 GATE:2 PRIV:0 CDUP:0 MWST:1
;
; NOTE: Some of these Keywords are quite critical and should be
; throughly understood PRIOR to attempting MSGTOSS.BBS
; configuration. The most critical Keywords are as follows:
;
; NODE:x RECS:xxxx ESEC:xxxx GATE:xxxx FMAS:x SECL:x USRH:x
;
; *************************** WARNING! ****************************
; * Read the documentation on the above critical Keywords PRIOR *
; * to configuring the default Keywords in the MSGTOSS.BBS file. *
; * Setting them incorrect will throughly screw things up!! *
; *****************************************************************
;
; Note the NODE:1 entry! This indicates that the following
; conferences are associated with your FIRST "NODE-------->"
; address in your MSGTOSS.CFG file. NODE:2 would mean the
; SECOND NODE--------> entry, NODE:3 means THIRD.
;
; Turn off USER hashing for the main message base (USRH:0), as
; there are too many users for MSGTOSS to efficiently purge as
; required (its unnecessary). Turn it back on after (USRH:1)
; for the rest of the small conferences.
;
-USRH:0
C:\RBBS\MESSAGES NETMAIL
-RECS:800 USRH:1
;
; All subsequent conferences are 800 records (RECS:800).
; Naturally, you will have to adjust these to match your system.
;
C:\RBBS\commm.def COMM 1:138/146
C:\RBBS\consultm.def CONSULTING 1:138/146
C:\RBBS\cookingm.def COOKING 1:138/146
C:\RBBS\c_prgmm.def C_ECHO 1:138/146
C:\RBBS\feminm.def FEMINISM 1:138/146
C:\RBBS\forsalem.def 4SALE 1:138/146
;
; Special Origin line to apply ONLY to the NEXT sequential message base
;
-ORGN:MSGTOSS - Accept no substitutes!
C:\RBBS\rbbsm.def RBBS-PC 1:138/146
;
; Default Origin line takes over
;
C:\RBBS\techm.def TECH 1:138/146
C:\RBBS\warningm.def WARNINGS 1:138/146
;
; Qmail-Style PASSTHRU areas are also supported, these have the
; following format:
;
; #[Optional Path] PASSAREA 1:138/146 301 301 666/1 2 3
;
; Note that the FIRST character must be a "#", followed by the AREA:
; name, followed by the list of NET/NODES. Note that the NET/NODES
; will ONLY be "fed" if you are using the "/FEED" switch. Note that
; QMAIL requires a Fido Path to follow the "#", and this CAN be listed,
; but MSGTOSS will ignore the path.
;
; The areas NETMAIL & UNKNOWN are required.
; The areas ROUTETHRU & MSGCAPTURE are optional
; For each unique domain/zone, separate areas are required
; The extensions of ".001" & ".008" (meaning Zone 1 & 8)
; are for illustrative purposes only
;
C:\MAIL\NETMAIL.001\ NETMAIL
C:\MAIL\UNKNOWN.001\ UNKNOWN
; C:\MAIL\ROUTEIT.001\ ROUTETHRU
; C:\MAIL\CAPTURE.001\ MSGCAPTURE
;
C:\MAIL\NET343\ NET343 1:138/146
C:\MAIL\RBBS.001\ RBBS-PC 1:138/146
C:\MAIL\LAN\ LAN 1:138/146
;
; The -NODE:2 entry signifies the SECOND NODE--------> entry in
; the MSGTOSS.CFG file. This keyword separates the MSGTOSS.BBS
; file into Domains/Zones. -NODE:3 would mean the THIRD
; NODE--------> entry (if exist).
;
;
-NODE:2 (The second AKA is RBBS-NET!)
C:\MAIL\NETMAIL.008\ NETMAIL
C:\MAIL\UNKNOWN.008\ UNKNOWN
; C:\MAIL\ROUTEIT.008\ ROUTETHRU
; C:\MAIL\CAPTURE.008\ MSGCAPTURE
;
C:\MAIL\MSGTOSS\ RBBS_MSGTOSS 8:918/1
C:\MAIL\MSGBETA\ MSGBETA 8:918/1
C:\MAIL\RBBS.008\ RBBS-PC 8:918/1
;
; Having two RBBS-PC conferences is not a misprint. What separates
; them is the NODE:2 keyword, meaning the second RBBS-PC conference
; belongs to RBBS-NET (Zone 8).


  3 Responses to “Category : BBS Programs+Doors
Archive   : MSGTOS2C.ZIP
Filename : MSGTOSS.BBS

  1. Very nice! Thank you for this wonderful archive. I wonder why I found it only now. Long live the BBS file archives!

  2. This is so awesome! 😀 I’d be cool if you could download an entire archive of this at once, though.

  3. But one thing that puzzles me is the “mtswslnkmcjklsdlsbdmMICROSOFT” string. There is an article about it here. It is definitely worth a read: http://www.os2museum.com/wp/mtswslnk/