FidoConfig Manual

a way to make your unix fido-capable

Matthias Tichy


Table of Contents


Copyright (C) 1998-99 Matthias Tichy

1 Design goals

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.

2 Config file

This chapter describes how a fidoconfig config-file is written, which keywords exist and where to put the file.

2.1 Configfile location

The fidoconfig library searches the config file on different locations:

linux:
/etc/fido/config
freebsd:
/usr/local/fido/config
os2/win32/dos:
c:\fido\config

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 to use the autoareacreate feature the config file must be writeable.

2.2 Syntax

The configfile must be readable to fidoconfig. If you plan to use the autoareacreate feature the writing process must have write-access to the configfile.

All symbols are not case-sensitiv.

{<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 first line matching the situation is valid. If no match is found, a default-value will be used.

"\" is used as escape-sequence. "\" has to be written as "\\".

non-printable characters can be expressed as \<hexValue>

"#" at the start of a line or <whiteSpace>#<whiteSpace> within the line starts a comment. The comment ends with the line.

If the first word in a line is an undefined keyword, the line will be ignored.

Each keyword has to start a new line.

Currently not supported:

"\" at end of line means that "\" and the following new-line- character(s) will be ignored. (concatenating lines)

2.3 Keywords

All statements are case-insensitive. A line which starts with a # is a comment and will be ignored.

2.3.1 version

Syntax:
version <integer>.<integer>
Example:
version 0.13

Here you specify to which version of fidoconfig your config belong. Currently this statement does nothing.

This statement cannot be repeated.

2.3.2 name

Syntax:
name <text>
Example:
name Leetebrok BBS

Here you specify your Systems name.

This statement cannot be repeated.

2.3.3 location

Syntax:
location <text>
Example:
location Dusseldorf

You specify your Location here.

This statement cannot be repeated.

2.3.4 sysop

Syntax:
sysop <text>
Example:
sysop Matthias Tichy

You specify your name with this keyword.

This statement cannot be repeated.

2.3.5 include

Syntax:
include <file>
Example:
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 your the ability to have some survey about your config.

This statement can be repeated. But dont make recursive includes. eg 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.

2.3.6 address

Syntax:
Address <aka> [Line [unsignedInteger]1* ]
Example:
Address 2:2433/1245 Line 1 4 5

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. If the Line options is empty this aka is displayed on all lines. In the above example this aka is displayed on line 1, 4 and 5. The first address statement is your main aka which will be used by tossers on different occasions, for example if zone number could not be taken from the @INTL Kludge in netmails.

This statement can be repeated.

The Line option is not supported The domain name is not full supported throughout fidoconfig

2.3.7 outbound

Syntax:
outbound <path>
Example:
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:

/var/spool/fido/out
This directory contains the files for your base zone.
/var/spool/fido/out.003
This directory contains the files for zone 3.
/var/spool/fido/out.00A
This directory contains the files for zone 10.

The zone directory contains the flow-files for each node. A Flow-file of a node has the name NNNNFFFF.?lo

NNNN
The 4-digit hex-number of the nodes netnumber.
FFFF
The 4-digit hex-number of the nodes nodenumber.
?
Here the flavour of the mails can be chosen. hold, crash, fnormal.

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.

2.3.8 tempoutbound

Syntax:
tempoutbound <path>
Example:
outbound /var/spool/fido/out.tmp

This command specifies your temporaryoutbound path. It is used for outgoing packets.

This statement cannot be repeated.

2.3.9 inbound

Syntax:
inbound <path>
Example:
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 ist 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.

2.3.10 protinbound

Syntax:
protinbound <path>
Example:
protinbound /var/spool/fido/in.sec

This command specifies where files should be stored which were received during a password-protected session. All types of mail are tossed from this path. But passwords are checked before.

This statement cannot be repeated.

2.3.11 listinbound

Syntax:
listinbound <path>
Example:
listinbound /var/spool/fido/in.lst

This command specifies where the files should be stored which were received during a non-password-protected session from a listed system. Only netmails are tossed from this path.

This statement cannot be repeated.

2.3.12 localinbound

Syntax:
localinbound <path>
Example:
localinbound /var/spool/fido/in.loc

This command specifies the path, from which all types of netmail and echomail are tossed without any password checking. You can put pktīs here which were created by a file tosser etc. So created by a you or a programm on your own system.

This statement cannot be repeated.

2.3.13 tempinbound

Syntax:
tempinbound <path>
Example:
tempinbound /var/spool/fido/in.tmp

This command specifies a path which is used while tossing. The incoming packets are unpacked there.

This statement cannot be repeated.

2.3.14 msgBaseDir

Syntax:
msgBaseDir <path>
Example:
msgBaseDir /var/spool/fido/msgb

This command specifies the path where autoareacreated msgBases are stored. For example: If an area called LINUX.GER was autoareacreated and the msgBaseDir is /var/spool/fido/msgb the resulting msgBaseName is

/var/spool/fido/msgb/linux.ger.sqd

If you specify the msgbasedir as PASSTHROUGH, the areas are created as passthrough areas.

This statement cannot be repeated.

2.3.15 intab

Syntax:
intab <file>
Example:
intab /var/spool/fido/recode/outaltkoi8

This statement specifies the file which should be used to recode the characters of the incoming messages from transport to internal charset. It is useful in russia. If you do not use this statement no recoding will be done.

This statement cannot be repeated.

2.3.16 outtab

Syntax:
outtab <file>
Example:
outtab /var/spool/fido/recode/outkoi8alt

This statement specifies the file which should be used to recode the characters of the outgoing messages from internal to transport charset. It is useful in russia. If you do not use this statement no recoding will be done.

This statement cannot be repeated.

2.3.17 importlog

Syntax:
importlog <file>
Example:
importlog /var/spool/fido/import.log

This statement specifies the file which a tosser fills with the names of the areas where echomails has been tossed in.

This statement cannot be repeated.

2.3.18 echotosslog

Syntax:
echotosslog <file>
Example:
echotosslog /var/spool/fido/echotoss.log

This statement specifies the file which is filled by a message editor with the names of the areas where new echomails have been entered. A tosser will only scan those areas which leads to a great speed-up. After scanning the tosser will remove the file.

This statement cannot be repeated.

2.3.19 linkWithImportLog

Syntax:
linkWithImportLog <yers|no|kill>
Example:
linkWithImportLog yes

This statement specifies if the importlog-file should be used to determine which echomail areas need to be linked.

yes
importlog-file will be read. areas which are in importlog, will be linked. the importlog-file will not be erased.
kill
like yes, but the importlog-file will be killed after using it.
no
DEFAULT. all areas will be linked.

This statement cannot be repeated.

2.3.20 public

Syntax:
public <path>
Example:
public /var/spool/fido/public

This command specifies the path where files which are requested are searched for. The files are searched in this directory and in all subdirectories.

This command can be repeated.

2.3.21 logFileDir

Syntax:
logFileDir <path>
Example:
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.

2.3.22 dupeHistoryDir

Syntax:
dupeHistoryDir <path>
Example:
dupeHistoryDir /var/spool/fido/dupes

This command specifies the path where the dupe history files are stored. The format and the names of the dupe-files are not standardized.

This statement cannot be repeated.

2.3.23 magic

Syntax:
magic <path>
Example:
magic /var/spool/fido/magic

Directory with executables to satisfy "magic" file requests if requested a file present in this directory, it will be executed and stdout sent to the remote system. If the file is not executable, it is read line by line and the lines are processed as if they were received file requests (recusively). Execution of commands may compromize security! You are warned.

This statement cannot be repeated.

2.3.24 lockfile

Syntax:
lockfile <file>
Example:
lockfile /var/lock/hpt

another session of hpt will be terminated if found lockfile

This statement cannot be repeated.

2.3.25 link

Syntax:
link <name>
Example:
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.

This statement can be repeated.

2.3.26 aka

Syntax:
aka <aka>
Example:
aka 2:2433/1245

This statement sets the aka for the current link.

This statement can only be repeated for different links.

2.3.27 ouraka

Syntax:
ouraka <aka>
Example:
ouraka 2:2433/1247

This statement sets the aka which is used with this link.

This statement can only be repeated for different links.

2.3.28 password

Syntax:
password <string>
Example:
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. Only passwords with maximal 8 characters are valid because of limitations of other software packages.

This statement can only be repeated for different links.

2.3.29 pktpwd

Syntax:
pktpwd [<string>]
Example:
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.

2.3.30 ticpwd

Syntax:
ticpwd [<string>]
Example:
ticpwd geheim

This statement sets the ticcer 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.

2.3.31 areafixpwd

Syntax:
areafixpwd [<string>]
Example:
areafixpwd geheim

This statement sets the areafix 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.

2.3.32 filefixpwd

Syntax:
filefixpwd [<string>]
Example:
filefixpwd geheim

This statement sets the filefix 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.

2.3.33 bbspwd

Syntax:
bbspwd [<string>]
Example:
bbspwd geheim

This statement sets the bbs 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.

2.3.34 sessionpwd

Syntax:
sessionpwd [<string>]
Example:
sessionpwd geheim

This statement sets the session 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.

2.3.35 handle

Syntax:
handle <name>
Example:
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.

2.3.36 email

Syntax:
email <name>
Example:
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.

2.3.37 tossgrp

Syntax:
tossgrp {<group>}
Example:
tossgrp fido

This statement connects a link to several echomails groups.

This statement can only be repeated for different links.

This statement is currently not supported.

2.3.38 ticgrp

Syntax:
ticgrp {<group>}
Example:
ticgrp gfd

This statement connects a link to several fileecho groups.

This statement can only be repeated for different links.

This statement is currently not supported.

2.3.39 bbsgrp

Syntax:
bbsgrp {<group>}
Example:
bbsgrp pay1

This statement connects a link to several bbs groups.

This statement can only be repeated for different links.

This statement is currently not supported.

2.3.40 accessgrp

Syntax:
accessgrp {<group>}
Example:
accessgrp pay1

This statement connects a link to several echomail groups. See also "publicgroup" and -g <group> in echoarea options.

This statement can only be repeated for different links.

2.3.41 optgrp

Syntax:
optgrp {<group>}
Example:
optgrp py

Export, Import & Mandatory restrictions uses "optgrp" areas instead of "accessgrp".

This statement can only be repeated for different links.

2.3.42 export

Syntax:
export (on|off)
Example:
export off

By default "export on".

if "export" is off, mail for groups defined in "optgrp" not tossed to link and if "optgrp" not defined, then no mail tossed to link at all.

This statement can only be repeated for different links.

2.3.43 import

Syntax:
import (on|off)
Example:
import off

By default "import on".

Same as "export", but this is for mail *from* link.

This statement can only be repeated for different links.

2.3.44 mandatory

Syntax:
mandatory (on|off)
Example:
mandatory on

By default "mandatory off".

This statament do not allow the link to subscribe/unsubscribe areas

This statement can only be repeated for different links.

2.3.45 level

Syntax:
level {<integer>}
Example:
level 200

Access level. Used in echoareas to control read/write access. By default "level 0".

This statement can only be repeated for different links.

2.3.46 autoareacreate

Syntax:
autoareacreate (on|off)
Example:
autoareacreate on

This statement gives a link the permission to create areas on your system just by sending msgs in them. The echoarea is created using the AutoCreateDef contents:

   EchoArea <areaName> <msgBaseDir><areaName> -a <mypktaka> -b Squish <linkAka> <autoCreateDef>

This statement can only be repeated for different links.

This statement is only a temporal solution for autoareacreating. It will be replaced by the group scheme, which is about to be implemented.

2.3.47 autoareacreatedefaults

Syntax:
autoareacreatedefaults [<string>]
Example:
autoareacreatedefaults -$m 200 -dupecheck move

Set defaults to autocreated echoareas.

This statement can only be repeated for different links.

2.3.48 packer

Syntax:
packer <packer>
Example:
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 no mail will be packed. The pktīs will be put in the outbound.

This statement can only be repeated for different links.

2.3.49 echomailflavour

Syntax:
echoMailFlavour <hold|normal|crash|direct|immediate>
Example:
echoMailFlavour hold

This statement sets the flavour which outgoing echomails for this link get. For example set echomailFlavour for points to hold and for uplink crash.

This statement can only be repeated for different links.

2.3.50 fileechoflavour

Syntax:
fileEchoFlavour <hold|normal|crash|direct|immediate>
Example:
fileEchoFlavour hold

This statement sets the flavour which outgoing files in fileechos for this link get. For example set fileEchoFlavour for points to hold and for uplink crash.

This statement can only be repeated for different links.

2.3.51 autoAreaCreateFile

Syntax:
autoAreaCreateFile <fileName>
Example:
autoAreaCreateFile /etc/fido/areas.matthias

This statement defines where autocreated areas by this link are going to. If you omit this statement the default configuration file will be used. The tosser must have the rights to create and change the file.

You must include the specified file for yourself into fidoconfig, so these autocreated areas are found in subsequent tosser-runs.

This statement can only be repeated for different links.

2.3.52 forwardRequests

Syntax:
forwardRequests (on|off)
Example:
forwardRequests on

By default "forwardRequests off". "on" allow forward requests to this link from other links.

This statement can only be repeated for different links.

2.3.53 forwardRequestFile

Syntax:
forwardRequestFile <fileName>
Example:
forwardRequestFile /etc/fido/fidonet.na

file for forward requests (also for available areas and descriptions) if not defined then forward requests unconditional

This statement can only be repeated for different links.

2.3.54 remoteRobotName

Syntax:
remoteRobotName <string>
Example:
remoteRobotName allfix

Set remote system "areafix" to new name. This token used when requests to subscribe/unsubscribe new areas forwarded to this link.

This statement can only be repeated for different links.

2.3.55 forwardPkts

Syntax:
forwardPkts <off|secure|on>
Example:
forwardPkts yes

If we receive a PKT file that is not addressed to our system, but to this link of us, this flag controls if the PKT file should be binary forwarded to this link. The default behaviour is not to forward the pkt file, but to remain it to <filename>.ntu and leave it in the inbound. If you specify <yes>, the file will instead be forwarded to the destination link (i.E. put into his arcmail bundle). If you specify <secure>, the file will only be forwarded if we have received it in the secure inbound. You should specify secure if the destination link does not check packet passwords.

PKT forwarding can be useful for tunneling purposes, for instance. Another example is if you are running two nodes, one IP node at your company and one PSTN node at your home. If you want to show both node numbers at both mailers, the tossers at each node must forward PKT files that are addressed to the other node, because they themselves cannot process it (each tosser has a different node number, because the systems operate on distinct outbound structures and distinct message base areas).

2.3.56 pause

Syntax:
pause
Example:
pause

Stop export echomail for this link.

2.3.57 arcmailsize

Syntax:
arcmailsize <integer>
Example:
arcmailsize 300

maximum arcmail size in kb for this link. default is 500kb.

2.3.58 allowEmptyPktPwd

Syntax:
allowEmptyPktPwd <off|secure|on>
Example:
allowEmptyPktPwd on

This flag is useful if you want to generate packet passwords for this link, but do not want to check the packet passwords that your link sends to you. This is sometimes necessary as a workaraound if your link sends you netmail packets without packet passwords, for example.

The default state is off. In this case the incoming packet password must match the packet password that you defined. This is the most secure option.

If you set this switch to secure, packets that do not contain a packet password and are received in the protected inbound will be processed. You can use this if your uplink sometimes sends you packets without packet passwords, as a workaround until the uplink has fixed his system. Still, if you receive packets with wrong packet passwords, they will be rejected.

The setting on works like the secure setting, with the difference that packets without packet passwords are allowed even in the unprotected inbound directory. It is not recommended to use this setting.

2.3.59 nodelistDir

Syntax:
nodelistDir <path>
Example:
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 section 2.3.61 nodelist). Also, compiled nodelists like the `FIDOUSER.LST' will be stored here.

This statement cannot be repeated.

2.3.60 fidoUserList

Syntax:
fidoUserList <filename>
Example:
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 section 2.3.59 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.

2.3.61 nodelist

Syntax:
Nodelist <name>
Example:
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 section 2.3.59 nodelistDir).

2.3.62 diffupdate

Syntax:
DiffUpdate <path_and_basname>
Example:
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.

2.3.63 fullupdate

Syntax:
FullUpdate <path_and_basname>
Example:
FullUpdate /var/spool/filebase/nodelist/nodelist

This statement works like DiffUpdate (see section 2.3.62 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.

2.3.64 defaultzone

Syntax:
DefaultZone <zone>
Example:
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.

2.3.65 nodelistformat

Syntax:
Nodelistformat <format>
Example:
NodelistFormat standard or 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 `points24', which is needed for the nodelist compiler to recognise a point list in the German points24 format as such, so that it can see the proper 5D point numbers instead of the fakenet numbers.

