home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 2 BBS
/
02-BBS.zip
/
MAXMAILP.ZIP
/
MAXMAIL.CFG
< prev
next >
Wrap
Text File
|
1991-01-01
|
11KB
|
203 lines
;
; MaxMail configuration file
;
; All parameters oriented as single line records, terminated by usual
; carraige return/linefeed. Use standard text editor to modify. Use
; a ';' to turn off line. Maxmaill will ignore anything on line record
; after it encounters a ';'. Notice that each active record begins with
; Keyword. You can move these lines to any position in file, but keyword
; itself can not be changed. Elsewise, MaxMail will ignore rest of line.
; Each token/field in record is seperated by 1 or more blanks/tab.
;
;
; SignOnMsg: Text message displayed to user when MaxMail signs out. Use
; underscore '_' to seperate words instead of blanks. Maxmail will
; substitute underscore for 1 blank space. This is parameter
; is optional.
;
SignOutMsg Thanks_for_visting_Maxmail!_C_you_later!!!
;
;
; TxtFile: This is filename MaxMail uses as name for capturing message
; records and embeds into archived file. No pathname is used here,
; just standard 12 letter DOS filename. MaxMail will default to
; "Maxmsgs.txt" if no parameter is specified.
;
TxtFile Maxmsgs.txt ; Text file for capturing messages
;
;
; MessageHeader: This is an optional text file that is written to the message
; capture file(TxtFile) *BEFORE* any of the messages. It can
; a little ad or whatever you want to annoy the user with.
; It probably should be made very short, if you use it at all!
;
;MessageHeader Header.txt
;
;
; CfgFile: User Configuration file. This is a special binary record MaxMail
; uses to track user configurations. No pathname is used here.
; MaxMail will create file if not existing. If you wish all users
; to redo their configurations, just delete this file and MaxMail
; will restart everyone as new user. Default name is "MaxMail.usr"
; if no parameter specified.
;
CfgFile Maxmail.usr
;
;
; LogFile: Log file to track what user does while inside MaxMail. Totally
; compatable with standard Maximus/Binkley log format. You can
; even specify the standard Maximus log file if wanted. It will
; automatically append to it. Logfile is optional,but reccomended
; Any errors occuring will also be logged.
;
LogFile MaxMail.log
;
;
; NewHelpFile: Text file displayed to new user. When MaxMail can not find
; user in config file, it will first display this file to new user,
; with automatic paging every 23 lines. Do not put any control
; characters in file, but IBM text (8 bit chars) may be used.
; This file is optional, but reccomended to explain to new user
; what MaxMail is all about. Keep file short and to the point.
;
NewHelpFile NewUsers.max
;
;
; MaxAreaScan: Maximum message area # to scan. Allows sysop to create a
; a 'ceiling" for message areas, so prevents scanning unwanted
; high message areas. This defaults to 999, but can set to anything
; above 0. Currently Maximus deals with message areas by numbers,
; like OPUS. This will be changed in future, and MaxMail will change
; accordingly.
;
MaxAreaScan 999
;
;
; MaximumMessages: Maximum count of messages to pack in 1 session. MaxMail
; will check remaining time for user and not allow larger archived
; file than user can download (current baud rate) during time. It
; is a rough estimate at best though, since we can only guess how
; big packed file will be. For sure, it will not be any large than
; maximum messages specified here. 400 is a good reasonable number.
; User can always recall MaxMail later for additional messages.
;
MaximumMessages 400
;
;
; Packer: Here is where you specify the packer programs user is allowed.
; You can specify as many packers as you want. Menu will display
; them in order appearing here. So if you change packers or the
; order of them, you probably want to force users to re-do their
; configuration (delete User Config file), or use Utility mode.
; There are 4 tokens (seperated by tab/blank) required. Any lines
; with less than 4 tokens will be ignored. Be sure each token has
; *NO* embedded spaces/tabs, else it will be considered another
; token! Use an underscore "_" in place of blank space. See the
; examples here if confused. Tokens are:
;
; Description Filename PackedFilename CommandLine
; ---------------------------------------------------
; Description: Simple short description of packer type.
; Obviously you should use something meaningful,
; as this text will be shown to user in menu
; selection for packer type.
;
; Filename: 12 letter filename (no paths!) of packer
; program. Be sure it's on your DOS path somewhere
; and MaxMail will find it. Just name and
; extension.
;
; PackedFilename: 12 letter filename (no paths!) which will
; be packed filename. Actually MaxMail will only
; use first 6 characters of filename and add a
; numeric series (00,01,02,etc) to pad onto name.
; Extension will be whatever you specify though,
; but it should be default one that packer program
; expects. Prob you should use name of your bbs
; (1st 6 chars or whatever) to indicate to user
; where file came from.
;
; CommandLine: Command line to pass to packer. Again, make sure
; there are no embedded spaces! Use an underscore.
; You have 2 substitute tokens you will have to
; embed here. They begin with '%' character:
;
; %a: Subtitutes PackedFilename.
; %t: Subtitutes TxtFile. (filename for
; captured messages).
;
; These tokens can be located anywhere in the
; command line string of course. See examples
; below for clarity. We use standard packers
; here but you can always add any exotic
; new packer you wish! Very flexible huh?
;
; ViewLine: This is an optional field. It is the command
; line for viewing the archived packfile. MaxMail
; ,if it sees this field, will call up the packer
; program again, executing this command line. It
; is expected this is the command to display the
; arcived file, using standard DOS output. MaxMail
; will re-route that output to a text file, then
; display the file to the user. Thus the use can
; confirm what the packed file looks like. Just
; a nice additional feature. It uses the same
; 2 substitute tokens as the previous field. If
; you don't want to bother with this, just put a
; semicolon in front of this, or remove the
; string.
;
;
Packer LHarc_(Tightest) Lh.exe Crnstn.lzh _a_%a_%t _l_%a
Packer Arc_(Universal) Arc2.exe Crnstn.arc _-a_%a_%t _-v_%a
Packer PKzip_(Popular) PkZipf.exe Crnstn.zip _-a_%a_%t _-vb_%a
;
;
; Protos: Here is where you specify the xfer protocols user is allowed.
; You can specify as many protocols as you want. Menu will display
; them in order appearing here. So if you change them or the order
; of them, you probably want to force users to re-do their
; configuration (delete User Config file), or use Utility mode.
; There are 3 tokens (seperated by tab/blank) required. Any lines
; with less than 3 tokens will be ignored. Be sure each token has
; *NO* embedded spaces/tabs, else it will be considered another
; token! Use an underscore "_" in place of blank space. See the
; examples here if confused. Tokens are:
;
; Description Filename PackedFilename CommandLine
; ---------------------------------------------------
; Description: Simple short description of protocol type.
; Obviously you should use something meaningful,
; as this text will be shown to user in menu
; selection for protocol.
;
; Filename: 12 letter filename (no paths!) of protocol
; program. Be sure it's on your DOS path somewhere
; and MaxMail will find it. Just name and
; extension. Currently we have used PCZ.exe here
; You can try out any others you wish, but be
; and test them first.
;
; CommandLine: Command line to pass to protocol program. Again,
; make sure there are no embedded spaces! Use an
; underscore. You have 3 substitute tokens you can
; embed here. They begin with '%' character:
;
; %a: Subtitutes PackedFilename.
; %p: Subtitutes current com port. 1 based,
; I.E. 1 = com1,2=com2,etc.
; %b: Current baud rate.
;
; These tokens can be located anywhere in the
; command line string of course. See examples
; below for clarity. We use standard packers
; here but you can always add any exotic
; new protocols you wish! Very flexible huh?
;
Protos Xmodem_(Worst) m2z.exe _-prot_XMODEM_-b_%b_-u_%p_-h_-n_-s%a
Protos 1Kxmodem_(Fair) m2z.exe _-prot_XMODEM1K_-b_%b_-u_%p_-h_-n_-s%a
Protos Ymodem_Batch_(Good) m2z.exe _-prot_YMODEMB_-b_%b_-u_%p_-h_-n_-s%a
Protos Zmodem_(Best!) m2z.exe _-b_%b_-u_%p_-h_-n_-s%a
;
;