Confmail Compatibility Origin ! Confmail Compatibility Name
;
; The first line of an Areas.Bbs file usually defines a default origin and
; optional SysOp name separated by an exclamation mark [!]. This program
; does not use this line since Origin and Name information are provided in
; the .CFG/.PRM configure definition files. The line must be present --
; even if blank -- for compatibility with other EchoMail processing
; software. If a message area is defined on the first line the program
; will ignore it.
;
;
; Comment lines begin with ; or % or * in the first non-blank
; position on a line.
;
;
; Message area definitions are defined on one line in three parts...
;
; - The first part is the path. This is an MS-Dos drive:\directory path
; for .Msg files; or a board number or topic path for TBBS. (see below)
; - The second part is the EchoMail conference tag or area name.
; - The third part is a list of Zone:net/node addresses the conference
; is exchanged with.
;
; The maximum line length is 4095 bytes.
; The maximum number of addresses that can be listed for an area is the
; smaller of 255 or the Maximum_Nodes configuration parameter in the
; .Cfg/.Prm file.
;
;
; Specially formatted comment lines (beginning with ; or % or *) can be
; used to set and clear custom processing MODEs for TBBS Message areas.
; Comment lines whose first 5 non-blank characters are << MODE= >> will
; be processed.
;
; Individual or groups of TBBS echomail areas can be set to keep/strip
; origins, wrap/not wrap, be made read-only, and override creation date
; by including parameters on comment lines. Multiple parameters are
; allowed per line. Commas must separate parameters. The parameters
; exclusive to TBBS support are...
;
; ; MODE = NOWRAP * TBBS: retains message formatting as received
; ; MODE = WRAP TBBS: reformats messages to fit the caller's screen
;
; ; MODE = ORIGIN * TBBS: Import message tear and origin line
; ; MODE = NOORIGIN TBBS: Do not import tear and origin line
;
; ; MODE = READWRITE * TBBS: Export locally entered messages to other BBSs
; ; MODE = READONLY TBBS: Do not export locally entered messages
;
; ; MODE = OLDDATE * TBBS: Use the original date on messages imported
; ; MODE = NEWDATE TBBS: Use today's date on messages imported
;
; ; MODE = LINK * TBBS: Message reply chain linking ok when requested
; ; MODE = NOLINK TBBS: Message reply chain linking bypassed
;
; * = default mode
;
; Two parameters are available to define TBBS message base ROLLOFF
; operations. Substitute a number for ### to set the number of messages
; and/or days to keep. The default is 0 to disable ROLLOFF operations.
;
; ; MODE = ROLLOFFCOUNT#### Set the maximum number of messages to keep
; ; MODE = ROLLOFFDAYS#### Set the maximum number of days to keep
;
;
; Another mode parameter -- LEVEL## -- is available to set/change the
; Areafix security/privilege level for areas. The numeric part of the LEVEL
; parameter can range from 0 thru 32000.
;
; ; MODE = LEVEL0 * Set the areafix/security level to 0.
; ; MODE = LEVEL10 Set the areafix/security level to 10.
; ; MODE = LEVEL250 Set the areafix/security level to 250.
;
;
; EchoMail is sometimes maintained for different and often unrelated network
; addresses. In that case it may be necessary to present different addresses
; for different message areas. Use the MYADDRESS parameter to set the address
; to present in MSGID, ORIGIN, PATH lines for messages exported. Use
; the EchoMail ZONEGATE facility to control SEEN-BY content.
;
; ; MODE = MYADDRESS 36:120/0
; ; MODE = MYADDRESS 1:13/13
; ; MODE = MYADDRESS off <- ends address override
;
;
; To disallow and allow TOSS or SCAN of EchoMail marked Private:
;
; ; MODE = NOPRIVATE
; ; MODE = PRIVATEOK <- default
;
;
; To allow the automatic areafix dead-end purge of this area when
; an areafix change leaves only one active connection for a
; passthrough area:
;
; ; MODE = NOPURGE <- default
; ; MODE = PURGEOK
;
;
; EchoMail origin lines for locally generated messages can be defined
; individually for each area or set/cleared using special comment lines
; beginning with ORIGIN. Origin definitions remain in effect for all areas
; that follow in that Areas_BBS or until another ORIGIN is defined. A
; blank ORIGIN definition cancels a special origin. An ORIGIN= definition
; must be the only definition on a line. Origin definitions can be up to
; 59 characters. It is up to the SysOp to make sure that the total origin
; line length (* Origin: plus this text plus the node address) do not exceed
; the accepted maximum of 79 characters.
;
; ; ORIGIN = This space available...
; ...
; ; ORIGIN =
; ...
;
;
; Areafix "Lock" strings are set/cleared under the same rules as ORIGIN=
; lines. Lock strings can have up to 50 characters including spaces. All
; characters on the line are used (up to 50) beginning with the first
; non-blank character after the equal sign.
;
; ; LOCK = ThisIsALockStringUpTo50CharsLong
; ; LOCK =
;
;
; Parameters remain in effect until a new parameter overrides a setting or
; until end of file is reached. All parameters are reset to defaults at
; the start of every Areas_BBS file.
;
; ----------------------------------------------------------------------------
;
; Example to set up several parameters for areas that follow.
;
; ; Mode = Wrap,Origin,Readwrite,Olddate,Level50,Link,PrivateOK
; ; Mode = Rolloffcount0,Rolloffdays5
;
; Example to set areas that follow to NOWRAP leaving other parameters unchanged.
;
; ; Mode = NoWrap
;
; Example to set areas that follow to WRAP leaving other parameters unchanged.
;
; ; Mode = Wrap
;
;
; -----------------------------------------------------------------------------
; -----------------------------------------------------------------------------
;
; Area definition lines
;
; Path To Messages Area Name Distribution List
;
; -----------------------------------------------------------------------------
; TBBS standard message board definitions.
; These definitions begin with the board number or board name assigned
; via CEDIT. If a board name begins with a number it must be defined
; using the board number.
;
11 TRAVEL 1:12/12 104/1 106/116 138/112 151/1003 209/209 260/1 283/657 396/1
TBBS TBBS 1:396/1 11/3 12/12 104/1 106/116 107/33 115/887 138/112 151/1003 209/209 260/1 266/22 267/200 283/657 321/109 3:54/54
50 WHO 1:10/8 11/3 12/12 104/1 106/116 107/33 138/112 139/630 151/1003 209/209 260/1 266/22 267/200 283/657 321/109 396/1
;
; -----------------------------------------------------------------------------
;
; TBBS topic message board definitions.
; These lines begin with the full topic path, including the root. The topic
; root can be represented as either the board name or the message board
; number.
;
; If a topic name contains spaces you must enclose it in quotes (single or
; double). If the topic root board name begins with a number it must be
; defined using the board number.
;
local/net270 NET270 1:270/211 13/13 270/102
sysop/protostar PROTOSTAR 1:13/13 270/102 10/8 12/12 13/75 100/375 104/1 107/10 33 109/104 115/333 887 116/29 138/112 139/630 141/888 151/1003 209/209 232/16 260/1 261/628 662 266/12 22 267/200 270/3 272/39 273/10 274/13 283/657 300/11 321/109 343/491 345/7 355/38 396/1 2220/250 2605/611 2606/583 2609/2 2613/210 2:2405/100 3:54/54 6:720/303
sysop/tbbs/tbbstech TBBSTECH 1:322/360 107/33 270/102 3:54/54
25/tbbs/tdbstech TDBSTECH 1:322/360 107/33 270/102 3:54/54
;
; -----------------------------------------------------------------------------
;
; .Msg area definitions
; Definitions for .Msg areas *MUST ALWAYS* begin with a three character
; C:\ drive sequence to differentiate them from TBBS area definitions.
;
c:\qm\test\msg\tech TECH 1:396/1 10/8 11/3 12/12 104/1 106/116 107/33 115/887 138/112 139/630 141/888 151/1003 209/209 260/1 266/22 267/200 283/657 321/109 345/7 6:730/2
c:\qm\test\msg\Hawaii HAWAII 1:345/7 12/12 273/10
;
; -----------------------------------------------------------------------------
;
; Passthru message area definitions.
; The PATH following the # is optional. If specified, the path must be in
; X:\PATH format. The three characters drive-colon-backslash is required.
; Spaces are not allowed in the path or between the # and the path.
;
; If a path is not specified for passthrough areas ( only the # ) SCAN is
; always active whenever TOSS is requested. If a space follows the # the
; area is always assumed to be a passthrough area without a path.
;
; Do *NOT* assign one path to multiple areas. If you ever do a TOSS-only
; operation (without a SCAN) you'll mix up multiple echos and export the
; wrong messages to your links.
;
#c:\qm\msg\Software SOFTWARE 1:261/662 12/12 116/29 138/148 141/730 209/209 283/657 321/109
#c:\qm\msg\Swcoord SWCOORD 1:261/662 12/12 141/730
# MYPASSTHRU1 1:13/13 270/102 103
# MYPASSTHRU2 1:13/13 270/102 103 211
;