home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Current Shareware 1994 January
/
SHAR194.ISO
/
email
/
dove0793.zip
/
NEWSSCAN.CFG
< prev
next >
Wrap
Text File
|
1993-07-30
|
20KB
|
425 lines
; Sample NewsScan.Cfg file
;
; NOTE: Minimal support for users of the KA9Q (NET.EXE) program is now
; included in NewsScan. See the keywords starting with "KA9Q".
; NOTE: The MaxGroups keyword is no longer needed nor supported in this file.
; NOTE: Leaving the UseNet "Path:" line in scanned messages is no longer the
; default. See comments on the "KeepPath" line below.
;
; PLEASE NOTE: If you have used earlier (beta test) versions of NewsScan, note
; carefully the usage of the TimeZone and TimeOffset words, since you may need
; to change these! Also, there are now maximum field lengths for newsgroup
; names and file paths, although I'd be real surprised if that causes a problem
; for anyone. Also, THE MAXIMUM MESSAGE LENGTH THAT NEWSSCAN WILL PROCESS IS
; 12K! Most Fidonet compatible BBS's will not let you enter a message anywhere
; near this long, but some message editors might. NewsScan will skip any
; messages that are too long. You can blame this limitation on the geniuses
; that decreed that Fidonet messages could have control information at both the
; top and bottom of the message, since it means that the entire message must
; fit in memory.
;
; Although this file uses many of the same tokens as DoveMail, it is NOT the
; same. You CANNOT use a DoveMail.Cfg file with NewsScan.
;
; The first lines deal with your log file. If you use a Binkley/Opus/Maximus
; format log file, and would like NewsScan to indicate when it runs and also
; place error information in the log file, then place the full path and
; filespec of your log file here. If you comment this line out, NewsScan won't
; try to use a log file.
;
LogFile C:\Bbs\Bbs.Log
;
;
;
;
; The next line is only for the use of those in non-English-speaking areas
; where you would like the three character abbreviations for the months of the
; year to be different than the English ones. Note that this affects many
; different aspects of how NewsScan operates (including how it deciphers and
; creates the date field in messages it exports) so you probably shouldn't
; change it unless you use the same abbreviations consistently. PLEASE NOTE:
; The string must be EXACTLY 36 characters long and must contain no spaces, or
; it will be rejected! I really VERY STRONGLY advise against using this
; feature, especially if you are connected to UseNet or the Internet, but you
; have the ability to change the string if you must...
;
; MonthString JanFebMarAprMayJunJulAugSepOctNovDec
;
;
;
;
; Now, some information about your system:
;
;
; This is your UUCP format address, as is placed in messages exported from
; your system. In NewsScan this is used in several of the messages header
; lines in exported messages. This line must be EXACTLY the same in both
; NewsToss and NewsScan for Path line dupe checking to work properly. This
; address, should NOT contain exclamation marks (!) since these are used as
; address delimiters. If you don't have a registed UUCP sitename but are in
; Fidonet, you'll probably use the [p#.]f#.n#.z#.fidonet.org format, like
; this:
;
Alias f8.n154.z1.fidonet.org
;
; If you have a registered name, you might use it instead, like this:
;
;Alias stjhmc.fidonet.org
;
;
;
;
; The above Alias will always be used in the "Relay-Version" line of created
; messages (don't worry about this too much because the "Relay-Version" line
; is changed by every system a message passes through), and unless you specify
; otherwise, it will also be used in the following three places:
; 1) In the "From" line of messages (i.e. From: user.name@alias)
; 2) In the "Message-ID" line of outgoing messages
; 3) In the "Path" line of outgoing messages (note the caution on this
; one as stated above under the "Alias" keyword).
; You can explicitly change any of these to use an alias other than the
; default, if you have special circumstances that require it, but you should
; NOT do this unless you absolutely have to and know what you are doing! If
; you don't need to do this, just leave the following lines commented out:
;
; FromAlias nbytes.myamiga.mixcom.com
; MsgIDAlias nbytes
; PathAlias nbytes
;
; Additional notes on "PathAlias": If you don't use it at all, or use it as
; shown above, only the system name will be placed in the Path line. However,
; in most cases you'll also want the user name as the originator of the message
; on the path line, in which case you can use one of the following special
; variations of the PathAlias line:
; 1) If you use "PathAlias !" (single exclamation point only), then the USER
; NAME (with periods substituted for spaces) will be placed in the PATH.
; This is probably what you want to use if you are also running DoveMail
; 2) If you use "PathAlias !!" (double exclamation point), then the default
; Alias AND the user name will be used (system.alias!john.doe)
; 3) You can also specify a PathAlias and append an exclamation point to
; specify an alias and that the user name should be used. For example,
; if you use "PathAlias nbytes!" then your path line would be of the form
; "Path: nbytes!john.doe"
; You should probably use either a PathAlias line of the form shown in #2 or
; #3 if you are NOT running DoveMail, but rather sending the output of
; NewsScan directly to your newsfeed.
;
;
;
;
; This is the text that goes into the "Organization" line of messages leaving
; your system. You could just say something like "No organization" but you
; could also put in the name of your BBS. You WILL incur the wrath of many
; if you try to put a "cute" saying or some such nonsense here. If you don't
; want an "Organization" line in your messages, just leave this commented out.
;
Organization Northern Bytes BBS - Sault Ste. Marie, MI U.S.A.
;
;
;
;
; Previous versions of NewsScan would always place a "Relay-Version" line as
; the first line of the message header. It now appears that such a line is no
; longer required, so NewsScan will NOT place a "Relay-Version" line in
; exported messages UNLESS you uncomment the following line:
;
;UseRelay
;
;
;
;
; When you (or a user of your BBS) is REPLYING to a message, if your BBS or
; message editor properly supports reply linking in the message header, you
; can place the character string "%R" (without the quotes) on a line by
; itself. If this reply macro is the ONLY thing on the line (*WITH NO
; PRECEDING SPACES OR TABS*), it will be expanded to a string of the
; following format:
;
; In article <message-ID> dated <date>, <user> wrote:
;
; The <message-ID>, <date> and <user> fields will be taken from the
; "Message-ID", "Date:" and "From:" lines of the message being replied to.
; You can change the text that will be used, or disable the reply macro
; entirely, by uncommenting the ReplyBanner statement. If you don't want
; reply macro expansion, just use the ReplyBanner keyword alone, like this:
;
;ReplyBanner
;
; However, if you want to change the text of the message associated with the
; %R character string, you can do something like this:
;
; ReplyBanner Message %m from %f, posted on %d, stated the following:
;
; In the above line, %m, will be expanded to the Message-ID of the message
; being replied to, %f will be expanded to the contents of the "From:" field,
; and %d to the contents of the "Date:" field of the message being replied to.
; PLEASE... Resist the urge to replace the standard message with something
; "cutesy" or sarcastic... your users will thank you (since they will take the
; heat if you change this to something provocative). Remember, the %d, %f,
; and %m macros only work in this file and MUST BE IN LOWERCASE. The %r
; (which is replaceed by the above banner message or the default message) goes
; in the message as entered on your system, on a line by itself, and it is case
; insensitive. If you don't quite understand all this now, just leave it
; all commented out and you'll be fine.
;
;
;
;
; This is the file name of the single newsgroup file that is created by
; NewsScan, which is then used as input to DoveMail. If you are feeding it
; to DoveMail, you should probably put it in your inbound files area with
; a *.PKU extension (Note: I suggest 7FFFFFFF.PKU since DovePack will never
; create a packet with this name). On the other hand, if you are a leaf node
; and just want to send this to your feed, then just give the path to your
; outbound area followed by an appropriately-named *.UUT file, like this:
;
OutFile C:\Opus\Outbound\009a0009.UUT
;
; NOTE: If you are using the KA9Q mode (see below), the OutFile line is
; irrelevent and may be left commented out (it will be ignored in KA9Q mode).
;
;
;
;
; The next two items deal with how the date and time string will look in
; messages exported from your system. If you want to use local time, then
; uncomment TimeZone and use the abbreviation (usually three characters long)
; for the time zone you are in (this will be appended to the date/time field
; of all messages exported from your system), and also use "TimeOffset 0"
; (this is very important if you have set the TZ environment variable from
; within your batch file). However, the preferable methodis to leave TimeZone
; commented out (in which case the default "GMT" will be used) and to use
; TimeOffset to indicate the difference in *MINUTES* between your Time Zone
; and Greenwich Mean Time. The reason for using minutes rather that hours is
; so that users living in places like Newfoundland (which have times that are
; not offset from GMT by an even hour amount) can be accommodated. TimeOffset
; will accept zero and negative numbers for those living on or east of the
; Greenwich Meridian. In North America, the following values for TimeOffset
; will be typical:
;
; Time Zone During Standard Time Use: During Daylight Time Use:
; --------- ------------------------ ------------------------
; Newfoundland 210 150
; Atlantic 240 180
; Eastern 300 240
; Central 360 300
; Mountain 420 360
; Pacific 480 420
; Alaska 540 480
; Hawaii 600 540
;
; If you leave both TimeZone and TimeOffset, commented out, the defaults used
; will be "GMT" and zero, respectively, which is probably NOT what you want
; unless you live on the Greenwich Meridian! Exception: If you have set the
; TZ environment variable in your batch file (to something like EDT04... note
; that the numeric part MUST start at the fourth character position!) and you
; leave TimeOffset commented out, NewsScan will try to calculate the offset
; from the environment variable. If you want to use the TZ environment
; variable, leave both of the keywords below commented out. If using the
; environment variable doesn't work properly, uncomment and use TimeOffset
; here. Note that the TimeOffset keyword is also used in NewsToss.Cfg and
; usually should be set to the same value in both files.
;
;TimeZone EST
TimeOffset 300
;
;
;
;
; NewsScan uses the same scheme of "high water marks" as most echomail
; processors. It uses the normal set unless you specify that you want to
; use the "alternate" set of high water marks by uncommenting the following
; line:
;
;AltHiWater
;
;
;
;
; NewsScan normally assumes that the messages it exports will NOT contain a
; tear line, SEEN-BY's, Path line, etc. If, due to software limitations you
; MUST create messages that have such lines, uncomment the following line and
; it will look for the last tear line in the message and strip everything
; following it before exporting the message.
;
;StripTear
;
;
;
;
; When NewsScan exports a message, it also writes some of the UseNet header
; lines back to the original message (these are used in reply linking). It
; will write a UseNet format "Subject: " line to the body of the message IF
; the message is a reply to another message and the Subject line is too long
; to fit in the Fidonet message header. However, you can force it to ALWAYS
; write the UseNet format Subject line to the body of the message by
; uncommenting the following line (Note: this is provided for compatibility
; with NewsToss. If you uncomment this line in NewsToss.Cfg, uncomment it
; here as well).
;
;KeepSubject
;
;
;
;
; When NewsScan exports a message, it will NOT write the UseNet format
; "Path: " line back to the original message unless the following line is
; uncommented (this is also provided for compatibility with NewsToss. If
; you uncomment this line in NewsToss.Cfg, uncomment it here as well).
; Should you be doing something as foolish as trying to convert newsgroups
; to echomail, leave this commented out or your echomail processor may
; complain that there is a PATH line but no SEEN-BY lines!
;
;KeepPath
;
;
;
;
; Normally NewsScan will "throw away" any control or high bit characters it
; finds in a message, because they aren't allowed in UseNet newsgroups. The
; following line, if uncommented, will disable the removal of control and high
; bit characters, but you should NOT do this except in VERY unusual situations.
;
;NoStrip
;
;
;
;
;
; When NewsScan exports a message that apparently did not originate on
; your system, it will include a "Sender" line in the exported message.
; If necessary, you can prevent this from happening by uncommenting the
; following line. You should probably always uncomment the following
; if using the "KA9Q" option below.
;
;NoSender
;
;
;
;
; NewsScan always places a batched newsgroup header line (consisting of
; the string "#! rnews <message length>") at the start of each message.
; If you are doing some unusual processing and do not require this header,
; uncomment the following line. DO NOT DO THIS unless you know what you
; are doing, since the header IS necessary in most applications.
;
;Nornews
;
;
;
;
; The following three lines are special for those using the KA9Q program and
; obtaining news from an NNTP news server that does not allow posting. The
; first modifies the behaviour of NewsScan to do the following: 1) Omit the
; "#! rnews" line on outgoing messages, 2) Output each message as a separate
; file in the specified mail queue directory, using the filename <sequence
; number>.txt, where the sequence number is obtained from the file
; SEQUENCE.SEQ in the same directory, 3) Create a *.WRK file for each
; message in the mail queue directory, 4) Use CRLF's instead of LF's as line
; terminators in eack message. If you use this line, you _MUST_ also use
; the "KA9QMailOut" and "KA9QNewsOut" lines (see below).
;
;KA9Q C:\KA9Q\SPOOL\MQUEUE\
;
;
;
;
; The idea behind the KA9Q Keyword is that exported messages are MAILED to a
; server at a site that can accept news articles (that already contain a
; valid "Newsgroups:" line) via mail and automatically post them to news.
; This allows you to receive mail from any NNTP news server (even one that
; does not allow posting) yet still be able to send outgoing messages to the
; newsgroups. In order to do this, NewsScan requires two piece of
; information. The first is the actual mail address of a server that can
; accept a news message via mail and automatically place it into news. The
; sample line below contains the actual address of one such server (valid as
; of July, 1993). For those familiar with the KA9Q *.WRK file format, this
; is what will go on the third line of the *.WRK file for each outgoing
; message.
;
;KA9QNewsOut mail2news@news.demon.co.uk
;
;
;
;
; The other piece of information required by the KA9Q support routine is the
; address of a "smart" mailer, or the actual address you want KA9Q's SMTP to
; connect to when sending news. Generally, this will be either the portion
; of the address used for the "KA9QNewsOut" keyword that FOLLOWS the "@"
; symbol (e.g. "news.demon.co.uk" following the above example) OR the name;
; of a smart host nearer to you. Again following the above example, if you
; live in the United States, for example, it would be preferable to send
; your mail to a smart host nearby and let it forward your mail to the U.K.
; via a high speed link. The example below uses merit.edu as the place to
; which your outgoing mail is sent; from there it would be forwarded to the
; address specified in the "KA9QNewsOut" line. For those familiar with the
; KA9Q *.WRK file format, this is what will go on the first line of the
; *.WRK file for each outgoing message.
;
;KA9QMailOut merit.edu
;
;
;
;
; This is the maximum message length that NewsScan will process. This defaults
; to 12288, however, if NewsToss locks up when tossing long messages you may
; need to reduce this slightly. Note that this implies that any messages
; longer than the set length will not be exported from your system. Please
; note that the message length limitation is required due to the fact that
; Fidonet format messages may contain control information at the bottom of the
; message, and therefore the entire message must be read into memory, and the
; compiler limits the amount of string space available. If anyone finds this
; length limitation truly objectionable, I am open to offers to purchase a
; better compiler for use in this project!
;
MaxLength 12288
;
;
;
;
; These are the actual newsgroup names, followed (on the same line) by one or
; more space characters and then the complete path to the message area. Please
; note that this section is NOT in the same format as is used by DoveMail.
; Also, each newsgroup must be EXPLICITLY specified, the use of the ".all"
; wildcard is not allowed. Note that there are a couple of length limitations
; that must be observed: The maximum permissible newsgroup name length is 64
; characters, and the maximum path length is 32 characters (if you have an
; entry that's too long, it will be truncated to the maximum length). If this
; causes anyone a real problem, please let me know. Finally, don't put blank
; or comment lines between "Begin_Newsgroups" and "End".
;
Begin_Newsgroups
alt.dcom.telecom D:\MSG\ATELECOM
alt.folklore.computers D:\MSG\FOLKLORE
rec.video.cable-tv D:\MSG\RV_CABLE
End
;
;
;
;
; The following are signature filenames (without paths, maximum twelve
; characters), followed by the user name with which the file name is
; associated. You may associate more than one user name with the same
; filename, but do not list a user name more than once. The way this works is
; that if the "From" field of a message being scanned contains a user name
; that is found in the list below, then the text of the associated signature
; file is appended to the text. The user name must match exactly, except that
; capitalization is not considered. The specified signature file will be
; searched for FIRST in the same directory as the message being scanned, and
; SECOND in the "current" directory (the one that NewsScan is running in).
; This lets you use special signature files in specific newsgroups, and/or a
; default signature file for all (other) newsgroups. If the signature file is
; not found in either directory, the message will be scanned out without any
; special treatment (and without the signature being added). Do NOT specify a
; drive or path with the signature filename, and do not use tab characters to
; separate the filenames from the user names (use spaces only). The signature
; file MUST be in a VERY specific format - see the NEWSSCAN.DOC file and the
; SAMPLE.SIG file included in the distribution archive. Comment this section
; out if you do not wish to use signature files. And, don't put blank or
; comment lines between "Begin_Sigfiles" and "End".
;
Begin_Sigfiles
smith.sig John Smith
sample.sig Alfred Neuman
End