OS/2 Shareware BBS: 2 BBS/02-BBS.zip/gigop806.zip/OPTIONS.CFG

Text File | 1994-05-29 | 18KB | 390 lines

;  GIGO will run faster if you enable direct video, but direct screen
;  writes can cause problems with some systems, or if you are using
;  Desqview.  If you use Desqview in 50 line text mode, or if you have
;  other incompatibility, you should specify "/BIOS" on the startup line.

;  GIGO can ALSO, simply turn off video once it has initialized.
;  Your only indication that it's working will be your drive access
;  indicator (drive light, norton disklight, etc).  You may either
;  specify NOVIDEO in the config, or add /NOVIDEO to your command line.

;NOVIDEO

;  For fastest results, use /NOLOGO /NOVIDEO when starting up.

;  GIGO, by default, does not require swapping to disk.  It normally leaves
;  the DOS portion of memory available for shelling.  However, if you find
;  that you need more memory to work with, and would like to make this memory
;  available to GIGO, you should simply make sure that SHROOM.COM is in the
;  gateway directory.  GIGO's loader will automaticly load SHROOM.COM up
;  before loading the dos extender up.

;  The following are if you wish to restrict GIGO by skipping
;  the RNEWS or RMAIL processes, or by not deleting the original file.
;
;  Alternately, you may use the following commands on the command line
;  when loading GIGO to specify the actions you *DO* want....  i.e.,
;  GATEWAY SACBBX.CFG /MAIL
;  Valid command line switches:  /MAIL /NEWS /FIDO


; If you are only testing, you can specify the TEST keyword, which only
; allows GIGO to run things once; it also forces GIGO to not delete the
; .PKT files or the .D/.X files when done.  Be forwarned, causes massive
; ammounts of dupes - only use this when you are _TESTING_!  Don't forget
; to remove it.

;TEST         ; Do not delete files when done

; The TRANSLATE keyword defines the translation table from fidonet->internet,
; as 8 bit characters are a naughty thing when posting world-wide.
; This table defines how GIGO will translate the characters.  It should be
; 128 characters long, and represents the 8 bit characters only.
; Alternately, you can disable TRANSLATE, and uncomment 8BIT, and GIGO will
; perform no translation at all.  Beware, you will get flamed from all
; parts of the world if you do this without a real good reason for it.

; Note that the TRANSLATE table may not have 2 consecutive spaces, due to the
; way that GIGO converts these config files to save memory.

;
;         "ÇüéâäàåçêëèïîìÄÅÉæÆôöòûùÿÖÜ¢£¥₧ƒáíóúñѪº¿⌐¬½¼¡«»░▒▓│┤╡╢╖╕╣║╗╝╜╛┐└┴┬├─┼╞╟╚╔╩╦╠═╬╧╨╤╥╙╘╒╓╫╪┘┌█▄▌▐▀αßΓπΣσµτΦΘΩδ∞φε∩≡±≥≤⌠⌡÷≈°∙·√ⁿ²■ "
TRANSLATE "Cueaaaaceeeiiiaae%AooouuuOUc###faiounN--?++/*!<>###|++++++|+++++++++-++++++++=+++++++++++++#####abg#E###########=#####/~Oo.#n2*-"
;8BIT      ; Leaves 8 bit text alone, instead of translating..


; At the request of garux@mdtn_bbs ..  a specialty option to allow outgoing
; _email_ only to be routed to different spools, based on where it is headed.
; If you don't understand this option, don't use it.

; _Most_ sites don't need this, and the inclusion of even one of these
; statements will slow down _all_ outbound email, as it turns on the extra
; checking needed to figure out where to send things.  The routines had to
; make use of scanning the config memory every pass, and make use of regex
; routines (which are always slower processing).
;
; * Before using these, make sure you _really_ need them! *
;
;ROUTESPOOL host1  host1          ; Sends all mail to host1 directly to host1 spool
;ROUTESPOOL frackit frackit.uucp  ; same for frackit.uucp
;ROUTESPOOL frackit wfs.uucp      ; put all [e-mail] mail in frackit's spool
;ROUTESPOOL host  *.uucp          ; Sends all user@....uucp messages to "host"

; Another option, that's for kludging value only, is to generate outgoing
; spool file names with your host's name in it, instead of your name in it.
; Don't use this option unless you know WHY you need it (it will be used by
; maybe 1% of the people around..)  Anyone using this option when they are
; not supposed to has about a 99% chance of losing their mail.
;
;BACKWARDSFEED     ; If you don't need this, don't use it - it will break!

