This document describes the use of fidoconfig to make fido work on your favorite platform.
This document applies to version 1.4 of fidoconfig.
The design goal of fidoconfig was to provide one config-file for several different fido software packages like editor, tosser etc. An additional aim was to have one library (fidoconfig) which can be used by all programs. The advantage is you only have to edit one config-file, so changing your system is much easier than with common software packages. Also bugs can only creep in one library and not in thousands over thousands libraries. The config definition can be used in all operating systems. Also the library should be quite portable.
This chapter describes how a fidoconfig config-file is written, which keywords exist and where to put the file.
The fidoconfig library searches the config file on different locations:
If you compile library with huskymak.cfg, the location will be overset with CFGDIR parameter.
Additionally you can set an enviroment variable called FIDOCONFIG which
points to the file:
set FIDOCONFIG=e:\bbs\fidoconfig\config
FIDOCONFIG=~/fidoconfig/config
export FIDOCONFIG
The config file(s) must be readable. If you plan using the autoareacreate feature of HPT / autofilecreate featute of HTick / etc..., the config file(s) must be writeable.
All symbols are not case-sensitive.
{<whiteSpace>} at the start of the line will be ignored.
All keywords are evaluated as occurring, the first matching keyword found is valid. If there are more then one keywords of the same type allowed, the last line matching the situation is valid. Another words: second definition overwrites the previous one. If no match is found, a default value will be used.
"#" at the start of a line or <whiteSpace>#<whiteSpace> within the
line starts a comment. The comment ends with the line. Comment char "#" can
be overwritten by commentChar token.
If the first word in a line is an undefined keyword, program exits with error message.
Each keyword has to start a new line.
Keyword parameters:
<integer>1234567890
<string><bool><addr>2:5000/117
<file><path>Note! [<parameter>] means that it can be omitted.
FIDOCONFIG library can set up internal variables:
set basedir=/home/user/fido/
[OS] variable is automatically set up for following operating systems:
You can set something like:
if [OS]==UNIX
tearline `uptime`
endif
Some programs can be compiled with module variable. It can be used to speed up config parsing:
if [module]==htick
include /etc/ftn/fileareas
endif
And if HPT is running, fileareas aren't parsed because [module]==hpt.
There are following modules available:
Also external variables can be parsed:
autoexec.bat:
SET VAR=myvar
fidoconfig:
if [VAR]==myvar
...
else
...
endif
ifdef UNIX
MsgBaseDir [home]/msgbase
endif
You can use external programs output via `cmd`. It is available
only for UNIX & OS/2+EMX:
Name Power Station under `uname -mrs`
List of the additional commands:
You can compare with a pattern by using =~ and !~ instead of == and !=:
if [VAR] =~ *substr*
...
endif
if [VAR] !~ bla?bla*
...
endif
These keywords may be used by several programs. More specific keywords you can find in the programs' individual documentations.
version <integer>.<integer>
version 1.4
Here you specify which version of fidoconfig your config belongs to. Currently this statement does nothing.
This statement cannot be repeated.
name <string>
name Leetebrok BBS
Here you specify your system's name.
This statement cannot be repeated.
location <string>
location Dusseldorf
You specify your location here.
This statement cannot be repeated.
sysop <string>
sysop Matthias Tichy
You specify your name with this keyword.
This statement cannot be repeated.
include <file>
include /etc/fido/areas
You can include other files into your config file. For example if you would like to have different config parts, you can include a file and (via cron job or manually) change the content of this file without changing the rest of the config. Additionally you can split your config in different parts. So you can have your fileareas definition in another file than your msgareas definition. This gives you the ability to have some survey about your config.
This statement can be repeated. But don't make recursive includes, e.g. include a file which includes another which includes the first. Although this will be detected and fixed many times, there is a chance that it will not be detected one time.
Address <addr>
Address 2:2433/1245
This command specifies which akas your system has. This statement is
full 5d compatible, which means you can have also addresses like
2:2433/1245.1@fidonet.org. The first address statement is your
main aka which will be used by tosser on different occasions, for
example if zone number could not be taken from the @INTL Kludge in
netmails.
This statement can be repeated. The domain name is not full supported throughout fidoconfig
commentChar <char>
commentChar ;
This command specifies which symbol is used to mark rest of line as comment. Default is '#'
This statement can be repeated.
outbound <path>
outbound /var/spool/fido/out
This command specifies your outbound path. This outbound path is binkley-style. A binkley style outbound consists of a base path and subdirectories. Each subdirectory represents a place for all the files for one zone. The base path is the zone path for your base zone.
Example:
The zone directory contains the flow-files for each node. A Flow-file of a node has the name NNNNFFFF.?lo
For points there is a subdirectory with nodes flowfilename with suffix.pnt. In this subdirectory the flowfiles have the names PPPPPPPP ( 8-digit point number in hex).
For a deeper background on a binkley-style outbound see the binkley-term documentation and source code.
This statement cannot be repeated.
inbound <path>
inbound /var/spool/fido/in
This command specifies where your inbound files are stored. This directory is the base directory which means if you have a connection which is not protected and the other system is not listed the files go in here. Only netmails are tossed from this inbound.
This statement cannot be repeated.
tempDir <path>
tempDir /var/tmp
This command specifies the path where the temporary files of the fido-programs should be stored. This directory can be erased while booting. Good idea is to set it to a memory disk.
Default value is path specified by TEMP, TMP or TMPDIR enviroment variables (use TEMP first, if it not defined then use TMP, next use TMPDIR). If these enviroment variables are not defined: - win32 versions use %WINDIR%\TEMP (usually c:\windows\temp for Win9x/Me and c:\winnt\temp for Windows NT/2000/XP) - versions for unix-like OS'es use /tmp - other versions use c:\
This statement cannot be repeated.
logFileDir <path>
logFileDir /var/spool/log/fido
This command specifies the path where the log-files of the fido-programs should be stored.
This statement cannot be repeated.
Some programs use logFileDir for persistent temporary/work files.
syslogFacility <facility>
syslogFacility local0
Some Husky programs are able to write logs via syslogd instead of via log
file. For those programs, this keyword defines which facility to use for
writing to the syslog. Syslogd will use this facility name to decide which
syslog logfile the log messages will go to. Common names that can be used
include mail, news, uucp, local0. The exact
values that can be used depend upon your operating system. Refer to the man
page for syslog.conf or /usr/include/sys/syslog.h for more
information.
Logging via syslogd is only supported on UNIX platforms, and currently only used by herp, but not by any other Husky program. If a Husky program logs via log file or via syslog or both depends on the program and not on your fidoconfig file. Consult the individual program's documentation.
loglevels <string>
loglevels 1345789,A-F Q
This statement defines log levels list for writing messages into log file. Hiphen is a range char (A-F expands to ABCDEF). Only alpha & numeric log level characters are recognized, others are ignored.
In example we output to log messages with levels 3,4,5,7,8,9,A,B,C,D,E,F,Q.
The log levels are following:
Default value: 1234567890ABCDEF
This statement cannot be repeated.
screenloglevels <string>
screenloglevels 2345789,A-C
Sets levels of log output to screen. See loglevels for details.
This statement cannot be repeated.
seqDir <path>
seqDir /var/spool/fido/seq
Sets path for current msgid sequence stamp directory. This directory should be used for msgid sequence stamp only to preventing surprises.
By default environment variable SEQDIR is used.
This statement cannot be repeated.
seqOutrun <string>
seqOutrun 1m
Sets maximum outrun for msgid sequence from current time.
Use decimal number with optional suffix.
Suffixes are:
Set seconds without suffix.
By default environment variable SEQOUT is used, or 3y if it isn't set.
This statement cannot be repeated.
Pack zip|tgz|rar|arc|arj|..... <call>
Pack zip zip -9 -g -q $a $f
This statement sets the command line call for the packer. The file will be moved into the archive, that means the file will be deleted from the harddisk. It only remains in the archive.
$a will be replaced by the archive file.
$f will be replaced by the file which should be packed into the archive.
This statement can be repeated.
See also hpt and htick documentation.
On some OSes, if a program called can't be found (can't be run) result of pack command is undefined. (Example: DOS. Reason of this: command.com does not return error code if executable file was not found.) To prevent danger write full path name for packer program, please.
Unpack "<call>" <offset> <matchcode>
Unpack "c:\arc\pkunpak /r $a $p $f" 0 1a
Unpack "c:\arc\pak e /wn $a $p" -2 fe
Unpack "c:\arc\lha e /m $a $p $f" 2 2d6c68
Unpack "c:\arc\zoo e:O $a $p $f" 0 5a4f4f
Unpack "c:\arc\jar e -y $a $p $f" 14 1a4a61721b
# *.rar
Unpack "c:\arc\unrar e -y -c- -o+ -inul $a $p $f" 0 52617221
# rar-sfx/DOS
Unpack "c:\arc\unrar e -y -c- -o+ -inul $a $p $f" 28 52534658
Unpack "/usr/bin/zoo e:O $a $p $f" 0 5a4f4f
Unpack "/usr/bin/arc eno $a $p'*.*' $f" 0 1a
Unpack "/usr/bin/unzip -joLqq $a -d $p $f" 0 504b0304
Unpack "cd $p && /usr/bin/unarj e $a $f>/dev/null" 0 60ea
Unpack "/usr/bin/unrar e -y -c- -o+ -inul $a $p $f" 0 52617221
Unpack "/usr/bin/unrar e -y -c- -o+ -inul $a $p $f" 28 52534658
Unpack "/usr/bin/jar e -y $a $p $f" 14 1a4a61721b
Unpack "cd $p && /usr/bin/ha eyq -e $a $f" 0 4841
This statement sets the call of certain unpackers according to the id in the archive file
call is the command line call for the packer (enclosed into quotes!);
offset position of recognition string in packed file;
match code hexdump of the recognition string for packed file, ?? can be used as any byte;
$a will be replaced by the archive file to extract from archive;
$p will be replaced by the path to unpacked files (usually tempoutbound);
$f will be replaced by the description file name if any (used by htick, see 'FileDescName' token; possibly other husky programs).
e.g.: unpack "unzip -joLqq $a -d $p $f" 0 504b0304
files packed by zip can be recognized by
504b0304(hex) at offset 0(integer)
they can be unpacked by htick using command
"unzip -joLqq <filename> -d <path> <descrption_filename>"
This statement can be repeated.
Also see hpt and htick documentation.
On some OSes, if a program called can't be found (can't be run) result of unpack command is undefined. (Example: MS DOS. Reason of this: command.com does not return error code if executable file was not found.) To prevent danger write full path name for unpacker program, please.
link <string>
link Matthias Tichy
This statement starts a new Link-definition. All the following link-related statements change the configuration of this link until a new link statement is found. The name is the name of this link.
Links must appear before any area definition. Virtual links for all AKAs defined in config will be created automatically.
This statement can be repeated.
linkdefaults [begin | end | destroy]
linkdefaults
This statement starts section of default definitions of links.
All the following link-related statements change default configuration
of link until a 'link' or 'linkdefaults end' or
'linkdefaults destroy' statement is found.
All parameters collected in linkdefaults sections are copied to link
configuration every time when 'link' statement is found in
configuration file. Link-related statements after 'linkdefaults end' or
'linkdefaults destroy' or before first 'link' or
'linkdefaults' statement are treated as error.
'linkdefaults' statement without 'begin' or 'end' means
'linkdefaults begin'
'linkdefaults destroy' destroys all default definitions.
Be careful with Pause, Export, etc. ;-)
This statement can be repeated. New definitions overwrite old ones.
aka <addr>
aka 2:2433/1245
This statement sets the aka for the current link.
This statement can only be repeated for different links.
ouraka <addr>
ouraka 2:2433/1247
This statement sets the aka which is used with this link.
This statement can only be repeated for different links.
password [<string>]
password secret
This statement sets the default password for the link. If you do not change the other passwords, they are set to this password. Password is case insensitive.
This statement can only be repeated for different links.
pktpwd [<string>]
pktpwd geheim
This statement sets the pktpassword for the actual link. Only passwords with maximal 8 characters are valid because of limitations of other software packages. An empty statement is allowed.
This statement can only be repeated for different links.
ticpwd [<string>]
ticpwd geheim
This statement sets the ticker password for the actual link. Only passwords with maximal 8 characters are valid because of limitations of other software packages. An empty statement is allowed.
This statement can only be repeated for different links.
areafixpwd [<string>]
areafixpwd geheim
This statement sets the areafix password for the actual link. An empty statement is allowed, but not recommended.
This statement can only be repeated for different links.
filefixpwd [<string>]
filefixpwd geheim
This statement sets the filefix password for the actual link. An empty statement is allowed, but not recommended.
This statement can only be repeated for different links.
bbspwd [<string>]
bbspwd geheim
This statement sets the bbs password for the actual link. An empty statement is allowed.
This statement can only be repeated for different links.
sessionpwd [<string>]
sessionpwd geheim
This statement sets the session password for the actual link. An empty statement is allowed.
This statement can only be repeated for different links.
handle <name>
handle eddie
This statements gives a link a nickname. This statement is supposed for bbs systems.
This statement can only be repeated for different links.
packer <packer>
packer zip
This statement sets the packer for the link. You can use the packer which you
has set up using the pack statement.
If you omit this statement or set packer none no mail will be
packed. The pkts will be put in the outbound.
This statement can only be repeated for different links.
BadArea <name> <file> [-b <msgbase>] [Options]
BadArea badarea /var/spool/fido/msgb/bad -b Squish
This statement specifies the BadArea.
Read HPT documentation for details.
This statement cannot be repeated.
dupeArea <name> <file> [-b <msgbase>] [Options]
dupeArea dupeArea /var/spool/fido/msgb/dupes -b Squish
This statement specifies the DupeArea.
Read HPT documentation for details.
This statement cannot be repeated.
EchoArea <name> <file> [-b <msgbase>] [Options] [linkAKAs] [linkOptions]
EchoArea linux.develop.ger /var/spool/fido/msgb/linux.develop.ger
-b Squish -a 2:2433/1247 -g A -dupeCheck move -dupehistory 11 -d "Linux
development" 2:2433/1245 -def
This statement specifies the echoarea. Read HPT documentation for details.
This statement can be repeated.
NetmailArea <name> <file> [-b <msgbase>] [Options]
NetmailArea netmail /var/spool/fido/msgb/netmail -b Squish
This statement specifies the NetMailArea.
Read HPT documentation for details.
This statement can be repeated.
LocalArea <name> <file> [-b <msgbase>] [Options]
LocalArea MyBBSarea /var/spool/fido/msgb/MyBBS -b Squish
This statement specifies the LocalArea: messages area in BBS.
Read HPT documentation for details.
FileArea <name> <fileareapath> <uplink> [options] [<downlinks>]
filearea Photoes /var/spool/fido/fileecho/Photoes 2:50/1 -d "Sysop photoes"
This statement specifies the FileArea: fileecho definition.
Read HTick documentation for details.
bbsarea <name> <bbsareapath>
BBSarea Incoming /var/spool/fido/BBS/incoming
This statement specifies the BBSArea: BBS file area definition.
It's used for filelist building.
Read HTick documentation for details.
This section contains keyword-list only. Read HPT Manual for more info.
accessgrp
address
addtoseen
advancedareafix
advisorylock
afterunpack
aka
allowemptypktpwd
allowpktaddrdiffer
arcmailsize
arcnetmail
areafix
areafixecholimit
areafixfrompkt
areafixhelp
areafixReportsAttr
areafixkillrequests
areafixmsgsize
areafixnames
areafixorigin
areafixpwd
areafixqueryreports
areafixqueuefile
areafixsplitstr
areafixfromname
areasfilenamecase
areasmaxdupeage
autoareacreate
autoareacreatedefaults
autoareacreatefile
autoareacreateflag
autoareacreatesubdirs
autopassive
autopause
availlist
badarea
beforepack
bundlenamestyle
carbonaddr
carbonandquit
carboncopy
carbondelete
carbonexcludefwdfrom
carbonextern
carbonfrom
carbonfromarea
carbongroups
carbonkeepsb
carbonkludge
carbonmove
carbonout
carbonreason
carbonrule
carbonsubj
carbontext
carbonto
createareascase
createfwdnonpass
defarcmailsize
denyfwdfile
denyfwdmask
denyfwdreqaccess
denyuncondfwdreqaccess
disabletid
disablepid
dupearea
dupebasetype
dupehistorydir
echoarea
echoareadefaults
echomailflavour
echotosslog
excludepassthroughcarbon
export
filebox
fileboxalways
fileboxesdir
forwardareapriority
forwardpkts
forwardrequestfile
forwardrequestmask
forwardrequests
forwardrequesttimeout
hptperlfile
idlepassthrutimeout
ignorecapword
ignoreseen
import
importlog
inbound
include
intab
keeptrsfiles
keeptrsmail
killedrequesttimeout
kludgeareanetmail
level
link
linkbundlenamestyle
linkdefaults
linkfilebasedir
linkgrp
linkmsgbasedir
linkwithimportlog
localarea
localinbound
lockfile
logechotoscreen
mandatory
mindiskfreespace
msgbasedir
name
netarea
netmailarea
netmailextern
netmailflag
newarearefusefile
noprocessbundles
norules
notvalidfilenamechars
optgrp
origin
ouraka
outbound
outtab
pack
packaka
packer
packnetmailonscan
password
pause
pktpwd
pktsize
processpkt
protinbound
publicgroup
readonly
reducedseenby
remap
remoterobotname
reportto
robotsarea
route
routefile
routemail
rulesdir
separatebundles
setconsoletitle
statlog
sysop
tearline
tempinbound
tempoutbound
tossingext
unpack
writeonly
This section contains keyword-list only. Read HTick Manual for more info.
AddDLC
AnnAreaTag
AnnAddrfrom
AnnAddrto
AnnExclude
AnnFileOrigin
AnnFileRFrom
AnnFrom
AnnInclude
AnnMessFlags
AnnOrigin
AnnounceSpool
AnnSubj
AnnTo
AutoFileCreateFlag
BbsArea
BusyFileDir
ConvertLongNames
ConvertShortNames
DLCDigits
ExecOnFile
FileArea
FileAreaBaseDir
FileAreaCreatePerms
FileDescPos
FileAreaDefaults
FileDescName
FileEchoFlavour
FileLDescString
FileFixFromName
FileFixHelp
FileFixReportsAttr
FileFixKillRequests
FileFixNames
MaxTicLineLength
OriginInAnnounce (obsoleted)
PassFileAreaDir
RemoteFileRobotName
SaveTic
TicOutbound
In Link section:
AutoFileCreate
AutoFileCreateDefaults
AutoFileCreateFile
AutoFileCreateSubdirs
DelNotRecievedTIC
FileFixEchoLimit
FileFixFSC87Subset
ForwardFilePriority
ForwardFileRequestFile
ForwardFileRequests
NoTIC
LinkFileBaseDir
PackAka
TickerPackToBox
nodelistDir <path>
nodelistDir /var/spool/fido/nodelist
This command specifies the path where the actual nodelists are or should be written to. This path contains the raw nodelist (see nodelist). Also, compiled nodelists like the FIDOUSER.LST will be stored here.
This statement cannot be repeated.
fidoUserList <filename>
fidoUserList fidouser.lst
If this keyword is present, the nodelist compiler (e.g. ulc) is
instructed to build a user list file with the given filename in the nodelist
directory (see nodelistdir). This is a simple text file with fixed line
length that contains user names (nodes, points) and their corresponding node
or pointnumbers. The file is sorted alphabetically by user name (case
insensitive), so that it can be bsearched to implement a quick node numer
lookup functinality. The fido user list file format is understood by
msged, for example.
Nodelist <name>
Nodelist nodelist or Nodelist points24
This statement starts a new nodelist definition. All the following
nodelist-related stamtements change the configuration of this nodelist until
a new nodelist statement is found.
The name that you specify must match the base name (without extension and
without pathname) of the raw, unpacked, nodelist file. The husky tools
ulc and nlupdate math the file name case-insensitively, but
other tools may need the exact spelling. The raw nodelist file is
expected to reside in the nodelist directory (see nodelistdir).
DiffUpdate <path_and_basname>
DiffUpdate /var/spool/filebase/nodediff/nodediff
Here you can specify the base filename of nodelist difference files (nodediffs) that are used to keep the corresponding nodelist up to date. The argument to the DiffUpdate is the full file name with path of a difference file, without the file extension. For example, if you have a file area at /var/spool/filebase/24000, where your ticker places the updates for the German Pointlist, and those update files are called points24.a26, points24.a33, and so on, you would use
DiffUpdate /var/spool/filebase/24000/points24
The Diffupdate keyword is used by nlupdate, for example. The
nodelist updater will unpack the difference file (if it is archived, of
course, unpacked diffs are also supported), apply the diff to the
corresponding nodelist, and delete the temporary unpacked diff again.
FullUpdate <path_and_basname>
FullUpdate /var/spool/filebase/nodelist/nodelist
This statement works like DiffUpdate (see diffupdate). The
difference is that here you don't specify the location of a nodelist
difference file, but the locations where complete nodelist files/archives can
be found. Some othernets do not (regularly) distribute a nodediff file, but
just hatch a new nodelist every few weeks. In this case, you need the
FullUpdate statement.
DefaultZone <zone>
DefaultZone 2
Some nodelist files do not start with a ‘Zone’ entry. This is the case
for the German Points24 list, for example, but could also happen for
othernets that only have one zone. In this case, you can use the
DefaultZone keyword to specify the default zone number for all nodes
listed in this nodelist.
Nodelistformat <format>
NodelistFormat standard
NodelistFormat points4d
NodelistFormat points24
Here you can specify the format of the unpacked nodelist. The default is ‘standard’; this is the normal Fidonet nodelist format. You can also specify ‘points4d’, which is needed for the nodelist compiler to recognise a standart pointlist in 4D format or ‘points24’ for the German points24 format as such, so that it can see the proper 5D point numbers instead of the fakenet numbers.
Common tokens:
Link definition tokens:
sendMailCmd string
sendMailCmd /usr/sbin/sendmail $a <$f
This keyword is used to define send mail command & its parameters. Macro '$a' specifies position of the recipient e-mail address; macro '$f' specifies position of name of file with message body. If '$f' is omitted then message body will be taken from stdin.
This statement can't be repeated.
email <email-address>
email eddie@ironmaiden.com
This keyword is used to set the email-address for the link. This can be used to send pkts via email.
This statement can only be repeated for different links.
emailFrom <email-address>
emailFrom fred@ironmaiden.com
This keyword is used to set the email-address used as sender address for outgoing emails to this link.
This statement can only be repeated for different links.
emailSubj <subject>
emailSubj Fido over EMail message in UUE format
This keyword is used to set the subject for emails to and from this link. It may be ignored by some encodings (e.g. SEAT).
This statement can only be repeated for different links.
emailEncoding (MIME | SEAT | UUE)
emailEncoding MIME
This keyword is used to set the encoding for outgoing emails to this link.
This statement can only be repeated for different links.
This section contains keyword-list only. Read BsoPack Manual for more info.
maxunpackednetmail
packnetmail
Herp is the Husky External file Request Processor. The following fidoconfig keywords are specific to herp. Some programs of herp, in particular herpidx, also use part of the htick configuration, i.E. filearea definitions.
reqidxDir <path>
reqidxDir /var/spool/fido/reqidx
This command specifies a subdirectory which will be used to store the request index generated by herpidx. This subdirectory should be writable for the herpidx process and at least readable for the user under which your mailer and herp will be run. herpidx will place various request index files here. The subdirectory should not be used for any other purposes. The index can become rather large, so plan for enough free disk space.
# sample fido config file for fidoconfig 1.4
# $Id: config,v 1.19.2.1 2006/03/11 21:25:52 stas_degteff Exp $
#
# This file is universal for unix-based and DOS-based OS. OS specific
# statements is specified using "if-elseif-else-endif" conditional operators.
##
## Section 1: common
##
version 0.14 # Config format version. Some software may check this.
Name hpt-HQ
Location Paderborn, GER
Sysop Matthias Tichy
LogLevels 23456789ABCDEF # see fidoconfig documentaion for log levels
Address 2:2432/645
Address 44:4932/110
#
# Define command lines of the packers and unpackers.
#
if "[OS]"=="UNIX"
set fidoconfigdir=/usr/local/etc/fido
set fidodatadir=/var/fido
set path_archivers=/usr/local/bin/
else
set fidoconfigdir=c:\fido\config
set fidodatadir=c:\fido
set path_archivers=c:\arch
endif
# INFO-ZIP
Unpack "[path_archivers]unzip -j -Loqq $a -d $p" 0 504b0304
Pack zip [path_archivers]zip -9 -j -q $a $f
if not "[OS]"=="UNIX"
# Unpack "[path_archivers]pkzipc -ext -dir=none -over=all -nozip -silent $a $p $f" 0 504b0304
# Unpack "[path_archivers]pkunzip -njCL $a -d $p $f" 0 504b0304
# Unpack "[path_archivers]pkzip25 -ext -silent -over=all -nofix -nozip $a $p $f" 0 504b0304
endif
Unpack "[path_archivers]arc eno $a $p'*.*'" 0 1a
if not "[OS]"=="UNIX"
Unpack "[path_archivers]pkunpak /r $a $p" 0 1a
Pack arc [path_archivers]pkpak -oct a $a $f
Unpack "[path_archivers]pak e /wn $a $p" -2 fe
Pack pak [path_archivers]pak a $a $f
Unpack "[path_archivers]lha e /m $a $p" 2 2d6c68
Pack lha [path_archivers]lha a /o /m $a $f
endif
Unpack "[path_archivers]zoo e:O $a $p" 0 5a4f4f
Pack zoo [path_archivers]zoo a: $a $f
if "[OS]"=="UNIX"
Unpack "cd $p && [path_archivers]unarj e $a > /dev/null" 0 60ea
else
Unpack "[path_archivers]arj e -+ -y $a $p" 0 60ea
Pack arj [path_archivers]arj a -+ -e -y $a $f
endif
Unpack "[path_archivers]jar e -y $a $p" 14 1a4a61721b
Pack jar [path_archivers]jar a -y $a $f
Unpack "[path_archivers]ha eyq $a" 0 4841
Pack ha [path_archivers]ha a21eq $a $f
# *.rar
Unpack "[path_archivers]unrar e -y -c- -o+ -inul $a $p $f" 0 52617221
# rar-sfx/DOS
Unpack "[path_archivers]unrar e -y -c- -o+ -inul $a $p $f" 28 52534658
# rar 2.90 R sfxs
Unpack "[path_archivers]rar e -y -c- -o+ -inul $a $p $f" 23040 52617221 # Default.sfx
Unpack "[path_archivers]rar e -y -c- -o+ -inul $a $p $f" 9573 52617221 # DOS.sfx
Unpack "[path_archivers]rar e -y -c- -o+ -inul $a $p $f" 9493 52617221 # Dos_US.sfx
Unpack "[path_archivers]rar e -y -c- -o+ -inul $a $p $f" 25099 52617221 # Os2.sfx
Unpack "[path_archivers]rar e -y -c- -o+ -inul $a $p $f" 13312 52617221 # WinCon.sfx
Unpack "[path_archivers]rar e -y -c- -o+ -inul $a $p $f" 13824 52617221 # WinConUS.sfx
Unpack "[path_archivers]rar e -y -c- -o+ -inul $a $p $f" 25088 52617221 # Zip.sfx
# Rar 3.0 R sfxs
Unpack "[path_archivers]rar e -y -c- -o+ -inul $a $p $f" 46592 52617221 # Default.sfx
Unpack "[path_archivers]rar e -y -c- -o+ -inul $a $p $f" 93816 52617221 # Dos.sfx
Unpack "[path_archivers]rar e -y -c- -o+ -inul $a $p $f" 37376 52617221 # WinCon.sfx
Unpack "[path_archivers]rar e -y -c- -o+ -inul $a $p $f" 31232 52617221 # Zip.sfx
# Rar 3.0 sfxs
Unpack "[path_archivers]rar e -y -c- -o+ -inul $a $p $f" 47104 52617221 # Default.sfx
# Rar 3.1b1 sfxs
Unpack "[path_archivers]rar e -y -c- -o+ -inul $a $p $f" 50688 52617221 # Default.sfx
Unpack "[path_archivers]rar e -y -c- -o+ -inul $a $p $f" 94128 52617221 # Dos.sfx
Unpack "[path_archivers]rar e -y -c- -o+ -inul $a $p $f" 34816 52617221 # Zip.sfx
# Rar 3.1b2 sfxs
Unpack "[path_archivers]rar e -y -c- -o+ -inul $a $p $f" 49152 52617221 # Default.sfx
Unpack "[path_archivers]rar e -y -c- -o+ -inul $a $p $f" 94016 52617221 # Dos.sfx
Unpack "[path_archivers]rar e -y -c- -o+ -inul $a $p $f" 34304 52617221 # Zip.sfx
# Rar 3.1b3 sfxs
Unpack "[path_archivers]rar e -y -c- -o+ -inul $a $p $f" 49664 52617221 # Default.sfx
Unpack "[path_archivers]rar e -y -c- -o+ -inul $a $p $f" 93932 52617221 # Dos.sfx
Unpack "[path_archivers]rar e -y -c- -o+ -inul $a $p $f" 37888 52617221 # WinCon.sfx
Pack rar [path_archivers]rar a -ep -md1024 -m5 -mm -inul -s $a $f
Unpack "[path_archivers]arj e -+ -y $a $p >nul" 0 60ea
Pack arj [path_archivers]arj a -+ -e -y $a $f >nul
Unpack "[path_archivers]unace e -y -c- $a $p $f" 7 2a2a414345
Pack 7ZIP [path_archivers]7za a -y $a $f
Unpack "[path_archivers]7za e -y $a $p $f" 0 377ABCAF
if "[module]"==hpt
route hold noroute 2:2432/645.*
route hold noroute 2:240/6223.*
route crash noroute 2:2432/646
route hold 44:4932/120 44:4932/120 44:4932/130
route crash 44:4932/100 44:*
route normal 2:2435/424 2:2435/*
route crash 2:2432/646 *
endif
Inbound [fidodatadir]in
ProtInbound [fidodatadir]in.sec
LocalInbound [fidodatadir]in.loc
Outbound [fidodatadir]out
tempOutbound [fidodatadir]out.tmp
tempInbound [fidodatadir]in.tmp
#MsgBaseDir Passthrough
MsgBaseDir [fidodatadir]msgb
FileAreaBaseDir [fidodatadir]files
public [fidodatadir]public
logFileDir [fidodatadir]log
DupeHistoryDir [fidodatadir]dupes
NodelistDir [fidodatadir]nodelist
PassFileAreaDir [fidodatadir]passFileDir
magic [fidodatadir]magic
if "[module]"=="hpt"
# include [fidoconfigdir]config.hpt
# HPT's transcoding isn't recommended to use,
# You shoulds use recode features of your message editor instead.
#intab [fidoconfigdir]outaltkoi8
#outtab [fidoconfigdir]outkoi8alt
lockfile [fidodatadir]lock.hpt
advisoryLock 9
echotosslog [fidodatadir]echotoss.log
importlog [fidodatadir]import.log
areafixhelp [fidodatadir]areafix.hlp
AreafixReportsAttr loc pvt k/s dir
endif
if "[module]"=="htick"
# include [fidoconfigdir]config.htick
FileFixHelp [fidodatadir]filefix.hlp
FilefixReportsAttr loc pvt k/s npd dir
lockfile [fidodatadir]lock.htick
advisoryLock 6
endif
##
## Section 2: Nodelists
##
if "[OS]"=="UNIX"
NodeList nodelist
DiffUpdate [fidodatadir]files/nodediff
NodeList linuxnet
DiffUpdate [fidodatadir]files/lin44.node
else
NodeList nodelist
DiffUpdate [fidodatadir]files\nodediff
NodeList linuxnet
DiffUpdate [fidodatadir]files\lin44.node
endif
##
## Section 3: define links
##
#
# Links for 2:2432/645
#
LinkDefaults
OurAka 2:2432/645
Level 65535
Packer ZIP
AutoAreaCreateDefaults passthrough -dupeHistory 11 -dupecheck move
AutoAreaCreateFile [fidoconfigdir]echoareas
AutoFileCreateFile [fidoconfigdir]fileareas
AutoFileCreateDefaults -lw 10
AutoFileCreateSubdirs on
EchomailFlavour direct
FileEchoFlavour normal
PackNetmail on
MaxUnpackedNetmail 64
EchomailFlavour Normal
EmailFrom fido@my.host
EmailSubj FTN Mail Transport : FTNbundle from 2:2432/645
EmailEncoding MIME
TickerPackToBox on
FileFixFSC87Subset
ArcmailSize 450
Pause off
LinkGrp COMMON
AccessGrp INTERNATIONAL,COMMON,LOCAL
LinkDefaults end
Link Matthias Schniedermeyer
Aka 2:2432/600
Password xxxxxxxxx
EchoMailFlavour Crash
AutoAreaCreate on
AutoFileCreate on
forwardRequests on
Link Carsten Ellermann
Aka 2:2432/215
password xxxxxxx
autoAreaCreate on
autoFileCreate on
Link Matthias Tichy
Aka 2:2432/646
Password xxxxxxxx
autoAreaCreate on
forwardPkts on
Link Matthias Born
Aka 2:240/6223
Password xxxxxxx
EchoMailFlavour hold
Link Sascha Silbe
Aka 2:2435/424
ourAka 2:2432/645
AutoFileCreate on
Password xxxxxxxx
#
# Links for 44:4932/110
#
LinkDefaults
OurAka 44:4932/110
Level 65535
Packer ZIP
AutoAreaCreateDefaults passthrough -dupeHistory 11 -dupecheck move
AutoAreaCreateFile [fidoconfigdir]echo44
AutoFileCreateFile [fidoconfigdir]file44
AutoFileCreateDefaults -lw 10
AutoFileCreateSubdirs on
EchomailFlavour direct
FileEchoFlavour normal
PackNetmail on
MaxUnpackedNetmail 64
EchomailFlavour Normal
EmailFrom fido@my.host
EmailSubj FTN Mail Transport : FTNbundle from 44:4932/110
EmailEncoding MIME
TickerPackToBox on
FileFixFSC87Subset
ArcmailSize 450
Pause off
LinkGrp LINNET
AccessGrp LINNET,LOCAL
LinkDefaults end
Link Matthias Schniedermeyer
Aka 44:4932/100
password xxxxxxxx
EchoMailFlavour Crash
AutoAreaCreate on
AutoFileCreate on
Link Matthias Born
Aka 44:4932/120
Password xxxxxxx
EchoMailFlavour hold
##
## Section 4: define areas
##
if "[OS]"=="UNIX"
#NetmailArea NetmailArea [fidodatadir]msgb/netmail -b msg
NetmailArea NetmailArea [fidodatadir]msgb/net -b Squish
BadArea BadArea [fidodatadir]msgb/bad -b Squish
DupeArea DupeArea [fidodatadir]msgb/dupe -b Squish
LocalArea carbonArea [fidodatadir]msgb/carbonArea -b Squish -manual
else
#NetmailArea NetmailArea [fidodatadir]msgb\netmail -b msg
NetmailArea NetmailArea [fidodatadir]msgb\net -b Squish
BadArea BadArea [fidodatadir]msgb\bad -b Squish
DupeArea DupeArea [fidodatadir]msgb\dupe -b Squish
LocalArea carbonArea [fidodatadir]msgb\carbonArea -b Squish -manual
endif
if "[OS]"=="UNIX"
LocalArea carbonArea [fidodatadir]msgb/carbonArea -b Squish -manual
else
LocalArea carbonArea [fidodatadir]msgb\carbonArea -b Squish -manual
endif
if "[module]"=="hpt"
CarbonTo Matthias Tichy
CarbonCopy carbonArea
endif
##
## SubSection 4.1: include areas configs
##
include [fidoconfigdir]echoareas
include [fidoconfigdir]fileareas
include [fidoconfigdir]echo44
include [fidoconfigdir]file44
Since original GoldEd by Odinn Sorensen does not support fidoconfig at all and msged and aquaed only in beta versions, we have developed three programs that convert your fidoconfig to these proprietary config file formats.
fconf2golded ~/golded/golded.cfg ~/golded/goldDefaults.cfg
fconf2msged ~/msged.areas
fconf2aquaed ~/aquaed/aquaed.cfg
You should run tparser everytime you have changed the config. If tparser found error in config please correct your config file and try again.
tparser -Dmodule=hpt | less
tparser (like any fidoconfig program) will display error messages if you have made an error in the config. It also may be display some warnings about your config settings. It will grumble on every Keyword it does not know. It will stop after the first error (not warning) to give you the ability to change your config.
var to value.
You can reach me at
mtt@tichy.de
2:2432/645
and in the fido echoarea
linux.develop.ger
fidosoft.husky
Max Levenkov:
sackett@mail.ru
ru.husky (russian)
ru.echoprocessors (russian)
fidosoft.husky (english)
The actual fidoconfig library and other fido software will be on http://husky.sourceforge.net.