2.3.66 netmailarea

Syntax:
NetmailArea <name> <file> -b [<msgbase>] {Option}
Example:
NetmailArea netmail /var/spool/fido/msgb/netmail -b Squish

This statement specifies the netmailarea. See section 2.3.69 echoArea, for details on Option. Like all areas Netmailareas are *.msg bases per default.

This statement can be repeated to use different netmailareas.

2.3.67 badarea

Syntax:
badArea <name> <file> -b [<msgbase>] {Option}
Example:
BadArea badarea /var/spool/fido/msgb/bad -b Squish

This statement specifies the badarea. Messages which have no area on your system go to the badArea. See section 2.3.69 echoArea, for details on Option. Like all areas Badareas are *.msg bases per default.

This statement cannot be repeated.

2.3.68 dupeArea

Syntax:
dupeArea <name> <file> -b [<msgbase>] {Option}
Example:
dupeArea dupeArea /var/spool/fido/msgb/dupes -b Squish

This statement specifies the dupeArea. Messages which area dupes e.g. come to your system the second time, will be put in the dupearea. See section 2.3.69 echoArea, for details on Option. Like all areas Dupeareas are *.msg bases per default.

This statement cannot be repeated.

2.3.69 echoArea

Syntax:
EchoArea <name> <file> -b [<msgbase>] {Option} {linkAka} {linkOption}
Example:
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

