home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 2 BBS
/
02-BBS.zip
/
gigp1106.zip
/
users.cfg
< prev
Wrap
Text File
|
1994-05-31
|
13KB
|
274 lines
;
KEEPUNKNOWN ; Same as defining both KEEPUNKNOWNUSERS and KEEPUNKNOWNSITES
KEEPUNKNOWNUSERS ; Keeps messages to users on the LOCAL system that are not explicity defined
KEEPUNKNOWNSITES ; Keeps messages to other systems that are not yet defined,
; so that you can manually forward/bounce/etc via netmail
; MAPSTYLE - Mapping style for default outbound email. Gigo supports
; practically any style of generating addresses now, as it is completely
; definable by you, the admin.
; If the message is being launched from the gateway itself, then no
; "othersite" should be evident in the outbound headers. See "SITE local"
; command below.
; EDIT THIS TO MATCH __YOUR__ SITE
;
; *user translates to the current user.name
; *site translates to the current SITE parameter
; *mysite translates to the current MYSITE variable
; *domain translates to the current DOMAIN variable
; *myfeed translates to the current MYFEED variable
; *fnz translates to .f##.n##.z## (ie, *user@*fnz.fidonet.org)
; *ftn translates to ##-##-##-## (may have fewer #'s; this
; variable is an alternative to *fnz, using fewer periods
; and (usually) a shorter string. The number of ##'s will
; vary from 1 to 4 (ie, 203-7707 is enough to say net 203,
; node 7707, in my zone).
;
;
; You MUST define MAPSTYLELOCAL and MAPSTYLESITE; MAPSTYLEUNDEF is optional,
; and defaults to a standard fidonet style address.
;
; You may use any of the above variables; most importantly, *user
; and *site. Anything else can be filled in by you with specific
; text, and may use the above variables if you wish.
MAPSTYLELOCAL *user@*mysite.*domain ; Used with SITE LOCAL statements
MAPSTYLESITE *user@*site.*mysite.*domain ; Used with other SITE statements
MAPSTYLEUNDEF *user@*fnz.fidonet.org ; Used when no SITE statement or bounced site
; Other examples:
; MAPSTYLELOCAL *user@wmeonlin.sacbbx.com
; MAPSTYLESITE *user@*site.wmeonlin.sacbbx.com
;
; MAPSTYLELOCAL vogon1!frackit!mdtn_bbs!*user@psuvax.psu.edu
; MAPSTYLESITE vogon1!frackit!mdtn_bbs!*site!*user@psuvax.psu.edu
; Here's the guts of the name and account translations done by the gateway.
; There are _several_ different ways of handling USER and SITE statements;
; my attempts at expressing documentation are poor, so instead we will have
; examples of everything.
; Remember that this example config file is for "swizzle.com".
; Individual accounts on your system are specified, with
; who their owner is and what their fidonet address is.
; They will appear as "account@swizzle.com"
USER richard.bollar 1:125/110 Richard Bollar
USER bollar 1:125/110 Richard Bollar
USER root 1:125/110 Richard Bollar
USER postmaster 1:125/110 Richard Bollar
USER sysop 1:125/110 Richard Bollar
USER d.j.hannah 1:125/110 D.J. Hannah
; The following two examples are where the person does not exist on your
; BBS or gateway, but instead somewhere else. You need to specify the
; entire address, __even_if_you_have_a_SITE_for_them_!. GIGO takes the
; USER statements as priority over SITE statements.
USER jdoe@somebbs.swizzle.com 1:125/1234.0 John Doe
; If someone starts abusing the gateawy, you can block them out.
; Note that the "bounce" statement is on the left hand side this time.
; When the gateway tries to create this user's email address, it will see
; that their account says "bounce", and will send them back a nasty-gram(tm).
USER bounce 1:2/3.4 User Name
USER bounce 1:203/7707.1 Twit
; GIGO has a built-in mail-daemon that can perform various functions,
; such as send back a text file when triggered, or bounce mail back
; to the sender, or even forward the mail from one address to another.
USER info@swizzle.com INFO infofile.txt ; Sends INFOFILE.TXT whenever
; someone sends email to
; info@swizzle.com
USER dead2@swizzle.com BOUNCE ; Bounces with generic message
USER dead@swizzle.com BOUNCE deaduser.txt ; Bounces the message back
; with the "deaduser.txt" file
SITE deadbbs BOUNCE deadbbs.txt ; Bounces messages to all users
; @deadbbs.swizzle.com, and
; sends the "deadbbs.txt" file
USER jfesler FORWARD jfesler@wmeonlin.sacbbx.com ; Forwards to the real address
; If you wish to capture the messages to a specific address, and have them
; saved to a text file (or appended to a log file), you can use the USER
; statements as such..
USER incoming SAVETEXT C:\incoming\ ; Saves as C:\incoming\*.in
USER logme LOGTEXT incoming.log ; Appends to incoming.log
; If you are willing to make your own hacks, interfacing with GIGO is easy.
; GIGO supports function requests triggered upon email to a given user.
; GIGO saves the entire message as FUNCTION.REQ, and runs your program
; or batch file. Upon return, if a file called FUNCTION.REP exists,
; it will be sent back to the party to sent you the email.
; Samples:
; USER dir FUNCTION dir c:\*.* /s >function.rep
; USER listserv FUNCTION listserv.exe
; USER gigo-request FUNCTION listserv.exe s gigo
; USER kaboing FUNCTION copy function.req function.rep
; The mail-daemon can even attempt to catch fidonet-style names
; and give them email addresses. For example, if someone sends a message
; to "Sysop" at your gateway's address, you can have it sent to
; your main account instead.
; (My appologies to M.Butler for stealing this verb's name from FredGate)
; The usage may/may not be the same as FredGate's; since I don't have
; FredGate, I don't know for sure.
; *******NOTE: THIS ONLY AFFECTS FIDONET->USENET MAIL!!!!**********
; Format: MAPUF internet-account Real Name
;
; The internet account _must_ be the _full_ internet account name, even
; if it is going to your own gateway.
MAPUF root@swizzle.com Sysop ; Mail sent to "sysop" is forward to root@swizzle.com
MAPUF jfesler@wmeonlin.sacbbx.com Jason Fesler ; Mail sent to "Jason Fesler" is forwarded to..
MAPUF bugs@wmeonlin.sacbbx.com Bugs
MAPUF jfesler@wmeonlin.sacbbx.com Author
; Ever get twits sending areafix messages to the gateway? Try this..
MAPUF areafix@swizzle.com Areafix ; Turns it to a valid address
USER areafix@swizzle.com BOUNCE wrongadr.txt ; and then the daemon can catch
; it, and send the user back a
; Some mail packers will pack file attach messages from Arcmail to the
; gateway. While I don't have a way to stop this from happening, you
; _can_ add these into your config:
USER arcmail foward null ; Any bounced messages back to Arcmail are disposed of.
; Whew! That's a lot you can do with mostly USER statements!
; Now, you've got this great gateway program setup, and you'd like to
; allow some/most/everyone access to using the gateway. However, you
; don't feel like manually putting everybody in... That gets to be VERY
; tedious.
; The SITE statements allow you to handle entire BBS's at a time,
; by defining them as a feed off of you (at least, as far as the internet
; is concerned). Or, it will allow you to generate the "standard"
; fidonet style addresses (for example, jason.fesler@f7707.n203.z1.fidonet.org)
; Alternately, you can deny access for specific sites altogether.
;
; Most important, you have to tell the gateway what YOUR address(s) are.
; They are not always the same as you had them defined at the top of the
; config file, and sometimes you may have more than one address (multiline
; hubs, etc).
; The SITE LOCAL <fido-address> command tells the gateway that if someone
; on your BBS posts a message, but they do not have a specific account name
; setup, then GIGO should create an address like "user.name@swizzle.com"
; or "user.name@yoursite.domain". (Uses MAPSTYLELOCAL template to define)
SITE LOCAL 1:125/110
; For the author, who runs a two-line system, the following is appropriate.
; All of his fidonet addresses are considered to be the "local" bbs.
; SITE LOCAL 1:203/7707
; SITE LOCAL 1:203/8055
; SITE LOCAL 1:1/141
; Now, you can define the BBS's that are local to you. Email addresses
; that are generate automaticly will look like
; "user.name@bbsname.yoursite.domain" (or something similiar, depending
; on how you configured MAPSTYLESITE). All of the users for a given BBS
; are defined at once with the single statement.
;
; Note that if the user has a USER statement in this config file, that will
; take priority, and the SITE statements will not even be looked at.
SITE joesbbs 1:125/1 ; user.name@joesbbs.swizzle.com
SITE nc 1:125/0 ; user.name@nc.swizzle.com
SITE mypoint 1:125/110.1 ; user.name@mypoint.swizzle.com
SITE somewhr 1:125/120 ; user.name@somewhr.swizzle.com
; You can deny a BBS by giving it the name "bounce".
SITE bounce 1:203/7707.1 ; This stops Jason Fesler's point address.
SITE bounce 1:125/9999 ; This stops "test" nodes using 1:125/9999
; If you wish to be a public gateway for your local area, but you can not
; get approval (or don't wish to) to become part of the .fidonet.org
; distribution people (those are the ones that are allowed to fly the
; GUUCP flag in the nodelist), GIGO has an option for you.
; SITE GATEWAY <fidonet-wildcard-address>
; This option will generate email messages that automaticly use YOUR site's
; address, with a numeric "bbs name" that the gateway can understand. This
; forces any return mail going back to that user to go via your gateway,
; which is (probably) faster than using the "standard" fidonet address.
SITE gateway 1:125/*.* ; Either of these statements are equivalent
;SITE *ftn 1:125/*.* ; (and in fact, SITE GATEWAY translates to *ftn)
; With this statement, if Joe Blow at 1:125/1234 posts a message, his
; email address will be Joe.Blow@1234.swizzle.com.
; If Joe Blow posts from 1:125/1234.5, then his email address will be
; Joe.Blow@125-1234-5.swizzle.com .
; It looks confusing, but it's simpler than it looks. The gateway includes
; just enough information in the numeric portion of the address to figure
; out where to send it back to if it needs to.
; Nodes in your net: user.name@<node>.swizzle.com
; Nodes outside....: user.name@<net>-<node>.swizzle.com
; Points : user.name@<net>-<node>-<point>.swizzle.com
; Outsize your zone: user.name@<zone>-<net>-<node>-<point>.swizzle.com
;
; You may specify multiple SITE GATEWAY .. statements if you wish to
; use this addressing style for more than one group of people.
; The Net 203 Gateway (wmeonlin.sacbbx.com) uses this format for
; the entire Northern California (USA) region, since I can deliver the mail
; faster than using the "standard" fidonet address.
; The next statement is to allow gating, but using the "standard" fidonet
; address. Use this for people that are outside of the area that you are
; normally willing to gate for.
;
; Note that we can specify the actual .fidonet.org name, or specify
; an alternate name ( rbbsnet.org ? etc ). Note that the SITE fidonet keyword
; implies the fidonet STYLE that has been used for many years...
SITE fidonet 1:*/*.* fidonet.org ; can also use SITE *user@*fnz.fidonet.org 1:*/*
SITE fidonet 2:*/*.* fidonet.org ; can also use SITE *user@*fnz.fidonet.org 2:*/*
SITE fidonet 3:*/*.* fidonet.org ; can also use SITE *user@*fnz.fidonet.org 3:*/*
SITE fidonet 4:*/*.* fidonet.org ; can also use SITE *user@*fnz.fidonet.org 4:*/*
SITE fidonet 5:*/*.* fidonet.org ; can also use SITE *user@*fnz.fidonet.org 5:*/*
SITE fidonet 6:*/*.* fidonet.org ; can also use SITE *user@*fnz.fidonet.org 6:*/*
SITE fidonet 8:*/*.* special.org ; can also use SITE *user@*fnz.special.org 6:*/*
; Last, but not least, the final statement. This is to bounce any
; remaining addresses, telling them that they are not authorizid
; to use the gateway. I only move mail for FidoNet; no other zones are
; allowed to go through me, as I can not guarantee that their mail can
; be returned back to them if needed.
SITE bounce *:*/*.* ; This declines allowing anyone else from sending
; email through your gateway. If they attempt,
; or if they post in a newsgroup (not protected
; by this security!) the MAPSTYLEUNDEF will be
; used to generate a temporary address for them.