home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Crawly Crypt Collection 1
/
crawlyvol1.bin
/
bbs
/
iosmailn
/
ios_uk.doc
next >
Wrap
Text File
|
1992-08-16
|
142KB
|
4,462 lines
Eddie Tao
THE
// //====// //====//
//// //// //// ////
//// //// //// ////
// // // //=====//
//// //// //// ////
//// //// //// //// //\/\ //\ | |
// //====// //====// // \//__\ | |__
MANUAL
_______________________________
__________________________________
/ / Inmail <<- - - - - - - - /-/ - - -
/ /
/ / OutMail - -- - - - - - -/ - - ->>
/ ^ ^ ^ /
/ / ScanMail <<- -|- -|- -|- - / /
-----------------------------------
-------------------------------
/ /====/ /====/
/// /// /// ///
/// /// /// ///
/ / / /=====/
/// /// /// ///
/// /// /// /// /\/\ /\ ||
/ /====/ /====/ / \/__\||__
Coded by Rinaldo Visscher
/ / / IOSmail Manual / / /
/ / / for / / /
version 0.89
/ / / / / /
/ / / 15 August 1992 / / /
IOSmail Manual : Eddie Tao and Dennis Steen
Chief Editor : Eddie Tao
Editor : STeVeN Green
Edited with : That's Write 2.05
Copyright 1991, 1992 Eddie Tao
Program : IOSmail
Coded by : Rinaldo Visscher
Coded in : Turbo C 2.00
Copyright 1991, 1992 Rinaldo Visscher
All rights reserved. No part of this document may be used or
reproduced in any manner whatsoever, stored in a retrieval system,
or transmitted, in any form or by any means, be it electronic,
mechanical, photocopying, recording, or otherwise, without the
prior permission of Eddie Tao.
CONTENTS
Preface
Chapter One: INTRODUCTION
1.1 IOSmail, what is it?
1.2 IOSmail, how does it work?
Chapter Two: ADDRESSES
2.1 The address number
2.2 What is the structure of the address number?
Chapter Three: KEYWORDS
3.1 The requirement for transferring messages
3.2 What are IOSmail's requirements?
3.3 The structure of the AREAS.BBS file
3.3.1 Origin line
3.3.2 Private messages
3.3.3 PrivateBoxArea/PrivateMailArea
3.3.4 The Trashcan
3.3.5 Extra AREAS.BBS keywords for IOSmail
3.3.6 Distribution areas
3.3.7 Compiling AREAS.BBS/DAREAS.BBS with IOSmail
3.3.8 AreaConsultant: Internal AreaFix
3.4 The IOSmail configuration file - IOSMAIL.CFG
3.4.1 Identification
3.4.2 Archiver keywords
3.4.3 LogFile, NoLog, NoDisplay: tracing IOSmail's actions
3.4.4 Path keywords
3.4.5 Messagebase management keywords
3.4.6 Routing keywords
3.4.7 Mail packet management keywords
3.4.8 File management keywords
3.4.9 Special keywords
3.4.10 Summary of IOSmail keywords
3.5 Labels & Events - automation
3.5.1 Keywords for labels
3.5.2 Events
3.6 Gatewaying
3.5 Example setup configurations
3.5.1 A Basic Point Setup
3.5.2 A Basic Node Setup
3.5.3 A Node Setup with Multiple Addresses
3.5.4 MultiPoint
3.5.5 MultiZone Setup
Chapter Four: THE COMMANDS
4.1 Summary of commands
4.2 Errorlevel
4.3 Errors
Chapter Five: WARRANTY
Chapter Six: QUESTIONS?
Appendix A: GLOSSARY
Appendix B: ECHOMAIL
Appendix C: NETMAIL
Appendix D: POINTS
Appendix E: REFERENCE
Appendix F: TECHNICAL INFORMATION
PREFACE
After eighteen (long) months of programming I'm very proud to
present you IOSmail. During the developement I had my ups and
downs as some bugs were very hard to track down. Though it has
laid great pressure on me, I've managed it. What you have in front
of you is the effort The Team of Beta Testers, Eddie and I put
together: the IOSmail package.
Well there are several point mail tossers available. But to the
people who have been testing my program it is the most
comprehensive mailtosser available for the Atari ST/TT series. Of
course many new ideas came from The Team.
In the beginning IOSmail was just a little program of 27kb, but
the one you will be working with has grown to 150kb. Subsequently
this has slowed down IOSmail a bit, but I could keep it as quick
as possible by using veeerrrry smart programming techniques (:-))
and still not violating Atari's programming guidelines - whatever
those may be. Though I've to say that on the TT screen output is
sometimes strange, though all is ok with the files. I guess this
is due to the Turbo C 2 compiler.
Some people don't know what they're talking about if they do not
see IOSmail as the ultimate mail processor for the Atari ST/TT
series. Don't get me wrong I'm not trying to be arrogant, but
compared to mail tossers or even point tossers on IBM compatibles
IOSmail is still lacking a great deal of features. What I'm trying
to do is keep up with those machines and to give Atari users what
they deserve: great software for their machine. If Atari users are
not aware that this is to only way to extend the ST/TT's life,
Atari can forget it. Look at all those who have switched over to
MSDOS, just because they could run a program which was not
available to their own their ST... So if Atari ST/TT users just
are willing to put aside simple software and explore new, but
comprehensive software, perhaps other great programmers will try
to program more of these comprehensive programs. Well, I hereby
challenge other programmers to beat IOSmail and other great
programs. Anyway, I'll try my best to keep up with MSDOS tosser
otherwise the ST and successors will be history.
This manual: IOS_UK.DOC, IOS_NL.DOC and IOS_GER.DOC are part of
the package IOSmail, which is a mail utility for the Atari ST/TT
series computers. It is intended to guide the user through the
possibilities of IOSmail. Within this manual you will find
examples of setups that will suit nodes, points, multipoints and
when using multizones. This document is written in such way that
it can be used by the first time user and also by more experienced
users. It is also suitable as a reference guide to IOSmail.
It is suggested that you read this entire manual instead of just
picking out the important keywords. At least read the paragraph
about the structure of the files AREAS.BBS and IOSMAIL.CFG. If you
wish to gather more information on special topics, please, read
the appendices at the end of this document.
I would like to thank you all for helping me to make IOSmail what
it is today. I would like to express my Special Thanks to Joerg,
Udo and Daniel. Without these great guys IOSmail wouldn't have
been the way it is now. I'm thankful to many beta testers of The
Team for their constructive criticism and suggestions which led to
useful features of IOSmail: especially Bernd, David, Alex and
Gary. And last but not least all people who showed their patience
while IOSmail was being developed, though bugs were flying all
over the place.
Good luck with the installation and have a nice time using
IOSmail.
R.Visscher, August 1992
Chapter One: INTRODUCTION
There are several mail utilities available for the Atari ST. But
as more advanced utilities were developed, demands on the users
knowledge became greater. Also many of the current utilities were
not suitable for use with multiple zones; or if they were quite
expensive.
IOSmail provides the capability to use multiple zones in one setup
only. Therefore it is not needed to have several different
configurations for different nets or even several folders in which
complete setups are found. This is the reason why IOSmail was
developed. The current capabilities of IOSmail are sufficient to
cope with the highest demands of its users. But still, the
development of IOSmail still continues.
1.1 IOSmail, what is it?
IOSmail is a program that imports, exports, scans and crunches
FidoNet mail and FidoNet compatible mail. IOSmail will import and
create files as described in the file FTS-0001. Only these type
of files are supported by IOSmail, since this program has not been
developed to do otherwise.
IOSmail recognises the following incoming - by modem or
disk-distributed (compressed) files, the so called: *.SU?, *.MO?,
*.TU?, *.WE?, *.TH*, *.FR?, *.SA? and (uncompressed) *.PKT files.
Where * represents any name and ? any numeral.
1.2 IOSmail, how does it work?
By using a so called mailer you can receive mail, nationally
and/or internationally. Mail is transferred by these mailers via
the telephone-network. Mail cannot be processed immediately
however; instead appropriate programs are required. IOSmail is
such a program.
Transferred mail packets are actually areas of messages that have
been processed by an archiver. You will need to request these
programs from your Boss. Even when these packets have been
extracted by such an archiver, we're not through yet. The messages
are actually packed twice. The extracted files always have the
extension: .PKT. These are the files that will be processed by
IOSmail. IOSmail requires a few things. E.g. what your FidoNet
address is, and where the messages should be put. That's what the
IOSMAIL.CFG configuration file is for. We'll return to this later.
Chapter Two: ADDRESSES
2.1 The address number
You are assigned an address when you become a `point', short for
point system or node, short for node system. The person who
assigned you this number (your Boss) also has an address. These
are arranged nationally. This number or address is called the 4
dimensional address (4D). Please bear this in mind as we will need
this further on.
2.2 What is the structure of the address number?
For FidoNet the current world is divided into six zones. The zone
where you are is the one preceding the colon. For example `2:'
means zone 2. Next number is the net number. This is the net to
which you are connected. 2:255 --> 255 is the net number. Then
there will be a forward slash followed by the node number. After
the period is a number that stands for point system. Node numbers
will show the number zero in this position.
2:255/375.1
| | | |
| | | Point number
| | Node number
| Net number
Zone number
Chapter Three: KEYWORDS
3.1 The requirement for transferring messages
What you need are:
o importer - IOSmail
o exporter - IOSmail
o packer - e.g. Pack
o mailer - e.g. BinkleyTerm
o message editor - e.g. LED 1.0
o a command line interpreter or GEM shell
o perhaps a few handy programs;
your boss can advise about these.
3.2 What are IOSmail's requirements?
IOSmail requires a configuration file - an ASCII file where all
the message areas are specified: AREAS.BBS.
This AREAS.BBS will be explained first. When you receive messages
they are gathered in one file. These messages belong in so called
`areas'. These areas are actually special interest groups. For
example, an area about Atari ST computers, C programming language,
music, etcetera. There are many areas and your boss should be
able to tell you more about them and their availability. Let's
assume you were interested in the following areas: ATARI, UNIX and
FILM.
You could connect yourself to those areas by writing a message to
AREAFIX. This is a program running at your boss. It will list the
areas to which you are connected and the available ones.
When messages arrive at your point system they have to be put into
the right area. IOSmail should be told where and what these areas
are. The configuration file IOSmail uses to find out what areas
exists in your system is called AREAS.BBS.
3.3 The structure of the AREAS.BBS file
One takes a simple but appropriate text editor - there are a lot
of those on the market. You create an ASCII file with the name
AREAS.BBS. Say, you want the above mentioned areas specified in
AREAS.BBS.
I am a point
E:\POINT\MSGS\0001 ATARI 2:280/301
E:\POINT\MSGS\0002 UNIX 2:280/301
E:\POINT\MSGS\0003 FILM 2:280/301
The first line is called an origin line. This must be on the first
line of this file. Every message you type and send will contain
this line at the bottom of your message. There are many
possibilities, they will be discussed later on. Look at the
following line:
E:\POINT\MSGS\0001 ATARI 2:280/301
| | |
| | This message area originates from
| | your boss. Messages you write
| | have to be sent to him.
| |
| The area name, your special interest group.
|
The path describing where the messages are located. These folders
(POINT and MSGS) must exist.
Areas are defined this way, each one on each line.
3.3.1 Origin line
Every message should contain an `origin' line at the bottom. The
first line in the AREAS.BBS file contains such an origin line.
This origin line will be added to every message written. Hence
every one who receives your message can see where your message has
originated from. Perhaps you are wondering if it is possible to
use a different origin line for different areas. Well, the answer
is "yes". By putting a `-ORIGIN' line before every area that you
want to have a different origin line.
For example -ORIGIN Blah-blah, blah.
or
-O Blah-blah, blah
This origin line will be put at the bottom of each message whose
area has this origin line.
I am a point
-ORIGIN Atari flies Dutchman data origin
E:\POINT\MSGS\0001 ATARI 2:280/301
-DAYS 2
-ORIGIN UNIX origin
E:\POINT\MSGS\0003 UNIX 2:280/301
E:\POINT\MSGS\0003 FILM 2:280/301
You notice the line containing `-ORIGIN'. The line `Atari flies
Dutchman data origin' will be put at the end of every message that
you write in the ATARI area. The other one, `UNIX origin' will be
put at the bottom of messages in the UNIX area. I haven't added an
origin line for the FILM area, but this doesn't mean there will be
no origin line in messages written in that area. This area will
have the default origin line `I am a point'.
You'll also see the line starting with `-DAYS'. This keyword will
indicate the number of days that imported messages will be kept
before being marked as deleted. Though after compacting the marked
messages will be deleted. IOSmail will also accept `-D' instead of
`-DAYS'.
If -DAYS had been placed at the beginning of AREAS.BBS all
messages in the areas would stay as long as the -DAYS specifies
except for the areas which have their own -DAYS keyword. In the
mentioned example messages of the UNIX area older than 2 days will
be marked as deleted. Also see DefDays.
3.3.2 Private messages
It is possible to write private messages. This kind of message
cannot be read by anyone other than the person you sent it to.
Private messages are held in a special area called MAIL. This area
should be specified to your message editor. Please read its manual
thoroughly. It is possible to add this area to AREAS.BBS. This
will look like this:
E:\POINT\MSGS\9999 MAIL
You will notice that this line does not contain the node number of
your boss. Though the path `E:\POINTS\MSGS\9999' has to correspond
with the `netmail path' stated in the configuration file of your
message editor. Please, refer to your editor's manual. Areas other
than MAIL are not suitable for exchange of private matters,
because they are echoed to other nodes.
3.3.3 PrivateBoxArea/PrivateMailArea
If there are messages to you, IOSmail can collect them in a local
message area. This area is called PRIVATEMAILBOX or
PRIVATEMAILAREA.
It is indicated in AREAS.BBS this way:
E:\POINT\9998 PRIVATEMAILBOX
Messages to you in other areas will be collected in this area.
Again you don't have to mention 2:280/301 - your boss' address.
The first line of messages in this area look like this:
<arrow right>AREA [<area name>]
If you want to reply to this message in this area, do not remove
this line, for IOSmail reads this line to determine where the
actual message area is. If you do remove it your reply will not
arrive.
3.3.4 The Trashcan
Sometimes, messages can not be placed in any particular area.
IOSmail has a solution to this. There is a special message area
where these kind of messages are put. It's called TRASHAREA.
You'll wonder how you can indicate this. Well, simple, in the
AREAS.BBS file:
E:\POINT\MSGS\9997\ TRASHAREA
Here, again, you don't have to add your boss' number. You cannot
reply to messages in this area, because during a scanning session
this area is skipped.
A more complete AREAS.BBS
I am a point
-ORIGIN Atari flies Dutchman data origin
E:\POINT\MSGS\9999 MAIL
E:\POINT\MSGS\0001 ATARI 2:280/301
-ORIGIN UNIX origin
E:\POINT\MSGS\0002 UNIX 2:280/301
E:\POINT\MSGS\0003 FILM 2:280/301
E:\POINT\MSGS\9997 TRASHAREA
E:\POINT\MSGS\9998 PRIVATEMAILBOX
You can modify AREAS.BBS to suit your preferences. But always
remember that each area has to be declared on one line, and where
appropriate should include your boss' number. You are free to
change folder or drive names. The folders POINT and MSGS are just
examples, they may have another name. Only the area's name must be
the same as the name your boss gave them.
"Suppose I'm a node and I have points who want to connect to an
area. How is this done?" Are you familiar with the format of the
AREAS.BBS file? If not, then read the paragraph about AREAS.BBS.
You've seen that after every area description the number of your
boss' is added. Well, to add the points who want to have feed to a
particular area you just add the numbers of these points. Suppose
your nodenumber is 2:280/300.0 and you want to add point 1 and 2.
E:\POINTS\MSGS\0001 ATARI 2:280/3 2:280/300.1 2:280/300.2
"But I've more points connected than fits on one line?" It is not
needed to fill in the complete number.
E:\POINT\MSGS\0001 ATARI 2:280/3 .1 .2
is sufficient. It also saves some space.
You notice the paths with following a number, e.g. 0001. This is
the filename of the message area. Actually a message area consists
of two parts. In our example, 0001, these are: 0001.HDR and
0001.MSG.
.MSG contains the message text and .HDR contains some binary data.
Filenames do not have to be numbers (unless you are using QBBS!).
However, the filenames specified in AREAS.BBS must be 8 characters
or less and must not include an extension, or else IOSmail will
not be able to find that area.
3.3.5 Extra AREAS.BBS keywords for IOSmail
The following AREAS.BBS keywords can be specified for each area
separately by putting them above the path line of the actual
message area. AREAS.BBS keywords distinguish themselves from
IOSMAIL.CFG keyword by their leading minus character.
DefaultGroup <group>
{ Not suitable for points }
With DefaultGroup defined in the IOSMAIL.CFG you can define the
letter to a standard group of areas that other systems can connect
themselves to. When -GROUP is not defined IOSmail will try to read
DefaultGroup.
Example:
DefaultGroup b
All areas will belong to group b. Note that this is not group B,
as the latter one is capitalized.
DUPE_AREA
If the areas.bbs contains such an area it will contain all
duplicate messages from other echos. Normally duplicate messages
will be imported in their area, but with this option they will be
gathered in the DUPE_AREA Its syntax is just like the one for
MAIL:
<drive><path><area number> DUPE_AREA
Example:
E:\MAILER\MSGS\9996 DUPE_AREA
Note that there is no node number after `DUPE_AREA'.
-FILE <drive><path><filename>
With -FILE you can specify a file that contains origin lines.
IOSmail will then use this file to pick up origin lines at random.
Each origin line may not be longer than 79 characters, including
the added address number and the file itself may not contain more
than 65 origin lines. The keyword -FILE should be put before the
area with random origin lines.
Example:
-DAYS 5
-FILE E:\POINT\ORIGINS\IOS_HELP.ORG
E:\POINT\MSGS\0002 IOSMAIL_HELP 2:280/301
The file IOS_HELP.ORG contains, for instance, a few origin lines.
About ten will be adequate. You can also use one file for several
areas. IOSmail will then put different origin line under each
message of that area.
-GROUP <character>
{ Not suitable for points }
-GROUP is to classify to which group a particular area belongs.
<character> is its identifier and is case sensitive. Characters
and numerals can be used as long they meet the following criteria:
<a..z>
<A..Z>
<0..9>
This gives us 62 different groups. Any other characters will not
be accepted.
Example 1:
-GROUP A
E:\MSGS\0003 MIDI 2:280/301
Example 2:
-GROUP a
E:\MSGS\0010 ATARI 2:280/301
These examples are not referring to the same group, for their
identifier is not equal. Group `A' indicates the area MIDI and
group `a' indicates ATARI.
-KEEP
-KEEP is a keyword to tell IOSmail that it should only remove
deleted messages from a particular area when those messages are
marked `deleted'. Even if messages are older than specified with
DefDays or -DAYS they won't be deleted if -KEEP is used.
-LOCAL
{ Not suitable for points }
-LOCAL allows only the SysOp to have write access to a particular
area. If messages arrive which have not originated from the SysOp
they won't be processed.
-MESSAGES <number>
You can use -MESSAGES to specify how many messages may remain
after compaction by either command -D or -V. You can fill in
<number>, which represents the number of messages that should
remain.
-NAME <fakename>
If you use -NAME all messages entered in that particular area will
originate from the name specified at <fakename>. Note: It is not
allowed to use fakenames in FidoNet.
Example:
-NAME The Trooper
Messages from this area will be written under the name `The
Trooper'.
-REMOTE <nodes>
{ Not suitable for points }
-REMOTE is the same as -LOCAL but in this case only nodes
specified with <nodes> have write access. It is permissible to use
wildcards in <nodes>.
Example:
-REMOTE 2:28?/*
All nodes from net 280 are allowed to write in this area.
Summary of AREAS.BBS related keywords
-DAYS DUPE_AREA -FILE -GROUP -LOCAL -KEEP
MAIL -MESSAGES -NAME -ORIGIN PRIVATEMAILBOX
TRASHAREA -REMOTE
3.3.6 Distribution areas
{ Not suitable for points}
Suppose you are a node and you have many areas. Some areas will
not be interesting to you, but will be to your points/nodes.
Unfortunately messages that you are interested in are among other
areas - it's getting cluttered.
It's possible to use the so called distribution area. You can
compile such an area yourself. The file should have the name
DAREAS.BBS. This file has the same format as AREAS.BBS, with one
difference: the main origin line may not be included, because it's
already defined in AREAS.BBS.
Here too, you can place different origin lines. IOSmail will
interpret this file as distribution areas. Incoming messages for
the distribution areas will not be saved into local areas. It is
literally a passthrough area. For the format of this configuration
file, please, refer to the paragraph about the configuration file.
3.3.7 Compiling AREAS.BBS/DAREAS.BBS with IOSmail
IOSmail will compile AREAS.BBS and DAREAS.BBS to output a file
called AREAS.BIN. This is a binary file, which increases the speed
with which IOSmail can read it. It is very efficient if you have
a huge number of areas. Compiling these files is also very useful
for the AreaConsultant, and output of data from the AreaConsultant
will also be speeded up. See also command -U.
Note: Only automatical compilation will occur on TOS versions
higher than 1.04, 1.04 including. Users with older TOS versions
should compile their AREAS.BBS/DAREAS.BBS by running IOSmail with
the command -F. This is a forced compilation.
Each time you change either AREAS.BBS or DAREAS.BBS IOSmail will
recompile it. You can also recompile these areas (if they have
changed) by running IOSmail without parameters.
3.3.8 AreaConsultant: Internal AreaFix
AreaConsultant is the built-in area manager. It offers easy to use
commands to connect and/or disconnect areas and after connection
you have the option to rescan it. It is very similar to AreaFix
ST.
Note that you can determine what commands are allowed to be used
by other systems when calling AreaConsultant by putting this
keyword in the IOSMAIL.CFG.
AreaConsultant <commands>
<commands> can be:
-r performs a rescan on a particular area
-l lists available areas
-q lists connected areas
Example:
AreaConsultant -l -q
This means nodes or points can only use the commands -l and -q in
their AreaConsultant messages. -r will not be processed.
AreaConsultant will be activated by sending it a message. In the
SUBJECT field should be the AreaConsultant password followed by
additional commands. The message body should contain the areas to
be connected or disconnected and terminated by three minus (---).
To disconnect an area just put a minus in front of a particular
area.
Example:
From : John Doe
To : AreaFix
Subject : JDPASSWORD
----------[ MAIL ]---------------------------
<message body>
ATARI_ST
-MSDOS
---
In this example John Doe has written a message to Areafix and uses
his AreaFix password `JDPASSOWRD'. He wants to connect to ATARI_ST
and to disconnect from MSDOS.
Note that the area names should correspond to the ones at your
boss/host.
Users can use the following commands:
In subject field: -q -r -l
In message body : %q %r %l
Each area can be rescanned individually by placing -R behind a
particular area.
Example:
<message body>
ATARI_ST %r
IOSMAIL
-MSDOS
---
In this example the area ATARI_ST will be connected and rescanned,
area IOSMAIL will be connected and area MSDOS will be
disconnected.
Receipts
The user will receive confirmation messages when: oareas have been
connected and/or disconnected oa list of available areas is
requested a list of connected area is requested.
When -l and -q are used at the same time three AreaConsultant
messages will be sent to the user.
Example:
From : IOS <version> AreaConsultant
To : John Doe
Subject : Area receipt
----------[ MAIL ]----------------------------
<message body>
You are connected to area ATARI_ST and rescanned.
You are connected to area IOSMAIL.
You are disconnected from area ATARI.ST
--- AreaConsultant v 0.1
3.4 The IOSmail configuration file - IOSMAIL.CFG
IOSmail has got to know a few things about you, e.g., your name,
your number, etcetera. I'll go through the configuration step by
step. This configuration is also an ASCII text file, which you can
edit with whichever editor you prefer, just as was done with
AREAS.BBS. This file is called IOSMAIL.CFG.
When necessary it will be noted if a particular keyword can be
used at point systems. Almost all keywords are suitable for nodes
and examples will adapted to nodes where possible. When a node is
mentioned this also includes hubs, hosts and higher.
3.4.1 Identification
These identification keywords let IOSmail know what address number
you have and under what name messages are exported. Also these
keywords define the passwords to be used in mailpackets.
Address <4d nodenumber> <fakenet>
Example:
Address 2:280/301.1 23301
Or if you are a node:
Address 2:280/300.0 23300
You notice that the complete number is to be used, including the
point number even if you are a node. This number is called four
dimensional address, abbreviated to 4d-addressing.
What is the fakenumber (23300) needed for? It is needed for points
to send and receive mail. The fakenet is used to provide access to
points with 3d addressing only. But nowadays more and more mail
utilities use 4d addressing, or even 5d. Please, ask your boss for
this number is you don't know it.
CheckNames
{ Not suitable for points }
When CheckNames is being used IOSmail will compare the name in the
netmail messages to that of the password lines during importing.
If the address number is absent or incomplete then IOSmail will
either add it or complete it. The names should already have been
specified at the password lines.
Note: If you are a point of your node (SysopPoint) then CheckNames
will automatically redirect the messages directed to your node
number to your point number. Let's say you have node number
2:245/52.0 and you have point number 2:245.52.99. Mail to
2:245/52.0 will be redirected to 2:245/52.99. Of course your name
and point number should be stated in the password lines.
Example:
Incoming message:
To: Rinaldo Visscher on 2:280/301.0
IOSmail will then complete the number to 2:280/301.1. The To; line
will then be:
To: Rinaldo Visscher on 2:280/301.1
In the password lines is stated:
Password 2:280/301.1 PASSWRD $NIRVANA "Rinaldo Visscher" %ARJmail
Password
In most cases your boss' system expects a password. This could be
agreed by phone. By specifying a password in the configuration
file you and your boss will be protected against illegal access
and misuse.
Passwords are specified as follows:
Password <node> <password> <type> <header> ! * $<areafixpwd>
"name" {group} + - %<archiver>
Note: each keyword enclosed by parentheses is separated by a
single space.
<node>4d node number
<password> is your password in capitals. No more than eight letter
are allowed.
<header> is for specifying the headertype you want to use.
The following header types are provided:
# Type 2+
This # symbol means the header type should be 2+. It is needed
when exchanging messages with a system that uses FrontDoor (MSDOS
utility). Though this header type is still not official it is used
by many MSDOS utilities.
& type 2.2
When & is used, header type 2.2 will be created.
* INTL line in echomail
* will cause echo mail message to carry an INTL line at the top of
the message. Some utilities cannot do without it when used in
MultiZone environments. This INTL line will not be included in
netmail, unless ! is used. Besides this is a sign for using 4d
addressing. For more information on INTL lines see below.
! INTL-line in netmail
! will tell IOSmail to put INTL lines in netmail messages.
∧ 3D INTL line in netmail
∧ will tell IOSmail that a 3D INTL line will be put in netmail
messages. This is as follows: zone:fakenet/pointnumber.
$<areafixpwd> is the password for AreaFix ST. This password may be
30 characters maximum.
"name" is the name which is to be compared to, when you use
CheckNames. You should only fill in "name" if you are a node.
{group}
At group you can fill in the letter of the appropriate area
groups. This way you can define what nodes/points may have access
to your areas. See also -GROUP.
+
With + you can specify a node should always receive crashmail.
Note that the meaning of + depends on the situation in which it is
used.
+ at point systems
If point systems include the + in their password line the mail
password will be included in crashmail to that particular
node. Any other message will not contain a mail password.
+ at nodes
If a node includes + in his/her password lines the
mailpassword will only be included in crashmail to a point if
that particular point has been specified in the Crash-Point
lines. Now this node can assign a password to an unknown point
for receiving crashmail from that point.
Example:
U have:
Password 2:245/52.0 STAR # ! + %ZIPmail
The node has:
Password 2:280/301.1 STAR # ! + %ZIPmail
In this case you are in the node's password lines of node
2:245/52.0, hence you can send crashmail with the password
STAR included. With this feature you can prevent that someone
else sends crashmail with your name in it.
If node 2:245/52.0 wants to crash a netmail to you it would go
via your boss, because this node has not included 2:245/52.0
in the Crash-Point lines.
-
With - upi can specify if you want to send an empty pkt header to
a particular node. Some MSDOS mail tossers won't fullfil their job
if they don't receive anything during the mailsession. They will
only start sending if they receive something: an empty pkt header.
See also SendAlwaysPkt.
%<archiver> is to specify the archive type to use for the mail
packets. Currently four archivers are recognised: LZHmail,
ARCmail, ZIPmail and ARJmail.
Example:
Password 2:280/301.0 MYPASS # $PWD %ZIPmail
MYPASS may not exceed eight characters, except for the areafix
password, which is limited to 30 characters. If you're a point,
you should fill in your boss' number at `node'. If you're a node
then you can specify all your points' passwords and your boss'.
For example, let's assume you have two points and your nodenumber
is 2:280/303.0 and your boss is 2:280/301.0.
Then you specify:
Password 2:280/301.0 BOSS
Password 2:280/303.1 POINT1 $AREAFIXPWD1 %ZIPmail
Password 2:280/303.2 POINT2 $AREAFIXPWD2 %LZHmail
If you've got Areafix from the IOSmail programmer, you could also
use $<areafixpwd>. It is also possible to specify a particular
type of message to send.
Namely: Password 2:280/301.0 BOSS *
The asterisk (*) will result in echo messages that contain the so
called INTL line. If it concerns a point then messages will also
contain TOPT and FMPT. TOPT and FMPT respectively stand for TO
PoinT and FroM PoinT. Hence it will be clear where a message came
from and where it is to go. Generally this * is not needed. In
rare cases, such as no mail coming through, it might solve
problems.
SysOp <name>
Your name is specified by:
SysOp <your name>
Example:
SysOp Rinaldo Visscher
IOSmail uses this name to determine if there are messages to you,
to place them in the PRIVATEMAILBOX area. See also command -B.
3.4.2 Archiver keywords
To unpack mail packets you will need the same program to
decompress those packets. If you do not know what kind of packer
is used I advise you to consult your boss. The most popular
packers are ARC, LZH, ZIP and ARJ. IOSmail can call these
programs automatically to unpack the archives. IOSmail need to
know where it can find such programs and what they're called. This
can be done by specifying one keyword:
???Archive <path><filename><commands><switches>
Example
ARCarchive E:\POINT\ARC.TTP -x -a
LZHarchive E:\POINT\LZH.TTP x a /m
ZIParchive E:\POINT\ZIP.TTP -x -a
Archiver E:\POINT\WHATARC.TTP x a
In the above mentioned example ARC.TTP is used, which is located
at E:\POINT\. For more information about TTP-programs, refer to
your Atari ST/TT user manual.
At <commands> you should fill in the appropriate commands to
compress and decompress archives. The first one is for
decompressing and the second one for compressing.
<switches> are optional commands. Refer to the archiver manual
for specific switches.
The last line is a special one. If IOSmail could not recognise an
archive it uses WHATARC.TTP for passing commands. This could be
done for ZOO-archives.
Anyway it is no problem to alter a point's archive type, even when
some mail has already been packed with a different archiver,
because IOSmail won't try to process ARC archives with LZH.TTP. It
will recognise the archive type by itself.
3.4.3 LogFile, NoLog, NoDisplay: tracing IOSmail's actions
IOSmail is able to create a so called logfile, which records what
IOSmail has done. This information is also shown on screen. Output
to logfile is enabled by running IOSmail with -T.
Table Date and time formats
%a abbreviated display of days
%A full display of days
%b abbreviated display of month
%B full display of month
%c date and time display
%d day of month display.
%H display of hours (00 - 24)
%h display of hours (00 - 12)
%j display of day of year
%m numerical display of month (1 - 12)
%M display minutes
%p AM/PM display
%S display of seconds
%w display day of week
%W display week of year (1 - 52)
%y display year (0 - 99)
Note: if the combination of displays exceeds 40 characters IOSmail
will truncate it to 40 characters.
Example:
DateFormat %d %b %H:%M:%S
This yields the following string:
(day of month> <naam of month> <uur>:<minute>:<second>
hence
6 Nov 20:01:46 IOS ...
As you have seen, you can decide for yourself wheter you want
colons between the display formats. Of course other characters are
also possible such as - and /.
DateFormat %a %d-%m-%y %H:%M yields
Sun 20-8-89 23:55 IOS ...
DateFormat <format>
With DateFormat you can specify the desired display format of date
and time, which IOSmail display on the screen and in the logfile.
Note that if you don't use this keyword nothing will be shown on
screen or written in the logfile.
LogFile <drive> <path>
LogFile is needed to specify the path for the logfile.
Example:
LogFile E:\POINT\IOSMAIL.LOG
IOSMAIL.LOG is an ASCII file which you can read conveniently.
Sometimes, too much logging is irrelevant. To keep the amount of
log information down you can use NoLog.
Example:
NoLog -#%
All warnings starting with -, # and % will not be output to
logfile. There is also an equivalent for screen output: NoDisplay.
LogLevel <number>
With LogLevel you can specify what amount of information you want
in the logfile. At <number> you can fill in any integer from 1 to
6, 1 and 6 included. Where 1 give you most information and 6
least. See also NoDisplay and NoLog.
NoDisplay has the same syntax as NoLog.
Example:
NoDisplay *
All lines preceded with * will not be shown on screen.
An example of an IOSmail logfile made with `NoLog -' after an
import session. ( Remarks are indicated by *)
15 Jan 92 21:03 IOS IOSmail 0.84 execute in * Label In
+ 15 Jan 92 21:03 IOS Scanning protected inbound directory.
# 15 Jan 92 21:03 IOS 001527F1.PKT assembled 15.01.1992 at 21:09
by FrontDoor * Type of software used
$ 15 Jan 92 21:03 IOS Size of packet: 1548 bytes.
# 15 Jan 92 21:03 IOS 001527EF.PKT assembled 15.01.1992 at 21:09
by FrontDoor
$ 15 Jan 92 21:03 IOS Size of packet: 3058 bytes.
# 15 Jan 92 21:03 IOS Received ZIPmail packet E:\BINKLEY\SYS\IN\
D685739C.WE3
$ 15 Jan 92 21:03 IOS Size of compressed packet: 624 bytes.
~ 15 Jan 92 21:03 IOS Running e:\binkley\stzip.ttp # 15 Jan 92
21:03 IOS 08146B51.PKT assembled 15.01.1992 at 20:25
by CDEhost
$ 15 Jan 92 21:03 IOS Size of packet: 577 bytes.
# 15 Jan 92 21:03 IOS Received ZIPmail packet E:\BINKLEY\SYS\IN\
A09D2B1E.WE3
$ 15 Jan 92 21:03 IOS Size of compressed packet: 16036 bytes.
~ 15 Jan 92 21:03 IOS Running e:\binkley\stzip.ttp *external prg
# 15 Jan 92 21:03 IOS 08135F03.PKT assembled 15.01.1992 at 19:22
by CDEhost
$ 15 Jan 92 21:03 IOS Size of packet: 1854 bytes.
# 15 Jan 92 21:03 IOS 08145149.PKT assembled 15.01.1992 at 20:19
by CDEhost
$ 15 Jan 92 21:03 IOS Size of packet: 29631 bytes.
# 15 Jan 92 21:03 IOS 08146B4B.PKT assembled 15.01.1992 at 20:25
by CDEhost
$ 15 Jan 92 21:03 IOS Size of packet: 755 bytes.
# 15 Jan 92 21:03 IOS 08150692.PKT assembled 15.01.1992 at 21:15
by CDEhost
$ 15 Jan 92 21:03 IOS Size of packet: 3997 bytes.
% 15 Jan 92 21:03 IOS +-------+-----------------+-------+------+
% 15 Jan 92 21:03 IOS | Msgs | Area | SysOp | Email|
% 15 Jan 92 21:03 IOS +-------+-----------------+-------+------+
% 15 Jan 92 21:03 IOS | 3 | DPOINTS_LOC | 0 | 0 |
% 15 Jan 92 21:03 IOS | 13 | ATARIST | 2 | 0 |
% 15 Jan 92 21:03 IOS | 5 | ATARI.028 | 0 | 0 |
% 15 Jan 92 21:03 IOS | 3 | FS.028 | 0 | 0 |
% 15 Jan 92 21:03 IOS | 8 | HANDEL.028 | 0 | 0 |
% 15 Jan 92 21:03 IOS | 1 | NEDERLANDS.028 | 0 | 0 |
% 15 Jan 92 21:03 IOS | 1 | N_COMMON | 0 | 0 |
% 15 Jan 92 21:03 IOS +-------+-----------------+-------+------+
% 15 Jan 92 21:03 IOS | 6 | MAIL | 6 | 0 |
% 15 Jan 92 21:03 IOS | 2 | PRIVATEMAILBOX | 2 | 0 |
% 15 Jan 92 21:03 IOS +-------+-----------------+-------+------+
% 15 Jan 92 21:03 IOS 40 message(s) imported.
% 15 Jan 92 21:03 IOS 0 echomail message(s) created.
% 15 Jan 92 21:03 IOS 0 message(s) trashed.
Below `SysOp' the number of messages in an area to the name
specified by SysOp are printed. Below `Email' the number of echo
messages in the area are displayed. At point systems this number
is always zero. `MAIL' indicates the number of messages in
netmail. Furthermore the number of echo mails which are created
will be displayed and the number of messages that couldn't be
imported is displayed as `message(s) trashed'.
Below is a list of prefixes for warnings in your logfile or those
displayed on your screen:
+ Major change
- Minor change
# Information about packed mailpackets
* Information about messages
% Results
= Information about the routing
$ Information about messages or size of mailpackets
Information about external programs that are run
! Warning
? Error message
> Debug information
MSGReport
MSGreport will create a report about incoming messages. This file
is output in plain ASCII. The first line gives information about
the date and time the report was created. The second line says
when the file was last updated. The other lines are: The areaname,
followed by the number of imported messages in the period between
the date mentioned in the first line, and the date mentioned in
the second line. The output file is called IOSMAIL.HIS. If
IOSMAIL.HIS does not exist yet, IOSmail will create one if
MSGReport is used.
MYAREA 10
| |
| Messages imported in that period
Areaname
If a new area is added in that period, this area will not be found
in the current report file. To include the added area just delete
the old report.
NiceOutput
Origin and Destination of a message will be written into the log
if this keyword is included.
Example:
! 22 Sep 18:00:33 IOS Rinaldo Visscher (2:280/301.1) > Eddie Tao
(2:280/301.9) MAIL
This means that this line will appear in the log.
3.4.4 Path keywords
Path keywords will pass the names of the folders to IOSmail.
IOSmail needs this information to determine where it should
retrieve or place its data.
Netmail (private messages)
You can specify this in AREAS.BBS by specifying the MAIL area. If
not, this should be specified in the configuration as: Netmail
<path>
Example:
Netmail E:\POINTS\MSGS\9999
If the path is not defined either in AREAS.BBS or IOSMAIL.CFG,
then you won't able to import private mail. Again it is not
allowed to add an extension as with the regular message areas.
FDataBase <drive><path>
FDataBase is for the specification of the path for the FidoNet
messagebase. This database is suitable for storing messages like
you are used to in your message editor. Retrieving these messages
is as easy as using your message editor, because you can copy
those message back and forth. This database will come in handy
when you need to look up particular messages but you don't want to
keep them in the message base of you message editor.
Example:
FDataBase C:\FIDODATA\
FDGetFrom <direction><name>
FGetFrom is for use in conjunction with FDataBase. It is used to
specify the person to whom messages are to or from. The direction
will determine whether those messages should be to or from this
person. Wildcards are allowed in <name>.
> means: messages to <name>
< means: messages from <name>
Example 1:
FGetFrom >Rinaldo Visscher
All messages to Rinaldo Visscher will be transferred to the
FidoDataBase.
Example 2:
FGetFrom <Eddie *
All messages from people whose name start with `Eddie' will be
transferred to the FidoDataBase.
Inbound & Outbound folders
Mail packets will be situated in the so called Inbound and
Outbound folders. Inbound for the messages which are imported and
Outbound for messages to be exported. Please, refer to your
mailer's manual. Paths that are specified in the IOSmail
configuration file should correspond to the ones of your mailer.
If this is not the case you will not able to receive or send
messages.
Outbound <path>
Example:
Outbound E:\POINT\OUTBOUND\
Inbound <path>
Example:
Inbound E:\POINT\INBOUND\
The paths mentioned in the examples are just common names. Since
these are references to folder(s). You may not specify a filename,
because there is a chance that mail packets will not be extracted.
This folder is to indicate the folder where mail should be put
from systems that are not listed in the nodelist.
KnownInbound <drive><path>
KnownInbound tells IOSmail that this is a Known Inbound folder, as
used by BinkleyTerm. This folder is used for inbound mail packets
from mail systems that are known in the nodelist but that do not
require a passworded session. All messages are imported to the
TrashArea except for netmail.
MailTemp <drive><path>
MailTemp is used for the specification of the path where mail
packets will be stored temporarily during the export of mail. If
no path is specified, IOSmail will create a folder itself in the
root: \outtemp.
PktTemp <drive><path>
PktTemp is used for the specification of the path where mail
packets should be stored during the extraction of mail. IOSmail
will look at that folder to determine if it is empty, if not it
will delete all non-pkt files found. Then IOSmail will put
extracted mail packet into that folder. IOSmail will create a
folder called \intemp in the root if no path is specified.
ProtInbound <drive><path>
This keyword is to indicate where the ProtInbound folder is as
used by BinkleyTerm. This folder is used to hold inbound
mailpackets from mail systems with which you have passworded
sessions.
TrashArea <drive><path>
If any message is imported which does not have an area ( yet )
IOSmail will put them into the TRASHAREA. Just put this keyword
into the IOSMAIL.CFG. See also AutoAddArea.
TrashArea <drive><path>
Example:
TrashArea E:\POINT\MSGS\9998
The area-less messages will be collected in the 9998 area.
3.4.5 Messagebase management keywords
Messagebase management keywords control built-in options of
IOSmail which can alter your messagebase. Some of them will change
the appearance of you messages by changing the SEEN-BY lines for
instance.
AddAKA
The AddAKA keyword will include all your `also known as' numbers
to the SEEN-BY line if it concerns mail within the same zone.
Example:
AddAKA
Address 2:280/3.0
Address 2:280/308.0
The SEEN-BY line will look like this:
SEEN-BY 280/3 308
AddDomain <domains>
If you use AddDomain your origin line will include the name of the
domain you are in. In some domains it is mandatory to add these
names. If <domains> is specified then the domain name is used from
the zone which is not indicated by ApplZone. If you wish you can
add multiple zone numbers at <domains>.
Example:
AddDomain 5 90
Domain 88 is PHETNet.ftn
Domain 90 is NeST.ftn
* Origin Thanks Daron B for NeST (90:4000/103.0@NeST.ftn)
* Origin Blub-blub all over the place (88:999/100.0@PHETnet.ftn)
CompactMSGS <number>
(Keyword is effective only in combination with -D switch.)
CompactMSGS tells IOSmail to compact the message bases mentioned
in AREAS.BIN. You have three options for <number>:
1. Compact messagebase after importing messages.
2. Compact messagebase after scanning messages.
3. Compact messagebase after importing, scan or both (always).
Compaction defaults to 2 (compact after a scanning session).
CompactMSGS can also be called without import or scan. Don't put
the -I or -S in the commandline. Then IOSmail only compacts the
messagebase. -L can be used if desired.
CopyArea <source><dest.><name>
CopyArea will copy messages from <name> in the source area to the
destination area. <name> can be specified using wildcards. See
also MoveArea.
Example 1:
CopyArea POINTS_LOC LOCAL Rinaldo Visscher
In this example all messages written by Rinaldo Visscher in
POINTS_LOC will be copied to LOCAL.
Example 2:
CopyArea POINTS_LOC LOCAL Eddie *
In example 2 all messages written in POINTS_LOC by people whose
name starts with `Eddie' will be copied to LOCAL.
Example 3:
CopyArea *_LOC LOCAL Eddie *
In the final example all messages written in _LOC areas by people
whose name starts with `Eddie' will be copied to LOCAL. For
instance messages from TEST_LOC, MAC_LOC and so on would be
included.
CopyPVTmail
CopyPVTmail can be used if you want incoming messages which are
directed to you to be copied into a special area called
PRIVATEBOXAREA or PRIVATEMAILBOX. Also Netmail will be copied. If
you like, it is possible to reply from within the PRIVATEBOXAREA.
Note that the line `<control-a>AREA [<areaname>]' must be present
and this area should to be specified in AREAS.BBS, otherwise you
won't be able to use this option and your reply will be deleted.
Copy-to-Point
If Copy-to-Point is used together with CopyArea or MoveArea
messages will also be forwarded to points. If you leave out
Copy-to-Point CopyArea will only be for local use.
DefDays <days>
(Keyword is effective only in combination with -D switch.)
The default number of days that messages will be held in the
message base. If -DAYS is not specified in AREAS.BBS or
DAREAS.BBS, the number of days in <days> defaults to DefDays'. If
no -DAYS is found the number of days defaults to 21 days.
DupeLog <aantal>
To filter already imported messages IOSmail compares the old
messages to the new ones in the DupeLog file. With this keyword
you can specify howmany messages IOSmail should keep track of. The
data of these messages will stored binary in a file called
IOSDUPES.LOG.
Example:
DupeLog 2000
In this case data of 2000 messages will be kept in the file
IOSDUPES.LOG
KeepPrivate
If you want to keep the messages you wrote in PRIVATEMAILBOX then
you ought to include the keyword KeepPrivate in your
configuration. Messages you have written will be kept in the
messagebase.
Nodes and to some extent points, are able to prepare the mail in
such a way that it is almost ready for transmission. If you're a
node you could by means of an commandline switch prepare messages
by an appropriate packer for a particular person. Only NetMail
will not be processed.
KillFrom <name>
It is possible to delete messages from a particular person. This
comes in very handy if that particular person is only allowed to
read messages, but not allowed to write any.
Example
KillFrom John Doe
KillSent and KillAll
{ Not suitable for points }
Suppose you are a node, but you do not want messages not directed
to you to be retained in the Netmail area. This can be done by
specifying one or both of the following keywords:
KillSent, KillAll
KillSent will delete all messages not directed to you. Messages
that are directed to you or your points will be kept. KillAll will
also delete the messages to your points, resulting in a
messagebase with only messages directed to you. In both cases
these messages will get the flag KILLSENT. You can only use this
feature if you're a node. Using it at point systems will have no
effect.
MaxMessages <number>
(Keyword is effective only in combination with -D switch.)
The maximum number of messages that may be held in the
messagebase. If the number of messages is higher than specified by
<number> the oldest ones will be deleted during compaction.
Default is 65534. This is also the highest possible number of
messages that can be held in a message base.
MinDiskSpace <kbytes>
This keyword allows IOSmail to check the available diskspace
before and after each mail packet has been imported. If diskspace
is less than amount specified by <bytes> you will be prompted and
the import session will abort.
Example:
MinDiskSpace 2048
If during import, diskspace is less than 2048 bytes. Any larger
packet will be skipped. If it is a message it will not be
imported.
If MinDiskSpace check is on, the diskspace is also checked when
compacting. If space is insufficient, the process is also stopped.
MinMessages <number>
(Keyword is effective only in combination with -D switch.) The
minimum number of message that may be held in a message base. If
the messagebase contains less than that specified by <number>,
nothing will be deleted during compaction. Default number of
messages is zero.
MoveArea <source><dest.> <name>
MoveArea has the same syntax as CopyArea. But instead of copying
the messages, the messages are moved.
NoZone
Some mail utilities do not recognise the use of zone numbers in
the SEEN-BY and PATH lines. To switch off the addition of zone
numbers NoZone should be included in IOSMAIL.CFG.
QbbsLastRead <drive><path>
(Keyword is effective only in combination with -D switch.) This
keyword will let IOSmail know that it has to update the lastread
pointers from QuickBBS messagebase after compacting its
messagebase.
Example:
QbbsLastRead E:\MAIL\LASTREAD.BBS
Realname
Sometimes we notice a line containing <control a>REALNAME:.
IOSmail can, if desired, read this line. This name will only be
written locally and will not be passed on to the exported mail.
There are three ways to use this option. It is also possible to
attach this line to your messages.
Example:
RealName 1 Only incoming mail. If this line is included in
the configuration file this REALNAME line will be
copied to the messages.
RealName 2 Only outgoing mail. This line will be added to
messages you write.
RealName 3 Both. Incoming and outgoing mail.
RealName In this case RealName 3 will be chosen by default.
SaveLocal
Message which are written locally will normally not be written
back - they look exactly as they were typed in. Sometimes it is
handy to know what IOSmail has done with your messages. For
instance, you might like to see what your origin line looks like,
etc. By using the keyword SaveLocal your locally typed messages
will be put back and the original message will be marked as
deleted.
StripPID
The keyword StripPID is used for stripping the PID:-lines in your
messages. This will save some disk space.
TinyPath
{ Only for points }
TinyPath will let IOSmail not include the fakenet numbers of
points in the path lines of echomail messages. See also
TinySeenBy.
TinySeenBy
{ Only for Points }
The keyword TinySeenBy will strip the fakenet numbers from the
SEEN-BY lines. This will save some disk space. It's for local use
only.
3.4.6 Routing keywords
Routing keywords tell IOSmail what path the mail packets should go
to arrive at their correct destination. IOSmail is extremely
flexible in handling routing, hence you'll be limited only by your
imagination.
A few notes on notation. You're probably familiar with wildcards
such as * and ?. Below you'll see an extension to increase
flexibility of routing even more.
2:280/(305,306,314).0 equals:
2:280/305.0 2:280/306.0 2:280/314.0 .
2:280/310.[1-9] equals:
point 1 to 9, 9 included for node 2:280/310.0.
2:280/310.[139] equals:
point 1, 3 and 9 from node 2:280/310.0.
It is even possible to combine these notations by using curly
brackets. Arguments should be separated by a comma: {10,90,150} or
2:280/{[301-306],200,226}.0.
ApplZone <zone><outbouund path><domain>
ApplZone has the same function as the Domain statement in
BinkleyTerm. Zone stands for the number with out a colon that
matches the Domain. <domain> is the name of the domain that has
been specified in the BINKLEY.CFG. Suppose you decide to join
NeST, which has zone 90. You should then include the following
keywords in BINKLEY.CFG and IOSMAIL.CFG:
Example:
BINKLEY.CFG has the following statement:
Domain Nest.ftn nest nestlist
IOSMAIL.CFG should include the following:
ApplZone 90 E:\BINKLEY\NEST\ NEST.FTN
The above mentioned `nest.ftn' can be used when AddDomain is used.
The folder `\NEST' corresponds to the folder specified in
BINKLEY.CFG. IOSmail will create the appropriate folder if it
doesn't exist. It will be called \NEST.05A'. The extension is
derived from the zone number and is denoted as a hexadecimal
number.
If ApplZone is not used mail packets will be put in the standard
folder as stated with the Inbound keyword.
Special Note:
For The Box users it is not recommended to use ApplZone.
Boss <node number>
IOSmail uses the node numbers stated by Boss to determine where
mail should be routed to.
Crash-Point <point1 point2 ...>
With Crash-Point a node of point can send crashmails to other
points. It is then necessary to set the CRASH flag in your message
editor. By including a point to your Crash-Point lines that point
will be crashed. Note that it is necessary that the point
telephone number is known to you and that the points should be
included in the password lines.
If you set the CRASH flag in a message directed to a point but you
didn't include this point in your Crash_point lines that
particular message will be sent (crashed) to its boss.
Example:
Your node number is 2:245/52.0 and the IOSMAIL.CFG has the
following lines:
Password 2:280/301 TEST # %ZIPmail
Crash-Point 2:280/301.1
If you now send a crashmail to 2:280/301.1 this message will be
sent without passing node 2:280/301.0. If Crash-Point was not
included then it would have gone via 2:280/301.0.
Crash-To <node1 node2...>
Crash-To indicates nodes that should receive crash mail. Even if
other unknown systems deliver their mail at yours, mail will be
crashed to nodes specified at <node1 node2...>.
Example:
Crash-To 2:255/355
As soon as a message for 2:255/355 is processed that message will
be crashed.
Example:
Crash-To 2:255/*
All mail routed to net 255 should be crashed.
Move-Mail <destination><source(s)>
Move-Mail will allow mail from <source(s)> to be merged in mail
packets routed to <destination>. Mail packets will be included
separately. In other words destination address numbers will not be
changed by IOSmail. See also RedirectNetmail.
Example:
Move-Mail 2:280/301.0 90:4000/103.0
Mail from node 90:4000/103.0 will be included in the mail packet
for node 2:280/301.0.
Example:
Move-Mail 2:280/301 90:4000/103 50:100/100 20:100/100
Mail from zone 90, zone 50 and zone 20 will be included in the
mail packet for 2:280/301.
ReAddress <origin>, <origin node>, <new origin>, <new node>
With ReAddress you can redirect netmail from someone to another
address. This comes in handy if you're node and point of your own
system. E.g. Mail that is addressed to your nodenumber will be put
on hold at your pointnumber.
For <origin and <origin node> wildcard may be used. Please not the
commas. These must be included.
Example:
ReAddress Rinaldo Visscher, 2:280/301.0, Eddie Tao, 2:280/312.0
All mail addressed to Rinaldo Visscher will be redirected to Eddie
Tao with nodenumber 2:280/312.0
Example:
ReAddress Bernd *, 2:*/*, Joerg Spilker, 2:245/69
All mail addressed to person whose first name is Bernd at zone 2
will be redirected to Joerg Spilker at 2:245/69.0.
RedirectNetmail
Redirectnetmail will allow you to write messages under let's say
zone 2 and readdress it with your zone 90: address. Suppose you
have 2:280/301.1 as zone 2 address and 90:4000/103 as zone 90
address. Messages for zone 90 will appear to be sent by
90:4000/103 instead of 2:280/301.1.
This keyword is really a key statement in MultiZone setups. It
allows you to have several zones or to be more precise several
nets in one single setup. RedirectNetmail also works for addresses
in the same network or zone.
For instance your mail is sent as 2:23301/1 (a so called three
dimensional address). IOSmail will convert it such that your new
address will be 2:280/301.1 (a so called four dimensional
address).
Route <destination><source1 source2...>
With the Route keyword it is possible to direct echo mail from
specific nodes to other nodes.
Example:
Route 2:245/8 2:24?/* 2:23?/*
All echo mail from nodes between 2:230/0 and 2:249/999 will be
routed to node 2:245/8.
Example:
Route 2:280/0 *
All echo mail from any node will be routed to node 2:280/0.
Multiple Route statements are allowed:
Example:
Route 90:1004/0 90:*
Route 2:245/8 2:24?/* 2:23?/{101,104,110}
Route 2:280/0 *
It is strongly advised that you put your main boss' or host's
address on the last line of the Route lines. If this line does not
exist IOSmail will search for the Boss keyword.
3.4.7 Mail packet management keywords
These keywords let IOSmail know how it should handle mail packets.
For instance, it is possible to determine the maximum allowable
size for a particular mail packet before it is deleted. Or the
type of mail packet that should be created to suit certain
mailers.
Arc-For <node1 node2 ....>
Arc-For ( ARCmail For ) indicates which nodes or points should
have ARCmail.
Example:
Arc-For .* 2:280/3 2:245/8
All points on your system, node 2:280/3 and node 2:245/8 should
receive ARCmail. (See also appendix A for the definition of
ARCmail.)
Capture
Suppose you're a node and one of your points will be on holiday
for a long time or he just cannot poll regularly to get his mail.
To reduce the size of his mail packet you might want to disconnect
him from his areas. But then you would have to browse through
AREAS.BBS and change this manually or the point in question could
write a message to Areafix to disconnect himself. But all this is
unnecessary with IOSmail. You just add the following line to your
configuration file:
Capture <node> <name>
Example:
Capture 2:280/301.1 Rinaldo Visscher
Incoming mail will then be compared to the capture name. Mail
directed to that particular person will be processed like other
outgoing mail, but mail not directed to that person will not.
4DMSGHeader
{ Only for points }
With 4dMSGHeader IOSmail will know that it should use 4D message
headers in contrast of the regular 3D message header which
consists of the so called a fakenet number. Its use is when the
receiving mailer cannot handle 3D point addresses, which is the
case with D'Bridge. See also *, INTL in echomail.
Though its advisable not to use 4MSGHeader at nodes, it is no
problem when both are using IOSmail, for IOSmail is capable of
handling 4D addresses.
DefaultPkt <type>
The keyword DefaultPkt is used to define the so called packet
header type when Crash mails are sent. The following type are
built-in:
o 2.0 Stone Age
o 2+ Type 2+, e.g. FrontDoor, Gecho
o 2.1
o 2.2 BinkScan
Example:
DefaultPkt 2+
All Crash mail should contain type 2+ message headers.
Deny-Except <node(s)>
Deny-Except determines if mail from particular nodes are allowed
to be processed. Sometimes it is not wanted to process large
packets, because the schedule will be wrong. It is advisable to
use Deny-Except in Event lines.
Example:
Event All 3:30 2:30 deny-Except 2:28?/*.*
Event All 2:30 3:30 Deny-Except *:*/*.*
In the first line all mail between 3.30 and 2.30 will not be
processed expect for mail from nodes of region 28. Thus 2:280/0.0
until 2:289/999.999.
At the second line alle mail will be processed which is received
between 2.30 and 3.30.
For points it suffices to include the next line in their
IOSMAIL.CFG:
Deny-Except *:*/*.* or
Deny-Except *
Hold-Del <kb><node1 node2 ...>
{ Not suitable for points }
Hold-Del will compare a mail packet's size to <kb>. Mail packets
bigger than this will be deleted. <kb> is its size in kilobytes.
Hold-Del works only with *.HA and *.HAT files. This keyword will
prevent you from running out of diskspace. This keyword may be
used in Events.
Hold-For <node1 node2 ...>
{ Not suitable for points }
Hold-For will tell IOSmail to put mail on hold for the nodes
specified in <node1 node2 ...>. This keyword may be used in
Events.
Example:
Hold-For .* 2:280/30?
Put mail on hold for all points on your system and nodes between
2:280/300 and 2:280/399, 2:280/300 included.
Hold-Max <kb><node1 node2 ...>
{ Not suitable for points }
Hold-Max will change a hold file into a poll file when its size
exceeds the amount in <kb>. <kb> is noted as kilobytes. It can
also be used in cases where Points are listed in the nodelist.
Your system can then poll your points.
Example:
Hold-Max 100 2:245/52
If a mail packet exceeds 100 kb the hold file will be changed into
a poll file. This keyword works only if applied on *.HA or *.HAT
files.
Hold-to-Poll <node1 node2 ...>
Hold-to-Poll will change hold files into poll files. This will
happen for nodes indicated at <node1 node2 ...>. You are advised
to do this in Events.
Example:
Event Wed 00:00 02:00 Hold-to-Poll 2:280/305
On Wednesday between twelve and two o' clock am hold files will be
changed into poll files for node 2:280/305.
MinPacketSize <kb>
IOSmail will only pack a mailpacket if it exceeds the size
specified in kilobytes. If not, the mail packet will remain a *.nm
file.
NewBinkley
NewBinkley indicates that IOSmail should produce mail packets
which support the BinkleyTerm 3.0 format. The benefits of this
format are fewer files in your outbound folder, because there is
only one file per node. It also becomes clear how much mail is on
hold for a particular node or point.
The *.mo?, *.tu? files are replaced by packets which are labeled
with base 36 numbers.
Example:
NNNnnnPP
NNN stands for net
nnn stands for node
PP stands for point
New extensions are:
o *.HAT hold files
o *.CAT crash files
o *.OAT poll files
The A in the middle of the extensions indicates whether the files
contain ARCmail or not. To the contrary U stands for unpacked
mail.
NoNetmailPack
{ For points only }
NoNetmailPack will allow echo mail to be packed whilst netmail
remains as it is. This is needed for points who call FrontDoor
mailers, which do not accept netmail attached files.
PackKnown
{ Not suitable for points }
Although it is possible to write mail packets locally for known
users, suppose you get some mail that has to be processed for
another point and that there is Netmail included in this mail
packet, that you would like to process. Then you ought to use the
keyword PackKnown. If this keyword is not present then it should
be processed by another program, for instance Pack. But you should
toggle the appropriate switch in the commandline. More about this
later on. This keyword has no use in case of points.
PathCheck
{ Not suitable for points }
If PathCheck is used IOSmail will check if a message already
exists. If so that message will not be exported by IOSmail. This
will prevent the message from `bouncing' between nodes. IOSmail
compares only net and node numbers during its check.
One should be careful when using PathCheck between (Fido)zones -to
be exact: nets, because similar net and node numbers could exist.
Prepare-Poll <node1 node2 ...>
Prepare-Poll will create a so called poll file. This file will
notify the mailer that it should dial the specified node. You
should fill in complete node numbers at <node1 node2 ...>
SendAlwaysPKT
When you use SendAlwaysPKT IOSmail will create a pkt file header
instead of a poll file. This pkt file is empty. This is useful
when polling FrontDoor mailers which have the annoying property of
not sending mail when you have nothing to send. See also
NewBinkley and Prepare-Poll.
The-Box
Using this keyword IOSmail will create files which are compatible
with the The-Box mailer. These file have the following extension:
*.Ha, *.Na and *.CA. See also NewBinkley for more information on
the created files.
3.4.8 File management keywords
File management keywords tell IOSmail how to handle files and what
restrictions they have.
File-Max <kb> <point1 point2 ....>
{ Not suitable for points }
File-Max will tell IOSmail which points are allowed to send each
other files and what size these files can be. <kb> is the size of
the individual file in kilobytes and point1, point2, etc, are the
points who are restricted.
Example:
File-Max 100 .*
All points may send each other file attached netmails but are
restricted to a maximum of 100 kb. The system will accept files
larger than 100 kb but will not pass them on.
File-To <kb><node1 node2 ...>
File-To indicates to IOSmail which node/points may receive file
attached netmails and what size the files are restricted to. <Kb>
is the size of a file in kilobytes. <node1 node2 ...> are the
nodes or points who are allowed to receive these file attached
netmails from your system.
Example:
File-To 20 2:280/301.0
Only netmails to node 2:280/301.0 with file attached netmails up
to 20 kb may be sent.
3.4.9 Special keywords
Below are keywords which do not deal with mail processing. But are
here to help IOSmail function in its environment.
FastImport
{ For points only }
Using FastImport will increase the rate at which messages are
imported greatly. IOSmail will try to read in as many of the pkt
file as possible and output the messages in one stream. It uses
many channels for achieving this high rate. IOSmail processing
mail as a node also need channels, but there are no more than 32
on the Atari ST. So nodes can run out of channels. Though a node
system with a few points can use FastImport, but it can fail.
MSGBuffer <bytes>
MSGBuffer is used to set the buffer space for incoming and
outgoing messages. It defaults to 32Kb. Systems where RAM is
sparse can set a smaller size for the buffer.
MultiTasker <tasker>
With MultiTasker you can specify which multitasker you use.
IOSmail will then adapt itself to your multitasker. Currently we
have two flavours: MiNT and MultiGEM. If you do not use
MultiTasker IOSmail will default to MiNT. You're advised to put
this keyword on the very first line of the IOSMAIL.CFG.
Example:
MultiTasker MultiGEM
IOSmail will behave like a GEM program, by issuing a GEM call
periodically. Don't forget to rename IOSMAIL.TTP to IOSMAIL.PRG
otherwise GEM will not recognise IOSmail as a GEM program.
IOSmail can also work as a TOS program within MultiGEM, in which
case you should rename IOSMAIL.TTP to IOSMAIL.TOS, and you should
not use the MultiTasker keyword. When IOSmail is run MultiGEM will
put IOSmail into its special MultiGEM window. Since MultiGEM will
only run from the Desktop it is necessary to control IOSmail via
Event lines, for it is not possible to pass parameters to TOS
programs within the Desktop.
IOSmail will be made compatible with other multitasking operating
systems as well. To name a few: RTOS, MINIX and OS/9.
3.4.10 Summary of IOSmail keywords
AddAKA AddDomain Address ApplZone
AreaConsultant Arc-For ARCarchive Archiver
ARJarchive Boss Capture CheckNames
CompactMSGS CopyArea CopyPVTmail Copy-to-Point
Crash-To Crash-Point DateFormat DefaultGroup
DefaultPKT DefDays Deny-Except Event
FastImport FDataBase FDGetFrom File-Max
File-To Hold-Del Hold-For Hold-Max
Hold-To-Poll Inbound KeepFidoBits KeepPrivate
KillAll KillFrom KillSent KnownInbound
LZHarchive LogFile MailTemp MaxMessages
MinDiskSpace MinPacketSize MoveArea Move-Mail
MSGBuffer MSGReport MultiTasker Netmail
NewBinkley NiceOutput NoDisplay NoLog
NoNetmailPack NoZone Outbound PackKnown
Password PathCheck PktTemp Prepare-Poll
ProtInbound QbbsLastRead ReAddress RealName
RedirectNetmail Route SaveLocal SendAlwaysPKT
StripPID SysOp The-Box Tiny-Path
TinySeenBy TrashArea ZIParchive
3.5 Labels & Events - automation
With labels you can simplify the way you control IOSmail. Multiple
commands can be passed to IOSmail, which in turn can be used at
different times. It is even possible to create a very tight
schedule with a resolution up to one minute.
Or you can use keywords only when certain things need to be done,
such as NoLog or NiceOutput or RealName, to name a few.
Labels are called by using the following statement:
IOSMAIL.TTP -E <label name>
3.5.1 Keywords for labels
The following keywords are used to control labels:
#<label>
#EndLabel
#EndAll
Commands <commandline>
#<label> specifies the name of a label.
#EndLabel specifies the end of a label.
#EndAll specifies the end of all labels. Labels which are
declared after #ENDALL will have no effect.
Commands can be used to pass commands to IOSmail as if you were
using it from a shell, commandline interpreter or from
the Desktop.
It is a good idea to put labels at the start of IOSMAIL.CFG,
because IOSmail interprets the keywords in a top-down sequence.
Example:
#ScanOnly
commands -scp
#EndLabel
#Import
commands -plirm
#EndLabel
#Crunch
commands -dt
#EndLabel
#DoAll
commands -scplirm
#EndLabel
#ScanCrunch
commands -scpd
#EndAll
It is not recommended to include Address lines within a label. If
you are multipoint and an Address line is contained in a label
which is not used you could have problems during import or
scanning sessions. Node numbers at the end of an AREAS.BBS line
won't be found and IOSmail will take your default address. But if
you insist on having Address line in a label, please check if the
correct address has been taken.
Example:
;AREAS.BBS
E:\POINT\MSGS\0001 IOS_BETA 2:280/301
E:\POINT\MSGS\0003 MYAREA 2:283/101
And you your IOSMAIL.CFG contains:
#Point1
Address 2:280/301.1 23301
#EndLabel
#Point2
Address 2:283/101.25 23101
#EndAll
And you use IOSmail with label Point1:
IOSMAIL.TTP -E POINT1
and you have written a message in MYAREA then IOSmail will use
2:280/301.1 as address - the wrong one. Please write messages
after the old ones have been processed. And please, insert Key
lines in the labels and use IOSmail with at least one -R.
An example of keywords used in labels is NoLog. One could use
different NoLog settings during an import or a scanning session.
Only one label at a time can be called, though you can use them
together with commands.
Example:
IOSMAIL.TTP -d -e ScanOnly
Final note on labels: -E and -H cannot be used in labels.
3.5.2 Events
With the use of Events you can execute commands at user defined
times. For instance you could poll boss X at the weekends and boss
Y at weekdays.
Event <days><start><stop><command>
Event will execute the accompanying commands between <start> and
<stop> time and on <days>.
<days> had the following formats:
Sun, Mon, Tue, Wed, Thu, Fri, Sat, Wkd, Week, All.
`Wkd' stands for weekends and `Week' for weekdays.
<start> and <stop> have the following formats: HH:MM, where you
can choose between 00:00 and 23:59 hours and minutes.
<command> can be any command or keyword except for label keywords.
Example:
Event Wkd 10:00 22:00 NoLog -#
Event Week 12:00 23:49 LogFile e:\binkley\iosmail.log
Event All 00:00 23:59 Prepare-Poll 2:245/8
Event Thu 10:00 12:00 Address 2:281/24.1
The flexibility and power of the Event command is that nodes or
points are free to choose whatever route they want their mail
packets to go by specifying the time and day. Therefore it is
possible to poll different nodes on different days automatically.
Or by putting Event lines into labels one has total control in the
way IOSmail processes the mail.
Example:
#AutoPost
event wkd 03:00 23:59
commands -i -l -p -r -o
event wkd 00:00 00:59
commands -i -l -p -r -o -s -c -d
event week 06:00 23:59
commands -i -l -p -r -o
event week 00:00 05:59
commands -i -l -p -r -s -c
#EndAll
3.6 Gatewaying
IOSmail has the capability to serve as a gateway between different
nets for netmails. If you're not a gateway IOSmail will not change
the original message and will pass it on as usual.
Example:
From : Rinaldo Visscher on 2:280/3.1
To : GateWay on 2:280/3
----------------------[NETMAIL ]--------------------------------
&To: Joe Jet@90:1000/0.0
<message text>
This message has been written at the gateway on 2:280/3 which has
a connection with NeST ( zone 90 ). This message has its
destinations specified at the &To: field.
The gateway will create the following message: From : GateWay on
90:5/0
To : Joe Jet on 90:1000/0
-----------------------[NETMAIL ]-------------------------------
&From: Rinaldo Visscher@2:280/3.1
<message text>
^aVia GateWay on 2:280/3 <time field> by OutMail
^aVia Node on 90:5/0 <time field> by OutMail
If the addressee wants to reply, he should write it to the gateway
on 90:5/0 like this:
From : Joe Jet on 90:1000/0
To : GateWay on 90:5/0
----------------------[NETMAIL ]--------------------------------
&To: Rinaldo Visscher@2:280/3.1
<message text>
Please bear in mind that IOSmail checks the way the &To field is
written. For example: `&TO:' or `&To :' are correct.
3.5 Example setup configurations
All lines in the configuration with a preceding semi colon (;) are
comment lines.
3.5.1 A Basic Point Setup
; Basic Point Setup example
;
; >> Labels for in- and export <<
#Import
commands -lit
#EndLabel
;
#Export
commands -sopt
#EndAll
;
; >>Identification<<
SysOp Rinaldo Visscher ; my name
Address 2:280/301.1 23301 ; my first address
Password 2:280/301.0 MYPASS %ZIPmail ; node you're polling
; with password MYPASS
;
; >>Logging<<
Logfile e:\binkley\system\iosmail.log
;
; >>Paths<<
Netmail e:\binkley\msgs\0001 ; Netmail area
Outbound e:\binkley\outbound\
Inbound e:\binkley\inbound\
TrashArea e:\binkley\msgs\9999 ; Trasharea
MailTemp e:\binkley\outbound\temp\
PktTemp e:\binkley\inbound\temp\
;
; >>Paths for archivers<<
Archiver e:\binkley\whatarc.ttp x a ; Archiver
LZHarchive e:\binkley\lzs.ttp x a -m ; LZH
ARCarchive e:\binkley\arc.ttp -x -a ; ARC
ZIParchive e:\binkley\zip.ttp -x -a ; ZIP
;
; >>Messagebase management<<
SaveLocal
CopyPVTmail
DefDays 30
Deny-Except 2:280/301 ; import all mail from node 2:280/301
;
; >>Routing<<
Route 2:280/301 *
;
; >>Mail packet management<<
Arc-For 2:280/301
;
; >> File management<<
File-To *
3.5.2 A Basic Node Setup
If you're a node and you have points. The following configurations
will give you some help.
; A basic node setup
;
; >>Labels<<
#IMPORT
commands -bilt
#ENDLABEL
;
#EXPORT
NiceOutput
commands -soptd
#ENDALL
;
; >>Identification<<
SysOp Rinaldo Visscher
Address 2:280/301.0 23301
Password 2:280/0.0 BOSSPWD %ZIPmail
Password 2:280/301.1 POINT1 $areafixpassword %ZIPmail Password
2:280/301.2 POINT2 $areafixpassword %LZHmail
;
; >>Logging<<
Logfile e:\binkley\system\iosmail.log
NoLog -
;
; >>Paths<<
Netmail f:\msgs\0001
Outbound f:\outbound\
Inbound e:\binkley\inbound\
TrashArea e:\binkley\msgs\9999
MailTemp e:\binkley\outbound\temp\
PktTemp e:\binkley\inbound\temp\
;
; >>Paths for archivers<<
Archiver e:\binkley\whatarc.ttp x a ; Archiver
LZHarchive e:\binkley\lzs.ttp x a -m ; LZH
ARCarchive e:\binkley\arc.ttp -x -a ; ARC
ZIParchive e:\binkley\zip.ttp -x -a ; ZIP
;
; >>Messagebase management<<
KillAll
CopyPVTmail
PathCheck
SaveLocal
DefDays 28
Deny-Except 2:280/0 2:280/301.*
CompactMSGS 3
;
; >>Routing<<
Route 2:280/0 *
;
; >>Mail packet management<<
PackKnown
Capture 2:280/301.2 Point X
Arc-For 2:280/0
;
; >>File management<<
File-To *
3.5.3 A Node Setup with Multiple Addresses
Say, you have more than one address. This is not a problem. By
adding the required number of address lines you will be able to
specify these addresses. Even if you're a point, a so called
multipoint.
; A Node setup with multiple address line
;
; >> Labels<<
#IMPORT
commands -blitrr
#ENDLABEL
;
#EXPORT
NiceOutput
commands -spot
#ENDALL
;
; >>Identification<<
SysOp Rinaldo Visscher
Address 2:280/301.0 23301
Address 2:280/220.0 23220
Password 2:280/0.0 BOSSPWD %ZIPmail
Password 2:280/301.1 POINT1 $areafixpassword %ZIPmail Password
2:280/301.2 POINT2 $areafixpassword %LZHmail ;
; >>Logging<<
;
Logfile f:\system\iosmail.log
NoLog -
MSGreport
;
; >>Paths<<
Netmail f:\msgs\0001
Outbound f:\outbound\
Inbound e:\mail\inbound\
ProtInbound e:\mail\protin\
KnownInbound e:\mail\knownin\
TrashArea e:\mail\msgs\9999
MailTemp e:\outbound\temp\
PktTemp e:\mail\inbound\temp\
;
; >>Paths for archivers<<
Archiver e:\binkley\whatarc.ttp x a ; general archiver
LZHarchive e:\binkley\lzs.ttp x a -m ; LZH
ARCarchive e:\binkley\arc.ttp -x -a ; ARC
ZIParchive e:\binkley\zip.ttp -x -a ; ZIP
;
; >>Messagebase management<<
RealName
KillAll
; KillAll is for nodes only
DefDays 30
Deny-Except 2:280/301.* 2:280/0
CopyPVTmail
PathCheck
; PathCheck is for nodes only
SaveLocal
;
; >>Routing<<
Route 2:280/0 *
;
; >>Mail packet management<<
Arc-For 2:280/0
PackKnown
Capture 2:280/301.2 Point X
;
; >>File management<<
File-To *
File-Max 100 2:280/*
3.5.4 MultiPoint
A setup for points who have more than one boss address.
; Point setup with multiple addresses: multipoint
; for use with BinkleyTerm 3.0
;
; >>Labels<<
#IMPORT
commands -bilt
#ENDLABEL
;
#EXPORT
NiceOutput
commands -sport
#ENDALL
;
; >>Identification<<
SysOp Rinaldo Visscher
Address 2:280/301.1 3303
Address 2:280/501.1 3501
Password 2:280/301.0 PWD1 %ZIPmail
Password 2:280/501.0 PWD2 %LZHmail
;
; >>Logging<<
Logfile e:\point\iosmail.log
NoLog -%
;
; >>Paths<<
Netmail e:\point\msgs\0001
Outbound e:\point\outbound\
Inbound e:\point\inbound\
TrashArea e:\point\msgs\9999
MailTemp e:\binkley\outbound\temp\
PktTemp e:\binkley\inbound\temp\
;
; >>Paths for archivers<<
Archiver e:\point\whatarc.ttp x a ; general archiver
LZHarchive e:\point\lzs.ttp x a -m ; LZH
ARCarchive e:\point\arc.ttp -x -a ; ARC
ZIParchive e:\point\zip.ttp -x -a ; ZIP
;
; >>Messagebase management<<
CopyPVTmail
SaveLocal
DefDays 30
Deny-Except 2:280/301 2:280/501
;
; >>Routing<<
Boss 2:280/301.0
Route 2:280/301 2:280/3??
Route 2:280/501 2:280/5??
;
; >>Mail packets management<<
Arc-For 2:280/301 2:280/501
;
; >>File management<<
File-To 25 *
If your boss has multiple addresses then it is possible to add
these extra address lines too. In fact this is the same as
multipoint.
3.5.5 MultiZone Setup
There is such a thing as multizone. Multizone nets are differing
only in the way they're using their zonenumber. IOSmail is able to
handle these nets within the one setup.
You just specify the address. Let's say that I have point number 1
and my address is 90:4000/103. My boss is 90:4000/101:
; Multizone setup
; For use with BinkleyTerm 3.00
;
; >>Labels<<
#IMPORT
commands -lit
#ENDLABEL
;
#EXPORT
NiceOutput
commands -sport
#ENDALL
;
; >>Identification<<
SysOp Rinaldo Visscher
Address 2:280/301.1 23301
Address 90:4000/103.0 4101
Password 2:280/301.0 PWDFIDO %LZHmail
Password 90:4000/101.0 PWDNEST %ZIPmail
;
; >>Logging<<
LogFile e:\point\iosmail.log
MSGReport
;
; >>Paths<<
Netmail e:\point\msgs\0001
Outbound e:\point\outbound\
Inbound e:\point\inbound\
TrashArea e:\point\msgs\9999
MailTemp e:\point\outbound\temp\
PktTemp e:\point\inbound\temp\
;
; >>Paths for archivers<<
Archiver e:\point\whatarc.ttp x a ; general archiver
LZHarchive e:\point\lzs.ttp x a -m ; LZH
ARCarchive e:\point\arc.ttp -x -a ; ARC
ZIParchive e:\point\zip.ttp -x -a ; ZIP
;
; >>Messagebase management<<
RealName 1
CopyPVTmail
SaveLocal
KillFrom Ban Fan Bokkam
DefDays 30
;
; >>Routing<<
ApplZone 90: e:\point\nest\ nest.ftn
Route 90:5/0 90:*
Route 2:280/301
RedirectNetmail
;
; >>Mail packet management<<
Arc-For 2:280/301 90:5/0
NewBinkley
;
; >>File management <<
File-To *
If you receive mail from your boss but the nodenumber doesn't
match those in your configuration file, it is possible that
IOSmail will send those messages back. You could prevent this by
specifying multiple address lines in the configuration. Please,
ask your boss about his address numbers.
Example:
You send your mail packets to 90:4000/101, but you receive from
90:5/0. If you haven't added 90:5/0 to your configuration, IOSmail
will send those messages to 90:4000/101 back, because 90:5/0 is
not known to IOSmail. By adding those address line you can prevent
IOSmail from sending back those messages. IOSmail will then
recognise you as a point from 90:5/0.
Example configuration
; Point setup, can also be used as node setup.
; If you you are a node change .1 to .0
;
; >>Labels<<
#IMPORT
Event week 00:00 23:59 commands -ilprtb
Event wkd 00:00 23:59 commands -ilrt
#ENDLABEL
;
#EXPORT
NiceOutput
Event wkd 00:00 23:59 commands -lprroscdt
Event week 00:00 23:59 commands -lprrsc
Event Fr 05:00 06:00 Prepare-Poll 90:5/0
#ENDALL
;
; >>Identification<<
SysOp Rinaldo Visscher
Address 2:280/301.1 23303
Address 2:280/220.0 23220
Address 90:4000/103.0 4101
Address 90:5/0.1 4101
Address 90:4000/0.1 4101
; If you are a node then the next line applies to you
; Address 90:4000/101.0 4101
Password 90:4000/101.0 PWD1 %LZHmail
Password 2:280/301.0 PWD2 %ZIPmail
;
; >>Logging<<
LogFile e:\point\iosmail.log
MSGreport
NiceOutput
;
; >>Paths<<
Netmail f:\msgs\0001
Outbound f:\outbound\
Inbound e:\point\inbound\
TrashArea e:\point\msgs\9999
MailTemp e:\point\outbound\temp\
PktTemp e:\point\inbound\temp\
;
; >> Paths for archivers<<
Archiver e:\point\whatarc.ttp x a ; Archiver
LZHarchive e:\point\lzs.ttp x a -m ; LZH
ARCarchive e:\point\arc.ttp -x -a ; ARC
ZIParchive e:\point\zip.ttp -x -a ; ZIP
;
; >>Messagebase management<<
RealName
KillAll
; KillAll is for nodes only
CopyPVTmail
PathCheck
; PathCheck is for nodes only
SaveLocal
DefDays 20
Deny-Except 2:280/301 2:280/220 90:5/0
CompactMSGS 3
MinMessages 15
MaxMessages 250
AddDomain 90
;
; >>Routing<<
ApplZone 90: e:\point\nest\ nest.ftn
Route 90:5/0 90:*
Route 2:280/301
RedirectNetmail
;
; >>Mail packet management<<
Arc-For 2:280/0 2:280/301 90:5/0
Hold-Del 5 2:281/* 2:284/*
PackKnown PackKnown is for nodes only
;
; >>File management<<
File-To 10 2:281/* 2:280/*
File-Max 150 2:280/301.*
The first address of every zone mentioned in the configuration is
the main address. In the example they are:
2:280/3.1
90:4000/103.0
Other addresses are to show IOSmail and yourself that you also
have these numbers. It's advisable to specify the addresses where
you get your mail in the password lines. Now you've prevented
mail from being sent back to your boss. Thus, if your boss sends
his mail under 90:5/0.0 you'd better use the same address in the
password lines: `password 90:5/0.0 PWD'.
If you are using multizone then you ought to specify this in
AREAS.BBS. Also mail from other zones ought to be specified this
way.
An example:
E:\POINT\MSGS\0001 ATARI 2:280/3 ; This is received from zone 2
E:\POINT\MSGS\0050 AZONE 90:4000/101 ; This is received from
zone 90
You will notice that the area ATARI originates from zone 2 - the
regular Fidonet mail. But the area AZONE originates from zone 90.
Two different zones can be held in one setup. If you are a node,
and you have points, you can specify this the same way as
described earlier in the paragraph about AREAS.BBS. IOSmail will
take care of everything and will put the message for each zone in
its appropriate areas.
If you're a point and you're getting your mail from 90:5/0 and
you've already specified this address in the area line of
AREAS.BBS, then it is not necessary to add an extra address line.
Though this line should be in your password lines, where the
password for your boss can be found.
Chapter Four: THE COMMANDS
IOSmail is a mail import, scan and pack program. This means
IOSmail can pack and unpack your mail and messages and then
prepare them for the mailer software. It boasts a number of
special functions which are triggered by specific parameters.
-A Preserve all mail. If you would like to keep the original
received packets -A will tell IOSmail not to delete these
files but to rename them. Received mail is normally
deleted when it has been unpacked.
-B Save echomail messages in PrivateBoxArea. You can have
IOSmail transfer messages addressed to you personally to
the private area. In contrast to CopyPVTmail -B does not
copy netmail to the PrivateBoxArea. Only messages in the
echomail areas mail addressed to you will be copied.
-C Scan changed areas only. If you have a large number of
areas, this function will come in handy. The switch makes
IOSmail search areas with new mail only. The scanning
process will be speeded up. This only works in combination
with -S.
-D Compact message areas. Old and deleted messages are
removed. See also DefDays and CompactMSGS.
-E Execute label. This command will tell IOSmail to execute
the label. It is also possible to include separate
commands in front of -E.
-F Forced AREAS.BBS compilation - command. When -F is used
IOSmail will compile the file AREAS.BBS to output the file
IOSMAIL.BIN, whether AREAS.BBS has changed or not. This
command is to compensate the lack of the feature of the
archive bit on TOS versions older than 1.04. Hence
AREAS.BBS and DAREAS.BBS file will not automatically be
compiled on those TOS versions.
-H Help. -H produces a list of all the switches and the
version number of the IOS-modules.
-I Import. -I triggers the import mail function. IOSmail will
examine the inbound folder and any found mail will be
unpacked.
-L Update lastread pointers. If you have the LED message
editor at your disposal -L will let LED know if there are
new or unread messages. This only works while using import
or compact.
-M Copy node number from message. In each message there are
^aMSGID- and ^aREPLY-lines. These lines always have a node
number in them. -M collects these node numbers in the
message. Very handy for sending that person a private
message. IOSmail can convert messages into private
messages. If you are answering a message and you would
like to do it in a private message you can simply answer
in that area. All you have to do is mark the message as a
CRASH message in the message header. It will then be sent
in the netmail and not the normal area. -M Lets IOSmail
know the address where the message should be sent.
-O Scan Netmail and pack all mail packets. Netmail will be
scanned for new messages and scanned echo mail will be
processed by an archiver to form mail packets that are to
be sent by a mailer.
-P Make packets. If you are a node and you have points
IOSmail is able to make packets which are almost ready for
transmission, a sort of semi-product, and will do so if -P
is used.
If you're a point you can use this parameter, but you
should have a program that understands these
semi-products, like Pack. If you do not have such a
program you had better not use -P. When -P isn't used the
new messages will be put in netmail.
-Q No log on screen. When using -Q your screen will not
display what functions IOSmail is performing. See also -T,
NoLog and NoDisplay.
-R Protection. With -R you can protect your system from
unwanted mail. You can include -R three times.
1st time: Mail from X:XXX/XXX.X is compared with the node
numbers in AREAS.BBS. Incoming mail for a non-connected
area will be deleted.
When you are scanning messages you can also use -R.
Mail intended for a point/node that isn't found in the
password section will not be sent. This will only work if
you're a node. Incoming mail for nodes or points not in
the AREAS.BBS won't be processed. This so called pack
protection will only work in conjunction with -P.
2nd time: All mail has a password. When -R is called twice
this password is compared with the password in the
password section of your configuration. For example point
1 sends mail with the password PWD1. Your configuration
says the password for point 1 is 2:280/3.1. PWD. They
don't match. Therefore the mail is deleted.
3rd time: If you receive mail from an unknown sender and
the mail is intended for an unknown receiver it will be
refused. Mail from an unknown sender intended for you will
not be discarded, but will be processed.
Should you call -R twice IOSmail presumes you have in fact
called it once and will therefore also perform the
function as if you had only called it once.
Calling -R three times will therefore invoke all three
described functions. The node numbers are compared, the
password is compared and mail from unknown people is
screened. Since points are not allowed to distribute
mail calling -R twice is sufficient for points.
-S Scan areas. All echo message areas will be searched for
new messages. These will then be prepared for
transmission. If no new messages are found nothing will be
prepared for transmission.
-T Write to logfile. This option makes IOSmail write to the
logfile as described in the chapter about the AREAS.BBS
structure. Without -T no logfile will be kept. IOSmail
will use the logfile specified in your configuration file.
-U Uncompile AREAS.BIN. Sometimes it is handy to reconstruct
the original AREAS.BBS and DAREAS.BBS. -U will do that for
you.
-V Compact special areas. When -V is used, only Netmail,
PRIVATEMAILBOX, DUPE_AREA and TRASHAREA will be compacted.
Other areas will be skipped. It has no use to use -V
together with -D.
-W Pause. IOSmail will not terminate upon completion but will
wait for <RETURN> before doing so. This will give you time
to examine what functions IOSmail has performed.
-X Multizone-specification. When you are working with a
multizone configuration it is possible for mail packets to
contain messages for more than one zone. This might cause
problems with the processing. Only use -X where there are
messages for more than one multizone type zone in a
packet.
4.1 Summary of commands
Note that it is also possible to pass switches as -ibtl instead of
-b -i -t -l.
InMail
{options}
-I {-R -R -R -T -Q -M -P -W -B -A -L -F}
ScanMail
{options}
-S {-C -R -T -Q -P -W -X -F}
OutMail
-O {-Q -R -T -W -F}
Crunch
-D or -V {-Q -T -L -F}
Special commands
-F, -H
4.2 Errorlevel
Upon termination IOSmail returns errorlevel 1 if messages were
imported, otherwise it returns 0. This means it will also give
errorlevel 0 if no messages were received. -39 means that there is
not enough free memory available and 10 will indicate a general
error.
4.3 Errors
InMail:
-Don't know the path of the logfile.
LogFile path is not specified in the MAIL.CFG ?Can't execute XXX
Archiver is not found.
-Archiver returns errorcode X, renaming.
Archiver returned an errorcode not equal to 0.
!Can't rename.
The packet cannot be renamed. Please check for duplicate file
names.
?Can't open X
File X cannot be opened. Perhaps a System error?
!Packet version is not 2 but X
This packet was not of type 2 but x. It probably is not a packet.
!Password error. His 'X' ours 'XXXX'
Password in packet does not match.
!Packet X renamed to bad.
Packet has been renamed to a file with extension .BKT.
!Illegal message type. Searching message header Illegal message
type. Next message will be processed.
-Unexpected end of PKT file.
The PKT file has no termination bytes.
-Non-processable message. Searching next message.
Message cannot be imported. The To-From field is too long. Next
message will be processed.
?Heavily damaged packet or not a packet.
A packet is severely damaged. IOSmail could not recognise it as a
packet.
?Unexpected end of message.
This message is not terminated by a null byte. Next message had
already started.
!Message too long. Partially saved.
Message is longer than 30 Kb. It is partially saved.
!Message found X bytes skipped.
A new message was found after illegal message type was found. X
bytes were skipped.
!Can't find message header.
The message header could not be found.
?Secondary arealine X in message.
Secondary AREA: line was found in one message. X was the second
one.
!No message.
IOSmail could not recognise this as a message.
!More arealines in message. Tossed to TRASHAREA.
Multiple area lines were found. The message will be put in the
TrashArea.
!INTL line error.
INTL line has an illegal format. Format should be INTL
<Dzone>:<Dnet>/<Dnode> <Ozone>:<Onet>/<Onode>.
!Message empty, copying '---' in it.
An empty message was found. Usually messages originating from Tick
2.00 DOS.
!Origin address not in password line(s).
-x error. The origin address was not found in the password lines.
!X:X/X.X not listed in area Q.
Security. X:X/X.X was not listed in area Q.
!Path of PRIVATEMAILBOX unknown. Please check.
Unknown PrivateMailBox path. Messages will be put in the root
directory.
?Can't open SYSTEM HEADER
XXXX.HDR could not be opened.
?Can't open SYSTEM AREA
XXXX.MSG could not be opened.
!Write error, disk full.
No diskspace available.
!Write error.
Write error. This can have many causes.
!X:X/X.X not known, message not exported.
Security level 1: Unknown password. Please check password lines.
!Please check passwords in CFG and/or area X.
See preceding error.
!Can't open packet.
PKT file could not be opened.
!Can't create packet.
PKT file could not be created. System error.
?Unknown error on packet.
An unknown error has occurred.
Netmail msg too long. This msg will not echoed anymore.
Netmail message is longer than 30 Kb. This message will not be
echoed.
ScanMail:
!Error on messagebase.
.MSG could not be opened or read.
!Error no AREA line found. Please rewrite.
Private area. <arrow right>[<AREANAME>] line has been removed.
!ERROR, unknown area number < 0 [X]
Area number was not listed. This message is put into the
privatemailbox area.
-Warning, origin X sign(s) too long in area Q.
Origin line exceeds 75 characters in area Q.
!Illegal ^aMSGID:
Illegal MSGID. This cannot be changed.
Message to big to add X
Message is too large to add to a certain area.
General:
!Memory error
Perhaps not enough RAM
!Path too long (X)
Path X is too long. It exceeds 80 characters.
-Can't open X
X cannot be opened.
?Can't handle X
Unknown keyword X.
-Configuration not found.
IOSMAIL.CFG is not found.
-Can't open logfile.
Logfile could not be opened.
!Don't know the path of the logfile.
Logfile path could not be found.
Don't know the path of your INBOUND/OUTBOUND.
Inbound or Outbound folders could not be found. Please check
MAIL.CFG.
!Error writing PKT.
Error whilst writing to PKT file.
!Can't open lastreadfile.
LED.NEW file could not be created or updated.
Chapter Five: WARRANTY
The author of this program and the authors of this document shall
not in any case be liable for special, incidental, consequential,
indirect, or other similar damages arising from the use or misuse
of this program or misinterpretation of this document.
This program is recommended for the import, export and crunch of
message areas in the format described in FTS-0001 only. Any other
use is not recommended.
The use of this program is at your risk. The program has been
tested thoroughly and we do not expect any errors. Errors caused
by misspelling in this document are not attended to.
Chapter Six: QUESTIONS?
If you have any questions, remarks, complaints or comments please
contact us at one of the following Fidonet address. We urge you to
re-read the manual before contacting us with your question. Ninety
percent of all questions we receive could normally have been
answered by just referring to the manual or READ-ME.NOW file!
Questions to which the answer can be found in the manual will not
be answered. This saves us time, which could be put to better use
developing IOSmail.
If however, you are still experiencing problems, then you can
write to us at in the IOSMAIL_HELP echo, available at your Fido
Host. If this echo cannot reach you, you can write netmail to us.
Check for your nearest IOSmail Support Centre. Any complaints,
comments, ideas or bug reports should be reported immediately to
IOSmail HeadQuarters via Netmail:
For users in The Netherlands, Belgium and Luxemburg and areas that
other IOSmail Support Centres do not cover:
IOSmail HeadQuarters
Eddie Tao, FidoNet address 2:280/312
(mail only and online between 00.00 and 05.30 GMT)
NeST address 90:4000/107
For users in United Kingdom and Ireland:
IOSmail Support Centre UK
Robert Darling, FidoNet address 2:255/375
NeST address 90:1/1
For users in Australia and Asia:
IOSmail Support Centre Australia & Asia
Andrew Davies, FidoNet address 3:712/520
NeST address 90:6/0
For users in North America:
IOSmail Support Centre USA
Bryan Hall, FidoNet address 1:103/1027
NeST address 90:3000/1005
For users in Germany, Switzerland and Austria:
IOSmail Support Centre Germany
Bernd Renzing, FidoNet address 2:245/52
NeST address 90:4/0
For users in Italy:
IOSmail Support Centre Italy
Magic.Alex Badalic, FidoNet address 2:331/317.1
NeST address 90:7/1
For users in Scandinavian countries:
IOSmail Support Centre Scandinavia
Rikard Oesterman, FidoNet address 2:201/631
NeST address 90:11/0
Since we strive for perfection, this program is constantly being
revised and improved. It is therefore possible that keywords and
options have been added that are not yet described in this
document. This document will be revised to reflect any essential
change in the program and will always accompany the program in the
most recent revision. Commands and keywords present in IOSmail
will be shown in the IOSMAIL.HLP file, which will be updated with
every release of the IOSmail program. See also the included
READ-ME.NOW file.
If you would like to stay informed on the latest news on the
development of IOSmail you should connect yourself to the
IOSMAIL_HELP echo, which will be available at your FidoNet host.
Progress and update reports will be announced periodically by
IOSmail HQ.
Appendix A: GLOSSARY
A
AddAKA
Keyword. Adds extra addresses to the SEEN-BY line. Not suitable
for points.
AddDomain
Keyword. Adds domain names after the address in the origin line.
Address
The number under which you are known and where your mail is sent
to.
ApplZone
Keyword. Used to define additional zones or networks. It has the
samefunction as BinkleyTerm's keyword "Domain".
ARCarchive
Keyword. Used to specify the path to Arc.ttp.
Archiver
A program that is used to compress and decompress files. If used
on mail packets it will reduce the time of file transfers and thus
save money.
It is also a keyword to specify the path to a general archiver.
IOSmail will recognise ZIP, LZH, ARC or ARJ automatically.
ARCmail
Mail that has been processed by an archiver. It is a short for
Arced Mail.
Arc-For
Keyword. Used to determine which nodes or points should receive
ARCmail packets.
Area or Echo
A message area with a specific topic. Anyone can receive Echos
whereas netmail is only between two people.
AREAS.BBS
An ASCII file that specifies the location of the message areas and
can also define the origin line used in the message areas.
AREAS.BIN
A binary file which contains information compiled from AREAS.BBS
and DAREAS.BBS.
AreaConsultant
A program that performs the task of opening and closing message
areas for use.
ARJarchive
Keyword. Used to specify the path to the Arj archiver.
ASCII
Short for American Standard Code for Information Interchange.
B
BBS
An electronic bulletin board system. A method of communicating
and sharing files with others by computer. Typically operated by
hobbyists.
BOSSPWD
A special password you use to gain entrance to you boss' system.
BOSS(NODE)
The person that provides the points with their mail and to whom
the points send their mail.
C
Capture
Temporary textfile.
Keyword. To determine which nodes or points
receive mail directed only to them.
CheckNames
Keyword. Compares the name of a message to the one in the password
lines. If necessary IOSmail will complement the address number.
Not suitable for points.
CompactMSGS
A keyword that tells IOS when the
message areas should be compressed.
CopyPVTmail
Mail addressed to the sysop is copied to a special area.
CopyArea
Keyword. Used to specify whose messages should be copied to a
particular area. See also MoveArea.
Copy-to-Point
Keyword. If used in conjunction with CopyArea or MoveArea, points
will get those message on hold.
CRASH
To send the message direct to addressee without first sending it
to your boss.
Crash-To
Keyword. Used to determine which nodes should receive CRASHmail.
Crunch
Permanent deletion of messages which are marked `killed' or which
are too old.
D
DAREAS
File for distribution areas. This has the same structure as the
AREAS.BBS file and will be compiled by IOSmail to AREAS.BIN
together with AREAS.BBS.
DefaultPKT
Keyword. Determines the packet type of the CRASHmail packets.
DefDays
Defines the period in days, that message is kept in a message area
before being deleted. Unless -DAYS or -KEEP is used.
Distribution area
A message area in which messages can be
shown selectively or used at nodes only. The particular areas are
specified in the DAREAS.BBS file.
E
EchoMail
Public messages which are `echoed' throughout the network. It was
devised by Jeff Rush.
Errorlevel
The name of an environment variable; contains a value returned by
a program on exit that indicates a certain pre-defined condition.
Event
Keyword. It is used to specify particular sets of commands which
should be executed at predefined days and on predefined times.
Export
Prepare mail for transmission. Comprises of a scan and pack
session. See also command -O and -P.
F
FastImport
Keyword. Can only be used on point systems. When used it will
speed up the import of messages, because it will rearrange message
in memory.
FDataBase
Keyword. It specifies the path to the FidoNet database. With this
database it is easy to copy messages to and from the regular
message base.
FDGetFrom
Keyword. Used to specify which kind of messages should be copied
to the FidoNet database. Messages from or to a person can be
picked out.
FidoNet
An electronic mail network operating on Atari STs, PCs,
Macintosh's and other makes that encompasses the world. It has
been designed by Tom Jennings Also see Appendix D. The FidoNet is
structured as follows:
ZONEgate/HOST/HUB/NODE/POINT, whereby ZONEgate is the highest
level and POINT is the lowest level.
File-Max
Keyword. It is used to indicate the number of kb that may be sent
by nodes or points.
File-To
Keyword. It is used to indicate which points of your node are
allowed to send files via your system.
FMPT
Short for FroM PoinT. This is found in a message from a point.
G
Gateway
A system on which several networks can exchange their mail.
IOSmail can be operated as a gateway for NetMail only.
-GROUP
AREAS.BBS keyword. It is used to specify to which group a
particular area belongs.
H
Help
Option -H shows a help screen. This screen will show available
commands and keywords.
HDR
The header file of a message area. It contains information about
its sender and receiver.
Hold-Del
Keyword. It indicates the maximum allowable size of a mail packet.
If this amount is exceeded the packet will be deleted.
Hold-For
Keyword. Used to specify which points or nodes IOSmail will put
mail on hold for.
Hold-Max
Keyword. Used to specify the file size of a mail packet. If this
is exceeded the hold file will be changed to a poll file.
Hold-To-Poll
Keyword. Change from hold file to poll file immediately.
HOST
Processes the mail for a net. A typical HOST in the UK would have
a 2:25x/0 number.
HUB
Supports the host in larger networks.
I
ImportUnpack
the received mail and put the messages in the appropriate message
areas. This task is done by the InMail module of IOSmail.
Inbound folder
This is a special folder for the acceptance of incoming mail or
files from other networks that area not listed your nodelist of do
not have passworded mail sessions with you.
INTL
International zone addressing for nodes. This can be used in
MultiZone systems. The INTL lines are put into the messages.
Either in echomail or netmail or both.
IOSMAIL.TTP
Import, export and scan and crunch program by Rinaldo Visscher.
IOSMAIL.HIS
The file that keeps track of the number of imported messages and
in which areas this has been done. It will only be created if
MSGReport is used and if it doesn't already exists.
IOSMAIL.LNG
A file which contains all of IOSmail's warnings.
IOS_GER.DOC
IOSmail manual, German.
IOS_NL.DOC
IOSmail manual, Dutch.
IOS_UK.DOC
IOSmail manual, English.
K
-KEEP
AREAS.BBS keyword. messages will only be deleted by IOSmail if
they are marked as `deleted'. It overrules DefDays and -DAYS, and
other related keywords.
KeepPrivate
The private mail you write will be preserved.
KillFrom
Delete any messages originating from
specified persons.
KillAll
Delete any mail not intended for the sysop except for other nodes
and/or points.
KillSent
Messages marked as KillSent will be deleted upon transmission.
KnownInbound
Used with secured inbound areas, this statement specifies the path
to the inbound file area used for mail received from "known"
systems. These are systems that are listed in your nodelist for
use with BinkleyTerm.
L
Label
A set of tasks for IOSmail. Labels are executed by calling them
with: -E Labelname.
local(ly)
On your system only.
-LOCAL
AREAS.BBS keyword. When used only the sysop can write in a
particular area. This keyword cannot be used by points.
LogFile
A text file containing a log of the functions IOSmail has
performed. Keyword. It is used to specify the path to the logfile.
See also NoLog and NoDisplay.
LZH
Particular compression method used by LHarc. Also the extension of
file which are prepared by LHarc.
LZHarchive
Keyword. It is used to specify the path to the archiver for LZH
archives.
M
MAIL
Electronic mail. Keyword for IOSmail. Also short for NetMail.
Mailer
A program that operates as a FidoNet-compatible mail handler,
using FidoNet protocols. A mailer answers the phone, accepts
and/or sends mail, and if possible passes human callers on to a
BBS.
Mail packet
A unit of mail as defined in the Fidonet Technical Committee
document FTS-0001.
MailTemp
Keyword. It is used to specify the folder in which temporary pkt
files are placed before being processed by an archiver.
MaxMessages
Keyword. The maximum number of messages allowed in a certain
message area. Any message over this number will be marked as
`deleted'.
-MESSAGES
AREAS.BBS keyword. This indicated the maximum allowable number of
messages that may be held in a particular area. See also
MaxMessages.
MinMessages
Keyword. The minimal number of messages that have to be preserved
in a certain message area.
MinDiskSpace
Keyword. Checks the disk for free space before importing. If free
space is less than specified then messages will not be imported.
MinPacketSize
Keyword. Used to indicated the size of a mail packet. If this size
is exceeded the mail packet will be processed by the archiver.
MoveArea
Keyword. MoveArea has the same syntax as CopyArea. But selected
messages will be moved instead of copied.
Move-Mail
Mail from other systems will be added to a particular system's
mail packet.
MSGID
Origin of a node/point message.
MSG
The message file. One of two files that make up a message area. It
contains the actual message in ASCII.
MSGReport
Keyword. Prepare a list of all imported messages. Data will be put
into the file IOSMAIL.HIS.
MultiZone
Working with multizone mail, mail originating from other zones
(and not FidoNet), but which are part of the same structure. See
also command - X.
MultiTasker
Keyword. Used to specify the MultiTasking environment you use.
message editor
A program intended for processing messages from FidoNet or similar
networks. LED or CANED for example.
N
-NAME
AREAS.BBS keyword. It is used to specify the name that has to be
used in a particular area.
Net
A subset of a FidoNet compatible network, usually a collection of
nodes within a certain geographical area.
Netmail
Private messages. They will not be arded
throughout the network. Also see Mail.
Keyword. Specification of the path to the netmail
area.
NetCoordinator(NC)
Processes the netmail and nodediffs for
nodes in his net.
Net Echomail Coordinator (NEC)
Processes and supervises the echomail structure in his net.
Net Number
This is the second number of a FidoNet address. 1:989/8.18, where
989 is the net number.
NewBinkley
Keyword. It is used to tell IOSmail to create BinkleyTerm 3.0
compatible packet types. See also the keyword IOS used in
BINKLEY.CFG.
NiceOutput
Origin and Destination of a message will be written into a log.
Node
A FidoNet compatible system, represented by a node address, and
listed in a nodelist.
Nodediff
A Host/Hub will update its nodes with NODEDIFF.Axx files. These
are files which contain the changes necessary to create
NODELIST.xxx from the previous week's nodelist. xxx stands for day
number.
Node number
This is the third part of a FidoNet address. 1:970/11.6, where 11
is the node number.
NoDisplay
Keyword. Determines which warnings or errormessages should not
appear on the screen whilst processing.
NoLog
Keyword. Determines which warnings should not appear in the
logfile.
NoNetMailPack
Keyword. NetMail will not be packed when used. This is to allow
netmail attached file transfers to FrontDoor mailers. { Only
suitable for points }
NoZone
Keyword. Zones will not be included in the SEEN-BY and PATH lines
of echomail.
O
Origin line
A line at the bottom of a message that shows where a message
originated. For more information, please refer to the FidoNet
Policy.
Open Message
A message which anyone can read. This message type is used in
EchoMail.
Outbound folder
Also known as the "Hold Area" this is a special subdirectory set
aside specifically for storing mail waiting to be sent to or
picked-up by another system. See also MailTemp.
P
Packer
A program that processes mail entered on a system, and prepares it
for transfer by a mailer.
It is also a name given to programs that compress
files.
Packet
Within FidoNet, a message unit conforming to FTS-0001
specifications.
PackKnown
Prepares mail for known points/nodes. These point/nodes can be
specified in IOSMAIL.CFG.
Password
The password option in IOSMAIL.CFG. This secures a system against
unwanted mail.
PathCheck
Check if a message already exists by looking at the net and node
numbers of the SEEN-BY and PATH
lines.
PKT files
Files that are processed by IOSmail. These are actually messages
with some binary data header followed by the actual message text.
See also FTS-0001 for more information.
PKTTemp
Keyword. It is used to specify the path to the folder in which PKT
files are held whilst importing. They are deleted afterwards.
Point system
A BBS user who types his/her messages off line and then sends them
to his/her boss with a mailer.
Point Number
This is the fourth part of a FidoNet address. 1:989/8.20, where 20
is the point number.
Point shell
A set of programs for points which allow the mailer system to do
its task in an easy to use manner.
Poll
A call to another mailer system, sending and picking up mail if
there is any.
Prepare-Poll
Keyword. It is used to make IOSmail create a file that tells the
mailer to call another system.
PrivateBoxArea
A special message area in which echo messages addressed to the
sysop are placed.
Private Mail
See Netmail
ProtInbound
Used with secured inbound areas, this statement designates the
path to the inbound file area used for mail received from
"protected" systems. These systems are listed in your nodelist and
require a mail session password.
R
RealName
Keyword. Use the registered name as sender. This information will
be added into echomail.
RedirectNetmail
Keyword. It will change the origination address in a message to
one of your addresses with the same zone as the destination if you
have one.
Region
With regard to FidoNet addressing, a region is handled the same
way as a network. With regard to operational infrastructure, this
is a higher level than a net.
Region Coordinator (RC)
Takes care of the information from the hosts to the Zone
Coordinator. For example: Region 25, The UK, RC: 2:25/0.
Region Echomail Coordinator (REC)
Takes care of the Echomail structure within his
Region.
-REMOTE
AREAS.BBS keyword. This keyword specifies which nodes have write
access to a particular area. This keyword is not suitable for
points.
Route
Path which echomail should follow. Several nodes or points can be
specified.
S
SaveLocal
Keyword. Rewrites messages locally after scanning by adding
tearlines and originlines so that you can see how your messages
look when they arrive at their destination.
Scan
Look if there are any new messages and then prepare them to be
processed by an export program, such as IOSmail for transmission.
SendAlwaysPKT
Keyword. When used, IOSmail will create a zero length pkt file so
that you will receive mail from Front Door systems. See also
Prepare-Poll.
SEEN-BY line
Lines at the bottom of echo mails. They indicate which nodes have
seen the message. Actually only systems with 3d addresses which
are still recognisable will be shown in the SEEN-BY lines.
SysOp
System Operator; the person who operates a BBS, and/or the
operator of a FidoNet node.
Also keyword to specify under what name messages
are written.
T
The-Box
Keyword. When used IOSmail will create mail packets which are
compatible to the The Box mailer. The filenames used by The Box
are different to BinkleyTerm's method.
TinySeenBy
Keyword. When used IOSmail will not add fakenet addresses to the
SEEN-BY lines.
TOPT
Short for TO PoinT. A message destined for a point. It is part of
the message identification.
TrashArea
Keyword. Used for specification of the path to the TRASHAREA. If
messages cannot be placed in existing areas they will be directed
to the TrashArea.
U
Unpack
The process of decompressing mailpackets by an archiver program.
After unpacking, a mail packet will have regained its original
size.
Unpacker
A general name for programs that unpack files. They are also
called `archivers'. Before IOSmail can do anything with ARCmail
packets they have to be unpacked.
Z
ZIParchive
Keyword. It is used to determine the path to the program ZIP,
which processes ZIP archives.
Zone
A large geographical sub-division in the network, the highest
level of the accepted FidoNet addressing scheme. Broad areas such
as continents are given zone designations. Also used to specify a
particular alternate network. For example NeST.
ZoneGate
A system that transfers mail between zones.
Zone Coordinator (ZC)
Takes care of Nodediffs for his zone. For instance
Zone EUR (Europe) has 2:2/0 for a ZC.
Zone Mail Hour
A time window used by mail systems for transferring netmail. This
is between 02.30 and 03.30 GMT in Zone 2 (Europe).
Zone Number
This is the first number in a FidoNet address. 1:989/8.25, where 1
is the zone number. FidoNet has zone number ranging from 1 to 6,
whereas NeST has zone number 90 only. (FidoNet actually consists
of 6 nets, called zones. ET)
Appendix B: ECHOMAIL
Echomail is a set of message areas that are publicly accessible.
Any messages written in Echomail will be echoed throughout the
network, hence the name echomail. Note that echomail is not the
same as Netmail. Echomail is transferred by being file attached on
Netmail messages. FidoNet actually is based on netmail
communication.
Usually echomail will be monitored by a so called moderator. The
moderator will check that the participants do not break any rules
or agreements appropriate to a certain echo. If participants
disobey rules too often the moderator has the right to disconnect
the participant(s) in question. Usually a user will get a warning
first. If this has no effect then more drastic measures can be
taken.
In the following paragraph there are some hints about using
echomail.
o Please, note which language a certain echomail is in. If it is
English, then you should not write in any other language.
Because people who do not understand English will still have
to pay for the costs to transfer those messages.
o To offer or swap illegal software is not allowed.
o Commercial advertisements are not allowed (in FidoNet).
o Please, stay with the subject of an echo. Otherwise echomail
areas would not have been classified.
o Please, note your language. Bad and/or abusive language will
not be useful information.
o It is only allowable to use ASCII characters ranging from 31
to 127. The other characters (such as accents and graphic
symbols) are not standard across different computer types, and
may be unreadable by many people.
If you need any further information, please, ask your Boss or
Host.
Appendix C: NETMAIL
Netmail messages are private messages sent between two
users/systems. These messages will not be routed through the
network. Netmail will be useful if you want to write a message to
somebody which other people should not read or when it is
necessary to reach the other person.
First you should know the address number of the BBS which the
addressee often calls. (See also chapter two)
An address number has the following structure:
2:280/301.0
This is the node number of Dutchman data BBS in Amsterdam. Where 2
is the zone number, 280 is the net number, 3 is the node number
and 0 is the point number.
The zone number is 2: which means we're situated in Europe. Zone 1
is Northern America. The net number is 280 which is more or less
the same as the net number of the phone network. In the
Netherlands Dutch FidoNet Foundation (DFF) supervises the nets 280
to 285, except for 282 and 283. Though there are other nets:
o 500, Home Computer Club (HCC)
o 512, Personal Computer Club (PCC)
o 286, Dutch Independent Net (DIN).
The node number, 3, is Dutchman's node number. In this case 3
signifies this address belongs to a Hub. If it was 308 this
address would be a regular node.
Appendix D: POINTS
Points
You've probably noticed that your favourite BBS is busy. Or that
your phone bill is too high. What can you do about it? Do you want
to know what's going on? If you feel you are this kind of user
being a point system might help.
What are Point Systems?
Point Systems, or Points for short, are users who call their BBS
at regular intervals. They collect mail and dump their own mail. A
BBS (or mailer system to be exact) will then process this mail as
if it were entered on line.
At home your newly collected mail is unpacked and messages put in
their appropriate area. Then you (as a point) can read and reply
to mail at your leisure. You can also request files from your
Boss without the hassle of wading through the file menus on-line.
Thus a point has regular contact with their BBS, receives any mail
they want and most importantly has less phone costs.
Mailers and other utilities
There are many point setups available. But most of them cost you
money. Obviously buying or downloading a shareware setup to become
a point will cost you some money. But nevertheless it will be
beneficial in the long run. For the Atari ST, generally available
mailers are BinkleyTerm-ST and The Box.
A Point Setup
The software which a point runs consists of three programs:
message editor, mail packer and the mailer. Furthermore a few
message areas should be available. Next is a scheme of a typical
point system:
Phone line Message Editor
| |
| +--------------------------------------+
| | | | |
| V V V V
| +---------+ +--------+--------+--------+
V | NetMail | |echomail|echomail|echomail|
Mailer <-> | Messages| <-+ | area | area | area |
+---------+ | |QUESTION| ATARI | MODEMS |
| Netmail | | +--------+--------+--------+
| Files | | ^ ^ ^
+---------+ | | | |
| V V V
+-----------------------------+
|
Mail Packer
Message areas
There are three kinds of message areas: Local, Netmail and
Echomail. Local messages usually aren't that interesting to
points. Since a point is a one man BBS, leaving mail to others
does not make any sense. Netmails are user to user messages.
Echomail areas contain public messages shared between many BBSs
and points, which you pick up from your Boss (the system to which
you connect).
The Message Editor
The message editor is actually a kind of a one man BBS. Messages
can be read, replied to, entered and deleted. Netmail messages may
have file attached to them.
The Mail Packer
Netmail is the only physical way to send messages through the
network and since Echomail is also intended for other boards it is
necessary to pack these messages. These packets will then be
attached to a dummy Netmail message. Such a file is called an
Arcmail packet, and packing messages is called exporting messages.
Received mail packet will be unpacked by the mail packer and will
be imported into appropriate message areas.
The Mailer
A Mailer is needed to transfer mail packets through the phone
line. A mailer will send and receive mail. The scanner will scan
the Netmail area for messages not yet sent. The export program
will determine the route that a mail mail packet will follow to
get to its destination. The mailer will determine what time the
mail packets are to be sent and if files could be sent along. This
will be setup during installation of the mailer. At a predefined
time the mailer will call BBSs and will ask if there's any mail to
pick up. Then the connection will be terminated. SysOps of point
systems don't have to supervise this. Usually these mail transfers
happen automatically at night.
Appendix E: REFERENCE
Commands and Switches
InMail
-I [ Import message(s) ]
-A [ Don't delete Arcmail after import ]
-B [ Copy message(s) to sysop to PrivateMailBox ]
-M [ Take numbers from ^aMSGID: & ^aREPLY: ]
-R [ Secure system (2 times = Password check) ]
ScanMail
-S [ Scan messagebase ]
-C [ Scan changed areas only ]
-D [ Compact all areas ]
-V [ Compact Netmail, PrivateMailBox and TrashArea ]
OutMail
-O [ Scan Netmail and pack messages ]
Miscelaneous
-E [ Execute label in configuration ]
-F [ Forced compilation of AREAS.BBS ]
-H [ This message ]
-L [ Update LED 1.00 lastread pointers ]
-P [ New or imported msgs to Packet for nodes ]
-Q [ Quiet mode: no output to screen ]
-T [ Log output to logfile ]
-U [ Uncompile AREAS.BIN ]
-W [ Wait for RETURN at end ]
Keywords
AddAKA
Extra AKA address in SEEN-BY line.
AddDomain
Add domain name after address number.
Address
FidoNet address specification.
ApplZone
Zone number specification.
Arc-For
ARCmail for particular nodes/points.
Archiver
Used archiver specification.
ARJarchive
Specification of ARJ packer.
Boss
Specification of your boss' number.
Capture
Hold Netmail for node/point. Only node usage.
CheckNames
Comparison of the name of a message to the one in the password
line.
CompactMSGS
Specification of the condition on which message bases should be
compacted.
CopyArea
Copy particular messages to an area.
CopyPVTmail
Copy mail to PrivateBoxArea including Netmail.
Copy-to-Point
Put messages on hold for points which are copied or moved by
CopyArea/MoveArea.
Crash-Point
Install a point as a crashable system.
Crash-To
Specification of nodes that receive crash mail.
DateFormat
Specification of the date and time format for the screen and
logfile.
DefaultGroup
Specification of the standard area group.
DefaultPKT
For specification of the PKT type used in crash mails.
DefDays
The number of days a message should be held in the message area.
Deny-Except
Selective processing of mail by specifying nodes/points.
DupeLog
Amount of message to track in order to filter to duplicate
messages.
Event
Declaration of a particular batch of commands which IOSmail has to
run.
FastImport
Import speeder for points only.
FDataBase
Specification of the path to the FidoNet database.
FDGetFrom
Pick out particular messages for the FidoNet database.
File-Max
Maximum amount of kb which nodes/points may send.
File-To
Nodes/points that are allowed to send eachother files via netmail.
Hold-Del
Maximum allowable size of a mail packet before it is deleted.
Hold-For
Specifications of nodes/points that receive mail from your system.
Hold-Max
Maximum allowable size before a mail packet is changed to a poll
file.
Hold-to-Poll
Change hold file to poll file.
Inbound
Folder specification for incoming mail and/or messages.
KeepPrivate
Mail in PrivateBoxArea will not be deleted.
KillAll
Delete all mail except mail to you. Node usage only.
KillFrom
Delete messages from specified people.
KillSent
Delete all mail except mail to you and point-to-point mail.
KnownInbound
Designation of the inbound path for mail from known systems.
LogFile
Keep a log of IOSmail's performed functions.
LZHarchive
Specification of the path to the LZH program and its parameters.
MailTemp
Specification of the path to the folder to store temporary pkt
files during export session.
MaxMessages
The maximum number of messages an area should contain after
compaction.
MinDiskSpace
Check available diskspace before message import.
MinPacketSize
The size of a packet. Exceeding will lead to
packing it.
MinMessages
The minimum number of messages an area should contain after
compaction.
MoveArea
See CopyArea. MoveArea moves instead of copying messages.
Move-Mail
Put messages directed to different systems in to a particular one.
MSGBuffer
Allocation of RAM for processing incoming and outgoing messages.
MSGReport
Write information about imported messages into the IOSMAIL.HIS
file.
MultiTasker
Specification of multi task environment.
Netmail
Specification of the path to the netmail area.
NewBinkley
Output BinkleyTerm 3.0 compatible mail packets instead of regular
BinkleyTerm 2.40.
NiceOutput
Origin and Destination will be written into the regular IOSmail
log.
NoDisplay
Specification of warnings that should not be shown on screen.
NoLog
Specification of warnings that should not be written to the
IOSmail logfile.
NoNetmailPack
Leave netmail unpacked.
NoZone
Leave out zone numbers from the SEEN-BY and PATH lines.
Outbound
Folder specification for outgoing mail and/or files.
PackKnown
Pack mail for known nodes/points.
Password
Password specification.
PathCheck
Check if a message already exists by looking at the net and node
numbers. ( Not suitable for points ).
PktTemp
Specification of the path to the folder which hold the pkt files
temporarily whilst importing.
Prepare-Poll
Write a poll file for a particular node. The mailer will then dial
out.
ProtInbound
Specification of the inbound path for mail from protected systems.
QbbsLastRead
Update the QBBS lastread pointer.
Realname
Use the name contained within messages.
Readdress
Redirect messages from particular nodes.
RedirectNetmail
Change the origination address to address of the zone you are
writing to.
Route
Specification of the route echomail should follow.
SaveLocal
Write back entered messages locally.
SendAlwaysPKT
Creating of a dummy pkt file with length zero.
StripPID
Strip the PID line in a message.
SysOp
Sysop's name definition.
The-Box
Create The Box compatible mail packets.
TinyPath
Leave out the fakenet number at point pathlines.
TinySeenBy
No fakenet addresses will be added.
TrashArea
Area used for storage of mail that could not be imported into any
known area.
ZIParchive
Path to the ZIP program and its parameters.
Appendix F: TECHNICAL INFORMATION
Technical data
Language:
IOSmail is written in Turbo C 2.0.
IOS Checks:
- AREA lines. Checking on double AREA lines.
- ^aAREA lines. Checking on double ^aAREA lines.
- SEEN-BY lines
- ^aSEEN-BY lines
- ^aPATH lines
- ^aMSGID line
- ^aREPLY line
- ^aREALNAME line
- If origin line exists. It will create one if not.
- If tearline exists. It will create one if not.
- Continuous checking of zone numbers.
- Checking mixed zones in packet.
- Checking mail password.
- Checking diskspace.
- Checking if destination exists in configuration.
- Checking length of From field in packet.
- Checking length of To field in packet.
- Checking length of Subject field in packet.
- Continuous checking of packet if this is a packet.
- Checking for empty From field in packet.
- Checking for empty To field in packet.
- Checking date and time in packet.
- Checking for empty Subject field in packet.
- Checking for unexpected message or PKT end in PKT file.
- Checking length of message.
- Checking on legal ^aMSGID
- Checking on legal ^aREPLY
- Checking on legal ^aFMPT
- Checking on legal ^aTOPT
- Checking on legal ^aINTL
- Checks area name is MAIL. Then this is Netmail.
- Checks for ^aTOPT if address in message header is 4d.
- Checks for ^aFMPT if address in message header is 4d.
- Checks if sender is using our address.
- Checks if this is an empty message.
- Checks inbound folders.
- Checks if receivers are in the configuration.
- Checks if receiver is allowed to have echomail.
- Deletes all duplicate nodes from the SEEN-BY lines.
- Checks ^aPATH line for strange things.
- Checks if receivers are not our node.
- Checks SEEN-BY for who has already had that message.
- Checks even on non-kludged PATH lines.
- Checks for SEEN-BY lines in the middle of the message.
- Checks for ^aPATH lines in the middle of the message.
- Checks for digits in SEEN-BY and ^aPATH lines.
- Continuous checking of written PKT files for NULL bytes at
the end of PKT.
- Checks ^aMSGID if the area is in the same zone as in ^aMSGID.
- Checks length of messagebase.
- Checks PKT header type, i.e. QMM or FrontDoor/D'Bridge.
Channels
Channels opened:
- 10 files for PKTs
- 6 files for message base
- 1 file for log.
IOSmail will keep all files open until the end of importing PKTs.
During the writing of this manual
Coffee: gallons of it! And not to forget Rock; Somewhere in Time
and Piece of Mind from Iron Maiden kept me awake.