;The BURT_JUDA_HACK option is meaningless for most people.  This option
;creates email headers with "From [e-mail]  date" instead of
;"From site!user date+time remote from site".
;*If this option helps you, great.  Don't do it unless you _know_ you need
;*it though.  Burt needed it for his special smtp scripts.
;BURT_JUDA_HACK


;The XQT_FROM_UUCP option is to force the XQT files to pretend to come
;from a user named "uucp" instead of from the original user.  Only
;use this if your host is having problems with your email packets;
;most hosts can handle actual user names in the xqt packet.
;XQT_FROM_UUCP


; ALTMUNGING
; If your host is sending you names that GIGO is complaining about
; (ie, MUNGE_ERROR(....) or not finding any of your files).
; it could be that you are getting files that are not using the standard
; naming conventions that most hosts are using to send files to their
; feeds.  Uncomment the ALTMUNGING option, and GIGO will attempt an
; alternative method to locate the files in your spool directory.
; Most people will not need this option.
;ALTMUNGING


;  If your BBS or editor supports the FSC-35 specification, the FSC-35
;  command should be enabled.  This causes GIGO to add the ^aREPLY-TO and
;  ^aREPLYADDR kludges to messages.  If you are not sure if your BBS
;  supports FSC-35, leave the command in, as it will not cause a problem
;  for most BBS or editor software.  The exception is RemoteAccess, for
;  which this line should be commented out.

FSC-35            ; Always do FSC-35
;PARTIAL-35       ; Only use FSC-35 when the fidonet headers are not capable
                  ; of returning a reply correctly.

;OLDTOSSER : If you are running GIGO as a point, and your mail tosser is
;  telling you that GIGO mail bundles are from Net 65535 or Net -1,
;  enable this keyword.  (GIGO by default makes FSC-0048 compliant
;  packets, noting that NET values should be set to 65535 when dealing
;  with points.  Wierd stuff, I know..)
;
;OLDTOSSER



;  RETURNADDRESS_EMAIL <optionalname>
;  RETURNADDRESS_NEWS  <optionalname>
;  tells GIGO to use the person's email address (name@site)
;  in the From: field of a fidonet message if it is small enough to fit in.
;  If the address is too long, the person's name is used instead.
;  Commenting this verb will only import names in the From portion rather
;  than email addresses.

;  By default, a person's real name is placed in the fidonet header.

;RETURNADDRESS_EMAIL     ; Uncomment this to put the email adddress in the hdr
;RETURNADDRESS_EMAIL UUCP; Uncomment to put "UUCP" in the message hdr
;RETURNADDRESS_NEWS      ; Uncomment this to put the email address in the hdr
;RETURNADDRESS_NEWS UUCP ; Uncomment to put "UUCP" in the message hdr

;  SPLIT - split up large messages SQUISH, QMAIL, TOSSCAN, GECHO, FMAIL,
;  FASTECHO, WILDMAIL, RENEMAIL, TELEMAIL,  and 95% of the rest of the
;  tossers out there require a relatively small individual message size to
;  work smoothly.  Nearly every tosser since then has taken this example
;  and imposed a relativley small limit on fidonet messages. if you change
;  this from 15000, be sure you know everyone receiving from you will be
;  able to handle the incoming large mail you send.
;  Technote:  Splits are made using FSC-0047;  "SPLIT" and "UNSPLIT" will
;  work on splitting/unsplitting *.MSG messages with this format.  Also,
;  PKTSORT by Rolf Wilms (sp? please correct me!) has the capability
;  of re-merging these messages while still in .PKT format.

SPLIT 15000

;  MAXPKT - provide a (approx) cuttoff point per .PKT do you REALLY want to
;  toss a 3.5 meg single packet? didn't think so, one small slipup and you
;  might lose a whole day's mail. commenting this verb will generate one
;  continuous mail packet, that may become questionable in the event of an
;  emergency abort. Unlike any other currently available gateway package
;  GIGO splices USENET batches into a seamless stream of fidonet poackets,
;  without pasing between each batch. This is necessarry to keep things
;  within a reasonable managability level.

MAXPKT 150000

;  LINEBREAK - specifies the longest line length allowed to to be sent to
;  the usenet site.  Any messages that have lines that are too long will be
;  wrapped.  Not always needed, and much faster off. Suggested: 80

LINEBREAK 80

