home *** CD-ROM | disk | FTP | other *** search
- # ====================================================================
- #
- # PostLink(tm) Configuration file
- # Copyright (C) 1992 by Kip Compton, ALL RIGHTS RESERVED.
- #
- # POSTLINK.CFG file for CollNet(tm), from The Radio Wave BBS. Only
- # the first 222 lines of this file should be edited.
- #
- # If you need any help call me at 609-764-0812 (1200 - 16.8k)
- #
- # ====================================================================
- #
- # This is your BBS tagline.
- #
- # 60 Chars max for CollNet(tm) please
- # |--------1---------2---------3---------4---------5---------|
- BBS-TAG-LINE=The Radio Wave BBS ■ 609-764-0812 ■ Delran, NJ
- #
- # --------------------------------------------------------------------
- #
- # If you are a Node then change this to YES, if not then leave this NO.
- #
- NODE-MODE=NO
- #
- # --------------------------------------------------------------------
- #
- # If set to YES PostLink will make a file called LASTTIME.TXT, which
- # contains a line telling when the last successful transfer was.
- #
- LASTTIME.TXT=YES
- #
- # --------------------------------------------------------------------
- #
- # Leave USE-REAL-SYSOPS-NAME= set to YES. Put you name where it says
- # SYSOPS-NET-NAME=
- #
- USE-REAL-SYSOPS-NAME=YES
- SYSOPS-NET-NAME=TYLER MYERS
- #
- # --------------------------------------------------------------------
- #
- # These directories are not needed, but will make PostLink run quicker
- #
- SHARED-DIR=C:\COLLNET
- PUBLIC-DIR=C:\COLLNET
- MDT-DIR=C:\COLLNET\MDT
- DUPE-DIR=C:\COLLNET\DUPE
- #
- # --------------------------------------------------------------------
- #
- # Timezone information: TIMEZONE=n sets the timezone. N should be the
- # number of hours after UTC (aka greenwich mean time) you are.
- #
- # 5 = Eastern
- # 6 =
- # 7 = Mountain
- # 8 = West Coast
- #
- # DAYLIGHT-SAVINGS should be set to NO if daylight savings time is not
- # in effect, YES if it is.
- #
- TIMEZONE=5
- DAYLIGHT-SAVINGS=YES
- #
- # --------------------------------------------------------------------
- #
- # Define MailStore...different MailStores are for different systems.
- # Currently supported MailStores:
- #
- # UTI2 : UTI Revision 2
- # PCB145 : PCBoard 14.5
- #
- MAILSTORE=PCB145
- #
- # If you are not using PCBoard 14.5 then these 3 lines should be commented.
- #
- PCBOARD.DAT=C:\PCB\PCBOARD.DAT
- UPDATE-PCB-MAIL-WAITTING=YES
- PCBSTATS-NODE=10
- #
- # --------------------------------------------------------------------
- #
- # This variable sets the name of the file to log activity to. To have no
- # log at all, just comment this line out.
- #
- LOG=C:\COLLNET\COLLNET.LOG
- #
- # --------------------------------------------------------------------
- #
- # SYSTEM MESSAGE CONFIGURATION:
- #
- # Messages for users (usually the SYSOP) from the networking software can
- # either be placed in a text file, or placed right into a message base on
- # your BBS.
- #
- # To place the messages into your message base, define the variable
- # "SYSTEM-MSG-CONFERENCE" and set it equal to the number of the conference
- # that you want sysop messages to be placed in (note: these numbers are
- # the same as the numbers used in MANAGE when editing conferences, and
- # do not necessarily correspond to the conference numbers on your BBS).
- #
- # To have the messages placed in a text file, define the configuration
- # variable "SYSTEM-MSG-FILE" and set it equal to the full path of the
- # file that you would like sysop messages placed in. If none is specified,
- # the messages will be placed in SYSMSG.TXT in the current directory.
- #
- #SYSTEM-MSG-FILE=C:\COLLNET\SYSMSG.LOG
- SYSTEM-MSG-CONFERENCE=1
- #
- # --------------------------------------------------------------------
- #
- # AUTO-ADD-NEW-NODES should be set to YES if you want to automatically add
- # new nodes when they call.
- #
- # HUBs should set this to YES
- #
- AUTO-ADD-NEW-SITES=NO
- #
- # --------------------------------------------------------------------
- #
- # File Transfer Protocol Information:
- #
- # Each protocol has a character associated with it (ie A-Z and 0-9).
- #
- # Warning: Do not change the characters that these represent without talking
- # to the others on your network. The software negotiates which protocol
- # to use based on which are available, and if the letters do not match up,
- # it will not work properly.
- #
- # (ie, if Z is ZModem on your system, it must be ZModem on all systems that
- # you call and that call you, unless they do not support ZModem, in which
- # case Z should not be defined as being any protocol)
- #
- # Each protocol has a letter associated with it. The first thing you
- # need is a listing of the available protocols:
- #
- # PROTOCOLS=A B C D E F G H I J K ..
- #
- # Just list the letters that are being used. NOTE: THE FIRST PROTOCOL LISTED
- # WILL BE THE DEFAULT FOR ADDED SYSTEMS.
- # Then, define 3 other attributes:
- #
- #
- # The name (for display purposes only)
- # PROTO-NAME-Z=Zmodem
- #
- # The send command
- #
- # PROTO-SEND-Z=$$ZMODEMS
- #
- # The receive command
- #
- # PROTO-RECV-Z=$$ZMODEMR
- #
- # Note: Use the following for built-in protocols:
- #
- # Protocol Send/Recv Suggested Letter
- # Zmodem $$ZMODEM Z
- # XModem-1k $$XMODEM-1K O
- # XModem-1K-G $$XMODEM-1K-G F
- # XModem-CRC $$XMODEM X
- #
- # For external protocols, the following variables are defined:
- #
- # $$PORT ---> an integer representing the port # (ie 1 for COM1)
- # $$RECDIR ---> Directory to place received files in (ie C:\UPLOAD)
- # $$RECNAME ---> Expected name of file to be received (ie 3.NUL)
- # $$SENDPATH ---> Full path of file to send (ie C:\POSTLINK\3.NDL)
- #
- # Note that it is perfectly acceptable to define "better" implementations
- # of protocols to these letters (for example, use DSZ ZModem for Z instead
- # of the built in one.)
- #
- #
- # In addition, some special protocol options must be configured. They
- # are put in the PROTO-OPTIONS-X where X is the letter of the protocol.
- #
- # Currently, the only two options are BIDIRECTIONAL and FULLSCREEN. So, for
- # a bidirectional protocol such as HSLINK, assuming that you're using H as the
- # protocol's letter, you would put the following to make it both FULLSCREEN and
- # BIDIRECTIONAL
- #
- # PROTO-OPTIONS-H=BIDIRECTIONAL FULLSCREEN
- #
- # NOTE THAT IT IS IN ALL CAPS. IT _IS_ CASE SENSITIVE.
- #
- # Supported protocols:
- #
- PROTOCOLS=Z F O X
- #
- # Built-in Zmodem
- PROTO-NAME-Z=Zmodem
- PROTO-SEND-Z=$$ZMODEM
- PROTO-RECV-Z=$$ZMODEM
- # If you want to use DSZ for your Zmodem, just uncomment the following
- # 2 lines, then comment PROTO-SEND-Z=$$ZMODEM and PROTO-RECV-Z=$$ZMODEM
- # above
- #PROTO-SEND-Z=dsz handshake both port $$PORT sz $$SENDPATH
- #PROTO-RECV-Z=dsz handshake both port $$PORT rz $$RECDIR
- #
- # -- built in Xmodem-1k-G
- PROTO-NAME-F=Xmodem-1k-G
- PROTO-SEND-F=$$XMODEM-1K-G
- PROTO-RECV-F=$$XMODEM-1K-G
- #
- # -- built in Xmodem-1k
- PROTO-NAME-O=Xmodem-1k
- PROTO-SEND-O=$$XMODEM-1K
- PROTO-RECV-O=$$XMODEM-1K
- #
- # -- build in Xmodem-CRC
- PROTO-NAME-X=Xmodem-CRC
- PROTO-SEND-X=$$XMODEM
- PROTO-RECV-X=$$XMODEM
- #
- # -- HSLink bidirectional protocol (external)
- #
- # Uncomment the following 4 lines AND add an "H" to the PROTOCOLS
- # setting above to enable HS/Link support.
- #
- #PROTO-NAME-H=HS/Link
- #PROTO-SEND-H=hslink -P$$PORT -U$$RECDIR $$SENDPATH
- #PROTO-RECV-H=hslink -P$$PORT -U$$RECDIR $$SENDPATH
- #PROTO-OPTIONS-H=BIDIRECTIONAL FULLSCREEN
- #
- # ====================================================================
- #
- # In most cases everything below this line will not need editing.
- #
- # ====================================================================
- #
- # Compression Scheme Information.
- #
- # Compression schemes are identified by strings of up to 3 characters.
- # These strings s hould correspond to the extension that the compression
- # program puts on the end of compressed files (ie ZIP for zip files).
- #
- # The first thing you need is a listing of available compression schemes
- #
- # COMPRESS=AAA BBB CCC ...
- #
- # Then you need to define the command to compress a file:
- #
- # COMPRESS-AAA=COMPRESS $$FPATH $$DESTDIR
- #
- # and the command to uncompress a file
- #
- # UNCOMPRESS-AAA=UNCOMPRESS $$FPATH $$DESTDIR
- #
- # Where AAA is the up to three character identifier for the compression
- # scheme.
- #
- # The following variables are available when defining compression programs:
- #
- # For both compressing and uncompressing:
- #
- # $$CMP-PATH --> Full path of compressed file without extension (ie C:\POSTLINK\RECV\U3)
- #
- # for uncompressing only
- #
- # $$DESTDIR --> Directory to place resutant file(s) in (ie C:\POSTLINK)
- #
- # for compressing only
- #
- # $$INCFILE --> Include these files (files or wildcards sep. by spaces)
- #
- #
- # NOTE : THE ABOVE VARIABLES ARE CASE-SENSITIVE, AND THUS MUST BE IN ALL CAPS!
- #
- COMPRESS=ZIP
- #
- # Definition for PKZIP
- COMPRESS-ZIP=PKZIP $$CMP-PATH $$INCFILES
- UNCOMPRESS-ZIP=PKUNZIP -o $$CMP-PATH $$DESTDIR
- #
- # --------------------------------------------------------------------
- #
- # Define the maximum number of channels that are available. The system can
- # have up to 16767 channels, but the more channels you have, the worse the
- # performance becomes. (ie, the site.lst file grows larger, etc)
- #
- # IF YOU NEED MORE THAN 16767 CHANNELS, CONTACT KIP COMPTON AS THE SOFTWARE
- # CAN EASILY BE CHANGED TO SUPPORT MANY MORE PORTS -- The 16767 limit was
- # introduced for efficency reasons...
- #
- MAX-CHANNELS=1400
- #
- # --------------------------------------------------------------------
- #
- # Options for mail..
- #
- # This option controls whether private mail addressed to the sysop is exported.
- #
- EXPORT-SYSOPS-PRIVATE-MAIL=NO
- #
- # --------------------------------------------------------------------
- #
- # This option is the name of the sysop as it should be on outside systems.
- #
- USE-SYSOPS-REAL-NAME=YES
- #
- # --------------------------------------------------------------------
- #
- # This option controls the default maximum number of packets to keep per
- # channel in the .PUB (public) files.
- #
- DEFAULT-MAX-TO-KEEP=10000
- #
- # --------------------------------------------------------------------
- #
- # This option controls the default minimum number of packets to keep per
- # channel in the .PUB (public) files.
- #
- DEFAULT-MIN-TO-KEEP=100
- #
- # --------------------------------------------------------------------
- #
- # The IMPORT-MODE and EXPORT-MODE variables control whether POSTLINK.EXE
- # automatically exports and imports on the fly. If you set EXPORT-MODE and/or
- # IMPORT-MODE to AUTOMATIC, then the corresponding operation will be performed
- # on the fly by POSTLINK.EXE, only when needed. You should then not have to run
- # EXPORT or IMPORT ever again. For example, to be fully automatic, set both
- # EXPORT-MODE and IMPORT-MODE to AUTOMATIC. To have mail imported onto your
- # board automatically (ie as it is uploaded) but not have mail exported from
- # your board until EXPORT.EXE is run, set IMPORT-MODE to AUTOMATIC and
- # EXPORT-MODE to MANUAL.
- #
- # If these variables are left out, the default is AUTOMATIC.
- #
- EXPORT-MODE=AUTOMATIC
- IMPORT-MODE=AUTOMATIC
- #
- # --------------------------------------------------------------------
- #
- # MINIMUM DISK SPACE REQUIREMENTS:
- #
- # On startup, PostLink programs check the free space
- # available in the work directory and shared directories. If the free
- # space is less than the minumum number of K to be free as defined by
- # the following variables, the software will signal an error and terminate.
- #
- # In addition, if the space free is within a certain percentage of the
- # minimum free space allowed, a message will be sent to the sysop. The
- # default percentages are 20%, but they can be changed by changing the
- # variables below:
- #
- # Note that the amount of free space is expressed in K, ie 5000 is 5 megs.
- # Setting the minimum free space to 0 will disable these checks.
- #
- # For the shared directory:
- SHARED-DIR-MIN-SPACE=5000
- SHARED-DIR-MIN-PERCENT=20
- #
- # For the work directory:
- WORK-DIR-MIN-SPACE=5000
- WORK-DIR-MIN-PERCENT=20
- #
- # --------------------------------------------------------------------
- #
- # DOS SHELL SWAPPING OPTIONS
- #
- # SHELL-SWAP controls whether the programs swap themselves to disk or
- # ems memory when they shell out to DOS. (ie to call UTIs, PKZIP, protocol
- # drivers, etc.) If it is YES, the programs will attempt to swap themselves
- # out, if it is NO, they will not.
- #
- SHELL-SWAP=YES
- #
- # --------------------------------------------------------------------
- #
- # SHELL-SWAP-EMS controls whether, if configured to swap, the programs
- # attempt to use EMS memory instead of disk when swapping out. If set
- # to YES, the programs will swap to EMS memory if enough is available;
- # if enough EMS memory is not available, they will swap to disk.
- #
- SHELL-SWAP-EMS=YES
- #
- # --------------------------------------------------------------------
- #
- # SHELL-SWAP-DIR controls where the programs place their swap files if
- # they end up swapping to disk. For example, if you have a RAM disk
- # D and wish to have your swap files put in the root directory of this
- # disk, you would use SHELL-SWAP-DIR=D:\. NOTE: By default the swap
- # file is placed in the current directory. If there is not enough space
- # on the drive that you specify, PostLink will not be able to shell to
- # whatever it is trying to shell to (PKZIP, DSZ, UTI driver, etc) and
- # will fail.
- #
- #SHELL-SWAP-DIR=C:\
- #
- # --------------------------------------------------------------------
- #
- # Site list Packing configuration:
- #
- # The MAX-SITE-LIST-IDLE-DAYS variable controls how many days a site must
- # be idle before it is automatically deleted by the packing routines. If
- # it is not specified, no sites will ever be deleted because they are too
- # old. Note that sites that you add yourself will not be deleted automaticaly
- # until the site has called at least once.
- #
- MAX-SITE-LIST-IDLE-DAYS=30
- #
- # --------------------------------------------------------------------
- #
- # Automatic Packing configuration:
- #
- # POSTLINK.EXE can be configured to automatically pack the dictionary, site list,
- # and/or .PUB files on a regular basis.
- #
- # AUTOMATIC-PACKING turns on and off the entire automatic packing apparatus.
- # if is it set to "YES" automatic packing will occur; "NO" means no automatic
- # packing.
- #
- # In addition, there is an variable for each of the files to be packed which
- # allows you to specify how often, in days, each file is packed. If
- # you set the number of days to 0, no automatic packing will take place.
- # (for example, 1 means pack every day, 2 every other day, etc.)
- #
- # The default values for these are 1 day for .PUB files and 10 days for
- # both the site list and dictionary.
- #
- AUTOMATIC-PACKING=YES
- PACKET-PACK-DAYS=1
- SITELIST-PACK-DAYS=10
- DICTIONARY-PACK-DAYS=10
- #
- # --------------------------------------------------------------------
- #
- # "Message Data" File Configuration
- #
- # The Message Data file is used to keep track of messages. The primary
- # function that this supports is reference numbers.
- #
- # You can control how many messages back the software keeps track of. You
- # can have the software keep track of 0 to 5000 messages in each conference.
- # The default is 1000 messages per conference.
- #
- NUM-RECS-IN-MSGDATA=1000
- #
- # --------------------------------------------------------------------
- #
- # Debugging Directory Option:
- #
- # Normally, when it is done with PREAMBLE, U##, and D## files, POSTLINK.EXE
- # deletes them. If you set the DEBUG-DIR option to a directory, POSTLINK.EXE
- # will, instead of deleting the files, move them to the directory specified.
- # You must not specify your work directory as this directory or things will
- # get screwed up. This option is intended to be used only if you are having
- # problems and need to examine exactly what was uploaded by the sites that
- # call you. Note that this directory must exist; the software will not
- # create it for you.
- #
- #DEBUG-DIR=C:\POSTLINK\DEBUG
- #
- # --------------------------------------------------------------------
- #
- # MAIL CONFIGURATION:
- #
- #
- # There are several options that control the _DEFAULTS_ for options that
- # control how mail is handled on a conference by conference basis. These
- # variables only take effect when put new conference onto the net (ie give
- # it a channel in manage.exe); they do not have any effect on conferences
- # that have already been set up. They are also only the DEFAULTS for these
- # new conferences; they can be changed when adding the conference or any
- # time later.
- #
- # The first option, DEFAULT-PRIVATE-MAIL, controls whether or not private
- # mail in general is exported and imported. Note that if you set this to
- # YES, the individual import and export Routed Mail options below have no
- # effect; if this option is set to YES, all private mail is exported and
- # imported regardless of whether it is routed or not. Generally, it is a
- # good idea to set this option to NO, as if it is set to YES, all private
- # mail in the conference will be exported, and if it is not routed, it
- # will appear on all boards that also have this flag set to YES and who
- # take the conference on the network.
- #
- DEFAULT-PRIVATE-MAIL=NO
- #
- # --------------------------------------------------------------------
- #
- # The next two options control whether Private and Public mail is "Auto
- # Routed". "Auto Routing" means that when exporting mail, the software
- # looks at messages that have reference numbers (and are thus replies to
- # a message) and routes that reply message back to the system where the
- # message that it is a reply to was written.
- #
- # In general, PRIVATE Auto Routing is very GOOD; it makes mail a lot more
- # "private" in that once a series of replies has gotten started, the
- # private messages only appear on the origin and destination systems.
- #
- # In general, PUBLIC Auto Routing is BAD; it keeps people from seeing
- # conversations that are going on. However, in extremely busy conferences
- # this may be desirable.
- #
- DEFAULT-AUTO-ROUTE-PRIV=YES
- DEFAULT-AUTO-ROUTE-PUBLIC=NO
- #
- # --------------------------------------------------------------------
- #
- # The next two options control whether Routed Private Mail is exported and
- # Imported. If Private Mail is turned on for the conference, these two
- # flags are ignored; all private mail is being exported and imported. If
- # Private Mail is turned off for the conference, these flags can allow you
- # to import/export private messages that are routed, including Auto Routing.
- # These options should generally be set ON, as a routed message is pretty
- # private.
- #
- # For Exporting:
- #
- DEFAULT-EXP-PRIV-ROUTED=YES
- #
- # For Importing:
- #
- DEFAULT-IMP-PRIV-ROUTED=YES
- #
- # --------------------------------------------------------------------
- #
- # The next two defaults control the default for Bridge Modes. Generally,
- # you want to have Bridge Mode turned OFF for all of your conferences.
- # Bridge mode is generally used for "bridging" conferences across networks.
- #
- #
- DEFAULT-BRIDGE-EXPORT=NO
- DEFAULT-BRIDGE-IMPORT=NO
- #
- # --------------------------------------------------------------------
- #
- # File Request Configuration
- #
- # This option controls whether a message is sent to the sysop when somone
- # attempts to request a file that they are not allowed to request in the
- # REQUEST.DAT. YES means a message is sent, NO means no message is sent.
- # The default is YES.
- #
- ILLEGAL-REQ-WARNING=YES
- #
- # --------------------------------------------------------------------
- #
- # This option controls whether a message is sent to the sysop when someone
- # attempts to request a file which is not found in any of the paths listed
- # in the REQUEST.DAT file. YES means a message is sent, NO means no message
- # is sent. The default is NO.
- #
- UNKNOWN-REQ-WARNING=NO
- #
- # --------------------------------------------------------------------
- #
- # Dictionary Administrative Update Configuration
- #
- # Normally, dictionary name publications (or unpublications) are noly honored
- # if they are from the site that they are updating. However, in some
- # situations it is desirable to let some site(s) update your dictionary
- # for any names. These updates are called "Administrative Updates" and this
- # configuration variable controls who is allowed to do them.
- #
- # To allow administrative dictionary updates, add the variable
- # DICTIONARY-ADMIN-SITES= and then put a list of ID(s) that are allowed
- # to send you administrative updates. For example,
- #
- DICTIONARY-ADMIN-SITES=
- #
- # Would allos sites 1,2,3, and 4 to send you administrative updates. Note
- # that you _can_ use names here instead if you like.
- #
- # --------------------------------------------------------------------
- #
- # DO NOT CHANGE THIS LINE AT ALL!
- #
- NET-TAG-LINE=CollNet
- #
- # --------------------------------------------------------------------
- #
-