This statement specifies the echoareas.

name:
area-tag
file:
filename(s) for this area without extension; should be the area-tag (as far as possible) if file == Passthrough then [<msgBase>] is skipped and msgarea is set as an passthrough area
msgbase:
*.msg is standard. Write Squish for an Squish-msgbase
LinkAKA:
aka's of up- and down links

Options:

-lr <integer>
required level for read access (see also "level" in link options)
-lw <integer>
required level for write access
-mandatory
forbid to subscibe/unsubscribe from this echo
<linkAka> -r
this link is read only
<linkAka> -w
this link is write only
<linkAka> -mn
this link is mandatory subscribed you may also set: "<aka> -r -mn" or "<aka> -w -r" and so on...
-p <integer>
purge after n days,
-$m <integer>
leave max n messages after purge in area
-killRead
kill read msgs in area on purging
-keepUnread
keep unread msgs in area on purging
-a <aka>
aka to use
-b <msgbase type>
type of msgbase (Msg, Squish, Jam)
-g <group>
group for this echoarea
-keepsb
keep seen-by's (used in CarbonCopy)
-tinysb
keep only seen-by's of links listed in {link} This statement is currently not supported.
-manual
disallow remote changes (only manual connect/disconnect). same as mandatory.
-dosfile
file name of area is in dos style (8+3)
-h
hide area
-d <"Description for the area between double quote (like this)">
describe area
-nopause
%PAUSE has no effect to this area
-ccoff
disables carbonCopies for this area
-DupeCheck off|move|del
toss in dupes, move dupes to dupeArea or delete dupes.
-DupeHistory <unsignedInteger>
size of dupecheck history file in days