; MAXNEWSGROUPS xx tells GIGO to allow up to xx copies
; of the same message to be cross-posted.  If the message is cross-posted
; to more newsgroups than the number you specify, GIGO will publish
; only the first copies.  Default=20

MAXNEWSGROUPS 20


; Control messages are regularly sent out in the newsgroups;
; these messages control automatic wide-area message deletion, area
; creation, etc.  GIGO has the ability to intercept the delete message;
; when used in combination with the NIKE option, GIGO can completely
; automate the wide-area message deletion when moderators and users
; wish to unpost their messages.
;  Alternate, GIGO can strip Control: messages entirely, since for all
; other practical purposes, they make no sense in a Fidonet environment.

TRANSLATE_CONTROL ; says "Control: cancel" messages are translated.
DELETE_CONTROL    ; says delete all (other) "Control:" messages.

; Message threading!  Here's a nasty option.  Turn this on
; to implement some really naaaaassssytty looking MSGID kludge lines.
; When people reply to these messages, most BBS packages will
; create a "REPLY" kludge line.  When GIGO gets a REPLY
; that it recognize, it will generate the "References:" line (the internet
; equivalent).   (This _was_ "NIKE" during some beta versions)
KEEP_THREADS         ; Also known as "NIKE"




;  THE MAILER-DAEMON
;
;  GIGO has a built-in mailer-daemon that can, if allowed, handle many
;  situtations in an automatic manner.

;  The mail-daemon can:
;    o Bounce incorrently addressed netmail
;    o Bounce email that is destined to a BBS that does not exist
;    o Send back textfiles when a certain email-address is addressed
;    o Perform file-by-email requests

;  Most importantly, it will check any messages written by Fidonet users
;  who are attempting to send email.  It will verify that they have the
;  security to write the message; it will also see if it can correctly
;  figure out where the user wants to send the message.  If either case
;  turns out to be a problem, the user is sent the message back via netmail,
;  with information on why it was denied, or (better), information on how
;  to properly address the gateway.
;
;  This should be most useful for ex-Fredgate users who kept getting all
;  those messages in their lostfu directory! :-)

;
;  Another useful function of the daemon is for incomming email that is
;  meant to be turned back into netmail.  GIGO will attempt to parse the
;  email address, and determine where it should send the mail to.  If it
;  can't, GIGO has one of two options:  either A: bounce it back to the
;  internet user, or B: put it with _your_ netmail, so you can manually
;  handle it.

; KEEP_UNKNOWN   ; Uncomment this line to manually handle unknown email

;  The mail-daemon can also be set up to send back a textfile whenever
;  a specific email-address is sent mail.  A fake user is setup,
;  slightly different from normal user statements.  More discussion on
;  this is in the USER statement area.

;  USER  [e-mail]  INFO  infofile.txt

;  The mail-daemon can handle things like forwarding mail to a user's
;  new address, or it can be set up to bounce the mail back to usenet,
;  with a text file of your choice. This is also covered in the USER
;  statement area.
;  ******** NOTE: THIS ONLY WORKS FOR USENET->FIDONET EMAIL! ******

;  USER  [e-mail]  FORWARD  [e-mail]
;  USER  [e-mail]  BOUNCE   dead.txt
;  SITE  deadjoebbs           BOUNCE   deadbbs.txt



;  The mailer-daemon can also instead take all email to a specific user,
;  and save it to disk, either in a contiguos log, or as individial
;  files.  An example use for this is to have a special address for
;  uudecoded files, where you can run an external program to turn them
;  back to binaries.

;  USER  logme   LOGTEXT  logtext.log         ;saves to specified log file
;  USER  saveme  SAVETEXT C:\gateway\saveme\  ;saves to unique ########.IN

;  The mailer-daemon can also be easily expanded by you, the administrator.
;  GIGO is the first gateway to support external functions.
;
;  When used, GIGO can watch for email going to a special address.  Whenever
;  email is sent to that address, GIGO will
;    1: create FUNCTION.REQ
;    2: Run the specified program
;    3: Look for and send back FUNCTION.REP if available
;  I have successfully made a listserv processor, as well as a fax
;  gateway, both with about 10k of code.  The listserv processor + source
;  is in the main GIGO archives for you to look at and hopefully expand on.
;
;  Usage:
;   USER  requestname  FUNCTION  programname parameters



