home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Current Shareware 1994 January
/
SHAR194.ISO
/
email
/
dove0793.zip
/
DOVEMAIL.CFG
< prev
next >
Wrap
Text File
|
1993-04-08
|
14KB
|
314 lines
; Sample DoveMail.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: The MaxGroups keyword is no longer needed nor supported in this file.
;
; NOTE: Please keep statements in the order shown... in most cases it doesn't
; matter but in a few cases it does, so be safe and don't move things around!
; You may remove comment lines, however.
;
;
;
;
; The first lines deal with your log file. If you use a Binkley/Opus/Maximus
; format log file, and would like DoveMail 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, DoveMail 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. In DoveMail this only affects
; the month name as placed in the log file, and is irrelevent if you aren't
; using a log (note that this is NOT the case for some of the other programs
; included in the DoveMail distribution archive). PLEASE NOTE: The string
; must be EXACTLY 36 characters long and must contain no spaces, or it will be
; rejected! I suggest you leave this commented out unless you REALLY need it.
;
; MonthString JanFebMarAprMayJunJulAugSepOctNovDec
;
;
;
;
; 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 DoveMail will probably crash and burn if
; you do! If you have problems with DoveMail 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.
;
HeaderLines 30
;
;
;
;
; This line specifies the maximum number of incoming batched newsgroup files
; you ever expect to process at one time (that is, in the same run of
; DoveMail). The default is 100 which is probably FAR more than you'll ever
; encounter, 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 200 or 300 you may run out of memory.
;
MaxFiles 100
;
;
;
;
; This line specifies the buffer size for output 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, particularly if you are sending feeds to many
; nodes. If you set it too low, you may increase disk thrashing. If you
; comment this line out entirely, the default size of 512 bytes will be used.
;
OutBuffer 4096
;
;
;
;
; This line specifies the buffer size for input files. The same limitations
; apply as for output files, but since there will only be one input file open
; at any time, you can afford to make this buffer larger (but, as with output
; file buffers, you should always use a power of 2). The default input
; buffer length is 2048, but I strongly recommend setting it 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, DoveMail will operate slightly faster if you leave it commented out.
; Please note that DoveMail will never CREATE a batched newsgroup file with
; carriage returns; this keyword just gives it the ability to process
; incoming batched newsgroup files that may contain carriage returns.
;
;KillCR
;
;
;
;
; The following line, if uncommented, inhibits the display of the Newsgroups
; line, message length, 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 address in Zone:Net/Node[.Point]@Domain format
;
Address 1:154/8@fidonet
;
;
;
;
; This is your UUCP format address, which will be added to the start of the
; Path line of all messages processed by DoveMail. If you don't have a
; registed UUCP sitename but are in Fidonet, use the [p#.]f#.n#.z#.fidonet.org
; format, like this:
;
Alias f8.n154.z1.fidonet.org
;
; If you have a registerd name, 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, DoveMail will discard the message as a duplicate. However, if
; you are using the NewsScan progam and are specifying the same Alias address
; in NewsScan's config file (as you normally would), then obviously you don't
; want to discard messages created by that program as dupes. To avoid that,
; leave the following line uncommented. DoveMail will still declare a
; message as a duplicate if it finds your alias somewhere OTHER THAN the
; first position in the Path line, and in any case, it will not send the
; message back out to you (i.e., put it in the packet it creates for NewsToss)
; if your alias is found in the Path line. PLEASE NOTE: If you use the -I
; argument on the command line when invoking DoveMail, then the state of the
; "IgnoreFirst" flag will "toggle" to the opposite of how you have it below.
; So, for example, you could leave "IgnoreFirst" uncommented and then use
; -I when you DO want to look at the first alias in the PATH line. This
; feature is provided so that you can ignore the first address when processing
; batched newsgroup files created by NewsScan, but not when processing incoming
; news from other nodes (to do this, leave the line below uncommented, and use
; the -I command line argument only when processing incoming news from other
; nodes, and NOT when processing news created by NewsScan).
;
IgnoreFirst
;
;
;
;
;
; The following 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.
; CAUTION! If you receive files from MORE than one node and some of the files
; have different filename patterns, you'll either have to move everything to
; a specific subdirectory set aside for the purpose and use *.*, or else use
; the DOS REN (rename) command in your batch file to rename the "oddball"
; files to match the specification you use here. I'm giving more than one
; example on this one because it's so important to get it right (but you must
; have ONE and ONLY ONE such line uncommented in your config file):
;
; Infiles C:\Newsin\*.*
; Infiles C:\inbound\fps????.d
Infiles C:\BBS\*.PKU
;
; Note in the above example that if you received files matching BOTH the
; patterns "*.PKU" and "fps????.d", you could either move all such files to
; the "C:\Newsin" directory and uncomment the first example, OR you could
; possibly use the DOS command REN fps????.d *.PKU in your batch file just
; prior to running DoveMail (if all such files are in the same subdirectory).
;
;
;
;
; This is the path to the Outbound directory for Fidonet mail for YOUR zone
; and domain:
;
Outbound C:\Opus\Outbound
;
;
;
;
; Normally, uncompressed outgoing mail will be placed into the appropriate
; outbound area in files with the extension ".UUT" (it's similar to an ".OUT"
; mail packet except it's in UseNet format). If you'd rather use a different
; extension, you can specify it here (but PLEASE NOTE that the same extension
; will be used for all mail to Fidonet nodes). You probably should not change
; this unless you know exactly what you are doing.
;
;PktExt .U
;
;
;
;
; Use this verb if you are running an unzoned system (this will cause all
; outgoing files to be placed in your primary outbound directory, regardless
; of the destination zone). This command is primarily included for those
; running an unzoned system that still like to specify the zone numbers in
; addresses, for whatever reason, since simply omitting the zone number will
; have the same effect.
;
NoZones
;
;
;
;
; These are the nodes you receive mail from and send it to. Up to 32 nodes
; may be specified. For each node, you need their address as it will appear
; in the PATH line on messages you receive, followed by their Fidonet address
; in Zone:Net/Node[.Point]@Domain format -OR- a filename mask preceeded by a
; "+". If you use a Fidonet address, a mail packet will be generated in the
; proper outbound directory using the filespec [net][node].uut, where [net]
; and [node] are four digit hexadecimal values (which your mail packer should
; change to a file with the extension ".pku"). A .uut file is treated like an
; .out file for Fidonet format mail except that it contains messages in UseNet
; format. Note that if you specify a point address, or a Fidonet-technology
; domain other than your own, the file will be created in the appropriate
; domain directory and/or ".PNT" directory as used by BinkleyTerm, so if you
; don't use domain support then don't give the domain, and if you have points
; but still use a fake pointnet you should give the fakenet/point address. If
; you specify a filename mask using the "+" format, then contiguous question
; marks in the filename will be changed to a random numeric value. For
; example, "+C:\uout\fps????.d" would be translated to C:\uout\FPSnnnn.D where
; nnnn is a random four digit number. NOTE: It is VERY important that the
; UseNet-format addresses EXACTLY match what you see on the PATH lines of
; messages originating from these systems, since this is the only method of
; dupe prevention used in this version. If you are not sure what address will
; appear on the PATH line, don't turn any newsgroups on to the system in
; question until you are sure. This version does NOT make use of the
; Message-ID lines for dupe prevention, though a future version might (if
; anyone has a good QuickBASIC routine for hashing a variable-length text line
; down to a long integer, I'd love to see it...)
; NEW! If you put a right angle bracket at the start of the address (with NO
; spaces after the angle bracket, e.g. >your.address), that node will get ALL
; messages that you receive in ANY of the newsgroups you carry (that is, in
; any of the groups listed under "Begin_Newsgroups") without you having to
; explicitly list that node as receiving each newsgroup! Also, if you put an
; At sign (@) at the start of the address (with NO spaces after the at sign),
; that node will get any messages that come in with NO newsgroups that appear
; to match any of the ones you have listed under "Begin_Newsgroups" (normally
; these should not be coming in, and the default is to delete them, but you
; can explicitly pass them on to nodes with the @ sign at the start of the
; node's alias). Both the ">" and "@" symbols can be used for the same node
; if desired (see examples below).
;
Begin_Newsnodes
f600.n154.z1.fidonet.org 1:154/600
stjhmc.fidonet.org 1:114/15
fps.mcw.edu 1:1999/1
test.test.test 1:1999/2
>all.known.groups 1:1999/3
@unknown.areas.node 1:1999/4
>@all.known.and.unknown 1:1999/5
End
;
; In the above lines, you can also specify a filename mask instead of a
; net/node number, like this:
;
;my.feed.wherever +C:\UOUT\fps????.d
;
; DON'T put blank lines, comment lines, or indented lines between the
; "Begin_Newsnodes" and "End" lines!
;
;
;
;
; These are the actual newsgroup names, followed (on succeeding indented
; lines) by the nodes to send them to using the UseNet format address. An
; indented line (space or tab at start of line) is considered to contain a
; node address to send the area to. Note that the node MUST have been
; specified above or it will be ignored (this allows temporarily shutting off
; a feed without removing every reference to it!). Also note that you can
; create a feed for your own system by setting up a "dummy" node (and
; specifying a filename rather than a node address under "Newsnodes"). The
; maximum allowable length for a newsgroup name is 64 characters, and you may
; use the characters ".all" at the end of a newsgroup name as a "wildcard",
; but doing so may slow down message processing considerably (a much faster
; search algorithm is used if no newsgroup names end in ".all"). Don't put
; blank or comment lines between "Begin_Newsgroups" and "End".
;
Begin_Newsgroups
comp.dcom.telecom
f600.n154.z1.fidonet.org
stjhmc.fidonet.org
news.groups
f600.n154.z1.fidonet.org
fps.mcw.edu
comp.sys.amiga.hardware
f600.n154.z1.fidonet.org
comp.sys.amiga.misc
stjhmc.fidonet.org
comp.sys.amiga.all
test.test.test
End