LinkOption:

-imp
import only for redundant echomail-supply This statement is currently not supported.
-def
default-uplink for redundant echomail-supply This statement is currently not supported.

This statement can be repeated.

2.3.70 localArea

Syntax:
localArea <name> <file> -b [<msgbase>] {Option}
Example:
localArea linux.develop.ger /var/spool/fido/msgb/linux.develop.ger -b Squish -a 2:2433/1247 -dupeCheck move -dupehistory 11 -d "Linux development"

This statement creates an localArea. The only difference between a localArea and a echoArea is that a localArea has no links and is not scanned for new mails.

This statement can be repeated.

2.3.71 PublicGroup

Syntax:
PublicGroup {<groups>}
Example:
PublicGroup abcde12

Tis is a list of groups for public echo acess.

2.3.72 GroupAutoAreaCreate

Syntax:
GroupAutoAreaCreate on|off {<groups>}
Example:
GroupAutoAreaCreate on fidonet fido.de

You can here define for all the members of a group, if they area allowed to autoCreate areas on your system. If no group is given, this is default for all groups.

This statement is currently not supported.

2.3.73 AutoCreateDefaults

Syntax:
AutoCreateDefaults <string>
Example:
AutoCreateDefaults -$m 200 -dupeCheck move -dosfile -d "Autocreated area"

Area options defaults for autoCreated Areas.

This will be replaced by the more flexible group definition.

2.3.74 GroupDefaults

Syntax:
GroupDefaults <groups> <path> [<msgbas>] {<option>} {<linkAka> {linkoption}}
Example:
GroupDefaults fidonet /var/spool/fido/msgb Squish -$m 200 -dupeCheck move -dupeHistory 14 -d "Autocreated Area"

This statement sets the default for auto created Areas according to the group of the creater.

This is currently not supported

2.3.75 Pack

Syntax:
Pack zip|tgz|rar|arc|arj|..... <call>
Example:
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 archiv, that means the file will be deleted on the harddisk. It only remains in the archiv.

$a will be replaced by the archiv file

$f will be replaced by the file which should be packed into the archiv

2.3.76 Unpack

Syntax:
Unpack "<Call>" <offset> <matchcode>
Example:
Unpack "unzip -joLqq $a -d $p" 0 504b0304

This statement sets the call of certain unpackers according to a id in the archiv file

call: see pack

offset: position of recognition string in packed file.

offset ::= <hexValue>

match code: recognition string for packed file, ?? can be used as don't care

$p will be replaced by the temp inbound path


e.g.: unpack "unzip -joLqq $a -d $p" 0 504b0304

       files packed by zip can be recognized by
         504b0304(hex) at offset 0(hex)
       they can be unpacked by "unzip -joLqq <filename> -d <path>"

2.3.77 afterUnpack

