home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
High Voltage Shareware
/
high1.zip
/
high1
/
DIR4
/
XMAIL100.ZIP
/
COMPLETE.CFG
< prev
next >
Wrap
Text File
|
1993-12-07
|
24KB
|
653 lines
;***************************************************************************
; xMail 1.00 Sample Configfile XMAIL.CFG
; This config file includes all possible config statements you can use
; with xMail. You may not need all them but please read this file to be
; able to see what powerful features xMail offers.
; For better performance you may remove the comment lines.
;***************************************************************************
;***************************************************************************
; SYSOP
; The Name of the Sysop. This name must be exactly the name your
; registration key has been created for !!!
Sysop Roger Kirchhoff
;***************************************************************************
; FILES
; The directory where incoming files are located, usually your
; mailer's inbound directory.
;
; Attention ! Very important !
; This directory and the directories for the INPACKET, OUTPACKET,
; OUTBOUND, NETOUTBOUND, MAILERPATH, MESSAGEBASE and NETMAIL
; parameters MAY NOT BE THE SAME (!!!) and may not be used by other
; programs !!! You have to declare seperate directories for all of
; them, otherwise you will have some very strange results...
Files E:\FILES
;***************************************************************************
; SECUREINBOUND
; Defines a directory from which xMail imports every mail packet
; without any security check. Use this if your mailer supports a
; secure inbound directory.
; SecureInbound E:\SECURE
;***************************************************************************
; INPACKET
; The directory where xMail can temporarely store your inbound
; mail packets.
;
InPacket E:\XM\INP
;***************************************************************************
; OUTPACKET
; The directory where xMail can temporarely store your outbound
; mail packets. You can speed up xMail if you let this point to
; a RAM disk!
OutPacket E:\XM\OUTP
;***************************************************************************
; OUTBOUND
; The directoy where xMail will store outgoing echomail
; arcmail packets.
Outbound E:\XM\OUTBOUND
; For Binkley the zone outbound directories are created
; automatically by xMail in the form
; E:\XM\OUTBOUND.xxx (001, 002 etc; Zone nr. in hex)
; in the subdirectory E:\XM (in this example).
;***************************************************************************
; FTSCOUTBOUND
; The directoy where xMail will store outgoing FTSC comp. echomail
; arcmail packets (if you use 'Use FTSC packet names').
FtscOutbound E:\XM\FTSCOUTB
;***************************************************************************
; NETOUTBOUND
; The directory where xMail stores packed netmail if you use the
; PACK option (FrontDoor only).
NetOutbound E:\XM\NETOUT
;***************************************************************************
; MESSAGEBASE
; Path to your QBBS style message files.
MessageBase E:\RA\MSGBASE
;***************************************************************************
; MSGBASE
; Defines where new *.MSG areas are created
MsgBase E:\MAIL
;***************************************************************************
; SQUISHBASE
; SquishBase defines where new squish areas are created.
; SquishBase E:\XM\SQUISH
;***************************************************************************
; JAMBASE
; JamBase defines where new JAM areas are created.
; SquishBase E:\XM\SQUISH
;***************************************************************************
; NETMAIL
; Your *.MSG style netmail directory.
Netmail E:\MAIL
;***************************************************************************
; KILLNETMAIL
; If 'ON', xMail will delete imported netmails after import to
; the messagebase
KillNetmail OFF
;***************************************************************************
; MAILER
; This can be FRONTDOOR, BINKLEY or DBridge.
Mailer FRONTDOOR
;***************************************************************************
; MAILERPATH
; Your mailer directory.
MailerPath E:\FD
;***************************************************************************
; NODEADR
; Your 4-D node address
NodeAdr 2:245/4.0
;***************************************************************************
; AKA
; You can define an unlimited number of AKA adresses !
; It is NOT neccessary to define your pointnet as an AKA.
; If you don't want your AKA to be added to the SEEN-BY line just
; add a '#' before the address.
Aka 21:100/59
Aka 66:490/0
; Aka #2:245/5
;***************************************************************************
; POINTNET
; If you have points that cannot handle 4-D adressing PointNet is
; your fakenet address.
PointNet 25004
;***************************************************************************
; DELETEFILE ON
; ON/OFF If ON xMail will delete incoming packets after Import,
; otherwise they will be marked with a '~' in the file extension.
DeleteFile OFF
;***************************************************************************
; LOGFILE
; Path and Name of xMail's main logfile.
Logfile E:\XM\XMAIL.LOG
;***************************************************************************
; AREAFIXLOG
; Logfile for Areafix requests
AreafixLog E:\FD\XMAIL.LOG
;***************************************************************************
; STATLOG
; Logfile for statistical information about the number of mails that
; flow through your system.
StatLog E:\FD\XMAIL.LOG
;***************************************************************************
; AREAFIXNAME
; You may define new names for Areafix and Filefix. Both will process
; every message which is addressed to one of these names.
AreafixName AREAFIX,AREAMGR,ECHOMGR,SQAFIX,POINTMGR,ECHOFIX
;***************************************************************************
; EXTERNNAME
; xMail usually sets the 'received' bit on every received netmail.
; Some external utilities require the 'received' bit NOT to be set, so
; you can define an unlimited number of 'EXTERNNAME'. If xMail finds
; a netmail addressed to one of these names it will NOT set the
; 'received' bit _and_ will not import the netmail to the base.
ExternName RAID
ExternName Allfix
ExternName Whatever You Want
;***************************************************************************
; ORIGIN
; Default Origin line for new echos created by xMail.
Origin Mister Musiker - Home of xMail
;***************************************************************************
; BADMESSAGE
; The name of the area, where xMail puts bad messages.
BadMessage BAD_MSGS
;***************************************************************************
; DUPEMESSAGE
; The name of the area, where xMail puts double messages.
DupeMessage DUPES
;***************************************************************************
; ILLEGALMESSAGE
; The name of the area, where xMail puts illegally imported messages.
IllegalMessage ILLEGAL
;***************************************************************************
; DUPECOUNT
; The number of duplicate messages info that xMail stores.
; Maximum is 100.000
DupeCount 100000
;***************************************************************************
; NEWMESSAGE
; If you receive an echomail in an unknown area, xMail creates
; this echo (only if the sending node is qualified for this).
; Optionally xMail writes the incoming echomail to the
; 'NEWMESSAGE' area, which will have 'Newmail' as mailtype
; definition.
NewMessage NEW
;***************************************************************************
; DEFAULTLEVEL
; For the new echos you can define defaults for the read and write security
; and for the conference new echos will have.
DefaultLevel 50 150 0
;***************************************************************************
; ADDAREA
; New Echomail areas will be created in the first free area from
; ADDAREA on. Example: 'AddArea 1' will create a new echo in the first
; free area available, 'AddArea 201' in the first available passthru
; area. You can also define in which type of messagebase new echos will
; be created. Use the AddArea statement as follows:
;
; AddArea 100 Hudson Create in Hudson base
; Msg Create as *.MSG area
; Squish Create as Squish base
;
; Default is create as passthru area.
; The directoryname (*.MSG) and the name of the squish base files will
; be automatically generated from the echoname. If a filename for a
; squish area already exists RA-Echo creates a new filename.
AddArea 1 Hudson
;***************************************************************************
; ADDREQAREA
; Where downlink requested echos will be installed
AddReqArea 201
;***************************************************************************
; ADDCMD
; When xMail creates a new echo you can automatically call a program
; or batch. Define the commandline with this keyword.
; xMail passes the name of the new echo as command line parameter 1.
; AddCmd E:\RA\NEWECHO.BAT
;***************************************************************************
; FORWARD
; With the keyword FORWARD netmail may be forwarded
; (a copy of the netmail is generated) or readdressed. Please read
; the docs for further information.
Forward "Roger Kirchhoff" ON 2:245/4 TO "Stefan Graf" ON 2:245/4.6
; |........| this is optional
; This is a setting I use on my BBS. Every netmail to me will be forwarded
; to Stefan.
Forward "Stefan Graf" ON 2:245/4.6 TO "Roger Kirchhoff" ON 2:245/4
; FORWARD #"Roger Kirchhoff" ON 2:245/4 TO "Stefan Graf" ON 2:245/4.6
; With a leading '#' the forwarded message will be deleted.
; This is in fact readdressing. The original netmail will be deleted
; after forwarding it.
;***************************************************************************
; PRIVATEUSER
; Many users requested this:
; Messages to defined name can be forwarded to an own message area, no
; matter if it's a netmail or echomail message. A mark will be inserted
; into that message that shows from what echo the message comes. Netmail
; will be marked too. If you answer any of these messages in the private
; area you have to quote this mark and xMail will know to what area it
; has to export the message. The quote characters at the begin of the
; tag line will be ignored by xMail, but the tag itself may not be changed.
; You can define multiple private mail areas in XMAIL.CFG:
;
; PRIVATEUSER <Name> <AreaName>
;
; Examples:
;
; PRIVATEUSER "Stefan Graf" PRIVATE
;
; PRIVATEUSER "Roger Kirchhoff" *MYMAIL
;
; If you add a '*' in front of the area name in PRIVATEUSER definition
; the original mail will not be set to 'received'.
; PrivateUser "Roger Kirchhoff" SYSOPMAIL
;***************************************************************************
; SYSOPALERTTEXT
; xMail will inform you with a netmail that a new echo has been
; received. You can define a textfile with the content of this message
; if you use the '@' tag or just define a short text here.
SysopAlertText @E:\XM\TXT\NEWECHO.TXT
;***************************************************************************
; ALERTMESSAGE
; You can inform your users or Points that a new echo area has been
; received. Simply let xMail post a message on a local Board or even
; in an echomail area. This is the board where xMail will do this.
AlertMessage HUB.245
;***************************************************************************
; ECHOALERTTEXT
; This is the text with which you want to inform them.
; EchoAlertText Mister Musiker has received the new area &Z from &N on &A.
; .... or:
EchoAlertText @E:\XM\TXT\ECHOALRT.TXT
;***************************************************************************
; ECHOQUERYTEXT
; xMail's Areafix Query answer text
EchoQueryText @E:\XM\TXT\QUERY.TXT
;***************************************************************************
; ECHOLISTTEXT
; Echolist header text the user gets from areafix in a %LIST message
EchoListText @E:\XM\TXT\ECHOLIST.TXT
;***************************************************************************
; ECHONOTIFYTEXT
; Areafix notify text
EchoNotifyText @E:\XM\TXT\NOTIFY.TXT
;***************************************************************************
; PAYECHOQUERYTEXT
; xMail's Areafix Query answer text for pay users
PayEchoQueryText @E:\XM\TXT\PAYQUERY.TXT
;***************************************************************************
; PAYECHOLISTTEXT
; xMail's Areafix List answer text for pay users
PayEchoListText @E:\XM\TXT\PAYELIST.TXT
;***************************************************************************
; PAYECHONOTIFYTEXT
; Areafix notify text for pay users
PayEchoNotifyText @E:\XM\TXT\PAYNOTIF.TXT
;***************************************************************************
; ECHOCANCELTEXT
; The text xMail sends to nodes that were connected to an echo which
; was removed by the sysop with CLEANUP or DELETEAREA.
EchoCancleText Area &Z was removed by Sysop
;***************************************************************************
; REQFAILTEXT
; If an ordered echo could not be received from an uplink the user will
; get informed about this. This is the message he will get when you run
; xMail CHECKSYSTEM.
ReqFailText @E:\XM\TXT\REQFAIL.TXT
;***************************************************************************
; UPLINK
; xMail's Areafix can forward echo area requests of downlinks
; to your uplink. See xMail.DOC for details.
;
; UPLINK <adr> <arealiste> <requestname> <passwort> <level>
UPLINK 2:245/31 E:\XM\LISTS\22450031.TXT Areafix MY_PASSW 10
UPLINK 2:245/60 +E:\XM\LISTS\22450060.TXT Areafix GRUMPF 10
; As it is impossible to recognize all different query formats of
; all echomail processors xMail will only create the area list
; file if the query message comes from xMail, Tosscan or the
; original Areafix.
;
; For all other Uplinks you can define a static list which could be
; the echolist of your network.
; IF you want xMail to create the echolist you must add a '+' before
; the filename of the list.
;
; Examples:
;
; UpLink 2:245/31 +24500406.LST Areafix PASSWORD 100
; The list will be created.
;
; UpLink 2:245/1 245004.LST Areafix DUMMY 100
; The list will not be created.
;***************************************************************************
; FORCEREQ
; If xMail gets an echo request from a downlink and cannot find the
; echo in any of your uplinks' echo lists the echo will usually not be
; ordered. You can force xMail to order the requested echo no matter
; if it could be found in one of the uplink echo lists. The node must
; also have the level you define here to let xMail do this.
ForceReq 100
;***************************************************************************
; QUERYSUBJECT
; Allows you to define up to 10 subjects to let xMail know that a message
; is actually a query message from an uplink and the echo list for this
; uplink has to be created from this message.
; xMail also looks for parts of what you define here in the query message.
; Notice: The query mail MUST have one of the names you defined in the
; AREAFIXNAME statement as the name of the sender. Otherwise xMail will
; not recognize that the message comes from another Areafix.
QuerySubject Query
QuerySubject Report
;***************************************************************************
; MAXMSGSIZE
; Maximum size a message may have to get imported by xMail
; min. 1024, max. 65000 Bytes
MaxMsgSize 64000
;***************************************************************************
; MAXMSGAGE + OLDMESSAGE
; On IMPORT xMail can check if a received message is too old
; (MaxMsgAge <days>). If the message is older it will not be imported
; and may optionally be stored in a message area.
; Keyword OldMessage defines where old messages are imported (same
; like IllegalMessage etc. you can define an areaname or path):
; OldMessage OLD_MSGS or OldMessage E:\MSGS\OLD
; MaxMsgAge 30
; OldMessage OLD
;***************************************************************************
; MAXEXPORTSIZE
; Maximum size a message may have to be exported.
; min. 1024, max. 65000 Bytes
; If a message > MaxExportSize is generated on your system, it will not
; be exported but copied to you BadMessage area.
MaxExportSize 64000
;***************************************************************************
; BASELIMIT
; Defines maximum size of hudson base
; BaseLimit <text_size> <max_msg_nr>
; text_size : Max. size of MSGTXT.BBS in kBytes
; max_msg_nr : Max. allowed message number
; Default: 15000 kByte Text and 15000 messages
BaseLimit 15000 15000
;***************************************************************************
; MINIMPFREE
; Minimum disk space (kB) that must be available on the destination
; drive to let xMail unpack incoming Arcmail packets.
MinImpFree 500
;***************************************************************************
; MINEXPFREE
; The minimum diskspace that must be available on the destination
; drive for packing arcmail packets (in kBytes)
MinExpFree 200
;***************************************************************************
; SWAPDRIVE
; The drive or directory where xMail will put its swap files when
; external programs like packers etc. are called.
SwapDrive E:\XM
;***************************************************************************
; SWAPEMS ON/OFF
; You can also tell xMail to swap to EMS.
SwapEms ON
;***************************************************************************
; POINTSYSTEM ON/OFF
; If 'PointSystem' is on xMail will NOT export while importing.
; NEVER use this if you have any downlinks!
PointSystem OFF
;***************************************************************************
; DBRIDGEPOINT ON/OFF
; If you are a Point system and your boss uses D'Bridge you have to
; use this keyword. If ON the pointnumber will be put into the path
; line as D'Bridge expects.
DbridgePoint OFF
;***************************************************************************
; ORIGINREPLACE ON/OFF
; If ON xMail will replace every origin line with the origin line
; that you defined in XMSETUP for that echo.
OriginReplace ON
;***************************************************************************
; TEARLINE
; The tearline xMail adds to every exported mail. If you comment this
; out xMail will leave the tearline untouched. Beta und unregistered
; versions have a non-changeable default tearline.
TearLine xMail 1.00/Pro
;***************************************************************************
; ZONEGATE ON/OFF
; ZoneGate ON strips your Path and Seen-By lines and inserts a
; ZPTH Kludge when a message changes to another zone. Should
; always be ON.
ZoneGate ON
;***************************************************************************
; AREACONF
; xMail can handle multiple Netmail areas. Usually a netmail
; will be imported to the netmail area with the address the
; netmail is addressed to. If you want to setup netmail areas
; for special nodenumbers you can do this with area conferences.
AREACONF 2:245/4 .99 777:2/0 21:100/59 66:490/0 666 493/0 1
; AREACONF 2:245/4 22:100/59
;***************************************************************************
; LHARC, PKZIP, ZOO, ARJ, PAK, LHA, PKARC,
; USERARC 1, USERARC 2, USERARC 3, USERARC 4, USERARC
;
; This is something very special. It allows you call any packer with
; any parameters. And it also allows you to define up to six NEW packers
; that now that xMail is going to be release might not even exist.
; Remember, YOU DON'T HAVE TO CHANGE these settings and you may leave
; these lines commented out unless you want to change the default
; packer parameters or add a new packer!
;
; LHA = 2,-lh5-
; LHA - LHA a -m %1 %2
; LHA + LHA e -c %1 %2 *.PKT
;
; Define a packer. '2' is the offset from the beginning of a
; packed file where xMail can find the packer's 'mark'.
; '-lh5-' is the packer's mark with which xMail can recognize
; that the packet is packed with LHA.
;
; '-' are the unpack parameters. '%1' is the name of the
; archive file, '%2' the name of the file that has to be
; added. '+' are the unpack parameters.
;
; These are the default settings for LHA, so you don't have to include
; this. But you can define any new packer too, please take a look
; at this:
; UserArc 1 = 0,DS #80 #64
; UserArc 1 + DSPACK a -o -e %1 %2
; UserArc 1 - DSUNPACK -o -m -v -y %1 %2 *.PKT
; Now, here is a list of the default settings for all packers.
;
; Packer Extract Add Offset, Mark
; ====================================================================
; LHARC LHARC e -c %1 %2 *.PKT LHARC a -m %1 %2 2,-lh1-
; LHA LHA e -c %1 %2 *.PKT LHA a -m %1 %2 2,-lh5-
; PKZIP PKUNZIP -o %1 %2 *.PKT PKZIP %1 %2 0,PK
; PAK PAK e %1 %2 *.PKT PAK a %1 %2 0,#26,#8
; ZOO ZOO -e %1 %2 *.PKT ZOO -a %1 %2 0,ZOO
; ARJ ARJ e %1 %2 *.PKT ARJ a %1 %2 0,#96 #234
; PKARC PKXARC %1 %2 *.PKT PKARC a %1 %2
;
; If you want to change PKZIP it could be like this:
;
;
; PKZIP = 0,PK <-- Declare PKZIP's mark
; PKZIP + PKZIP -m %1 %2 <-- How to Zip
; PKZIP - PKUNZIP -o %1 %2 *.PKT <-- and how to Unzip
;
; YOU DON'T HAVE TO DECLARE A PACKER UNLESS YOU WANT TO CHANGE THE
; PARAMETERS OR DECLARE A NEW UNKNOWN PACKER!
;
;***************************************************************************
; ZEROMSGCLEAR ON/OFF
; Messages with zero length will be deleted. This will be documented
; in the logfile. You can use this to delete fileattach messages on
; Binkley systems.
ZeroMsgClear Off
;***************************************************************************
; USEINTL ON/OFF
; All netmail can be created with a INTL line even if this seems not to be
; neccessary
UseIntl OFF
;***************************************************************************
; LOCKCOUNT
; Number of messages that xMail will import before unlocking the base
; temporarely. Valid entry from 1 to 255.
; ATTENTION! This is indeed the most important factor for processing
; speed of xMail, as locking/unlocking always takes some time.
; I highly recommend to leave this at the default setting 10.
; LockCount 10
;***************************************************************************
; END of xMail.CFG
;***************************************************************************