home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Amiga Elysian Archive
/
AmigaElysianArchive.iso
/
comm
/
wizfix.lha
/
AF.Cfg
next >
Wrap
Text File
|
1993-07-05
|
6KB
|
163 lines
; **********************************************************
; My AreaFix. :-)
; **********************************************************
;
; Keywords not yet supported are commented out (they'll be parsed by my
; AreaFix, but not acted upon).
;
; Tag this on the END of your Fido.Cfg - I don't know whether it'll work
; at the front end yet!
;
[AreaFix] ;My pvt area!
; Hmm, what's this do I wonder..
;
LOGFILE LOGS:AreaFix.Log
; Specify whether to use the TrapList passwords or not (I use the same
; passwords for AreaFix as for mail-sessions, but you don't have to..).
;
; This keyword MUST come before any passwords are declared in this section
; of the configuration file (else the passwords will be ignored - assumed
; to be TrapList passwords which you don't want)!
;
USETRAPLISTPW
; I use SKYTICK as it's *FREE* :-) Thanks Luca - you're a gent!!
;SKYTICK MAIL:Tick.Cfg
;FTICK ;Uncomment this if you use Foozle Tick instead
; Specify any other password here. Same format as per TrapList (of
; course!)
;
password "hidden" 1:234/567 39:876/543 2:123/456.7
password "guess" 39:999/999.999 40:40/40.40 ;etc..
;Ignore this please - it's not yet implemented.
;ALLOWCREATE 39:133/1 AUTOADD 39:136/1 39:133/1 39:138/1 39:135/1 DIR MAIL:Mail/Amiganet/
; A help file to be sent when requested:
;
HELPFILE MAIL:WiZFix.hlp
; And some echo lists (a formatted list, with descriptions maybe?)
; HOSTLIST is my list and HUBLIST is my feeds list. Note that a
; Request from a ZONE 2 address gets the ZONE 2 list etc.
; HUBPASSWORD is needed for forwarded requests that you may allow.
;
; Specify '*' if you have no file to send/search. See docs for detailed
; description..
;
; The format of this option is as follows:
;
; ZONE HOSTLIST HUBLIST HUBADDRESS HUBPASSWORD
;
ZONE 2 MAIL:Fidonet.txt MAIL:HubFido.txt 2:255/1 MAGIC
ZONE 1 * * 2:255/1 MAGIC
ZONE 39 MAIL:Amiganet.txt MAIL:HubAmiga.txt 39:138/1 MORE_MAGIC
ZONE 40 MAIL:Amiganet.txt MAIL:HubAmiga.txt 39:138/1 MORE_MAGIC
ZONE 41 MAIL:Amiganet.txt MAIL:HubAmiga.txt 39:138/1 MORE_MAGIC
; Can points forward requests for new echoes? (prefix with 'NO' as req.)
ALLOWFORWARDINGPOINTS ;Yes
; How about Nodes? (prefix with 'NO' as req.)
NOALLOWFORWARDINGNODES ;No. :-)
; The default security level - unless otherwise listed below (see LEVEL)
; any PASSWORD PROTECTED AreaFix netmail will assume a level of
; <DEFAULTLEVEL> and will be able to link into any Echomail conference
; unless the conference itself has a higher access level.
; Must be greater than zero - suggested level is 100, giving plenty of
; scope. This is a 32 bit integer, so the number can be stupidly large if
; you so desire. :-)
;
DEFAULTLEVEL 100
; Some privileged/dork users - set their access accordingly:
; You can use these parameters if you want to BAN a user on an
; otherwise UNSECURE system (complicated I know, but configurable too!! :-)
;
; These statements MUST come after a nodes password has been defined using
; the 'password' keyword (either in TrapList's or this config area).
;
; Note: a [Q] means send them an ECHOLIST via the CLI option 'ECHOLIST'
; A [-] means don't do so (wait for them to ASK). Handy for a weekly
; list to points maybe? :-)
;
LEVEL 2:250/320 500 [-] ;etc.
LEVEL 2:253/404 65535 [-] ;Trustworthy
LEVEL 2:255/58 500 [-]
LEVEL 2:255/171.33 500 [Q] ;Increased access for this point.
LEVEL 39:138/1 65535 [-]
LEVEL 39:138/14 500 [-]
LEVEL 39:133/1 500 [-]
LEVEL 39:135/1 500 [-]
LEVEL 39:136/1.8 500 [Q]
LEVEL 39:136/1.35 050 [Q]
LEVEL 39:136/1.999 000 [Q] ;Bozo - unwelcome here ;)
; Now we come to set the access of echoes. Note that they are all ASSUMED
; to be <DEFAULTLEVEL> unless specified below - you need to specify
; restricted areas AND those that can be granted to anyone (even if they
; don't have an AreaFix password - see (NO)SECURE).
; The assumed <DEFAULTLEVEL> means that any password protected
; points/nodes that call can link in/out of any area. Thus you only need
; to protect restricted areas, and de-protect public ones.
;
; Numbers can range from 0-2^32 (i.e. 0-4294967295 ;-)
;
ECHOLEVEL BAD 9999999 ; Hardly anyone (silly numbers..). :-)
echolevel dice 0 ; Anyone can have this.
ECHOLEVEL 255_SYSOP 65535 ; SysOps only
ECHOLEVEL SYSOP_AMY 65535 ; Ditto.
ECHOLEVEL ANNOUNCE 60 ; All but 136/1.35
ECHOLEVEL ANDROMEDA 10 ; etc.
ECHOLEVEL R13HOST 965535 ; Not many get to see this..
ECHOLEVEL P-WARE_BETA 500 ; Get it yet? :-)
echolevel xenolink_SYSOP 1000 ; NOT case sensitive BTW!
ECHOLEVEL Z39_AMY 65535
; Do we insist on a matching password for each session? This is often
; a real pain, as sometimes I'd be quite happy to let any node link into
; a public echo that I'm hosting, so it's nice to let them send a msg
; to AreaFix and not get it bounced coz I hadn't setup a password etc.
; So, you can use the NOSECURE keyword - this lets ANYONE link into
; ANY area that's got an access level BELOW the <DEFAULTLEVEL>; note that
; you can still keep village-idiots out by assigning them a LEVEL even
; lower than <DEFAULTLEVEL>. You can also prevent some asshole from
; linking into say 'normal' fidonet etc. areas. Use with care though!!
; Default is SECURE
;
NOSECURE ;Anyone can link into DICE, ANNOUNCE and ANDROMEDA
;(See above).
; Who can RESCAN an area? Again, if you set a user (even a node/points)
; LEVEL to less than this RESCANLEVEL then they can't rescan. Please
; note that this means if someone links into an echo that your hosting
; using the NOSECURE method then they cannot order a rescan (I figured
; that this was the safe way to go?).
;
; Sorry, not yet implemented
;RESCANLEVEL 100 ;Any node/point that I know about, no-one else!
; But restrict the No. of messages that can be rescanned from
; the following listed areas (all other areas can be fully rescanned):
;
; Ditto - not yet implemented
;RESCANPROTECT BIG_ECHO 100 ; 100 msgs per rescan max.
;RESCANPROTECT HUGE_ECHO 100 ; etc.