Syntax:
afterUnpack <string>
Example:
afterUnpack pktpack /home/fido/in.tmp/*.pkt

This <string> executes after unpacking arcmail bundle. You may process your pkt files in tempInbound directory with external utility.

2.3.78 beforePack

Syntax:
beforePack <string>
Example:
beforePack pktpack /home/fido/out.tmp/*.pkt

This <string> executes before packing pkt files to arcmail bundles. You may process your pkt files in tempOutbound directory with external utility.

2.3.79 route

Syntax:
route <flavour> [enc|noenc] <target> {<linkWW>}
Example:
route crash 2:2433/1245 2:2433/* 2:2432/*

This statement defines a route.

flavour:

  1. hold
  2. normal
  3. crash
  4. direct
  5. immediate

enc: means encrypted msgs

noenc: means unencrypted msgs

target:

  1. <aka>
  2. host
  3. hub
  4. boss
  5. no-route

linkWW is a dos pattern with ? and *.

Route statements are parsed in descending order: Pseudo-code:

  1) actual = first statement

  2) if linkWWW = msg-destination using pattern matching

  2a) take this routing and return

  2b) else actual = next statement

  3) jump to 2)
  

if no route statement found whose pattern matchs witch the aka, then the mail is left alone.

2.3.80 routeFile

Syntax:
routeFile <flavour> [enc|noenc] <target> {<linkWW>}
Example:
routeFile crash 2:2433/1245 2:2433/* 2:2432/*

This statement is the same as the route statement, but considers only msgs with an file attached.

2.3.81 routeMail

Syntax:
routeMail <flavour> [enc|noenc] <target> {<linkWW>}
Example:
routeMail crash 2:2433/1245 2:2433/* 2:2432/*

This statement is the same as the route statement, but considers only msgs without file attached.

2.3.82 carbonTo

Syntax:
carbonTo <name>
Example:
carbonTo Max Levenkov

If an echomail is tossed whose to-field is the same as <name>, the echomail is copied to the area specified by the carbonArea keyword. The names must be an exact match.

This statement can be repeated.

2.3.83 carbonFrom

Syntax:
carbonFrom <name>
Example:
carbonFrom Matthias Tichy

If an echomail is tossed whose from-field is the same as <name>, the echomail is copied to the area specified by the carbonArea keyword. The names must be an exact match.

This statement can be repeated.

2.3.84 carbonKludge

Syntax:
carbonKludge <kludge-substring>
Example:
carbonKludge MSGID: 2:5000/117.

If an echomail is tossed which has a kludge line which includes the <kludge- string> as a substring, he echomail is copied to the area specified by the arbonArea keyword.

This statement can be repeated.

2.3.85 carbonSubj

Syntax:
carbonSubj <subj-substring>
Example:
carbonSubj beer

If an echomail is tossed which has a subject line which includes the <subj- string> as a substring, this echomail is copied to the area specified by the arbonArea keyword.

This statement can be repeated.

2.3.86 carbonText

Syntax:
carbonText <text-substring>
Example:
carbonText cool beer

If an echomail is tossed which has a kludge line which includes the <text- string> as a substring, he echomail is copied to the area specified by the arbonArea keyword.

This statement can be repeated.

2.3.87 carbonArea

Syntax:
carbonArea <area-tag>
Example:
carbonArea written.from.points

This statement sets the area for the previous carbon{To|From|Kludge} statement. If this statement is ommitted. The carbon Copy goes to the badArea.

This statement can be repeated for each different carbon{To|From|Kludge} statement.

2.3.88 carbonArea

Syntax:
carbonCopy <area-tag>
Example:
carbonCopy written.from.points

This statement sets the area for the previous carbon{To|From|Kludge} statement. If this statement is ommitted. The carbon Copy goes to the badArea.

This statement can be repeated for each different carbon{To|From|Kludge} statement. It's similiar to carbonArea, which I (KN) propose to remove

2.3.89 carbonArea

Syntax:
carbonMove <area-tag>
Example:
carbonMove written.from.points

This statement sets the area for the previous carbon{To|From|Kludge} statement. If this statement is ommitted. The carbon msg gets moved to the badArea.

This statement can be repeated for each different carbon{To|From|Kludge} statement. Unlike carbonArea and carbonCopy msg gets moved, not copied into this area

2.3.90 carbonArea

Syntax:
carbonExtern <program name>
Example:
carbonExtern douuedecode

This statement specifies external program to run for the previous carbon{To|From|Kludge} statement. If this statement is ommitted. The carbon msg gets moved to the badArea.

This statement can be repeated for each different carbon{To|From|Kludge} statement. If program name is prepended with '|' sign, hpt tries to pass data thru the pipe, not temporary file.

2.3.91 carbonArea

Syntax:
carbonDelete <program name>
Example:
carbonDelete douuedecode

This statement specifies that selected by previous carbon{To|From|Kludge} statement msg should not be stored into echoarea.

This statement can be repeated for each different carbon{To|From|Kludge} statement.

2.3.92 carbonAndQuit

Syntax:
carbonAndQuit
Example:
carbonAndQuit

By default one message can be processed by Carbon Copy several times. For example: you set CarbonTo "max" to echoarea MY.MAIL and CarbonSubj "beer" to echoarea MY.PLEASURE :-) And message to "max" and with this subject line carbons to each echoarea. If you turn on <carbonAndQuit> message will copy to MY.MAIL only.

2.3.93 carbonKeepSb

Syntax:
carbonKeepSb
Example:
carbonKeepSb

For each CC message SEEN-BY's and PATH fields are killed. If you set up carbonKeepSb then all kludges will be saved. But you may also set up -keepsb in options of echoarea where you carbon messages.

2.3.94 carbonReason

Syntax:
carbonReason <string>
Example:
carbonText msged carbonReason Found 'msged' in message carbonArea my.searches.echo

This statement sets the 'reason string' for the previous carbon{To|From|Kludge|Subj|Text} statement.

This string would be printed after ' * Forwarded ...' line in message begining. That's useful when many carbons are made to single area. No reason string is printed if this statement is ommitted.

This statement can be repeated for each different carbon{To|From|Kludge|Subj|Text} statement.

2.3.95 areafixFromPkt

Syntax:
areafixFromPkt
Example:
areafixFromPkt

Process areafix requests on the fly. Check "areafix", "areamgr" & "hpt" keywords in toUserName field.

2.3.96 areafixKillReports

Syntax:
areafixKillReports
Example:
areafixKillReports

Set kill/sent flag to areafix reports.

2.3.97 ReportTo

Syntax:
ReportTo <name>
Example:
ReportTo netmail

Set area or netmail for areafix reports.

2.3.98 areafixMsgSize

Syntax:
areafixmsgsize <integer>
Example:
areafixmsgsize 20

this option set up maximum areafix message size (20 kb) if not defined, areafix reports will be not splitted...

2.3.99 areafixSplitStr

Syntax:
areafixSplitStr <string>
Example:
areafixSplitStr > Message splitted. To be continued...

this string added after splitted araefix message.

2.3.100 logEchoToScreen

Syntax:
logEchoToScreen
Example:
logEchoToScreen

Set output to screen log messages.

2.3.101 Remap

Syntax:
Remap <toUserName>,<toAka>,<newAka>
Example:
Remap Max Levenkov,2:5000/117,2:5000/117.1

Remap mail to other address.

2.3.102 SeparateBundles

Syntax:
SeparateBundles
Example:
SeparateBundles

This statament move echomail for all links to his own directory.

2.3.103 defarcmailsize

Syntax:
defarcmailsize <integer>
Example:
defarcmailsize 1024

default arcmail size in kb for all links. 500kb if not defined.

2.3.104 ignoreCapWord

Syntax:
ignoreCapWord
Example:
ignoreCapWord

ignoring Capability Word in pkt files. if some pkt moved to bad. this may help, but not recommended. it is better to change old software.

2.4 Working sample config

# sample fido config file

version 0.14 # test for new stripComment
Name hpt-HQ 
Location Paderborn, GER
Sysop Matthias Tichy

LogLevels 456789

Address 2:2432/645
address 2:2432/605.14
Address 2:2433/1247 #
Address 2:2433/1245.1
Address 44:4932/110
Address 44:4932/100.14

# This is taken from Serge Koghin's ParToss
# Hope he wouldn't be angry for this
# ATTENTION the commeneed lines are not tested by me (mtt)
# and will mostly only useful on dos-systems
 
Unpack  "unzip  -j -Loqq $a -d $p" 0 504b0304
Pack  zip zip -9 -j -q $a $f

#Unpack  "pkunpak /r $a $p" 0 1a
#Pack  arc pkpak -oct a $a $f
 
#Unpack  "pak e /wn $a $p" -2 fe
#Pack  pak pak a $a $f
 
#Unpack  "lha e /m $a $p" 2 2d6c68
#Pack  lha lha a /o /m $a $f
 
#Unpack  "zoo e:O $a $p" 0 5a4f4f
#Pack  zoo zoo a: $a $f
 
#Unpack  "arj e -+ -y $a $p" 0 60ea
#Pack  arj arj a -+ -e -y $a $f

Unpack  "unrar e -y  $a $p \* > /dev/null"   0 52617221
#Pack  rar rar a -std -ep $a $f
 
#Unpack  "jar e -y $a $p" 14 1a4a61721b
#Pack  jar jar a -y $a $f
 
#Unpack  "ha eyq $a"  0 4841
#Pack  ha ha a21eq $a $f

# include /etc/fido/areas

Link Matthias Schniedermeyer
Aka 2:2432/600
ourAka 2:2432/645
Password xxxxxxx
EchoMailFlavour Crash
AutoAreaCreate on
AutoAreaCreateDefaults -p 14 -dupeCheck move -dupeHistory 11
AutoFileCreate on
forwardRequests on
Packer zip

Link Matthias Schniedermeyer
Aka 44:4932/100
ourAka 44:4932/110
password xxxxxxx
EchoMailFlavour Crash
AutoAreaCreate on
AutoAreaCreateDefaults -p 14 -dupeCheck move -dupeHistory 11
Packer zip

Link Carsten Ellermann
Aka 2:2432/215
ourAka 2:2432/645
password xxxxxxxx
autoAreaCreate on
AutoAreaCreateDefaults -p 14 -dupeCheck move -dupeHistory 11
autoFileCreate on

Link Matthias Tichy
Aka 2:2432/646
ourAka 2:2432/645
Password xxxxxxxx
autoAreaCreate on
AutoAreaCreateDefaults -p 14 -dupeCheck move -dupeHistory 11
forwardPkts on

#route crash 2:2433/1245 *
#route hold  2:2433/1247.100 2:2433/1247.100
#route Crash  2:2433/1245 2:2433/* 
#route hold noroute 2:2433/1245.*
#route crash host 2:2433/*
#route crash enc no-route *

route hold noroute 2:2432/645.*
Route crash 44:4932/100 44:*
route crash noroute 2:2432/646
Route crash 2:2432/600 *

Inbound		/home/mtt/fido/in/
ProtInbound	/home/mtt/fido/in.sec
LocalInbound    /home/mtt/fido/in.loc
Outbound	/home/mtt/fido/out/
tempOutbound    /home/mtt/fido/out.tmp
tempInbound     /home/mtt/fido/in.tmp
#MsgBaseDir      Passthrough
MsgBaseDir      /home/mtt/fido/msgb
FileAreaBaseDir /home/mtt/fido/files

public		/home/mtt/fido/public
# public		/home/mtt/fido/public2

# intab           /home/mtt/fido/recode/outaltkoi8
# outtab          /home/mtt/fido/recode/outkoi8alt

echotosslog     /home/mtt/fido/echotoss.log
importlog       /home/mtt/fido/import.log

logFileDir      /home/mtt/fido/hpt/linux
DupeHistoryDir	/home/mtt/fido/dupes
NodelistDir	/home/mtt/fido/nodelist
magic		/home/mtt/fido/magic
lockfile        /home/mtt/fido/lock

areafixhelp     /home/mtt/fido/hpt/misc/areafix.hlp
FileFixHelp     /home/mtt/fido/htick/misc/filefix.hlp

NetmailArea NetmailArea /home/mtt/fido/msgb/netmail -b msg
# NetmailArea NetmailArea /home/mtt/fido/msgb/net -b  Squish
BadArea     BadArea     /home/mtt/fido/msgb/bad -b Squish
DupeArea    DupeArea    /home/mtt/fido/msgb/dupe -b Squish

EchoArea 2432.points      /home/mtt/fido/msgb/2432/points       -a 2:2432/645  -b  Squish -p 14 2:2432/600 
EchoArea 2432.Talk        /home/mtt/fido/msgb/2432/talk         -a 2:2432/645  -b  Squish -p 14 2:2432/600
EchoArea C_ECHO.ger       /home/mtt/fido/msgb/c_echo_g          -a 2:2432/645  -b  Squish -p 14 2:2432/600
EchoArea C_PLUSPLUS.ger   /home/mtt/fido/msgb/c_plpl_g          -a 2:2432/645  -b  Squish -p 14 2:2432/600 
EchoArea binkley          /home/mtt/fido/msgb/binkley           -a 2:2432/645  -b  Squish -p 14 2:2432/600
EchoArea Binkley.ger      /home/mtt/fido/msgb/binkley_g         -a 2:2432/645  -b  Squish -p 14 2:2432/600
EchoArea hardrock.ger     /home/mtt/fido/msgb/hardrock_g        -a 2:2432/645  -b Squish -p 14 2:2432/600
EchoArea   linux.ger        /home/mtt/fido/msgb/linux/ger           -a 2:2432/645  -b Squish -p 14 -dupecheck move -dupeHistory 11  2:2432/600
echoArea linux.develop.ger /home/mtt/fido/msgb/linux/develop_g   -a 2:2432/645 -b Squish  -dupeCheck move -dupeHistory 11  2:2432/600
#echoarea linux.ger /home/mtt/fido/msgb/linux/ger -a 2:2433/1247 -b Squish 2:2433/1245 2:2433/1200
# echoarea linux.develop.ger /home/mtt/fido/msgb/linux/develop_g -a 2:2433/1247 -b Squish 2:2433/1245 2:2423/605 2:2433/1245.100
EchoArea os2.base.ger     /home/mtt/fido/msgb/os2/base_g        -a 2:2432/645  -b Squish -p 14 2:2432/600 
EchoArea os2.beta.ger     /home/mtt/fido/msgb/os2/beta_g        -a 2:2432/645  -b Squish -p 14 2:2432/600
EchoArea os2bbs.ger       /home/mtt/fido/msgb/os2/bbs_g         -a 2:2432/645  -b Squish -p 14 2:2432/600
EchoArea os2.debate.ger   /home/mtt/fido/msgb/os2/debate_g      -a 2:2432/645  -b Squish -p 14 2:2432/600
EchoArea os2.install.ger  /home/mtt/fido/msgb/os2/install_g     -a 2:2432/645  -b Squish -p 14 2:2432/600 
EchoArea Os2.wps.ger      /home/mtt/fido/msgb/os2/wps_g         -a 2:2432/645  -b Squish -p 14 2:2432/600 
EchoArea Os2.prog.ger     /home/mtt/fido/msgb/os2/prog_g        -a 2:2432/645  -b Squish -p 14 2:2432/600
EchoArea Os2.lan.ger      /home/mtt/fido/msgb/os2/lan_g         -a 2:2432/645  -b Squish -p 14 2:2432/600
EchoArea os2.hw.ger       /home/mtt/fido/msgb/os2/hw_g          -a 2:2432/645  -b Squish -p 14 2:2432/600 
EchoArea os2.online.ger   /home/mtt/fido/msgb/os2/online_g      -a 2:2432/645  -b Squish -p 14 2:2432/600
EchoArea os2.tec.ger      /home/mtt/fido/msgb/os2/tec_g         -a 2:2432/645  -b Squish -p 14 2:2432/600 
EchoArea OWL.Newfiles     /home/mtt/fido/msgb/owl/newfiles      -a 2:2432/645  -b Squish -p 14 2:2432/600
EchoArea owl.announce     /home/mtt/fido/msgb/owl/announce      -a 2:2432/645  -b Squish -p 14 2:2432/600
EchoArea owl.flea         /home/mtt/fido/msgb/owl/flea          -a 2:2432/645  -b Squish -p 14 2:2432/600
EchoArea owlserver.news   /home/mtt/fido/msgb/owl/snews         -a 2:2432/645  -b Squish -p 14 2:2432/600 
EchoArea Paderborn.Flohmarkt  /home/mtt/fido/msgb/pader/floh    -a 2:2432/645  -b Squish -p 14 2:2432/600
EchoArea Tolkien.ger      /home/mtt/fido/msgb/tolkien_g         -a 2:2432/645  -b Squish -dupeCheck move -p 14 2:2432/600
EchoArea Schweden.ger     /home/mtt/fido/msgb/schweden_g        -a 2:2432/645  -b Squish -tinySB -p 14 2:2432/600

LocalArea carbonArea       /home/mtt/fido/msgb/carbonArea  -b Squish

CarbonTo Matthias Tichy
CarbonArea carbonArea

EchoArea paderborn.mailbox /home/mtt/fido/msgb/paderborn.mailbox -a 2:2432/645 -b  Squish -dupeCheck move -dupeHistory 11 -p 14 2:2432/600
EchoArea owl.allfix /home/mtt/fido/msgb/owl.allfix -a 2:2432/645 -b  Squish -p 14 -dupeCheck move -dupeHistory 11 2:2432/600
EchoArea fidosoft.winpoint.ger /home/mtt/fido/msgb/fidosoft.winpoint.ger -a 2:2432/645 -b  Squish -p 14 -dupeCheck move -dupeHistory 11 2:2432/600
EchoArea net_dev.ger /home/mtt/fido/msgb/net_dev.ger -a 2:2432/645 -b  Squish -p 14 -dupeCheck move -dupeHistory 11 2:2432/600
EchoArea net_dev /home/mtt/fido/msgb/net_dev -a 2:2432/645 -b  Squish -p 14 -dupeCheck move -dupeHistory 11 2:2432/600
EchoArea fidosoft.ger /home/mtt/fido/msgb/fidosoft.ger -a 2:2432/645 -b  Squish -p 14 -dupeCheck move -dupeHistory 11 2:2432/600
EchoArea linux.bbs /home/mtt/fido/msgb/linux.bbs -a 44:4932/110 -b  Squish -p 14 -dupeCheck move -dupeHistory 11 44:4932/100 
EchoArea linux.software /home/mtt/fido/msgb/linux.software -a 44:4932/110 -b  Squish -p 14 -dupeCheck move -dupeHistory 11 44:4932/100
EchoArea linux.setup /home/mtt/fido/msgb/linux.setup -a 44:4932/110 -b  Squish -p 14 -dupeCheck move -dupeHistory 11 44:4932/100 
EchoArea linux.reg /home/mtt/fido/msgb/linux.reg -a 2:2432/645 -b  Squish -p 14 -dupeCheck move -dupeHistory 11 2:2432/600 
EchoArea linux.netzwerk /home/mtt/fido/msgb/linux.netzwerk -a 44:4932/110 -b  Squish -p 14 -dupeCheck move -dupeHistory 11 44:4932/100
EchoArea linux.announce /home/mtt/fido/msgb/linux.announce -a 44:4932/110 -b  Squish -p 14 -dupeCheck move -dupeHistory 11 44:4932/100
EchoArea linux.hardware /home/mtt/fido/msgb/linux.hardware -a 44:4932/110 -b  Squish -p 14 -dupeCheck move -dupeHistory 11 44:4932/100
EchoArea darkness.info /home/mtt/fido/msgb/darkness.info -a 2:2432/645 -b  Squish -p 14 -dupeCheck move -dupeHistory 11  2:2432/600
EchoArea linux.coord /home/mtt/fido/msgb/linux.coord -a 44:4932/110 -b  Squish -p 14 -dupeCheck move -dupeHistory 11 44:4932/100
EchoArea 2432.nodes.info /home/mtt/fido/msgb/2432.nodes.info -a 2:2432/645 -b  Squish -p 14 -dupeCheck move -dupeHistory 11 2:2432/600
EchoArea linux.office /home/mtt/fido/msgb/linux.office -a 44:4932/110 -b  Squish -p 14 -dupeCheck move -dupeHistory 11 44:4932/100
EchoArea linux.develop /home/mtt/fido/msgb/linux.develop -a 44:4932/110 -b  Squish -p 14 -dupeCheck move -dupeHistory 11  44:4932/100
EchoArea linux.x /home/mtt/fido/msgb/linux.x -a 44:4932/110 -b  Squish -p 14 -dupeCheck move -dupeHistory 11  44:4932/100
EchoArea 2432.nodes /home/mtt/fido/msgb/2432.nodes -a 2:2432/645 -b  Squish -p 14 -dupeCheck move -dupeHistory 11 2:2432/600
EchoArea fido2000.ger /home/mtt/fido/msgb/fido2000.ger -a 2:2432/645 -b  Squish -p 14 -dupeCheck move -dupeHistory 11 2:2432/600
EchoArea java.ger /home/mtt/fido/msgb/java.ger -a 2:2432/645 -b  Squish -p 14 -dupeCheck move -dupeHistory 11 2:2432/600
EchoArea ftsc_public /home/mtt/fido/msgb/ftsc_public -a 2:2432/645 -b  Squish -p 14 -dupeCheck move -dupeHistory 11 2:2432/600
EchoArea BINKLEY.DEVELOP /home/mtt/fido/msgb/binkley.develop -a 2:2432/645 -b  Squish -p 14 -dupeCheck move -dupeHistory 11 2:2432/215

FileArea binkley.dev /home/mtt/fido/files/binkley.dev -a 2:2432/645  -d "Binkleyterm Development: Source Diffs, Misc, stuff" 2:2432/215
FileArea btxebos2 /home/mtt/fido/files/btxebos2 -a 2:2432/645  -d "Binkleyterm Development: Beta Binaries for OS/2" 2:2432/215
FileArea btxebsrc /home/mtt/fido/files/btxebsrc -a 2:2432/645  -d "Binkleyterm Development: Beta Source" 2:2432/215
FileArea btxebw32 /home/mtt/fido/files/btxebw32 -a 2:2432/645  -d "Binkleyterm Development: Beta Binaries for Win32" 2:2432/215

EchoArea golded.ger /home/mtt/fido/msgb/golded.ger -b Squish -a 2:2432/645 -p 14 -dupeCheck move -dupeHistory 11 2:2432/600

EchoArea darkness.points /home/mtt/fido/msgb/darkness.points -a 2:2432/645 -b  Squish -p 14 -dupeCheck move -dupeHistory 11 2:2432/600
EchoArea linux.fido.ger /home/mtt/fido/msgb/linux.fido.ger -a 2:2432/645 -b Squish -p 14 -dupeCheck move -dupeHistory 11 2:2432/600
EchoArea FUSSBALL.GER /home/mtt/fido/msgb/fussball.ger -a 2:2432/645 -b Squish -p 14 -dupeCheck move -dupeHistory 11 2:2432/600
EchoArea PGP.GER /home/mtt/fido/msgb/pgp.ger -a 2:2432/645 -b Squish -p 14 -dupeCheck move -dupeHistory 11 2:2432/600
EchoArea HARDWARE.SCSI.GER /home/mtt/fido/msgb/hardware.scsi.ger -a 2:2432/645 -b Squish -p 14 -dupeCheck move -dupeHistory 11 2:2432/600
EchoArea TV.GER /home/mtt/fido/msgb/tv.ger -a 2:2432/645 -b Squish -p 14 -dupeCheck move -dupeHistory 11 2:2432/600
EchoArea CDWRITER.GER /home/mtt/fido/msgb/cdwriter.ger -a 2:2432/645 -b Squish -p 14 -dupeCheck move -dupeHistory 11 2:2432/600
EchoArea FASTECHO.GER /home/mtt/fido/msgb/fastecho.ger -a 2:2432/645 -b Squish -p 14 -dupeCheck move -dupeHistory 11 2:2432/600
EchoArea URTEILE.GER /home/mtt/fido/msgb/urteile.ger -a 2:2432/645 -b Squish -p 14 -dupeCheck move -dupeHistory 11 2:2432/600
EchoArea PRO_WRESTLING /home/mtt/fido/msgb/pro_wrestling -a 2:2432/645 -b Squish -p 14 -dupeCheck move -dupeHistory 11 2:2432/600
EchoArea SPORT.EISHOCKEY.GER /home/mtt/fido/msgb/sport.eishockey.ger -a 2:2432/645 -b Squish -p 14 -dupeCheck move -dupeHistory 11 2:2432/600
EchoArea RAETSEL.GER /home/mtt/fido/msgb/raetsel.ger -a 2:2432/645 -b Squish -p 14 -dupeCheck move -dupeHistory 11 2:2432/600
EchoArea WRESTLING.GER /home/mtt/fido/msgb/wrestling.ger -a 2:2432/645 -b Squish -p 14 -dupeCheck move -dupeHistory 11 2:2432/600

3 Converting fidoconfig to golded, msged and aquaed

Since goldEd not support fidoconfig, and msged and aquaed only in beta versions, we have developed two programs which converts your fidoconfig to the proprietary config file format.

  1. fconf2golded fconf2golded <goldedConfigFileName> [<default.cfg>]
    fconf2golded ~/golded/golded.cfg ~/golded/goldDefaults.cfg
    
  2. fconf2msged fconf2msged <msgedConfigFileName>
    fconf2msged ~/msged.areas
    
  3. fconf2aquaed fconf2aquaed <aquaedConfigFileName> [<default.cfg>] (if you specify default.cfg there will be a include <default.cfg> generated in your config file)
    fconf2aquaed ~/aquaed/aquaed.cfg
    

4 Testing the config

You should run tparser everytime you have changed the config. If tparser crashes please correct your config file and send your config or the line which causes the crash.

./tparser | less

tparser (like any fidoconfig program) will display error messages if you have made an error in the config. It will grumble on every Keyword it does not know. It will stop after the first error to give you the ability to change your config.

5 Contacting the author

You can reach me at

@email{mtt@tichy.de}
2:2432/605.14
2:2433/1245

and in the fido echoarea

linux.develop.ger

The actual fidoconfig library and other fido software will be on www.tichy.de.


This document was generated on 11 January 2000 using the texi2html translator version 1.51.