home *** CD-ROM | disk | FTP | other *** search
- ;----------------------------------------------------------------------------;
- ; ;
- ; FAN (File Announcement Utility) Configuration file ;
- ; ;
- ;----------------------------------------------------------------------------;
-
- ;============================================================================;
- ; The following commands MUST be defined. ;
- ;============================================================================;
-
- ;----------------------------------------------------------------------------;
- ; RegistrationKey ;
- ; ;
- ; Please register FAN! There is no obligation on your part when you ;
- ; register FAN. This simply lets me know how many folks are using FAN, and ;
- ; will have a direct effect on the amount of time I allocate to FAN ;
- ; enhancements. ;
- ; ;
- ; Registering FAN is easy! Simply type REGISTER at the OS/2 or DOS command ;
- ; prompt. That's it! FAN will create a message which will be sent to my ;
- ; system. FAN will prompt you whether you want to send the message Crash, ;
- ; or let it be routed. Routing can only be used for FidoNet node addresses. ;
- ; ;
- ; After my system receives the FAN registration request, you will receive ;
- ; an automated response with your registeration key. ;
- ; ;
- ; When the registration key is installed in your configuration file, all ;
- ; ^aPID lines will be written as FAN x.xx Reg where x.xx is the version ;
- ; number. Otherwise, the ^aPID line will read FAN x.xx Eval. ;
- ; ;
- ; Until you receive your registration key, please use the keyword ;
- ; "Evaluation". ;
- ; ;
- ; Please note: The registration key is based on your primary node address, ;
- ; system name, and sysop name (PrimaryAddress, SystemName, and ;
- ; SystemSysopName). If any of these should change after you ;
- ; receive a registration key, you will have to re-register FAN ;
- ; to receive a new registration key. ;
- ;----------------------------------------------------------------------------;
-
- RegistrationKey Evaluation
-
- ;----------------------------------------------------------------------------;
- ; SystemName ;
- ; SysopName ;
- ; ;
- ; Information specific to your system. These are primarily used to create ;
- ; the registration key. ;
- ;----------------------------------------------------------------------------;
-
- SystemName LiveNet OS/2 BBS
- SysopName Dave Fisher
-
- ;----------------------------------------------------------------------------;
- ; PrimaryAddress ;
- ; ;
- ; Primary default node address in [<zone>]:<net>/<node>[.<point>] format. ;
- ; Zone defaults to 1, point to 0 if not specified. Alternate addresses can ;
- ; be defined on an area-by-area basis within each MsgAreaName definition ;
- ; below. ;
- ;----------------------------------------------------------------------------;
-
- PrimaryAddress 1:170/110.0
-
- ;----------------------------------------------------------------------------;
- ; InboundPathTICS ;
- ; InboundPathFiles ;
- ; PacketPath ;
- ; ;
- ; Use these keywords to define the paths for your incoming files and mail ;
- ; packets. ;
- ; ;
- ; These paths MAY or MAY NOT be used depending upon other configuration ;
- ; options. For example, if you decide to have FAN write messages to your ;
- ; message *.MSG formatted message base instead of creating *.PKT files, ;
- ; the PacketPath will never be used. Or, if you only have FAN scan your ;
- ; FILES.BBS files instead of *.TIC files, then InboundPathTICS and ;
- ; InboundPathFiles will never be used. ;
- ; ;
- ; However, in the interest of completeness and ease of use, these ;
- ; configuration definitions are required. ;
- ;----------------------------------------------------------------------------;
-
- InboundPathTICS c:\binkley\inbound ; Path for TIC files
- InboundPathFiles c:\binkley\inbound ; Path for files associated with TIC's
- PacketPath c:\binkley\inbound ; Destination directory for *.PKT files
-
-
- ;============================================================================;
- ; The following commands are OPTIONAL. ;
- ;============================================================================;
-
- ;----------------------------------------------------------------------------;
- ; If you are going to write messages directly to a message base, and not ;
- ; to *.PKT files, then you will probably want to define one or more of the ;
- ; following statements to resolve the physical paths to the message base data;
- ; files and message base type (*.MSG or Squish): ;
- ; ;
- ; MaximusMsgAreaFileName : Control file used by Maximus to define all ;
- ; echo message areas. ;
- ; ;
- ; SquishCfgFileName : Configuration file used by Squish to define ;
- ; all echo message areas. ;
- ; ;
- ; AreasBBSFileName : Standard AREAS.BBS file used to define all ;
- ; echo message areas. ;
- ;----------------------------------------------------------------------------;
-
- MaximusMsgAreaFileName c:\bbs\max\system\msgarea.ctl
-
- SquishCfgFileName c:\bbs\squish\squish.cfg
-
- ;AreasBBSFileName c:\bbs\squish\areas.bbs
-
- ;----------------------------------------------------------------------------;
- ; OriginLine ;
- ; ;
- ; The origin line will be included at the bottom of every message. If ;
- ; 'OriginLine' is not specified, it will default to: ;
- ; * Origin: (Zone:Net/Node) ;
- ; ;
- ; The node address will automatically be appended to the origin line and ;
- ; should not be added manually here. ;
- ;----------------------------------------------------------------------------;
-
- OriginLine LiveNet! Tulsa's OS/2 Warehouse. 918-481-5715
-
- ;----------------------------------------------------------------------------;
- ; [No]Quiet ;
- ; ;
- ; Prevents output to standard out (the screen, normally) except for the logo.;
- ;----------------------------------------------------------------------------;
-
- NoQuiet ; Send output to the screen.
-
- ;----------------------------------------------------------------------------;
- ; TossLogFile ;
- ; ;
- ; If .PKT's are created, the tag name for each message area will be added to ;
- ; this file. This file name can then be used as an input file for many ;
- ; tosser/scanner programs. ;
- ;----------------------------------------------------------------------------;
-
- TossLogFile c:\bbs\fan\fantoss.log
-
- ;----------------------------------------------------------------------------;
- ; [No]INTLkludge ;
- ; ;
- ; If defined, and the destination and origination zone numbers are different,;
- ; the netmail kludge line ^aINTL <dest z:n/n> <orig z:n/n> will be used for ;
- ; inter-zone addressing. ;
- ;----------------------------------------------------------------------------;
-
- INTLkludge ; Use ^aINTL kludge
-
- ;----------------------------------------------------------------------------;
- ; [No]PID ;
- ; ;
- ; Currently there is a FidoNet proposal (FSC-0046.002) to replace the tear ;
- ; and origin line with the kludge construct: ;
- ; ;
- ; ^aPID: <pID> <version> <serial#> ;
- ; ;
- ; Enabling this keyword will instruct FAN to add this construct to the top ;
- ; of each message. ;
- ;----------------------------------------------------------------------------;
-
- PID ; Use PID kludge
-
- ;----------------------------------------------------------------------------;
- ; [No]VerboseTearLine ;
- ; ;
- ; Since the ^aPID construct is still in the proposal stage, and not official ;
- ; FidoNet policy, [no]VerboseTearLine is provided. If the ^aPID statement ;
- ; is used, you will normally set NoVerboseTearLine to eliminate the version ;
- ; number information from the tear line of the message since this is ;
- ; included in the ^aPID kludge of the message. ;
- ;----------------------------------------------------------------------------;
-
- VerboseTearLine ; Keep tearline short ("--- FAN"), on version info
-
- ;----------------------------------------------------------------------------;
- ; [No]Seen-Bys ;
- ; ;
- ; If enabled, ^aSEEN-BYs will be included at the bottom of the message for ;
- ; *.PKT type messages. ;
- ;----------------------------------------------------------------------------;
-
- Seen-Bys ; Include SEEN-BYs at end of packet.
-
- ;----------------------------------------------------------------------------;
- ; [No]PATHkludge ;
- ; ;
- ; If defined, the echomail kludge line ^aPATH: net/node is included at ;
- ; the end of messages for *.PKT type messages. ;
- ;----------------------------------------------------------------------------;
-
- PATHkludge ; Include ^aPATH at end of packet.
-
- ;----------------------------------------------------------------------------;
- ; [No]AppendSequenceNumber ;
- ; ;
- ; Some mail processing software (such as Squish) may detect consecutive ;
- ; messages produced by FAN as duplicates. The only failsafe method that ;
- ; I have been able to determine is to append a sequence number at the end ;
- ; of the subject line to avoid this. ;
- ; ;
- ; If 'AppendSequenceNumber' is defined, then the phrase "(nn)" will be ;
- ; appended to the subject line if multiple messages must be created ;
- ; for a message base. The only reason multiple messages would be produced ;
- ; is if there are more files to announce than 'MaxAnnouncementsPerMessage'. ;
- ;----------------------------------------------------------------------------;
-
- AppendSequenceNumber ; Append sequence number if necessary
-
- ;----------------------------------------------------------------------------;
- ; [No]ProcessBadTics ;
- ; ;
- ; If defined, FAN will process TK*.BAD files. FAN will announce these ;
- ; files to the built-in Announce name BAD_TICS (if you have set up an ;
- ; Announcement Definition including the name BAD_TICS below), and rename ;
- ; the TK*.BAD files to TK*.FAN. ;
- ;----------------------------------------------------------------------------;
-
- ProcessBadTics
-
- ;----------------------------------------------------------------------------;
- ; TickConfigurationFile ;
- ; ;
- ; If 'TickConfigurationFile' is defined, FAN will read TIC and File Area ;
- ; information used with Barry Geller's TIC program. If you wish to have ;
- ; FAN announce files that are locally HATCHed from your machine, you will ;
- ; want to enable this keyword so that FAN knows where the *.RAD files ;
- ; are created. ;
- ;----------------------------------------------------------------------------;
-
- TickConfigurationFile c:\bbs\tick\tick.cfg
-
- ;----------------------------------------------------------------------------;
- ; TickFileMask ;
- ; BadTickFileMask ;
- ; ;
- ; If you receive files that use *.TIC formatted files, you can instruct ;
- ; fan what file mask to use when searching for those files. For example, ;
- ; TIC uses TK*.TIC, while AllFix uses AF*.TIC. The default is *.TIC. ;
- ; However, some packages use an extention of .TIC for non-TIC files (such as ;
- ; Portal Of Power) which may be in the inbound directory. Thus you may want ;
- ; FAN to be more discriminating in the matching pattern used to find TIC ;
- ; files. ;
- ; ;
- ; Bad TIC files are normally rename to the same basename, with the extension ;
- ; of ".BAD". However, to support numerous different TIC processors, this ;
- ; file mask is also user-selectable. ;
- ; ;
- ; If not defined, TickFileMask defaults to *.TIC, while BadTickFileMask ;
- ; defaults to TK*.BAD. ;
- ; ;
- ; Do not include paths on these masks. If you do, they will be stripped and ;
- ; ignored. ;
- ;----------------------------------------------------------------------------;
-
- TickFileMask TK*.TIC
- BadTickFileMask TK*.BAD
-
- ;----------------------------------------------------------------------------;
- ; Months ;
- ; ;
- ; The month names are used both in the log file and announcement text. It ;
- ; is possible to define several different month lists, primarily to ;
- ; accomodate the creation of announcements in various languages. If not ;
- ; defined, the english 3 letter month abbreviations will be used. Each ;
- ; line is in the following format: ;
- ; ;
- ; Months <index number> <January Month Name>, <February Month Name>, ... ;
- ; ;
- ; The index number is used in the MsgAreaName definitions below. If not ;
- ; indicated in the MsgAreaName definition, DefaultMonthIndex will be used (if;
- ; it is not defined, then Index 1 will be used). After the index number, ;
- ; 12 month names must be defined, separted by a comma or space, and must be ;
- ; declared all on one line. ;
- ; ;
- ; A total of 9 'Months' indexes may be defined. ;
- ;----------------------------------------------------------------------------;
-
- Months 1 Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov, Dec
- Months 2 January, February, March, April, May, June, July, August, September, October, November, December
- Months 3 Jan, Fév, Mar, Avr, Mai, Jun, Jui, Aoû, Sep, Oct, Nov, Déc
-
- ;----------------------------------------------------------------------------;
- ; DefaultMonthIndex ;
- ; ;
- ; If defined, the specified 'Months' index will be used for the template ;
- ; macros [curmonthname] and [filemonthname]. Otherwise, Index 1 will be ;
- ; used. Remember, this index can be overridden by forcing a particular ;
- ; month list index in the template file itself by using [filemonthname1], ;
- ; [filemonthname2], etc. where the number is the month list index. ;
- ;----------------------------------------------------------------------------;
-
- DefaultMonthIndex 1
-
- ;----------------------------------------------------------------------------;
- ; AnnounceLogFile ;
- ; AnnounceLogTemplate ;
- ; AnnounceLogMonthIndex ;
- ; ;
- ; If 'AnnounceLogFile' is defined, ALL files announced will be logged ;
- ; to this file. The file is formatted according to the definitions found ;
- ; in the 'AnnounceLogTemplate' file. ;
- ;----------------------------------------------------------------------------;
-
- AnnounceLogFile c:\bbs\fan\filelist.log
- AnnounceLogTemplate c:\bbs\fan\filelist.tpl
- AnnounceLogMonthIndex 1 ; Month index to use from 'Months' above.
-
- ;----------------------------------------------------------------------------;
- ; MaxAnnouncementsPerMessage ;
- ; ;
- ; This limits the number of announcements which will be written to one ;
- ; message. It is a good idea to limit the number of announcements within ;
- ; in one message since most mail processing software will not be able to ;
- ; handle a message over 16k in size. ;
- ; ;
- ; The default is 40 announcements per message. ;
- ;----------------------------------------------------------------------------;
-
- MaxAnnouncementsPerMessage 10
-
- ;----------------------------------------------------------------------------;
- ; SortMethod ;
- ; ;
- ; Files within an announcement message can be sorted with any of the ;
- ; following methods: ;
- ; ;
- ; None : No sort. Files will be announced in the order they are ;
- ; processed. ;
- ; Alpha : Files will be sorted alphabetically. ;
- ; Group : Files will be sorted by group (TIC/FILESBBS) name, and then ;
- ; alphabetically within the group. ;
- ; ;
- ; SortMethod can also be Announcement Definition specific. Thus, you can ;
- ; have different sorting/presentation strategies for different message areas.;
- ; If define here, outside any Announcement Definition, this will become the ;
- ; default for any areas in which a SortMethod is not specified. ;
- ;----------------------------------------------------------------------------;
-
- SortMethod Group
-
- ;----------------------------------------------------------------------------;
- ; AnnounceList ;
- ; ;
- ; AnnounceList contains a list of all the files that have been announced, ;
- ; one file name per line. ;
- ; ;
- ; The AnnounceList is solely used as a duplicate announcement mechanism ;
- ; when using FILESBBS statements. If you do not define an AnnounceList, ;
- ; all files entries in a FILESBBS file will be announced until you move ;
- ; them to another file area which FAN does not know about. ;
- ; ;
- ; Thus, it is a good idea to define this if using FILESBBS statements. The ;
- ; AnnounceList file will be checked to prevent duplicate announcements if ;
- ; you haven't had a chance to move the files from your "newup" areas since ;
- ; the last run of FAN. ;
- ; ;
- ; It can be deleted periodically if it grows too large. ;
- ; ;
- ; However, if you are using FAN and do not receive new files via *.TIC ;
- ; distributions and only create announcements from FILESBBS files, then ;
- ; you will never want to delete the AnnounceList file since it must ;
- ; represent every file in the defined FILESBBS statements above. ;
- ;----------------------------------------------------------------------------;
-
- AnnounceList c:\bbs\fan\announce.lst
-
- ;----------------------------------------------------------------------------;
- ; MaximusFileAreaFileName ;
- ; ;
- ; If you are running Maximus or Opus and do not want to define all the ;
- ; FILES.BBS files below in this configuration file, FAN can read Maximus' ;
- ; or Opus' File Area Control file. Simply specify the name of the control ;
- ; file and define an Announce Name (which will be used in the Announcement ;
- ; Definitions to reference new files found in the file area) for each file ;
- ; area. ;
- ;----------------------------------------------------------------------------;
-
- MaximusFileAreaFileName c:\bbs\max\system\filearea.ctl
-
- ; Maximus File
- ; Area Name FAN Announce Name
- ; ------------ -----------------
-
- MaximusFileArea 98 LIVENETOS2
- MaximusFileArea 99 NEWGENFILES
-
- ;----------------------------------------------------------------------------;
- ; FILES.BBS File Definitions ;
- ; ;
- ; If FILESBBS_FileName is defined, then this file will also be searched ;
- ; for new incoming files to announce, in addition to any .TIC files in the ;
- ; inbound directory. The format of each line in the FILESBBS file is: ;
- ; ;
- ; FileName FileDescription ;
- ; ;
- ; FILESBBS_Files is the directory in which the actual files reside. ;
- ; ;
- ; FILESBBS_AnnounceName is the name to use in the Announcement ;
- ; Definition below when referring to new files found in the Files.BBS. ;
- ; ;
- ; If this option is used, ALL FILESBBS_xxxxx statements must be ;
- ; defined, and in the order of _FileName, _Files, _AnnounceName, and ;
- ; then _Description. ;
- ;----------------------------------------------------------------------------;
-
- ;FILESBBS_FileName c:\max\files\os2new\files.bbs
- ;FILESBBS_Files c:\max\files\os2new
- ;FILESBBS_AnnounceName LIVENETOS2
- ;FILESBBS_Description New undesignated OS/2 files
-
- ;FILESBBS_FileName c:\max\files\newup\files.bbs
- ;FILESBBS_Files c:\max\files\newup
- ;FILESBBS_AnnounceName NEWGENFILES
- ;FILESBBS_Description New undesignated general files
-
- ;----------------------------------------------------------------------------;
- ; FileAreaDescriptions ;
- ; ;
- ; If you wish to use the [FileAreaDesc] token in your announcement, FAN will ;
- ; need to associate a description with each TIC/FILESBBS area name. If you ;
- ; use SEAL, FAN will automatically fill in the description using the SEAL ;
- ; configuration verg ;FileDesc in the TIC configuration file. Otherwise, ;
- ; you can uncomment FileAreaDescriptions to have FAN read a text file which ;
- ; is in RAID.CFG/FILEBONE.NA format. ;
- ; ;
- ; This is not necessary for FILESBBS areas, since the description is filled ;
- ; in using the FILESBBS_Description configuration verb. ;
- ;----------------------------------------------------------------------------;
-
- FileAreaDescriptions c:\max\files\fidonet\filebone.na
-
-
- ;----------------------------------------------------------------------------;
- ; Logging definitions ;
- ; ;
- ; Log messages are ranked between 1 to 4, where 1 is the most important ;
- ; type of message (usually a fatal error of some sort), and 4 is the ;
- ; most extraneous (an informational message of some sort). This gives ;
- ; you control over how verbose to make the status log. ;
- ; ;
- ; Each message in the log file is preceded by a special symbol indicating ;
- ; it's level of importance as follows: ;
- ; ;
- ; For BinkleyTerm style logs: ;
- ; ;
- ; LogLevel Characters That Precede Included Entries ;
- ; ;
- ; 1 ! (Usually error messages) ;
- ; 2 * ;
- ; 3 + ;
- ; 4 : ;
- ; ;
- ; For FrontDoor style logs: ;
- ; ;
- ; LogLevel Characters That Precede Included Entries ;
- ; ;
- ; 1 ! (Fatal and non-fatal error messages) ;
- ; 2 + (Brief messages) ;
- ; 3 - (Trivial messages) ;
- ; 4 - (Trivial messages) ;
- ; ;
- ; Since FrontDoor really only has three levels of messages when dealing ;
- ; with the ranking of "importance" of those messages, levels 3 and 4 will be ;
- ; considered the same. ;
- ;----------------------------------------------------------------------------;
-
- Log ; [No]Log - Log process information to log
- ; file
-
- LogLevel 4 ; Level of logging where 1 is the most minimal
- ; amount of information, and 4 is the most
- ; detailed.
-
- LogFile c:\bbs\logs\fan.log ; Name of the log file (MUST be defined to
- ; use the logging feature.) There is no
- ; default.
-
- LogStyle BinkleyTerm ; Sytle of the log entries--either
- ; 'BinkleyTerm' or 'FrontDoor'.
-
- LogMonthIndex 1 ; Month names to use from the defined lists
-
- LogWarnings ; Print warnings to log and/or screen
-
- ;----------------------------------------------------------------------------;
- ; Announcement Area Definitions ;
- ; ----------------------------- ;
- ; ;
- ; Templates can be used to customize the actual appearance of the ;
- ; announcement. Various macros can be used in the template itself. ;
- ; ;
- ; See the FAN documentation (FAN.DOC) for more detailed descriptions of ;
- ; creating template files and using template macros. Included with FAN ;
- ; are many template files (*.TPL) for examples of actual usage. ;
- ; ;
- ; The following templates can be defined to act as default values for all ;
- ; Announcement Definitions, or they can be individually specifed in ;
- ; each Announcement Definition below. ;
- ;----------------------------------------------------------------------------;
-
- PrefixTemplate c:\bbs\fan\prefix.tpl ; Template used at beginning
- ; of each message
- FileTemplate c:\bbs\fan\file.tpl ; Template used to announce each
- ; specific file received
- SuffixTemplate c:\bbs\fan\suffix.tpl ; Template used at end of message
-
- GroupTemplate c:\bbs\fan\group.tpl ; If SortMethod=Group, this template
- ; will be the header for each group
-
- ;----------------------------------------------------------------------------;
- ; DefaultMsgAreaType ;
- ; ;
- ; FAN is able to create announcement messages in a variety of formats. ;
- ; Normally you specify the format of the announcement for each Announcement ;
- ; Definition at the end of this configuration file. However, if all your ;
- ; Announcement Areas are the same format--or most of them are the same ;
- ; format, then you can avoid defining the area type for each one by ;
- ; designating a "default" message area type here. ;
- ; ;
- ; Valid Message Types: ;
- ; ;
- ; Packet : FAN will create announcements in FTS-0001 FidoNet *.PKT ;
- ; standard format in the directory defined by 'PacketPath'. ;
- ; These can then be tossed by your mail processing software. ;
- ; ;
- ; *.MSG : FAN will write announcements to a *.MSG message base. ;
- ; ;
- ; Squish : FAN will write announcements to a Squish message base. ;
- ; ;
- ; ASCII : FAN will write announcements to an Ascii text file. ;
- ;----------------------------------------------------------------------------;
-
- DefaultMsgAreaType Packet
-
- ;----------------------------------------------------------------------------;
- ; DefaultMsgAttributes ;
- ; ;
- ; Default message attributes for any messages created by FAN. If the keyword;
- ; 'Attributes' is not specified within an Announcement Area Definition ;
- ; below, these default message attributes will be used. ;
- ; ;
- ; Attributes can be any combination of the following: ;
- ; ;
- ; P = Private ;
- ; C = Crash ;
- ; H = Hold ;
- ; K = Kill/Sent ;
- ; L = Local ;
- ; F = Forward ;
- ; R = Read/Received ;
- ; S = Sent ;
- ; X = Scanned (Squish only) ;
- ; ;
- ; Do not separate attributes with spaces. For example, to mark a message ;
- ; as Hold, Private, and Local, use "HPL". Order is not significant. ;
- ;----------------------------------------------------------------------------;
-
- DefaultMsgAttributes L
-
- ;----------------------------------------------------------------------------;
- ; Each announcement definition starts with "MsgAreaName". This is the ;
- ; actual name of the echo/message base to receive the announcement message. ;
- ; Each definition is fully self contained, and does not relate to other ;
- ; definitions in any way. ;
- ; ;
- ; Defaults values are as follows: ;
- ; ;
- ; AddressFrom : [Default Primary Address defined at top of file] ;
- ; AddressTo : [Default Primary Address defined at top of file] ;
- ; From : File Announcer ;
- ; To : All ;
- ; Subj : Files received for distribution ;
- ; Attributes : L (or DefaultMsgAttributes, if defined) ;
- ; MonthIndex : 1 ;
- ; MsgAreaType : *.MSG/Squish/Ascii/Packet or DefaultMsgAreaType. If FAN ;
- ; FAN searches Squish/Maximus/AREAS.BBS config. files, the ;
- ; MsgAreaType will be overridden, except for ASCII areas. ;
- ; MsgAreaPath : Physical path/name of echo data file. Not necessary if ;
- ; FAN searches Squish/Maximus/AREAS.BBS config. files. ;
- ; SortMethod : [Default SortMethod defined earlier] ;
- ; ;
- ; Some tosser/scanners need the Local flag set to indicate that the ;
- ; message originated from your machine. ;
- ; ;
- ; There are two fixed MsgAreaNames used internally by FAN. They are as ;
- ; follows: ;
- ; ;
- ; MsgAreaName NETMAIL ;
- ; ;
- ; This will tell FAN to format the message for netmail, and not ;
- ; echomail. The NetMail path will be read from your Squish or Maximus ;
- ; configuration/control files. If you have not defined these, you will ;
- ; have to include MsgAreaType and MsgAreaPath in the NETMAIL definitions ;
- ; below. There is no limit to the number of NETMAIL announce areas. ;
- ; ;
- ; MsgAreaName ASCII ;
- ; ;
- ; This will tell FAN to format the message for an ascii text file. The ;
- ; MsgAreaType should also be set to "ASCII". ;
- ; ;
- ;----------------------------------------------------------------------------;
-
- ;============================================================================
- ; Specific Announcenment Area Definitions
- ;============================================================================
-
- ;
- ; Bad TIC file announcement area
- ;
- ; The Announce name of 'BAD_TICS' is a fixed keyword used internally
- ; by FAN.
- ;
-
- MsgAreaName LOCAL
-
- From File Announcer
- To Dave Fisher
- Subj Bad TIC Files Received
- Attributes LP
- FileTemplate c:\bbs\fan\local.tpl
-
- Announce BAD_TICS
-
- ; -------------------------------------------------------------------------
- ; Announcements for Sysop170
- ; -------------------------------------------------------------------------
-
- MsgAreaName SYSOP170
-
- From Dave Fisher
- To All Net 170 Sysops
- Subj New OS/2 files received via Fernwood File Distribution
- SuffixTemplate c:\bbs\fan\sysop170.tpl
-
- Announce FWDRIVRS FWGAMES FWUTILS FWSYSUTL FWLAN FWCOMM FWREXX
- Announce FWGRAPHX FWAPPS FWFONTS FWOS2NFO
-
- ; Other OS/2 files I pull in
-
- MsgAreaName SYSOP170
-
- From Dave Fisher
- To All Net 170 Sysops
- Subj New OS/2 files received for distribution
- SuffixTemplate c:\bbs\fan\sysop170.tpl
-
- Announce LIVENETOS2
-
- ; ibmNET files
-
- MsgAreaName SYSOP170
-
- From Dave Fisher
- To All Net 170 Sysops
- Subj New OS/2 files received via ibmNET
- SuffixTemplate c:\bbs\fan\sysop170.tpl
-
- Announce IBM* LEXMARK
- Exclude IBMNET
-
- ; -------------------------------------------------------------------------
- ; Local announcement area
- ; -------------------------------------------------------------------------
-
- MsgAreaName LOCAL
-
- From Dave Fisher
- To All
- Subj New file(s) received via SDS/SDN
- MonthIndex 2
- FileTemplate c:\bbs\fan\local.tpl
-
- Announce SDSMAX SDSOS2 SDSBINK SDSFIDO NEWSLETR
- Announce PDNOS2 PDNNEWS PDNCEE
-
- MsgAreaName LOCAL
-
- From Dave Fisher
- To All
- Subj New file(s) received via the SIO/VSIO Beta Distribution
- MonthIndex 2
- FileTemplate c:\bbs\fan\local.tpl
-
- Announce SIO
-
- ; Fernwood and other OS/2 files
-
- MsgAreaName LOCAL
-
- From Dave Fisher
- To All
- Subj New OS/2 files available for downloading
- MonthIndex 2
- FileTemplate c:\bbs\fan\local.tpl
-
- Announce LIVENETOS2 PDNGNU
- Announce FWDRIVRS FWGAMES FWUTILS FWSYSUTL FWLAN FWCOMM FWREXX
- Announce FWGRAPHX FWAPPS FWFONTS FWOS2NFO
-
- ; ibmNET files
-
- MsgAreaName LOCAL
-
- From Dave Fisher
- To All
- Subj New OS/2 files received via ibmNET
- MonthIndex 2
- FileTemplate c:\bbs\fan\local.tpl
-
- Announce IBM* LEXMARK
- Exclude IBMNET
-
- ; ibmNET private file area
-
- MsgAreaName LOCAL
-
- From File Announcer
- To Dave Fisher
- Subj ibmNET private files received
- Attributes LP
- MonthIndex 2
- FileTemplate c:\bbs\fan\local.tpl
-
- Announce IBMNET
-
- ; OS2NET private file areas
-
- MsgAreaName LOCAL
-
- From File Announcer
- To Dave Fisher
- Subj OS2NET private files received
- Attributes LP
- MonthIndex 2
- FileTemplate c:\bbs\fan\local.tpl
-
- Announce OS2-DIFF OS2-INFO
-
- ; Fernwood private file area
-
- MsgAreaName LOCAL
-
- From File Announcer
- To Dave Fisher
- Subj Fernwood Administrative files received
- Attributes LP
- MonthIndex 2
- FileTemplate c:\bbs\fan\local.tpl
-
- Announce FWOS2ADM
-
- ; General files
-
- MsgAreaName LOCAL
-
- From Dave Fisher
- To All
- Subj Newly uploaded general files
- MonthIndex 2
- FileTemplate c:\bbs\fan\local.tpl
-
- Announce NEWGENFILES
-
- ; Private files not available on the BBS
-
- MsgAreaName LOCAL
-
- From File Announcer
- To Dave Fisher
- Subj New files received
- Attributes LP
- MonthIndex 2
- FileTemplate c:\bbs\fan\local.tpl
-
- Announce BACKBONE PDNAI ECHOLIST FTSC SNDSBVOC SNDSBUTL SNDGAMES WIN_*
-
- ; -------------------------------------------------------------------------
- ; Announcements written to ASCII Text Files
- ; -------------------------------------------------------------------------
-
- ;
- ; The following area is enabled when I use /TestMode on the command line
- ;
-
- ;MsgAreaName ASCII
- ;
- ;MsgAreaType Ascii
- ;PrefixTemplate c:\bbs\fan\testpre.tpl
- ;FileTemplate c:\bbs\fan\testfile.tpl
- ;SuffixTemplate c:\bbs\fan\testsuf.tpl
- ;MsgAreaPath c:\usr\proj\bbs\fan\testmsg.tst
- ;
- ;Announce *
-
- ; -------------------------------------------------------------------------
- ; Announcements written to NetMail
- ; -------------------------------------------------------------------------
-
- ;MsgAreaName NETMAIL
-
- ;From Dave Fisher
- ;To Mark Barbee
- ;Subj New file(s) received -- Just testing FAN's netmail function. :-)
- ;Attributes LP
- ;MonthIndex 2
- ;FileTemplate c:\bbs\fan\local.tpl
- ;AddressFrom 40:4372/0
- ;AddressTo 1:170/110.7
-
- ;Announce *
-