;  The mailer daemon can allow you to prevent fidonet users from
;  sending email to various addresses.  This is useful, for instance,
;  if you have a measured-rate UUCP service (or long distance charges),
;  and you don't feel like letting users request files on _your_ call.
;  BLOCKADDRESS allows you to specify a pattern for an address; if the
;  address that the user is emailing fits any of these patterns, the
;  message will be returned to him as undeliverable.
;
;  Note that this will block even YOUR attempts.  It doesn't discriminate
;  on who it blocks.
;
BLOCKADDRESS  *listserv*
BLOCKADDRESS   *fileserv*
BLOCKADDRESS   *ftpmail*
BLOCKADDRESS   *BITFTP*


;  Last, GIGO has the ability to check a nodelist index.  A seperate
;  nodelist compiler is included with GIGO, and comes with it's own docs.
;
;  If you specify the directory where NODELIST.GIG can be found, GIGO will
;  look up this nodelist index any time an email address comes in in the
;  form of user@f###.n###.z###.site.domain, or in the form of
;  user@##-##-##-##.site.domain.  If GIGO can not verify the existance of
;  that nodelist entry, GIGO will send the message back to the internet
;  user.
;
;  This option is here mainly because MsgTrack is not gateway aware, and will
;  bounce messages back to the gateway.  The gateway would in turn send a
;  message back to MsgTrack saying that it wrote the message wrong.  What
;  a mess!  If possible, please, use the NODELIST option in GIGO, to prevent
;  such a mess happening for you..
;
; NODELIST C:\NODELIST\  ; Should point to where NODELIST.GIG will be found.





;  GIGO can act as a server for FILESERV requests.  Comment the following
;  disable FILESERV access to your files.  This is a list of your file
;  requestable directories, one on each line.  You can point this to your
;  bink style okfiles catalog if you wish; magic names will be honored.
;
;  I have tried to make GIGO understand both FrontDoor style and Bink Style
;  request lists; you can list magic names and directory names with either
;  method.

FILESERV-LIST      C:\FD\FLSEARCH.CTL ; See box below
FILESERV-MAXFILES  10         ; Maximum file count per request
FILESERV-MAXBYTES  10000000   ; Maximum binary size per request
FILESERV-DEFAULT   75000      ; Default segment size for binaries
;FILESERV-FIDONET             ; Allows fidonet style people to send
                              ; messages to fileserv (NOT ALLOWED IN
                              ; FIDONET!  IT'S CONSIDERED FILE ROUTING!)
;FILESERV-ATTACH               ; If you want to allow file attachments
;FILESERV-INBOUND c:\fd\files\ ; Your fidonet inbound directory
;FILESERV-HOLD    c:\fd\hold\  ; Where to move files that were attached
; See the NOTES file re: file attachments for more detailed information.


;┌────────────────────────────────────────┐
;│The format of this file is as follows:  │
;│                                        │
;│MAGICNAME   C:\path\realname.ext        │
;│@MAGICNAME  C:\path\realname.ext        │
;│@GIGO       C:\pub\ufgate\gigo1129.zip  │
;│                                        │
;│C:\PUB\DIRECTORY\                       │
;│C:\PUB\DIRECTORY\*.*                    │
;│C:\PUB\UFGATE\*.*                       │
;└────────────────────────────────────────┘




; The following command allows for "fast return" of mail that is addressed
; to the internet, but is actually supposed to be processed by your system.
; In these cases, the gateway will generate _incomming_ bundles instead of
; outgoing bundles, making the messages never even leave your system.
; Best use for this is "fidonet.org" addresses, since we are not allowed
; to send from fidonet, to fidonet, via the internet backbone (as part of
; our charter to get .fidonet.org).

; Note, to force compliance with this charter, "fidonet.org" is a forced issue
; with GIGO.  If you do not want GIGO to FASTRETURN anything for fidonet.org,
; contact me.  I will only grant the key to disable this function to very
; special circumstances that do not violate fidonet.org's charter.
; An example of this exception would be if you are the gateway for a
; different (and registered) organization, ie rbbsnet.org, where it _is_
; desirable to be able to email someone@*.fidonet.org ..

FASTRETURN fidonet.org
FASTRETURN myspecialnetwork.org

; IGNORE_CHARTER xxxx       ; If you do NOT want fidonet.org put into the
;                           ; FASTRETURN statements automaticly, you must
;                           ; get a special key, simply email me with a
;                           ; good reason why.  Mostly, this is for people
;                           ; gating networks other than fidonet.
;                           ; The key itself is free, so long as the
;                           ; circumstances do not violate the fidonet.org
;                           ; charter.