home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ARM Club 3
/
TheARMClub_PDCD3.iso
/
hensa
/
internet
/
fidomail_1
/
!FidoMail
/
Dox
/
Config
< prev
next >
Wrap
Text File
|
1994-02-19
|
11KB
|
279 lines
Config file syntax
------------------
The Config file contains information about your system and your preferences.
It consists of lines of the following form:
<command> <parametres>
If the first char on a line is '|', the rest of the line is ignored.
The <command> is one of the words defined below.
The <parametres> are any numbers or strings required by the command, separated
by spaces.
Strings must be surrounded by "" if they contain spaces.
The order of the commands is currently of no significance.
Mandatory commands.
-------------------
There are certain commands which MUST be there. These are:
Address <zone>:<net>/<node>.<point>
This is to tell FidoMail your fidonet address.
Sysop <name>
Your name for writing mail, and for spotting mail addressed to you.
The 'Address' and 'Sysop' commands actually just set the first AKA you have.
You can therefore omit them and have an AKA line instead, if you wish.
Origin <origin_line>
This line is written at the bottom of your echomails. See the 'ExpandInfo' file
if you wish to have a fancy origin line.
RouteMap <dest_addr> <scan_addr> [H]
You should have at least one of these lines. It tells FidoMail how to route
netmails, normally they are all routed to your boss. More details below.
Also, you must have a 'SetArea' command for both netmail and junk, these are
described below.
Other commands.
---------------
Include <filename>
This command can be used to split the configuration into several files.
You could, for example, have a separate file with the area-definitions
(described below), and then use 'Include <FidoMail$Dir>.!Areas' in the main
config file. DO NOT include a file from within itself!
AKA <zone>:<net>/<node>.<point> <name>
This line will make FidoMail accept packets for other systems than the one
given in the 'Address' line. You will need to use this if you are receiving
packets from more than one node.
The <name> is what name you want to use when writing from this address.
You will be able to select which AKA to use from the summary and outgoing
windows.
SetArea <name> ECHO <id> [<options>]
This command is used for defining an area. You must define an area if you wish
to be able to read and write messages in it.
The <name> is any name you want to give to the area. It is usually a prettier
version of the <id>. (Eg. "Archimedes Communications" instead of "ARCCOMMS")
The <id> is the fidonet identifier of the area. (Eg. "ARCCOMMS")
<options> is any number of these special keywords:
ReadOnly If this is used, you will not be able to write messages in the
area.
FileLists This makes the 'Reply' button initiate a file request from the
sender of the message. Also, if you click in the message text,
the freq filename will be the first word of the line on which
you clicked.
SetArea <name> NET
This command is used for defining the netmail area. You must have exactly one
of these lines in your config file.
SetArea <name> JUNK
This command is used for defining the junk area. As with netmail, you must
have exactly one of these. The junk area is used if you get mail in an area
which isn't defined. If you ever see mail in the junk area, check the area-ID
with 'Full info' and define the area if you expect to receive more.
RouteMap <dest_addr> <scan_addr> [H]
Lines of this form defines the route map. It is used for netmails only, and
determines where to send them if they have got a specific destination address.
For example, if you write a netmail to Australia, you wouldn't want your
computer to actually call Australia and deliver the mail (unless you actually
live there of course). Instead, you send the mail to your boss, who then in
turn sends it to his boss and so on... until the mail arrives at it's
destination. The way to do that is to set up different routes for different
destinations. To define that example, if your boss is called 2:252/102.0:
RouteMap 3:*/*.* 2:252/102.0
So everything aimed at zone 3 (where Austalia is) will instead go to 252/102.
The '*' means any number. Now, if you live in zone 2, you wouldn't want to
write the above line for each possible zone, so there's an easier way. The
RouteMap lines are checked from the top until FidoMail meets a line that
matches the destination address. So, for example, to make everything to zone 2
go direct, and everything else via 252/102, you would write:
RouteMap 2:*/*.* 2:*/*.*
RouteMap *:*/*.* 2:252/102.0
Note that the stars in the <scan_addr> means that the real destination numbers
will be used there. You should always have a '*:*/*.*' at the end of your
RouteMap list, to ensure that there is always somewhere to send netmails.
If you haven't got that, and a netmail comes in with a destination which can't
be found in the route map, it will be put on hold for that destination, so
your system will not begin calling anywhere unpleasant.
(This is equivalent to a 'RouteMap *:*/*.* *:*/*.* H' at the end of the list)
Let's take a final example. You may need to send all national netmails to your
boss, all international mail to another node, and if you have any points, you
would want to put everything to those on hold for them to pick it up.
So, if you are called 2:252/256.0, your boss is 2:252/102.0, and the
international node is 2:254/27.0, you would write:
RouteMap 2:252/456.* 2:252/456.* H
RouteMap 2:25?/*.* 2:252/102.0
RouteMap *:*/*.* 2:254/27.0
There are some unknown things here: Appending an 'H' to the line means 'put the
packet on hold', so your system won't dial out, but wait for someone to call
and fetch the packet.
'?' means 'any digit', so 25? matches the numbers from 250 to 259.
If the netmail has crash status, the routing is disabled.
DummyPkt <addr>
When scanning, FidoMail will normally generate a 'dummy packet' to your
boss. This is to force the mailer to call your boss, even if you don't have any
mail for him. You may want to change this or turn it off (e.g. if your boss
calls you), by writing another address or omitting this line.
5DOutbond <directory>
This command will change the format of the outbound files. The files will then
end up as '<FM$Outbound$Dir>.<directory>.zzzznnnn.ooooppppxx' instead of
'<FM$Outbound$Dir>.nnnnooooxx'.
Spark <pathname>
This command is used to define the location of Spark. It is needed if you
wish to be able to use '-unarc' or '-sparkmail' or the equivalent menu entries.
SparkMail <pathname>
This command is used to define the location of SparkMail. It is needed if
you wish to be able to use '-sparkmail' or the equivalent menu entry.
Quote <quote_header>
Footer <footer>
TearLine <tearline>
These commands defines the quote-header, footer, and tear line. See the file
'ExpandInfo' for details.
ForwardFile <filename>
GroupSplit <filename>
These commands points to files, which defines the format of forwarded messages,
and how saved groups should look. See the file 'SaveAGroup' for details.
DateFormat <format>
TimeFormat <format>
These commands defines how you want the date and time to appear when using %d
and %t in footers, quote-headers etc. The <format> is a string with the same
syntax as Sys$DateFormat uses.
WeedType <name> <flags>
This command defines a weedtype. See the 'WeedHelp' file for details.
ArcMail <pattern>
MailPkt <pattern>
These commands defines what pattern is used when looking after inbound
mail-files. ArcMail files are arc'ed MailPkt files, and are unarced before
being tossed. See the default Config file for the most common definitions.
BaseOrder <sort_method>
This command instructs FidoMail to keep the message base sorted with the given
<sort_method>. The sort method is one of the following:
'Date',
'Subject',
'Sender',
'Area'.
If any other method is given (or the command is missing), the 'Area'-method
is selected. This order of the messages is not defined with this method
(but in the current version, they are actually sorted by their size).
The message base will be completely resorted after a toss. The 'Area' method
is barely noticeable, but the others takes time. If you are using a floppy-
msgbase and are tossing manually, it may become annoying.
FidoMail keeps a record of how the base is currently sorted, and will keep it
that way until you specify otherwise. If you change the sorting method using
the Sort-menu, FidoMail will resort the messages next time it starts up.
This can be avoided by _not_ having a 'BaseOrder' command in the Config file.
The order of the base will then remain as after the last sort requested.
EditAll
This command defines the default state of the 'Edit all' switch in the incoming
window. Present=On.
OutMaximise
This is what the outgoing editor does when you move beneath the bottom edge of
the window. If there's room on the screen and this command is present, it will
extend itself.
OpenSummary
OpenStatus
Including these commands will open the summary and/or status windows whenever
you start FidoMail.
QuickToss
This will reserve space on the disc before tossing, so use it if you have the
space. It will speed the toss up by about 1.8 times.
AutoBook <mode>
If this line is omitted, the address book will never update itself unless
requested by you. If it is present, you have 2 choices:
1. AutoBook Quiet
2. AutoBook Confirm
1. will make FidoMail change the address book, if it discovers that a known
person is using a different number. It will also add any unknown persons,
if you write netmail to them.
2. will do the same, but it will ask for confirmation before updating the
address book.
AutoWeed <id> <flags>
Lines of this type defines an autoweed sequence. The <id> is the area
identifier of the area you want to weed in, and the <flags> are equivalent
to the ones in the WeedType command. When an autoweed is requested, the
message base is weeded according to these lines, from the first to the last.
That way you can have different 'expiry' dates on different areas, and you can
choose to keep e.g. personal mail longer than all the rest.
There are 3 special kinds of <id>:
'<NET>' is the netmail area.
'<JUNK>' is the junkarea.
'<ALL>' will weed in all the areas.
AutoWeedAfter <action>
This command will make FidoMail initiate an autoweed operation after <action>
has happened. <action> can be one of:
'Scanning' will autoweed after scanning
'Startup' will autoweed every time you start the program.
This command has no influence on your ability to use the -autoweed CLI-option.
NoFuss
This command will disable the warnings given when you are about to discard an
edited outgoing message.
KeepLogOpen
Including this command will cause the log file to be kept open while FidoMail
is running. The result is faster operation, especially on floppy.