Current Shareware 1994 January/SHAR194.ISO/email/dove0793.zip/NEWSTOSS.CFG

Text File | 1993-04-08 | 22KB | 487 lines

; Sample NewsToss.Cfg file
;
; NOTE: If you receive batched newsgroup files from a newer version of KA9Q's
;       NET.EXE (or if for some reason you receive batched newsgroup files
;       containing carriage returns) see the KillCR keyword below.
; NOTE: NEW - *LIMITED* support for tossing incoming uncompressed MAIL
;       messages to your netmail area.  See below.  If you do receive
;       mail, be sure to adjust the HeaderLines and MaxFiles values to
;       higher numbers if necessary.
; NOTE: The MaxGroups keyword is no longer needed nor supported in this file.
; NOTE: Leaving the UseNet "Path:" line in tossed messages is no longer the
;       default.  See comments on the "KeepPath" line below.
; NOTE: The TimeOffset keyword is NEW in NewsToss.Cfg.  Be sure it is set
;       properly or your messages may be dated improperly.
;
; Although this file uses many of the same tokens as DoveMail, it is NOT the
; same.  You CANNOT use a DoveMail.Cfg file with NewsToss.
;
; The first lines deal with your log file.  If you use a Binkley/Opus/Maximus
; format log file, and would like NewsToss 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, NewsToss 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 NewsToss operates (including how it deciphers the
; date field of incoming newsgroup messages) so you probably shouldn't change
; it unless your newsgroup feed uses different abbreviations.  PLEASE NOTE: The
; string must be EXACTLY 36 characters long and must contain no spaces, or it
; will be rejected!  I really advise against using this feature but you can
; change the string if you must...
;
; MonthString JanFebMarAprMayJunJulAugSepOctNovDec
;
;
;
;
; The following line, if uncommented, will write additional information to the
; log file as each incoming packet is tossed, including the total number of
; messages received in each newsgroup.  Please note that the totals given are
; for each individual *.PKU (or other incoming newsgroup) packet received, so
; you may want to keep this commented out if your log gets too large.
;
Summary
;
;
;
;
; These next lines allow you to modify some internal defaults.  Don't modify
; them unless you need to because you are running out of memory, and don't set
; them too low or too high because NewsToss will probably crash and burn if
; you do!  If you have problems with NewsToss aborting prematurely, check
; these lines first.
;
;
;
;
; This line specifies the maximum number of header lines you ever expect to
; see in a message.  The default is 30, which should be adequate in all but
; very unusual situations, but you can set it at anything from 20 to 32766,
; but don't set it much higher than necessary or you'll run out of memory.
; If you receive MAIL messages with a large number of header lines
; (especially "Received:" lines), you may need to tweak this upward a bit.
;
HeaderLines 30
;
;
;
;
; This line specifies the maximum number of incoming batched newsgroup and/or
; unbatched mail files that you ever expect to toss at one time (that is, in
; the same run of NewsToss).  The default is 100 which is probably FAR more
; than you'll ever encounter unless you get LOTS of mail, but this should be
; set high so as to have an adequate safety margin.  Any value from 1 to 32766
; is valid here, though I wouldn't set it any lower than about 20 under any
; circumstances if I were you!  And if you set it much over 400 or 500 you may
; run out of memory.
;
MaxFiles 100
;
;
;
;
; This line specifies the buffer size for input files.  The minimum size is
; 512 bytes, and the maximum is 32767, but for best results you should always
; use a power of 2 (e.g. 1024, 2048, 4096, etc.).  If you set this value too
; high you may run out of memory, whereas if you set it too low, you may
; increase disk thrashing.  If you comment this line out entirely, the default
; size of 2048 bytes will be used.   I strongly recommend setting this higher
; if possible (the maximum is 32767, but remember that a power of 2 is most
; efficient).
;
InBuffer 8192
;
;
;
;
; Normally, when a batched newsgroup feed is received the file contains only
; linefeeds, and no carriage returns.  However, certain MS-DOS software
; (notably certain more recent versions of KA9Q's NET.EXE program) can create
; batched newsgroup files that contain carriage returns followed by
; linefeeds.  If you receive batched newsgroup files from any source that
; contain carriage returns, uncomment the following line.  If you don't need
; it, NewsToss will operate slightly faster if you leave it commented out.
;
;KillCR
;
;
;
;
; The following line, if uncommented, inhibits the display of the Newsgroups
; line, message length, names of *.msg files that are being created, and some
; other lines that would normally be displayed during operation of the program.
;
;Quiet
;
;
;
;
; Now, some information about your system and your newsgroups and feeds:
;
;
; This is your Fidonet format address, in Zone:Net/Node.Point format (NO
; DOMAIN!).  In most installations this isn't even really necessary; it's the
; address placed in the Fidonet binary message header (as both the originating
; and destination addresses) and if it's not given, 0:0/0.0 will be used, which
; generally isn't a problem.  However, if you routinely forward messages from
; newsgroups to echomail areas, you might find that the header address is used
; in the creation of the MSGID kludge line of the echomail message (GoldED in
; particular does this, if you change the message after copying it to an
; echomail area).  To avoid that, or other unforseen problems, just put your
; system's primary Fidonet address here.  You may omit the point portion of
; the address if you're not a point.  NOTE:  Should you have need to change
; this address, don't forget that you may also need to change your address in
; the "Kludge" control file statement (further down in this file).  Also, if
; you receive unbatched MAIL messages, this address is placed in both the "from
; address" and "to address" fields of the Fidonet netmail message header (I
; told you that mail support was limited!).
;
Address 1:1234/5678.0
;
;
;
;
;
; This is your UUCP format address, as is placed in messages exported from
; your system.  In NewsToss this is used for dupe checking purposes only.
; If this address is found in the Path line, the message will be discarded as
; a duplicate.  If you don't want this form of dupe checking enabled, leave
; this line commented out.  Remember that this address must EXACTLY match your
; address, and 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 registerd name, you might use it instead, like this:
;
;Alias stjhmc.fidonet.org
;
;
;
;
;
;
; Normally, if your Alias appears in the first position of the Path line in
; a message, NewsToss will discard the message as a duplicate.  However, if
; you are using DoveMail to create the batched newsgroup packets that NewsToss
; processes, and are specifying the same Alias address in both DoveMail's and
; NewsToss' config file (as you normally would), then obviously you don't
; want to discard messages processed by DoveMail as dupes.  To avoid that,
; leave the following line uncommented.  NewsToss will still declare a
; message as a duplicate if it finds your alias somewhere OTHER THAN the
; first position in the Path line.
;
IgnoreFirst
;
;
;
;
;
; The following is the filename mask (including path) of filenames that MIGHT
; appear on your system containing newsgroups.  Note that if the file does not
; start with the characters "#! rnews", it will not be procssed in any case
; (unless it matches the "MailPattern" string, in which case it will be
; processed as incoming mail).   Note that if you are running DoveMail, this
; is the place to put the filespec for the batched newsgroup files that
; DoveMail tosses for YOUR system.  If no one pattern matches all the incoming
; files you want to process, then in your batch file move all your incoming
; files to a single holding directory, specify that directory below and use
; *.* for the filespec.  For example, I use something like this in my batch
; file:
;      dmove C:\BBS\*.PKU C:\BBS\MAILIN
;      dmove C:\FILE\NET\nbytes??.d C:\BBS\MAILIN
;      newstoss
; [DMOVE is one of a number of "move" type utilities for the PC available
; from BBS's around the world.]
; And, in the statement below, I use C:\BBS\MAILIN\*.* as the filename mask.
; For the more common case where you are just getting news, you might get by
; with something like this:
;
Infiles C:\Inbound\*.PKU
;
;
;
;
;
; The following is a path to your "Bad Messages" area.  If you define this
; area, NewsToss will toss messages here that don't get tossed to other areas
; because they are dupes, or because none of the areas listed in the
; "Newsgroups" line correspond to areas you carry.  If you just want to send
; such messages to the bit bucket, leave this line commented out.
;
BadMsg D:\Msg\Bad_Msgs
;
;
;
;
;
; When NewsToss imports a message, it takes the date and time from the
; "Date:" line and converts it to GMT (also known as UTC).  This would be the
; date and time placed in the Fidonet message header.  However, unless you
; live on the Greenwich Meridian, you'll most likely want to use the
; TimeOffset keyword to adjust the time to local time.  If you use TimeOffset
; in NewsScan.Cfg, you should also use it here and the number of minutes
; should be the same in both files.  The number following the TimeOffset
; keyword should be 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 TimeOffset commented out, the default used will be zero,
; 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 that doesn't work properly, uncomment 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.
;
TimeOffset 300
;
;
;
;
; When NewsToss is tossing a message it will take the "Subject: " line and put
; the contents of that line (after the "Subject: " tag) into the portion of
; the Fidonet message header reserved for the subject.  If the subject is too
; long to fit in this area, it will truncate it to 71 characters, and then put
; the complete "Subject: " line in the text of the message; otherwise the
; "Subject: " line will be omitted from UseNet message header lines written to
; the message TEXT.  However, you can force NewsToss to always leave the
; Subject line in the TEXT portion of the message by uncommenting the
; following line.  If you do this, you should also uncomment the corresponding
; line in NewsScan.Cfg, if you use NewsScan.  There's normally no reason to
; uncomment this line, except in certain unusual situations (such as when you
; are archiving some of your received UseNet messages to a text file, and you
; are throwing away the Fidonet message header).
;
;KeepSubject
;
;
;
;
; When NewsToss is tossing a message it will discard the UseNet "Path: " line
; unless the following line is uncommented.  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
;
;
;
;
; When NewsToss is tossing a message (particularly a mail message) it will
; discard any "Received: " lines it sees unless the following line is
; uncommented.  Generally, the "Received:" lines are not too useful, but
; they sometimes are helpful in tracking down routing problems.
;
;KeepReceived
;
;
;
;
; Most users won't need this, but you can force NewsToss to set the LOCAL bit
; in news messages it tosses (in addition to the SENT bit, which is always
; set).  Please note that this affects news messages only (use MailAttrib if
; you need to set specific bits in tossed Mail messages). If you are trying to
; convert newsgroups to echomail (or if you sometimes manually hurl messages
; from newsgroups to echomail areas), it may be necessary to uncomment this
; line, depending on the echomail processor you use.  Leave it commented out
; if you don't know why you'd need it.
;
;SetLocal
;
;
;
;
; The following line is for advanced users only, and if you don't know how to
; use it, I suggest you just use the one sample line shown below but CAREFULLY
; substitute your Fidonet address in full zone:net/node.point@domain format as
; shown below.  This statement is for inserting "IFNA Kludge Lines" at the
; start of each message written out by NewsToss (an "IFNA Kludge Line" is a
; line that is "hidden" behind a "Control-A" character, making it invisible to
; most readers of the message).  If you are not distributing newsgroups
; ALREADY CONVERTED TO ECHOMAIL beyond your system (something I don't
; recommend anyway), then just use the one line shown (it aids in duplicate
; message prevention), but insert your own address.  However, should you have
; the need to do so, you can insert up to ten such lines (although if you have
; a need for more than two or three, I have to wonder about you!).  This
; feature is NOT for inserting "vanity lines", political statements, or other
; extraneous text. It is ONLY for lines that are interpreted by
; Fidonet-technology software.  Also, it is NOT inserted in mail messages
; tossed to your netmail area.
;
Kludge PTH @Usenet 1:1234/5678.0@Fidonet
;
; Note: The spelling "PTH" is CORRECT!  See Fidonet standard FSC-0044
; *revision 2* for technical details regarding the use and construction of the
; above line.  Note also that the ".0" could (and probably should) be omitted
; if you are not a point, but otherwise the format of this line must be
; exactly as shown.
;
;
;
;
; Now some keywords that provide LIMITED support for incoming netmail.  I may
; expand this a bit in the future, but keep in mind that NewsSCAN has no
; corresponding ability to send out messages FROM your netmail area.  This
; support is designed primarily to meet the needs of leaf nodes, that is,
; nodes that do NOT pass mail on to any other node.
;
; This is what will be placed in the "from" field of the Fidonet message
; header of incoming MAIL messages:
;
MailFrom UUCP
;
;
;
;
; This is the Fidonet type address that will be placed in the "from" address
; fields of the Fidonet message header of incoming MAIL messages.  If you don't
; use this, the address from the "Address" keyword will be used.  Note that if
; you use a non-zero point address, a FMPT kludge line will be placed in the
; body of the created message.
;
MailFromAddress 1:1234/5678.0
;
;
;
;
; This is the Fidonet type address that will be placed in the "to" address
; fields of the Fidonet message header of incoming MAIL messages.  If you don't
; use this, the address from the "Address" keyword will be used.  Note that if
; you use a non-zero point address, a TOPT kludge line will be placed in the
; body of the created message.
;
MailToAddress 1:1234/5678.0
;
; NOTE: An INTL kludge line will be created in your netmail messages if the
; zones given in the above two statements are both non-zero and are not equal.
; If both zones are the same, or if either is zero (or not given) then the INTL
; kludge line will NOT be created.
;
;
;
;
; This is the attribute word that will be used in each MAIL message.  By
; placing various values here, you can mark messages as private, sent, local,
; etc.  This is for advanced users only, and I suggest that you NOT use this
; keyword unless you are familiar with the Fidonet message header attribute
; word.  However, if you need to set the "local" bit in all messages for some
; reason, you can do it by using the following:
;
; MailAttrib 256
;
;
;
;
; This is the path to your netmail area:
;
MailPath C:\MSG\NETMAIL
;
;
;
;
; This is the pattern to match at the start of each mail message.  If a file
; does not start with this pattern or "#! rnews", it will be ignored by
; NewsToss:
;
MailPattern From
;
;
;
;
; These are the valid Internet-format addresses of mail recipients at your
; site.  If an address in a "To:" line matches exactly an address shown below,
; the corresponding user name will be placed in the Fidonet message header's
; "to" field.  If no match is found, any lines beginning with "Cc:" or
; "Apparently-To:" are also checked.  If no match is found on any of these,
; the phrase "<unknown at this site>" will be placed in the Fidonet message
; header.  Note that you can use this to map any mailing lists you receive to
; unique user names, so that you can easily find messages from a mailing list.
; First, a word about how TO: line addresses are parsed:
;      To: user@site     or
;      To: Joe User of Some Site <user@site>     or
;      To: user@site (Joe User)     or
;      To: userx@sitey,user@site,userz@siteq
; Would all be parsed as user@site, assuming that user@site were listed below.
; In the final example, only the FIRST valid address would be used... that is,
; if both userx@sitey and user@site were in your list, the message would be
; addressed to the name associated with userx@sitey.
;
Begin_NameAliases
  jack                          Jack Decker
  jack@myamiga                  Jack Decker
  [e-mail]       Jack Decker
  @f8.n154.z1.fidonet.org       C
  [e-mail]     Mailing List
  [e-mail]  Navigate
End
;
; In the example above, the last two entries are mailing lists.  The entry
; just preceeding those is a special type of entry, which says to take
; whatever name you find in front of the "@" and use it as the user name.
; This is indicated by the "@" as the first non-space character on the line.
; Instead of the user name, use the letter "C" (or any word starting with a
; "C") if you want NewsToss to attempt to capitalize the name, or any
; character other than a "C" if you want NewsToss to leave the capitalization
; alone.  In the above example, if I received a message addressed to
; [e-mail], the user name "John Doe" would be placed
; in the "to" (or "john doe" if capitalization were not used).  Please note
; that the capitalization routine is not perfect and may not operate exactly
; as expected on certain names (e.g. names starting with "Mac").  Also please
; note that this does NOT attempt to extract a Fidonet address from the
; entry... in other words, if my Fidonet address were not 1:154/8, the
; message would still be addressed to "John Doe" on my system.  I may add
; some ability to gate messages for other Fidonet addresses if there are any
; requests for this capability.
;
;
;
;
; That ends the LIMITED mail support section... now back to newsgroups....
;
; 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
  comp.dcom.telecom      D:\MSG\TELECOM
  comp.dcom.modems       D:\MSG\MODEMS
  private.newsgrp        D:\MSG\PRIVATE
End
;