bbs/deb-mbse
Archived
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Initial revision

Browse Source
This commit is contained in:
Ken Bowley
2001-08-17 05:46:24 +00:00
commit 40420d900a
750 changed files with 177485 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

44
html/setup/archiver.html Normal file
View File

@@ -0,0 +1,44 @@
<HTML>
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META name="author" lang="en" "content="Michiel Broek">
<META name="copyright" lang="en" content="Copyright Michiel Broek">
<META name="description" lang="en" content="MBSE BBS Manual">
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
<TITLE>MBSE BBS Setup - Archiver programs.</TITLE>
<LINK rel=stylesheet HREF="../manual.css">
</HEAD>
<BODY>
<BLOCKQUOTE>
<h5>Last update 29-Jan-2001</h5>
<P>&nbsp;<P>
<H1>MBSE BBS Setup - archiver programs</H1>
<P>
To process mail, files and test new uploads you need archivers to process those
files. For each (un)archiver you must setup the full path and filename and
commandline switches. Archivers and unarchivers may be different programs such
as <strong>zip</strong> and <strong>unzip</strong>.<p>
There is a little
difference in processing mail and files, mail will always work on the same
directory, while for ticfile processing the archives can contain subdirectories.
So it is obvious that for rearchiving a file you need the recursive
switches to keep the directory structure within an archive as it was.<P>
There is also a special command to replace a banner in an archive. This is when
you receive files with the banner of your uplink in it and you want to replace
it with the add of your own bbs and you don't want to mess with the files in
the archive. <P>
The last option is to extract the file FILE_ID.DIZ from the
archive, this can be used for file description when the file is imported in
your bbs. To make life a little more easy, during the first bbs setup the most
common archivers already configured. You only need to make sure that they are
really present on your system.
<p>
<A HREF="./"><IMG SRC="../images/larrow.gif" ALT="Back" Border="0" width="40" height="30"> Back to index</A>&nbsp;
<A HREF="../"><IMG SRC="../images/b_arrow.gif" ALT="Home" Border="0" width="33" height="35"> Back to main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>

42
html/setup/bbs.html Normal file
View File

@@ -0,0 +1,42 @@
<HTML>
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META name="author" lang="en" "content="Michiel Broek">
<META name="copyright" lang="en" content="Copyright Michiel Broek">
<META name="description" lang="en" content="MBSE BBS Manual">
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
<TITLE>MBSE BBS Setup - Edit BBS Setup.</TITLE>
<LINK rel=stylesheet HREF="../manual.css">
</HEAD>
<BODY>
<BLOCKQUOTE>
<h5>Last update 29-Jan-2001</h5>
<P>&nbsp;<P>
<H1>MBSE BBS Setup - Edit BBS Setup.</H1>
<P>
<H3>Edit BBS Setup.</H3>
<P>
The BBS setup is split in the following sections:
<P>
<ol>
<li><A HREF="security.html">Security limits</a>
<li><A HREF="language.html">Language setup</A>
<li><A HREF="../menus/index.htm">BBS menus</a>
<li><A HREF="files.html">File areas</a>
<li><A HREF="protocol.html">Transfer protocols</a>
<li><A HREF="bbslist.html">BBS List data</a>
<li><A HREF="oneliner.html">Oneliners</a>
<li><A HREF="timebank.html">TimeBank data</a>
<li><A HREF="safe.html">Safe Cracker data</a>
</ol>
<A HREF="./"><IMG SRC="../images/larrow.gif" ALT="Back" Border="0" width="40" height="30"> Back to index</A>&nbsp;
<A HREF="../"><IMG SRC="../images/b_arrow.gif" ALT="Home" Border="0" width="33" height="35"> Back to main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>

28
html/setup/bbslist.html Normal file
View File

@@ -0,0 +1,28 @@
<HTML>
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META name="author" lang="en" "content="Michiel Broek">
<META name="copyright" lang="en" content="Copyright Michiel Broek">
<META name="description" lang="en" content="MBSE BBS Manual">
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
<TITLE>MBSE BBS Setup - BBS Setup - BBS List Data.</TITLE>
<LINK rel=stylesheet HREF="../manual.css">
</HEAD>
<BODY>
<BLOCKQUOTE>
<h5>Last update 29-Jan-2001</h5>
<P>&nbsp;<P>
<H1>MBSE BBS Setup - BBS Setup - BBS List Data.</H1>
<P>
This is not available yet.
<P>
<A HREF="bbs.html"><IMG SRC="../images/larrow.gif" ALT="Back" Border="0" width="40" height="30"> Back to BBS index</A>&nbsp;
<A HREF="./"><IMG SRC="../images/larrow.gif" ALT="Back" Border="0" width="40" height="30"> Back to index</A>&nbsp;
<A HREF="../"><IMG SRC="../images/b_arrow.gif" ALT="Home" Border="0" width="33" height="35"> Back to main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>

48
html/setup/domains.html Normal file
View File

@@ -0,0 +1,48 @@
<HTML>
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META name="author" lang="en" "content="Michiel Broek">
<META name="copyright" lang="en" content="Copyright Michiel Broek">
<META name="description" lang="en" content="MBSE BBS Manual">
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
<TITLE>MBSE BBS Setup - Edit Domains.</TITLE>
<LINK rel=stylesheet HREF="../manual.css">
</HEAD>
<BODY>
<BLOCKQUOTE>
<h5>Last update 30-Jan-2001</h5>
<P>&nbsp;<P>
<H1>MBSE BBS Setup - Edit Domains.</H1>
<P>
<H3>Introduction.</H3>
<P>
The domains table is used to translate Fidonet domains to internet domains
and back for the Fidonet &lt;-&gt; Internet gateway. When you add entries to
this table make sure that the entry <strong>.fidonet</strong> and
<strong>.ftn</strong> is always the last entry. This is the default entry.
New added domains can be moved in place with the <Strong>M</strong>ove
command.
<P>&nbsp;<P>
<H3>Edit Domains.</H3>
<P>
<pre>
<strong>Fidonet </strong>The Fidonet domain to match.
<strong>Internet </strong>The internet domain to match.
<strong>Active </strong>If this domain is active.
<strong>Deleted </strong>If this domain must be deleted.
</pre>
<P>
Next is an example table.
<P>
<IMG SRC="../images/domains.gif" Border=0 width="587" height="342">
<A HREF="./"><IMG SRC="../images/larrow.gif" ALT="Back" Border="0" width="40" height="30"> Back to index</A>&nbsp;
<A HREF="../"><IMG SRC="../images/b_arrow.gif" ALT="Home" Border="0" width="33" height="35"> Back to main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>

164
html/setup/emareas.html Normal file
View File

@@ -0,0 +1,164 @@
<HTML>
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META name="author" lang="en" "content="Michiel Broek">
<META name="copyright" lang="en" content="Copyright Michiel Broek">
<META name="description" lang="en" content="MBSE BBS Manual">
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
<TITLE>MBSE BBS Setup - Mail Setup - Mail Areas.</TITLE>
<LINK rel=stylesheet HREF="../manual.css">
</HEAD>
<BODY>
<BLOCKQUOTE>
<h5>Last update 08-Jun-2001</h5>
<P>&nbsp;<P>
<H1>MBSE BBS Setup - Mail Setup -> Mail Areas.</H1>
<P>
<H3>Introduction.</H3>
<P>
Mail areas have fixed area numbers, just like file areas. But if you want you
can move areas.
Some offline readers don't like changing the area numbers. All areas can
be of the following types: local, netmail, echomail and news. If you gate
news and echomail in the same area, then select echomail
if this area is a Fidonet area, select news if this area is a Usenet news area.
<P>
There is a global setup tool, if you are in the main message area setup screen then
you can choose the Global command. This will allow you to do bulk changes on areas
selected by the mail groups. Options are delete connection, add new connection,
replace connection, change connection status, change days old for purge, change
maximum messages for purge, change user security, change aka to use, change origin line,
change netmail reply board and delete message area.
<P>&nbsp;<P>
<H3>Message Area Setup.</H3>
<P>
<pre>
<strong>Area Name </strong>The description of the area.
<strong>Area Tag </strong>The echomail area tag.
<strong>Newsgroup </strong>The newsgroup name if you are gating this area.
<strong>Moderator </strong>Leave this blank for now!
<strong>JAM base </strong>The path and name of the JAM message base without extension.
<strong>Origin </strong>The origin line to add to echomail messages.
<strong>Fido Aka </strong>The Fidonet aka for this area.
<strong>QWK name </strong>The name of the area for OffLine Readers.
<strong>Group </strong>The name of the echomail group.
<strong>Distrib. </strong>Leave this blank for now!
<strong>Area Type </strong>Local, Netmail, Echomail or News.
<strong>Msg Kinds </strong>Private/Public, Private, Public, Read Only, FTN moderated, Usenet Moderated
<strong>FTN chars </strong>FTN characterset, not in use yet, defaults to IBMPC 2
<strong>RFC chars </strong>RFC characterset, not in use yet, defaults tp LATIN-1 2
<strong>Days Old </strong>The maximum age of the messages before purging.
<strong>Max. Msgs </strong>The maximum messages in this area.
<strong>Netreply </strong>Netmail reply area if this is echomail.
<strong>Active </strong>If this area is active.
<strong>User Del. </strong>Users may delete their own messages.
<strong>Read Sec. </strong>The security level to read messages.
<strong>Write Sec. </strong>The security level to write messages.
<strong>Sysop Sec. </strong>The security level to do sysop actions.
<strong>Aliases </strong>Allow the use of an Alias.
<strong>Random org </strong>Create random origin lines (Oneliner database).
<strong>Quotes </strong>Add a random quote under new messages (Oneliner database).
<strong>Mandatory </strong>If this area is mandatory for downlinks.
<strong>UnSecure </strong>Don't check link address during toss (Dangerous!).
<strong>OLR Default </strong>Switch area default on for OLR users.
<strong>OLR Forced </strong>Area is always on for OLR users.
<strong>Connections </strong>This will take you to the screen to edit up and downlinks.
</pre>
<P>
<IMG SRC="../images/emareas.gif" width="587" height="342">
<P>&nbsp;<P>
<H3>Edit connection</H3>
<P>
<pre>
<strong>Aka </strong>The network address.
<strong>Send to </strong>Export mail to this node.
<strong>Recv from </strong>Import mail form this node.
<strong>Pause </strong>The node is temporary disconnected.
<strong>Excluded </strong>The node is disconnected by the sysop.
<strong>Delete </strong>Delete this connection.
</pre>
<P>
A note about the excluded switch. This can be used to disconnect a node
from the area by moderator request. AreaMgr requests from that node
for this area are not processed anymore, he cannot disconnect this area
and reconnect. If you want to prevent a node to connect the area while
he is not connected, you should manually connect the node and then set
the Excluded flag to yes. However, the status of this flag is reported to the
node in the notify messages, so this action is not invisible.
<P>&nbsp;<P>
<H3>Global Commands.</H3>
<P>
From menu 9.2 you can enter the global commands menu. In this menu you can:
<ol>
<li>Delete connection
<li>Add new connection
<li>Replace connection
<li>Change connection status
<li>Change days old
<li>Change max. messages
<li>Change security
<li>Change aka to use
<li>Change origin line
<li>Change netmail reply
<li>Delete message area
</ol>
After you have selected the action you want and added the items to do, you will see
a screen were you can select message area groups. You can then tag one or more
groups and press enter when you are done. Then you have one chance to perform the
actions or to bail out. All areas matching in that group are affected by your
changes. If you are not happy with the result, don't save the database and no
harm is done. The file mbsetup.log shows all affected areas.
<P>&nbsp;<P>
<H3>Automatic area creation.</H3>
<P>
If you want to use the automatic area creation you have to define a fictitious
area tagged 'DEFAULT' with the options you want for new areas like this:
<pre>
1. Area Name Area autocreada:
2. FTN area DEFAULT
3. Newsgroup
4. Moderator
5. JAM base /var/spool/mbse/mail/
6. Origin Parolas BBX. Por fin.
7. Fido Aka 0:0/0@ 22. Sysop Sec. 100
8. QWK name 15. Days Old 40 23. Aliases No
9. Group AUTOCREADAS 16. Max. Msgs 1000 24. Quotes No
10. Distrib. 17. Netreply 0 25. Mandatory No
11. Area Type Echomail 18. Active Yes 26. UnSecure No
12. Msg Kinds Public 19. User Del. Yes 27. OLR Default No
13. FTN chars IBMPC 2 20. Read Sec. 5 28. OLR Forced No
14. RFC chars LATIN-1 2 21. Write Sec. 5 29. Connections
</pre>
The FTN area's Tag must be 'DEFAULT' exactly. Connections will be left blank. Fill
the remaining options with your defaults for the new areas.
If Fido AKA has not been filled in, the best fitting AKA according to the origin of
the message will be used from the configuration.<BR>
<P>
Areas will be created as is laid out in this template, the tag of a new area
will be added to the name and base path, the new tag will be placed in the tag
and qwk name (truncating it if needed).
Only the node from which the new area is received will be added in connections.
<P>
You will need to change the setup, menu 18, item 2, to change the command
'mbfido tic toss'. Add the -a parameter if you want the automatic
creation of areas to work when importing received mail.
So the commandline would be like <b>/opt/mbse/bin/mbfido tic toss web -a -quiet</b>.
<P>
<A HREF="mail.html"><IMG SRC="../images/larrow.gif" ALT="Back" Border="0" width="40" height="30"> Back to Mail Setup</A>&nbsp;
<A HREF="./"><IMG SRC="../images/larrow.gif" ALT="Back" Border="0" width="40" height="30"> Back to index</A>&nbsp;
<A HREF="../"><IMG SRC="../images/b_arrow.gif" ALT="Home" Border="0" width="40" height="30"> Back to main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>

50
html/setup/emgroup.html Normal file
View File

@@ -0,0 +1,50 @@
<HTML>
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META name="author" lang="en" "content="Michiel Broek">
<META name="copyright" lang="en" content="Copyright Michiel Broek">
<META name="description" lang="en" content="MBSE BBS Manual">
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
<TITLE>MBSE BBS Setup - Mail Setup - Message Groups.</TITLE>
<LINK rel=stylesheet HREF="../manual.css">
</HEAD>
<BODY>
<BLOCKQUOTE>
<h5>Last update 29-Jan-2001</h5>
<P>&nbsp;<P>
<H1>MBSE BBS Setup - Mail Setup - Message Groups.</H1>
<P>
<H3>Introduction.</H3>
<P>
Message Groups are to logically divide your echomail areas in groups for
different mail networks. It makes sense to select the groups by uplink, and
areas file that is available for each network. By doing that downlinks can
automatic connect areas that are not available at your bbs but are available
from your uplink. NOTE: uplink requesting is not yet implemented!
<P>&nbsp;<p>
<H3>Message Group Setup.</H3>
<P>
<pre>
<strong>Name </strong>The name of the group.
<strong>Comment </strong>The description of the group.
<strong>Active </strong>If this group is active.
<strong>Use Aka </strong>The Fidonet aka to use.
<strong>Uplink </strong>The Fidonet aka of your uplink.
<strong>Areas </strong>The name of the areas file (~/etc/file.ext).
<strong>Deleted </strong>If this group must be deleted.
</pre>
<P>
<IMG SRC="../images/emgroup.gif" width="589" height="343">
<P>
<A HREF="mail.html"><IMG SRC="../images/larrow.gif" ALT="Back" Border="0" width="40" height="30"> Back to Mail Setup</A>&nbsp;
<A HREF="./"><IMG SRC="../images/larrow.gif" ALT="Back" Border="0" width="40" height="30"> Back to index</A>&nbsp;
<A HREF="../"><IMG SRC="../images/b_arrow.gif" ALT="Home" Border="0" width="33" height="35"> Back to main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>

58
html/setup/fdb.html Normal file
View File

@@ -0,0 +1,58 @@
<HTML>
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META name="author" lang="en" "content="Michiel Broek">
<META name="copyright" lang="en" content="Copyright Michiel Broek">
<META name="description" lang="en" content="MBSE BBS Manual">
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
<TITLE>MBSE BBS Setup - Files Database.</TITLE>
<LINK rel=stylesheet HREF="../manual.css">
</HEAD>
<BODY>
<BLOCKQUOTE>
<h5>Last update 30-Jan-2001</h5>
<P>&nbsp;<P>
<H1>MBSE BBS Setup - Files Database.</H1>
<P>
<H3>Introduction.</H3>
<P>
This option allows you to manually edit the files in the files database.
The option to edit the file description is not present at this moment, but
will be when I have the time. The basic file entries can't be changed.
<P>&nbsp;<P>
<H3>Edit File.</H3>
<P>
<pre>
<strong>FileName </strong>The 8.3 filename of the file.
<strong>Long fn </strong>The long filename of the file, not in use yet.
<strong>FileSize </strong>The size of the file in bytes.
<strong>FileDate </strong>The real date of the file.
<strong>Last DL. </strong>The date of the last download of the file.
<strong>Upl.Date </strong>The upload date.
<strong>Uploader </strong>The name of the uploader.
<strong>Times DL </strong>The number of times downloaded from the BBS.
<strong>Times FTP </strong>Not in use yet.
<strong>Times Req </strong>The number of times requested by mailer.
<strong>Password </strong>The password to access this file.
<strong>Cost </strong>Not in use yet.
<strong>Free </strong>If this file is free for download.
<strong>Deleted </strong>If this file should be deleted.
<strong>Missing </strong>If this file is missing on disk.
<strong>No Kill </strong>Don't delete this file with <strong>mbfile</strong>
<strong>Announced </strong>If this file is ever announced as new.
</pre>
<P>
<IMG SRC="../images/fdb.gif" width="589" height="343">
<P>
<A HREF="./"><IMG SRC="../images/larrow.gif" ALT="Back" Border="0" width="40" height="30"> Back to index</A>&nbsp;
<A HREF="../"><IMG SRC="../images/b_arrow.gif" ALT="Home" Border="0" width="33" height="35"> Back to main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>

64
html/setup/fegroup.html Normal file
View File

@@ -0,0 +1,64 @@
<HTML>
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META name="author" lang="en" "content="Michiel Broek">
<META name="copyright" lang="en" content="Copyright Michiel Broek">
<META name="description" lang="en" content="MBSE BBS Manual">
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
<TITLE>MBSE BBS Setup - File Echo's Setup - File Groups.</TITLE>
<LINK rel=stylesheet HREF="../manual.css">
</HEAD>
<BODY>
<BLOCKQUOTE>
<h5>Last update 30-Jan-2001</h5>
<P>&nbsp;<P>
<H1>MBSE BBS Setup - File Echo's Setup - File Groups.</H1>
<P>
<H3>Introduction.</H3>
<P>
File echo groups are to logically divide your file echo's for different
file distribution networks. It makes sense to select the groups by uplink and
area file that is available for that file distribution network. By doing that
downlinks can connect areas that are not yet connected at your bbs but are
available from your uplink. NOTE: uplink requests is not yet implemented.
<P>&nbsp;<p>
<h3>Cost Sharing.</H3>
<P>
With the setup of groups you can also specify the Cost Sharing for the
files distribution. The unit cost is the cost for each transmitted file
if the unit size field is zero, or the unit price per transmitted unit size.
The final cost is multiplied with the "Add Prom." factor to add taxes or so.
Also if your uplink sends advanced .tic files, the cost found in that .tic
file will be added to the cost as well. Further you can set the final price
to divide between your downlinks or let them all pay the full price.
<H3>File Group Setup.</H3>
<P>
<pre>
<strong>Name </strong>File Echo Group name.
<strong>Comment </strong>The description of that group.
<strong>Active </strong>If this group is active.
<strong>Use Aka </strong>The Fidonet aka to use for this group
<strong>Uplink </strong>The Fidonet aka of the uplink.
<strong>Areas </strong>The name of the areas file (in ~/etc).
<strong>Unit Cost </strong>The cost per unit.
<strong>Unit Size </strong>The size in Kbytes per unit.
<strong>Add Prom. </strong>The prommilage to add to the cost.
<strong>Divide </strong>Divide cost over downlinks.
<strong>Deleted </strong>If this group must be deleted.
</pre>
<p>
<img src="../images/fegroup.gif" width="589" height="343">
<P>
<A HREF="tic.html"><IMG SRC="../images/larrow.gif" ALT="Back" Border="0" width="40" height="30"> Back to File Echo's Setup</A>&nbsp;
<A HREF="./"><IMG SRC="../images/larrow.gif" ALT="Back" Border="0" width="40" height="30"> Back to index</A>&nbsp;
<A HREF="../"><IMG SRC="../images/b_arrow.gif" ALT="Home" Border="0" width="33" height="35"> Back to main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>

42
html/setup/fidonet.html Normal file
View File

@@ -0,0 +1,42 @@
<HTML>
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META name="author" lang="en" "content="Michiel Broek">
<META name="copyright" lang="en" content="Copyright Michiel Broek">
<META name="description" lang="en" content="MBSE BBS Manual">
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
<TITLE>MBSE BBS Setup - Fidonet Networks.</TITLE>
<LINK rel=stylesheet HREF="../manual.css">
</HEAD>
<BODY>
<BLOCKQUOTE>
<h5>Last update 29-Jan-2001</h5>
<P>&nbsp;<P>
<H1>MBSE BBS Setup - fidonet Networks</H1>
<P>
Each fidonet network can have maximum 6 zones. The main zone (where you are)
must be the first zone, the others will follow. You can add 6 additional
nodelists to merge with the main nodelist. These additional nodelists are
normally more recent that the main nodelist, so entries in the additional
nodelists will replace entries from the main nodelist when you compile the
nodelists. In the shown example you can see that I have a regional nodelist
and a pointlist added for my region. For each additional list you must
specify the RC address because that information is normally present in these
nodelists. <U>Watch out!</U> Nodelist names are case sensitive. If you receive a
nodelist and automatic put them in place with the <strong>mbfido</strong>
program, and the resulting file is uppercase, you must use uppercase names
here also. You don't need to give the extension of the nodelist name, the
<strong>mbindex</strong> will figure that out.
<p>
<IMG SRC="../images/mbsetup2.gif" width="589" height="343">
<HR>
<A HREF="./"><IMG SRC="../images/larrow.gif" ALT="Back" Border="0" width="40" height="30"> Back to index</A>
<BR>
<A HREF="../"><IMG SRC="../images/b_arrow.gif" ALT="Home" Border="0" width="33" height="35"> Back to main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>

94
html/setup/fileecho.html Normal file
View File

@@ -0,0 +1,94 @@
<HTML>
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META name="author" lang="en" "content="Michiel Broek">
<META name="copyright" lang="en" content="Copyright Michiel Broek">
<META name="description" lang="en" content="MBSE BBS Manual">
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
<TITLE>MBSE BBS Setup - File Echo's Setup - TIC Areas.</TITLE>
<LINK rel=stylesheet HREF="../manual.css">
</HEAD>
<BODY>
<BLOCKQUOTE>
<h5>Last update 08-Jun-2001</h5>
<P>&nbsp;<P>
<H1>MBSE BBS Setup - File Echo's Setup - TIC Areas.</H1>
<P>
<H3>Introduction.</H3>
<P>
In this setup you can define the File Echo's or TIC areas. Files received or
send from this areas are bound together with a *.tic file with information
about the file and where to store that file. Each file echo must belong to a
group, in this grouprecord is the information about costsharing and some
other details. When a file is received at your system you can do several
things with that file before it is stored in your download areas such as;
scanning the file for virusses, extracting the FILE_ID.DIZ file to use as
description, allow update of magic alias, convert to another compression
format, replace the file archive comment with an add of your own bbs and limit
the number of files (nodelists).
<P>&nbsp;<p>
<H3>TIC Area Setup.</H3>
<P>
<pre>
<strong>Comment </strong>A description for this area.
<strong>Area tag </strong>The tag for this area.
<strong>BBS area </strong>The BBS download area number, 0 means passthru.
<strong>Message </strong>Not in use yet.
<strong>Group </strong>The group where this area belongs to.
<strong>Keep # </strong>The number of files to keep, the name must match.
<strong>Fido aka </strong>The Fidonet aka to use for this area.
<strong>Convert </strong>The archiver to convert to, leave blank for none.
<strong>Banner </strong>The bannerfile (in ~/etc) to replace in the archive.
<strong>Replace </strong>Honor the "Replace" command in the .tic file.
<strong>Dupecheck </strong>Check for duplicates in this area.
<strong>Secure </strong>Check if the sending system is connected.
<strong>No touch </strong>Don't touch the filedate, keep it original.
<strong>Virus sc. </strong>Try to scan for virusses.
<strong>Announce </strong>Files may be announced in this area.
<strong>Upd magic </strong>Allow update magic request name.
<strong>File_id </strong>Try to use the FILE_ID.DIZ file for description.
<strong>Conv.all </strong>Convert archive even if it is already right.
<strong>Send org. </strong>Send original received file instead of the file from the BBS.
<strong>Mandatory </strong>Downlinks can't disconnect from this area.
<strong>Notified </strong>Not in use yet.
<strong>Upl discon </strong>Not in use yet.
<strong>Deleted </strong>If this area must be deleted.
<strong>Active </strong>If this area is active.
<strong>Systems </strong>To the screen with connected systems.
</pre>
<P>
<IMG SRC="../images/fileecho.gif" width="589" height="343">
<P>
<H3>Global Commands.</H3>
<P>
From menu 10.2 you can enter the global commands menu. In this menu you can:
<ol>
<li>Delete connection
<li>Add new connection
<li>Replace connection
<li>Change connection status
<li>Change aka to use
<li>Delete TIC area
</ol>
After you have selected the action you want and added the items to do, you will see
a screen were you can select TIC file area groups. You can then tag one or more
groups and press enter when you are done. Then you have one chance to perform the
actions or to bail out. All areas matching in that group are affected by your
changes. If you are not happy with the result, don't save the database and no
harm is done. The file mbsetup.log shows all affected areas.
<P>&nbsp;<P>
<A HREF="tic.html"><IMG SRC="../images/larrow.gif" ALT="Back" Border="0" width="40" height="30"> Back to File Echo's Setup</A>&nbsp;
<A HREF="./"><IMG SRC="../images/larrow.gif" ALT="Back" Border="0" width="40" height="30"> Back to index</A>&nbsp;
<A HREF="../"><IMG SRC="../images/b_arrow.gif" ALT="Home" Border="0" width="33" height="35"> Back to main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>

58
html/setup/filefind.html Normal file
View File

@@ -0,0 +1,58 @@
<HTML>
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META name="author" lang="en" "content="Michiel Broek">
<META name="copyright" lang="en" content="Copyright Michiel Broek">
<META name="description" lang="en" content="MBSE BBS Manual">
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
<TITLE>MBSE BBS Setup - Filefind Areas.</TITLE>
<LINK rel=stylesheet HREF="../manual.css">
</HEAD>
<BODY>
<BLOCKQUOTE>
<h5>Last update 30-Jan-2001</h5>
<P>&nbsp;<P>
<H1>MBSE BBS Setup - Filefind Areas.</H1>
<P>
<H3>Introduction.</H3>
<P>
The filefind idea on Fidonet came from the program Allfix written by Harald
Harms. The idea is
that a user writes a mail in a filefind area addressed to "Allfix" with in the
subject line the items to search for. On all BBS'es with a filefind utility
those programs try to find the requested files and then produce a reply of
which files they have found. That reply can be in the same area, in a special
reply echo or can be sent by netmail. Usually the user gets a lot of replies
from which he can see if someone has the file(s) available he was searching
for.
<P>&nbsp;<P>
<H3>Filefind Setup.</H3>
<P>
<pre>
<strong>Comment </strong>The comment for this area.
<strong>Origin </strong>The origin line to use for the reply.
<strong>Aka to use </strong>The Fidonet aka to use in this area.
<strong>Scan area </strong>The JAM area in which to scan for requests.
<strong>Reply area </strong>The JAM area to put the replies in, leave blank if in the same area.
<strong>Language </strong>Not in use yet, but DO select one!
<strong>Template </strong>Not in use yet.
<strong>Active </strong>If this area is active.
<strong>Deleted </strong>If this area must be deleted.
<strong>Net. reply </strong>If the reply will be sent by netmail.
<strong>Hi ACSII </strong>If high ASCII is allowed in the replies.
</pre>
<P>
<IMG SRC="../images/filefind.gif" width="589" height="343">
<P>
<A HREF="./"><IMG SRC="../images/larrow.gif" ALT="Back" Border="0" width="40" height="30"> Back to index</A>&nbsp;
<A HREF="../"><IMG SRC="../images/b_arrow.gif" ALT="Home" Border="0" width="33" height="35"> Back to main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>

79
html/setup/files.html Normal file
View File

@@ -0,0 +1,79 @@
<HTML>
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META name="author" lang="en" "content="Michiel Broek">
<META name="copyright" lang="en" content="Copyright Michiel Broek">
<META name="description" lang="en" content="MBSE BBS Manual">
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
<TITLE>MBSE BBS Setup - BBS Setup - File Areas.</TITLE>
<LINK rel=stylesheet HREF="../manual.css">
</HEAD>
<BODY>
<BLOCKQUOTE>
<h5>Last update 29-Jan-2001</h5>
<P>&nbsp;<P>
<H1>MBSE BBS Setup - BBS Setup - File Areas.</H1>
<P>
<H3>File Areas introduction.</H3>
<P>
This is the setup for the file areas in which users can up and download files.
This database has fixed area numbers, the database can't be packed. This is
done because areas can point to other areas and users are "used" to use
areas by number. Also the .tic areas reference the file areas by record
numbers. Extending the database is allways possible. One important note,
before you can set this up, you need to define the <A HREF="newgroups.html">
newfiles groups</A>.
<P>&nbsp;<p>
<H3>File Areas Setup.</H3>
<P>
<pre>
<strong>Area Name </strong>The area name.
<strong>Path </strong>The full path to the file area.
<strong>Down Sec. </strong>The download security level.
<strong>Upl. Sec. </strong>The upload security level.
<strong>List Sec. </strong>The security level to list the files in this area.
<strong>Files.bbs </strong>The full path and filename if this area is on CDROM.
You may leave this blank if it is in the Path together
with the files.
<strong>Available </strong>If this area is available.
<strong>Check New </strong>Check this area for new files if a user logs in.
<strong>Dupecheck </strong>Check this area for duplicates if a user uploads a file.
<strong>Free area </strong>If all files in this area are free.
<strong>Direct DL </strong>Allow direct download from this area.
<strong>Pwd upl. </strong>Allow users to password protect their uploads.
<strong>Filefind </strong>Search in this area for filefind requests.
<strong>Add alpha </strong>Add .tic files alphabetic sorted or at the bottom of the list.
<strong>CDrom </strong>Is this a CDROM area. The affects the behaviour of some
other utilities because the Path is read-only.
<strong>File req. </strong>Allow File Request from this area.
<strong>BBS group </strong>Not in use yet.
<strong>New group </strong>New files announce group. See <A HREF="newgroups.html">Newfiles groups</A> for more info.
<strong>Min. age </strong>Minimum user age to access this area.
<strong>Password </strong>The password for this area. If blank, no password is needed.
<strong>DL days </strong>How long must a file not been downloaded to (re)move it.
<strong>FD days </strong>How old must a file be to be (re)moved.
<strong>Move area </strong>The area to move the file to, if zero it is deleted.
<strong>Cost </strong>The cost in units to download from this area.
<strong>Archiver </strong>The archiver to use to repack the files with.
<strong>Upload </strong>Alternate upload area. If a user uploads a file in this
area, it will be placed in the alternate area. If the
value is zero, the file will be placed in the current
file area. On CD-rom areas you must not leave this zero
unless you set the upload security level so high that
nobody can upload in this area.
</pre>
<P>
<IMG SRC="../images/files.gif" width="589" height="343">
<P>
<A HREF="bbs.html"><IMG SRC="../images/larrow.gif" ALT="Back" Border="0" width="40" height="30"> Back to BBS index</A>&nbsp;
<A HREF="./"><IMG SRC="../images/larrow.gif" ALT="Back" Border="0" width="40" height="30"> Back to index</A>&nbsp;
<A HREF="../"><IMG SRC="../images/b_arrow.gif" ALT="Home" Border="0" width="33" height="35"> Back to main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>

464
html/setup/global.html Normal file
View File

@@ -0,0 +1,464 @@
<HTML>
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META name="author" lang="en" "content="Michiel Broek">
<META name="copyright" lang="en" content="Copyright Michiel Broek">
<META name="description" lang="en" content="MBSE BBS Manual">
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
<TITLE>MBSE BBS Setup - Global Setup.</TITLE>
<LINK rel=stylesheet HREF="../manual.css">
</HEAD>
<BODY>
<BLOCKQUOTE>
<h5>Last update 22-Jun-2001</h5>
<P>&nbsp;<P>
<H1>MBSE BBS Setup - Global Setup</H1>
<P>
In this setup you can edit all global settings for MBSE BBS. All sections will
be discussed below.
<P>
<h3>1.1. Edit Registration Info.</H3>
<P>
<pre>
<strong>System name </strong>The name of your BBS
<strong>Domain name </strong>Your internet domain name (or a fake name if you have
no direct connection).
<strong>Sysop uid </strong>The Unix name of your Sysop account
<strong>Sysop Fido </strong>The Fidonet name of your Sysop account
<strong>Location </strong>The Location of your BBS
<strong>QWK/Bluewave </strong>The packet name for Offline mail downloads.
<strong>Omed id. </strong>Not in use
<strong>Comment </strong>A comment line for your BBS
<strong>Origin line </strong>The default origin line for echomail
<strong>Startup uid </strong>The default username &quot;bbs&quot;
</pre>
<P>
<h3>1.2. Edit Global Filenames.</H3>
<P>
<pre>
<strong>System logfile </strong>The name of the main logfile
<strong>Error logfile </strong>The name of the errors logfile
<strong>Default menu </strong>The name of the default main menu
<strong>Default language </strong>The name of the default language
<strong>Chat logfile </strong>The name of the logfile for chatting
<strong>Welcome logo </strong>The name of the BBS logo ANSI file
</pre>
<P>
<h3>1.3. Edit Global Paths</H3>
<P>
<pre>
<strong>BBS Menus </strong>The path to the default menus
<strong>Txtfiles </strong>The path to the default ANSI and ASCII textfiles
<strong>Home dirs </strong>The path to the users home directories
<strong>Nodelists </strong>The path to the nodelist directory
<strong>Inbound </strong>The unprotected fidonet inbound
<strong>Prot inb. </strong>The (password) protected fidonet inbound
<strong>Outbound </strong>The outbound for the main aka
<strong>Bad TIC's </strong>Where bad TIC files are saved
<strong>TIC queue </strong>Where TIC files for downlinks are kept
<strong>Magic's </strong>Where the magic filerequests are kept
<strong>DOS path </strong>The DOS drive and path
<strong>Unix path </strong>The Translated DOS path in real
<strong>LeaveCase </strong>Leave outbound .flo filenames as is, No forces to uppercase
</pre>
The DOS path and Unix path are translated for in and outbound mail sessions,
so the outside world will be happy. The DOS path is a fake, you can put
anything you like in there, but "C:\OUT" is a good choice. Note that
the TIC queue must be somewere in the Unix path, otherwise it is
impossible to create a DOS path from the path to the TIC files in that
directory. To set this up correctly is also important if you use other mailers
as well, for example binkd, or even a DOS binkly-style mailer running from
a network. All those mailer must "see" the same file attaches in the .flo
files. If you leave the DOS path empty, no translation will be performed
and the Unix paths will be stored in the .flo files.
<P>
<h3>1.4. Edit BBS Configuration</H3>
<p>
<pre>
<strong>Private system </strong>Set to true when only pre-registered users are allowed
<strong>Exclude Sysop </strong>True is Sysop will be invisible
<strong>Show connect </strong>Show connection info at logon
<strong>Ask protocols </strong>Ask protocol before each up/download
<strong>Sysop level </strong>The Sysop security level
<strong>Password Length </strong>The minimum password length, should be 6.
<strong>Password Char. </strong>The password hiding character
<strong>Idle timeout </strong>The idle timeout in minutes
<strong>Login Enters </strong>Maximum times for only enter <Enter>
<strong>Login Attempts </strong>Maximum login attempts
<strong>Homedir Quota </strong>Maximum size in MBytes for each user
<strong>Location length </strong>The minimum length of the location (3 in Holland!)
<strong>Show new msgarea </strong>Show new available message areas at logon (for OLR users)
<strong>OLR Max. msgs. </strong>Maximum messages to download, 0 is no limit.
<strong>OLR Newfile days </strong>The maximum age for newfiles in the OLR packet
<strong>OLR Max Filereq </strong>Maximum filerequests allowed for OLR users
<strong>BBS Log Level </strong>What will be logged or not the BBS program
<strong>Utils Log Level </strong>What will be logged or not for utilities
<strong>Utils slowly </strong>Should utilities release <A HREF="../misc/usleep.html">timeslices</A>
<strong>CrashMail level </strong>Minimum level to allow sending netmail crash
<strong>FileAttach level </strong>Minimum level to allow attach files to netmail
<strong>Min diskspace MB </strong>At which low diskspace level utilities should stop working.
</pre>
The minimum diskspace setting is to prevent that files get corrupted if your filesystem
is full. All drives are checked except CD-roms and floppies and the /boot directory if that
one is on a separate filesystem. Ext2, msdos and vfat partitions
are checked. The lowest free diskspace found counts. Default is 10 MB.
Note, Reiserfs is not supported at this moment because I don't have access to a
system with reisefs volumes. This means that if you use Reiserfs that you are not
protected against a full filesystem.
<p>
<h3>1.5. New users defaults.</h3>
<p>
<pre>
<strong>Access level </strong>The access level and flags after registration
<strong>Cap. Username </strong>Capitalize the username
<strong>Ask ANSI </strong>Ask for ANSI screen (default is yes)
<strong>Ask Sex </strong>Ask for Male/Female
<strong>Ask Voicephone </strong>Ask for voice phonenumber
<strong>Ask Dataphone </strong>Ask for data phonenumber
<strong>Telephone scan </strong>Scan for duplicate numbers
<strong>Ask Handle </strong>Ask for handle (nickname)
<strong>Ask Birth date </strong>Ask for birthdate (needed for checks)
<strong>Ask Location </strong>Ask for users location
<strong>Ask Hot-Keys </strong>Ask for hot-keyed menus (default is yes)
<strong>One word names </strong>Allow one word names
<strong>Ask address </strong>Not implemented
<strong>Give email </strong>Give new users email access (default is yes)
</pre>
<p>
<h3>1.6. Text Colors.</h3>
<p>
Several prompts use different colors. They can be changed with the following
menu.
<P>
<IMG SRC="../images/mbsetup1.6.gif" width="589" height="343">
<IMG SRC="../images/mbsetup1.6.S.gif" width="589" height="343">
<P>
<h3>1.7. Next User Door.</h3>
<p>
This is a "message to nextuser" door I found in RapidBBS. It allows a user
to write a message to the next BBS user.
<pre>
<strong>Text file </strong>The textfile to display
<strong>Quote </strong>The prompt to show
</pre>
<p>
<h3>1.8. Safe cracker door.</h3>
<p>
This is a door I found in RapidBBS, it is a simple number guessing game.
<pre>
<strong>Digit 1 </strong>The first digit to guess
<strong>Digit 2 </strong>The second digit to guess
<strong>Digit 3 </strong>The third digit to guess
<strong>Max trys </strong>The maximum number of trys per day
<strong>Max numb </strong>The highest number to guess
<strong>Num gen </strong>Automatic number generation
<strong>Prize </strong>The prize to win
<strong>Welcome </strong>The welcome file to display
<strong>Opened </strong>The file to display to the winner
</pre>
<p>
<h3>1.9. Time Bank Door.</h3>
<p>
This is the timebank door I found in RapidBBS. It allows a user to deposit
time or download kilobytes on his bank account so when he needs it for
big downloads he can use his savings for extra large downloads. Anyway,
I haven't figured this one out completly for myself, so the meaning of all
these settings are not well explained right now.
<pre>
<strong>Time balance </strong>Maximum time balance
<strong>Max time withdraw </strong>Maximum time to withdraw
<strong>Max time deposit </strong>Maximum time to deposit
<strong>Kb. balance </strong>Maximum Kilobytes balance
<strong>Max Kb. withdraw </strong>Maximum Kilobytes to withdraw
<strong>Max Kb. deposit </strong>Maximum Kilobytes to deposit
<strong>Users time ratio </strong>Time ratio
<strong>Users Kb. ratio </strong>Kilobytes ratio
</pre>
<p>
<h3>1.10. Sysop paging</h3>
<p>
For sysop chat we use a program that will connect to the users tty. This is
not a nice solution because it will not work over a network, but at least
it works.
<pre>
<strong>Ext. chat </strong>External chat program, not in use!
<strong>Chat device </strong>The device where the sysop is called (beeped)
<strong>Call script </strong>For future use
<strong>Page length </strong>The length of a page in seconds
<strong>Page times </strong>Maximum number of times a user may page the sysop
<strong>Sysop area </strong>Message from user to Sysop area number
<strong>Ask reason </strong>Ask reason for chat, this will be logged
<strong>Use Extern </strong>Use external chat
<strong>Log Chat </strong>Log the chat conversation
<strong>Prompt Chk. </strong>Check at menu prompts for Sysop breaking in
<strong>Freeze Time </strong>Freeze users time during chat
<strong>Sunday..Saturday </strong>The times the Sysop is normal available
</pre><p>
<h3>1.11. Flag Descriptions.</h3>
<p>
In this menu you can give the 32 users flags a meaningfull description.
<p>
<h3>1.12. Fileecho Processing.</h3>
<p>
A note, when you change the number of Systems or Groups, the databases affected
will be updated automatic.
<pre>
<strong>Keep days </strong>How long TIC files should be kept on hold
<strong>Hatch pwd </strong>The internal hatch password. Make this weird.
<strong>Drv space </strong>The minimal free space on your disk in kilobytes
<strong>Systems </strong>The maximum number of connected nodes
<strong>Groups </strong>The maximum number of fileecho groups
<strong>Max. dupes </strong>The maximum number of entries in dupe database
<strong>Keep date </strong>Keep original filedate
<strong>Keep netm </strong>Keep sent netmails
<strong>Res future </strong>Reset dates in the future
<strong>Loc resp </strong>Respond to local created filefind messages
<strong>Repl ext </strong>Replace filename extension with .* before filesearch
<strong>Plus all </strong>Allow filemgr +all command
<strong>Notify </strong>Allow filemgr notify=on/off command
<strong>Passwd </strong>Allow filemgr passwd command
<strong>Message </strong>Allow filemgr message=on/off command
<strong>Tic on/off </strong>Allow filemgr tic=on/off command
<strong>Pause </strong>Allow filemgr pause/resume commands
</pre><p>
<h3>1.13. Edit Fidonet mail and echomail processing.</h3>
<p>
Note that the first 2 mailboards must also exist in the normal mail areas if
you want to see what is in them. Here they are defined for quick access of the
tosser. For the Max. systems and groups see 1.12. If you use MBSE BBS together
with a DOS based BBS (using DOSEMU or mars netware emulator), you can set the
behaviour of the outbound to 4d. addressing instead of 5d. This option may
dissapear in the future.<br>
Another option is present, this is the <strong>pktdate</strong> option. This
is the full path and filename to an external program that can inspect and
correct the mail .pkt files. Originally I put this in to run pktname of Tobias
Ernst of 2:2476/418 to fix y2k problems in the incoming mail. At this time
most y2k fixes are build in, but in case you need it it's there. To make it
clear; the y2ktools written by Tobias are static compiled for Linux and they
should run on all Linux i386 versions. Until now, I still use pktdate because
it is necessary.<br>
<pre>
<strong>Badboard </strong>The path and filename of the bad messages
<strong>Dupeboard </strong>The path and filename of the duplicate messages
<strong>Pktdate </strong>Full path and filename of a .pkt preprocessor
<strong>Max pkts. </strong>Maximum Kb. of mail packets before a new one is created.
<strong>Max arcs. </strong>Maximum size in Kilobytes of an arcmail file
<strong>Keep days </strong>How many day should we keep ARCmail on hold
<strong>Echo dupes </strong>Maximum number of entries in the echomail dupe database
<strong>Reject old </strong>Reject echomail messages older then n days
<strong>Max msgs </strong>Default maximum number of messages in each area
<strong>Days old </strong>Default number of days old to keep messages
<strong>Max systems </strong>Maximum number of nodes to connect to echomail
<strong>Max groups </strong>Maximum number of echomail groups
<strong>4d address </strong>Use 4d. addressing (not needed you only use MBSE BBS)
<strong>Split at </strong>Gently split messages after n KBytes (12..60)
<strong>Force at </strong>Force split of messages after n KBytes (16..63)
</pre><p>
A note about the splitting of messages. Some tossers can't handle
messages greater than 16 KBytes, these tossers are rare these days. Most
tossers can handle messages of 32 KBytes. To set these values on the safe
side set "Split at" to 27 and "Force at" to 31. This means that a long
newfile report will be split after 27 KBytes when a new group of files
should start in the report. If it can't find that point because a large
number of files is in the group that is just being processed, the message
split will be forced right after the file that passes the 31 KBytes limit.
I use values of 1 KBytes below maximum for overhead such as SEEN-BY and
PATH lines. Values larger then 32 KBytes is not a good idea, recent tests
in May 1999 have shown that your messages will not reach all systems
if they are larger then 32 KBytes. Splitting is used for newsfiles reports
and gated news articles to Fidonet.
<P>
<h3>1.14. Edit Internet mail and news processing.</h3>
<p>
Email and news is setup here. There are three possible configurations which you
can set with 1.14.11:
<ul>
<li><strong>No ISP</strong>. If you don't have any connection to the internet
use this setting. Email will come from the default Fidonet UUCP gate and will be send out
via the UUCP gate. Users have email addresses like
<strong>user@f2802.m280.z2.fidonet.org</strong> Note, the username is their
Unix name when sending email.
<li><strong>Dial ISP</strong>. If you dial the internet regulary or are connected
with a cable modem without a valid DNS (Nameserver) entry you should use
this mode. Email will be sent via your local SMTP port, then through your
own sendmail (or whatever you use) to your ISP.
As soon as you are connected to the internet
the mail will be sent to your ISP's mailer. In your sendmail you should
define the mailer of your ISP as Smarthost. Incoming email will still come
from the UUCP gate. Users have email addresses like
<strong>user@f2802.m280.z2.fidonet.org</strong> Note, the username is their
Unix name.
<li><strong>Perm ISP</strong>. If you are permanent connected to the internet
either with a static or dynamic IP address use this option. Use this option
also if you have an UUCP domain and hav a dialup UUCP connection. You need to
register a DNS name and MX record for your system, if you don't you won't be able to
receive email from the internet and must use the previous Dial mode.
If you have a dynamic IP address you can still get a DNS name from for
example <A HREF="http://www.dynip.com">dynip.com</A>
Incoming email will come directly from the internet, but if someone sends
email via the UUCP gate it is also accepted. Users have email addresses like
<strong>user@yourbbs.domain.org</strong>. Note, the username is their
Unix name.
</ul>
Another word of wisdom from my side, configuration of the internet, ppp, sendmail etc. is not discussed
here, see the HOWTO's and other documentation that exists at <A HREF="http://www.linuxdoc.org">
www.linuxdoc.org</A>, it's all there.
<pre>
<strong>POP3 node </strong>The POP3 node to use, should be localhost
<strong>SMTP node </strong>The SMTP node to use, should be localhost
<strong>NNTP node </strong>The NNTP node to use, should be localhost
<strong>NNTP m.r. </strong>If the NNTP server needs the Mode Reader command
<strong>NNTP user </strong>The username for the NNTP server if needed
<strong>NNTP pass </strong>The password for the NNTP server if needed
<strong>News dupes </strong>The number of entries for the news dupes database.
<strong>Email aka </strong>The Fidonet aka to use for the fidonet.org UUCP gate
<strong>UUCP aka </strong>The default Fidonet UUCP gate, 2:292/875@fidonet
<strong>Emailmode </strong>The email mode, discussed above
<strong>News mode </strong>Newsfeed mode, INN, rnews or UUCP.
<strong>Split at </strong>Gently split newfiles reports after n KBytes (12..60)
<strong>Force at </strong>Force split of newfiles reports after n KBytes (16..63)
<strong>Control ok </strong>Allow news control messages to be gated
<strong>No regate </strong>Don't regate already gated messages
In rnews mode the NNTP entries are replaced by:
<strong>Path rnews </strong>The full path and filename to the rnews binary.
In UUCP mode the NNTP entries are replaced by:
<strong>UUCP path </strong>The full path to the uucppublic directory.
<strong>UUCP node </strong>The UUCP nodename of your ISP.
</pre><p>
<P>
<h3>1.15. Allfiles and Newfiles lists.</h3>
<p>
These are the settings that affect the generation of newfiles and allfiles reports.
<pre>
<strong>Ftp base </strong>The root of the public download area (.../ftp)
<strong>New days </strong>The number of days old files are &quot;newfiles&quot;
<strong>Security </strong>The highest security level to include files in the reports
<strong>Groups </strong>The number of newfile groups the newfiles database can hold
</pre><p>
<h3>1.16. Fidonet Aka's.</h3>
<p>
Here you can enter 40 fidonet addresses. These are 5d addresses.
<p>
<h3>1.17. Mailer Setup.</h3>
<p>
Note that you can't disable FTS-0001 sessions as that is a mandatory session
protocol in Fidonet. There are 40 phonenumber translations present, this is for
countries with lots of telephone operators with all kind of prefixes for
carrier select functions.
<pre>
<strong>Mailer logl. </strong>The logging level for mailer sessions
<strong>Default phone </strong>The default phonenumber for EMSI sessions
<strong>TCP/IP flags </strong>The TCP/IP capability flags for TCP/IP sessions
<strong>Default speed </strong>The default speed for EMSI sessions
<strong>Timeout reset </strong>The timout for normal modem commands
<strong>Timeout connect </strong>The timeout for waiting for connect
<strong>Dial delay </strong>The maximum delay between calls, minimum is 10 seconds.
<strong>No Filerquests </strong>Disable filerequests
<strong>No callout </strong>Disable callout
<strong>No hold mail </strong>Send &quot;hold&quot; mail if we make the call
<strong>No pickup all </strong>Exchange mail for one aka only
<strong>No EMSI session </strong>Disable EMSI
<strong>No YooHoo/2U2 </strong>Disable FTS-0006 sessions
<strong>No Zmodem </strong>Disable zmodem protocol
<strong>No Zedzap </strong>Disable zedzap protocol
<strong>No Hydra </strong>Disable Hydra protocol
<strong>No TCP/IP </strong>Disable TCP/IP protocol, set to Yes if you don't have internet.
<strong>Phonetrans 1..40 </strong>Maximum 40 phone number translations
<strong>Max. files </strong>Maximum files to request, 0 is unlimited
<strong>Max. MBytes </strong>Maximum MBytes to request, 0 is unlimited
</pre>
<h3>1.18. FTPD Settings.</h3>
<p>
A new program is <strong>mbftpd</strong>. This is a replacement for the normal
ftp server for Linux with special futures for MBSE BBS. This is not working
yet so don't use it. Setting it up is adviced.
<pre>
<strong>Base path </strong>The ftp base directory (ie. /SYS/usr/ftp).
<strong>Upload pth </strong>Incoming files (ie. /SYS/usr/ftp/incoming).
<strong>Banner msg </strong>The banner file to display before login.
<strong>Path filter </strong>The legal character in upload filenames.
<strong>Path msg </strong>Message to display if illegal characters in upload.
<strong>Email addr </strong>Your email address.
<strong>Shutdown </strong>Shutdown message if FTP server is closed.
<strong>Readme login </strong>Readme to display after login.
<strong>Readme cwd* </strong>Readme to display after chdir.
<strong>Msg login </strong>Welcome message after login.
<strong>Msg cwd* </strong>Message to display in directory.
<strong>Userslimit </strong>Maximum FTP users allowed.
<strong>Loginfails </strong>Maximum login failures.
<strong>Compress </strong>If compress command is allowed.
<strong>Tar </strong>If tar command is allowed.
<strong>Mkdir ok </strong>If users may create directories.
<strong>Log commands </strong>Log user commands.
<strong>Anonymous </strong>If anonymous login is allowed.
<strong>User mbse </strong>If user <strong>mbse</strong> is allowed. Dangerous!
</pre>
<h3>1.19. Edit HTML pages setup.</h3>
<p>
Here you setup the HTML pages that can be created with the <strong>
mbfile web</strong> command. These are HTML pages of your download
areas and indexes of all areas. If there are pictures in these areas
thumbnails are created if you have the <strong>convert</strong>
command available. The document root is the same as defined in your
web server. The link to ftp must be created from that directory to
your ftp base directory. To do that become root, cd to the document root
and type <strong>ln -s /var/spool/mbse/ftp files</strong> In this case the link
is called <strong>files</strong>. Note that all download areas are accesible,
there is no user authentication yet available.
<pre>
<strong>Docs root </strong>The path to the httpd documents root.
<strong>Link to ftp </strong>The link to the ftp directory.
<strong>URL name </strong>The URL of your webserver.
<strong>Charset </strong>The default character set, ISO-8859-1.
<strong>Table color </strong>The tables background color.
<strong>Header color </strong>The tables header background color.
<strong>Author name </strong>The author name you want in the HTTP headers.
<strong>Convert command </strong>The graphics convert command. (ImageMagick needed).
<strong>Files/page </strong>The number of files to display per web page.
<strong>Icon Home </strong>The name of the Home icon file.
<strong>Text Home </strong>The text to display for Home.
<strong>Icon Back </strong>The name of the Back icon file.
<strong>Text Back </strong>The text to display for Back.
<strong>Icon Prev. </strong>The name of the Previous page icon file.
<strong>Text Prev. </strong>The text to display for Previous page.
<strong>Icon Next </strong>The name of the Next page icon file.
<strong>Text Next </strong>The text to display for Next page.
</pre>
<P>
<A HREF="./"><IMG SRC="../images/larrow.gif" ALT="Back" Border="0" align="bottom" width="40" height="30"> Back to index</A>
<BR>
<A HREF="../"><IMG SRC="../images/b_arrow.gif" ALT="Home" Border="0" align="bottom" width="33" height="35"> Back to main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>

61
html/setup/hatch.html Normal file
View File

@@ -0,0 +1,61 @@
<HTML>
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META name="author" lang="en" "content="Michiel Broek">
<META name="copyright" lang="en" content="Copyright Michiel Broek">
<META name="description" lang="en" content="MBSE BBS Manual">
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
<TITLE>MBSE BBS Setup - File Echo's Setup - Hatch Manager.</TITLE>
<LINK rel=stylesheet HREF="../manual.css">
</HEAD>
<BODY>
<BLOCKQUOTE>
<h5>Last update 30-Jan-2001</h5>
<P>&nbsp;<P>
<H1>MBSE BBS Setup - File Echo's Setup - Hatch Manager.</H1>
<P>
<H3>Introduction.</H3>
<P>
Hatch files is nothing more than entering a new file into a file echo. That
file is searched for on your system in a specific directory with a certain
filemask. This can be for example a new created nodelist or an allfiles listing.
Everytime <strong>mbfido tic</strong> is run it will scan for files defined
in this setup. If such a file is found, a special .tic file is written and
stored in the mailers inbound directory. When the <strong>mbfido</strong>
starts processing .tic files, that new hatched file will be processed as if
it was received form another system. To let this work, you obviously need
an existing TIC area.
<P>&nbsp;<P>
<H3>Hatch Manager Setup.</H3>
<P>
<pre>
<strong>Mask </strong>The path and filename mask to search for.
"?" matches any character, "#" matches digits and "@" matches
alpha characters. Don't use "*", this doesn't work!
<strong>Area </strong>The area to hatch this file in.
<strong>Replace </strong>The filename to replace, ie. "nodelist.z*"
<strong>Magic </strong>The filerequest magic name, ie. "nodelist"
<strong>Desc </strong>The description of the file, %12 in the description
means copy the 12th character of the name in place.
<strong>Dupe </strong>Check for duplicates.
<strong>Active </strong>If this area is active.
<strong>Deleted </strong>If this area must be deleted.
<strong>Days </strong>The days in the week to scan for this file.
<strong>Month </strong>The dates in the month to scan for this file.
</pre>
<P>
<IMG SRC="../images/hatch.gif" width="589" height="343">
<P>
<A HREF="tic.html"><IMG SRC="../images/larrow.gif" ALT="Back" Border="0" width="40" height="30"> Back to File Echo's Setup</A>&nbsp;
<A HREF="./"><IMG SRC="../images/larrow.gif" ALT="Back" Border="0" width="40" height="30"> Back to index</A>&nbsp;
<A HREF="../"><IMG SRC="../images/b_arrow.gif" ALT="Home" Border="0" width="33" height="35"> Back to main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>

80
html/setup/index.htm Normal file
View File

@@ -0,0 +1,80 @@
<HTML>
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META name="author" lang="en" "content="Michiel Broek">
<META name="copyright" lang="en" content="Copyright Michiel Broek">
<META name="description" lang="en" content="MBSE BBS Manual">
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
<TITLE>MBSE BBS setup.</TITLE>
<LINK rel=stylesheet HREF="../manual.css">
</HEAD>
<BODY>
<BLOCKQUOTE>
<h5>Last update 27-May-2001</h5>
<P>&nbsp;<P>
<h1>MBSE BBS Setup Guide</h1>
<P>
<H3>Invoking mbsetup</H3>
<P>
As user <strong>mbse</strong> type <strong>mbsetup</strong> to start the setup
program. This version is not yet finished. There are a few items you can't
setup yet.
When you start <strong>mbsetup</strong> you will see the following screen:
<p>
<IMG SRC="../images/mbsetup0.gif">
<P>&nbsp;<P>
<H3>mbsetup main options</H3>
<P>
<ol>
<li><A HREF="global.html">Edit Global configuration</a>
<li><A HREF="fidonet.html">Edit Fido networks</a>
<li><A HREF="archiver.html">Edit Archiver programs</a>
<li><A HREF="virscan.html">Edit Virus scanners</a>
<li><A HREF="modems.html">Edit Modem types</a>
<li><A HREF="ttyinfo.html">Edit TTY lines info</a>
<li><A HREF="nodes.html">Edit Fidonet nodes</a>
<li><A HREF="bbs.html">Edit BBS setup</a>
<ol>
<li><A HREF="security.html">Edit Security limits</a>
<li><A HREF="language.html">Edit Language setup</A>
<li><A HREF="../menus/index.htm">Edit BBS menus</a>
<li><A HREF="files.html">Edit File areas</a>
<li><A HREF="protocol.html">Edit Transfer protocols</a>
<li><A HREF="bbslist.html">Edit BBS List data</a>
<li><A HREF="oneliner.html">Edit Oneliners</a>
<li><A HREF="timebank.html">Edit TimeBank data</a>
<li><A HREF="safe.html">Edit Safe Cracker data</a>
</ol>
<li><A HREF="mail.html">Edit Mail setup</A>
<ol>
<li><A HREF="emgroup.html">Echo mail groups</a>
<li><A HREF="emareas.html">Echo mail areas</a>
</ol>
<li><A HREF="tic.html">Edit File echo's setup</a>
<ol>
<li><A HREF="fegroup.html">Edit Fileecho groups</a>
<li><A HREF="fileecho.html">Edit Fileecho areas</a>
<li><A HREF="hatch.html">Edit Hatch manager</a>
<li><A HREF="magic.html">Edit Magic files</a>
</ol>
<li><A HREF="newgroups.html">Edit Newfiles groups</a>
<li><A HREF="newfiles.html">Edit Newfiles reports</a>
<li><A HREF="filefind.html">Edit Filefind setup</a>
<li><A HREF="fdb.html">Edit Files database</a>
<li><A HREF="users.html">Edit BBS users</a>
<li><A HREF="services.html">Edit Services</a>
<li><A HREF="domains.html">Edit Domains</A>
<LI><A HREF="taskmgr.html">Edit Task Manager</A>
<li><A HREF="softinfo.html">Show software information</a>
<li><A HREF="sitedoc.html">Create site documents</a>
</ol>
<A HREF="../index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" border="0" width="33" height="35">Back to index</A>
</BLOCKQUOTE>
</BODY>
</HTML>

57
html/setup/language.html Normal file
View File

@@ -0,0 +1,57 @@
<HTML>
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META name="author" lang="en" "content="Michiel Broek">
<META name="copyright" lang="en" content="Copyright Michiel Broek">
<META name="description" lang="en" content="MBSE BBS Manual">
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
<TITLE>MBSE BBS Setup - BBS Setup - Language Setup.</TITLE>
<LINK rel=stylesheet HREF="../manual.css">
</HEAD>
<BODY>
<BLOCKQUOTE>
<h5>Last update 25-Jul-2001</h5>
<P>&nbsp;<P>
<H1>MBSE BBS Setup - BBS Setup - Language Setup.</H1>
<P>
<H3>Language introduction.</H3>
<P>
You need to define at least one language, this is the default language.
The paths to the BBS menus and Txtfiles for the default language
must be exactly the same as defined in the global setup, menus 1.3.1 and 1.3.2<br>
I did this so you can make your
own local languages next to the default languages. If something is not
present in your local language, the BBS will fall back to the default
language. This is true for the menus and textfiles for the BBS. It is
therefore wise to name all menus and textfiles the same for all languages used.
When you setup the languages for the first time, entries for English, Dutch,
Spanish and Italian are created.
<P>&nbsp;<p>
<H3>Language setup.</H3>
<P>
<pre>
<strong>Select </strong>The letter to select this language.
<strong>Name </strong>The name of this language.
<strong>Menupath </strong>The path to the menu files.
<strong>Textpath </strong>The path to the ANSI and ASCII textfiles.
<strong>Macropath </strong>Not in use yet.
<strong>Available </strong>If this language is available.
<strong>Datafile </strong>The name of the language datafile in ~/etc
<strong>Security </strong>The minimum security level to select this language.
<strong>Deleted </strong>If this language must be deleted.
</pre>
<P>
<IMG SRC="../images/language.gif" width="589" height="343">
<P>
<A HREF="bbs.html"><IMG SRC="../images/larrow.gif" ALT="Back" Border="0" width="40" height="30"> Back to BBS index</A>&nbsp;
<A HREF="./"><IMG SRC="../images/larrow.gif" ALT="Back" Border="0" width="40" height="30"> Back to index</A>&nbsp;
<A HREF="../"><IMG SRC="../images/b_arrow.gif" ALT="Home" Border="0" width="33" height="35"> Back to main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>

74
html/setup/magic.html Normal file
View File

@@ -0,0 +1,74 @@
<HTML>
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META name="author" lang="en" "content="Michiel Broek">
<META name="copyright" lang="en" content="Copyright Michiel Broek">
<META name="description" lang="en" content="MBSE BBS Manual">
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
<TITLE>MBSE BBS Setup - File Echo's Setup - Magic Files Setup.</TITLE>
<LINK rel=stylesheet HREF="../manual.css">
</HEAD>
<BODY>
<BLOCKQUOTE>
<h5>Last update 30-Jan-2001</h5>
<P>&nbsp;<P>
<H1>MBSE BBS Setup - File Echo's Setup - Magics Files Setup.</H1>
<P>
<H3>Introduction.</H3>
<P>
Magics are special actions that you can perform if files received in a .tic
area. The actions are: copy file to a directory, unpack file in a directory,
set number of files to keep, move file to another .tic area, update magic
request alias, adopt file into another area, store in another path,
delete file (don't process it further) and execute a command. The edit screen
is different for all kinds of actions you select. More than one magic record
may exist for each area. With all these actions you can for example can setup
processing of nodediff's and unpacking nodelists in the nodelist directory.
<P>&nbsp;<P>
<H3>Magics Setup.</H3>
<P>
<pre>
<strong>Magic </strong>The action to perform, select with the spacebar.
<strong>Filemask </strong>The filemask to scan for. "?" Matches all characters,
"#" matches any digit and "@" any alpha character.
<strong>Active </strong>If this magic is active.
<strong>Deleted </strong>If this magic must be deleted.
<strong>Area </strong>The area in which this magic is found.
<strong>To path </strong>The destination path. (Copy, Other path and Unpack).
<strong>To area </strong>The destination area. (Adopt and Move).
<strong>Command </strong>The command to execute. (Execute).
<strong>Keep # </strong>The number of files to keep. (Keep).
<strong>Compile </strong>Trigger "compile nodelists". (Copy, Unpack and Execute).
</pre>
<P>&nbsp;<P>
<H3>Macro's</H3>
<P>
In the commandline for the magic execute command you may use macro's to replace
parts of the commandline. The following macro's are defined:
<pre>
<strong>%F </strong>Replaced by the full path and filename of the file.
<strong>%P </strong>Replaced by the full path to the file.
<strong>%N </strong>Replaced by the filename without dot and extension.
<strong>%E </strong>Replaced by the extension of the filename.
<strong>%L </strong>The last 2 characters of the filename extension.
<strong>%D </strong>The day number of the year, 3 digits.
<strong>%C </strong>The last 2 digits of the day number of the year.
<strong>%A </strong>The .tic area name.
</pre>
<P>
<IMG SRC="../images/magic.gif" width="589" height="343">
<P>
<A HREF="tic.html"><IMG SRC="../images/larrow.gif" ALT="Back" Border="0" width="40" height="30"> Back to File Echo's Setup</A>&nbsp;
<A HREF="./"><IMG SRC="../images/larrow.gif" ALT="Back" Border="0" width="40" height="30"> Back to index</A>&nbsp;
<A HREF="../"><IMG SRC="../images/b_arrow.gif" ALT="Home" Border="0" width="33" height="35"> Back to main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>

35
html/setup/mail.html Normal file
View File

@@ -0,0 +1,35 @@
<HTML>
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META name="author" lang="en" "content="Michiel Broek">
<META name="copyright" lang="en" content="Copyright Michiel Broek">
<META name="description" lang="en" content="MBSE BBS Manual">
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
<TITLE>MBSE BBS Setup - Mail Setup.</TITLE>
<LINK rel=stylesheet HREF="../manual.css">
</HEAD>
<BODY>
<BLOCKQUOTE>
<h5>Last update 29-Jan-2001</h5>
<P>&nbsp;<P>
<H1>MBSE BBS Setup - Mail Setup.</H1>
<P>
<H3>Edit Mail Setup.</H3>
<P>
The Mail Setup is split in the following sections:
<P>
<ol>
<li><A HREF="emgroup.html">Echo mail groups</a>
<li><A HREF="emareas.html">Echo mail areas</A>
</ol>
<A HREF="./"><IMG SRC="../images/larrow.gif" ALT="Back" Border="0" width="40" height="30"> Back to index</A>&nbsp;
<A HREF="../"><IMG SRC="../images/b_arrow.gif" ALT="Home" Border="0" width="33" height="35"> Back to main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>

88
html/setup/modems.html Normal file
View File

@@ -0,0 +1,88 @@
<HTML>
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META name="author" lang="en" "content="Michiel Broek">
<META name="copyright" lang="en" content="Copyright Michiel Broek">
<META name="description" lang="en" content="MBSE BBS Manual">
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
<TITLE>MBSE BBS Setup - Modem types.</TITLE>
<LINK rel=stylesheet HREF="../manual.css">
</HEAD>
<BODY>
<BLOCKQUOTE>
<h5>Last update 29-Jan-2001</h5>
<P>&nbsp;<P>
<H1>MBSE BBS Setup - Modem types</H1>
<P>
In the setup screen you can define all kinds of modems you use. This includes
ISDN modems.
This is not the setup of individual lines, that is in the next section, so
if you own a bbs with 5 analogue lines with only two brands and types of
modems connected, you need only to define those two types of modems here. Some
defaults are installed during initial bbs setup.
<P>&nbsp;<P>
<h3>Setup a modem.</h3>
<p>
<pre>
<strong>Type </strong>The description of this modem.
<strong>Init 1 </strong>The first modem init string.
<strong>Init 2 </strong>The second init string (if needed).
<strong>Init 3 </strong>The third init string (if needed).
<strong>Reset </strong>Not in use
<strong>Hangup </strong>Only needed if drop DTR doesn't work.
<strong>Dial </strong>The dial command.
<strong>Info </strong>Command to get caller-id (not tested).
<strong>Ok </strong>The modem "OK" response.
<strong>Offset </strong>The answer/connect time offset.
<strong>Speed </strong>The maximum modem linespeed, ie 28800.
<strong>Available </strong>If this modem is available.
<strong>Deleted </strong>If this modem must be deleted.
<strong>Stripdash </strong>Strip dashes from the dial command.
<strong>Connect strings </strong>Here you can define 20 connect strings.
<strong>Error strings </strong>Here you can define 10 non-connect strings.
</pre>
<p>&nbsp;<P>
<H3>Special characters</H3>
<p>
<pre>
<strong>\\ </strong>Send one backslash.
<strong>\r </strong>Send the CR character.
<strong>\n </strong>Send the LF character.
<strong>\t </strong>Send the TAB character.
<strong>\b </strong>Send the BS character.
<strong>\s </strong>Send a space character.
<strong>\d </strong>Wait one second.
<strong>\p </strong>Wait 0,25 second.
<strong>\D </strong>Send untranslated phone number.
<strong>\T </strong>Send translated phone number.
</pre>
<p>&nbsp;<P>
<H3>The Hangup field</H3>
<p>
This is only needed if your modem doesn't hangup by dropping the DTR line for
one second. Most modems do that if &D2 or &D3 is in the init string.
<p>&nbsp;<P>
<H3>The Offset field.</H3>
<p>
The <strong>Offset</strong> field is to calculate the cost for outgoing calls.
Analogue modems need time to establish the connection, 6 seconds is quite
common. So when you see the CONNECT BLABLA message, the phone connection
is there already 6 seconds and you are already paying for 6 seconds. This
offset is thus added to the total calculated connect time for cost
calculations. For ISDN modems this can be 1 or 0.
<p>&nbsp;<P>
<IMG SRC="../images/modems0.gif" width="589" height="343">
<P>
<A HREF="./"><IMG SRC="../images/larrow.gif" ALT="Back" Border="0" width="40" height="30"> Back to index</A>&nbsp;
<A HREF="../"><IMG SRC="../images/b_arrow.gif" ALT="Home" Border="0" width="33" height="35"> Back to main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>

54
html/setup/newfiles.html Normal file
View File

@@ -0,0 +1,54 @@
<HTML>
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META name="author" lang="en" "content="Michiel Broek">
<META name="copyright" lang="en" content="Copyright Michiel Broek">
<META name="description" lang="en" content="MBSE BBS Manual">
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
<TITLE>MBSE BBS Setup - Newfiles Reports.</TITLE>
<LINK rel=stylesheet HREF="../manual.css">
</HEAD>
<BODY>
<BLOCKQUOTE>
<h5>Last update 30-Jan-2001</h5>
<P>&nbsp;<P>
<H1>MBSE BBS Setup - Newfiles Reports.</H1>
<P>
<H3>Introduction.</H3>
<P>
For each network you can define one or more newfiles reports to announce the
newfiles that arrived on your BBS. The files to include in the reports are
specified by the newfiles groups you can include or exclude for announcement.
<P>&nbsp;<P>
<H3>Reports Setup.</H3>
<P>
<pre>
<strong>Comment </strong>The comment for this report.
<strong>Msg area </strong>The JAM message base to write the report in.
<strong>Origin line </strong>The origin line to use.
<strong>From name </strong>The name to use in the "From:" field.
<strong>To name </strong>The name to use in the "To :" field.
<strong>Subject </strong>The text to use in the "Subj:" field.
<strong>Language </strong>Not in use yet, but DO select!
<strong>Template </strong>Not in use yet.
<strong>Aka to use </strong>The Fidonet aka to use in this area.
<strong>Active </strong>If this report is active.
<strong>Deleted </strong>If this report must be deleted.
<strong>High ASCII </strong>Allow high ASCII in this area.
<strong>New groups </strong>The screen to define the groups to include.
</pre>
<P>
<IMG SRC="../images/newfiles.gif" width="589" height="343">
<P>
<A HREF="./"><IMG SRC="../images/larrow.gif" ALT="Back" Border="0" width="40" height="30"> Back to index</A>&nbsp;
<A HREF="../"><IMG SRC="../images/b_arrow.gif" ALT="Home" Border="0" width="33" height="35"> Back to main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>

49
html/setup/newgroups.html Normal file
View File

@@ -0,0 +1,49 @@
<HTML>
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META name="author" lang="en" "content="Michiel Broek">
<META name="copyright" lang="en" content="Copyright Michiel Broek">
<META name="description" lang="en" content="MBSE BBS Manual">
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
<TITLE>MBSE BBS Setup - Newfiles Groups.</TITLE>
<LINK rel=stylesheet HREF="../manual.css">
</HEAD>
<BODY>
<BLOCKQUOTE>
<h5>Last update 30-Jan-2001</h5>
<P>&nbsp;<P>
<H1>MBSE BBS Setup - Newfiles Groups.</H1>
<P>
<H3>Introduction</H3>
<P>
The newfiles group are there to create separate newfiles announcements for
several networks and areas. Even if you don't want to make different
announcements you still need to define at least 2 groups. One is a group
where you don't announce files in and one where you do. These groups are
linked to the BBS file areas and must be defined before you define the BBS
file areas. As you can see in the example picture I seperated the groups
in subjects.
<P>&nbsp;<P>
<H3>Newfiles Groups Setup.</H3>
<P>
<pre>
<strong>Name </strong>The tag name of the group.
<strong>Comment </strong>The comment for this group.
<strong>Active </strong>If this group is active.
<strong>Deleted </strong>If this group must be deleted.
</pre>
<P>
<IMG SRC="../images/newgroups.gif" width="589" height="343">
<P>
<A HREF="./"><IMG SRC="../images/larrow.gif" ALT="Back" Border="0" width="40" height="30"> Back to index</A>&nbsp;
<A HREF="../"><IMG SRC="../images/b_arrow.gif" ALT="Home" Border="0" width="33" height="35"> Back to main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>

146
html/setup/nodes.html Normal file
View File

@@ -0,0 +1,146 @@
<HTML>
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META name="author" lang="en" "content="Michiel Broek">
<META name="copyright" lang="en" content="Copyright Michiel Broek">
<META name="description" lang="en" content="MBSE BBS Manual">
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
<TITLE>MBSE BBS Setup - Fidonet nodes.</TITLE>
<LINK rel=stylesheet HREF="../manual.css">
</HEAD>
<BODY>
<BLOCKQUOTE>
<h5>Last update 22-Jun-2001</h5>
<P>&nbsp;<P>
<H1>MBSE BBS Setup - Fidonet nodes.</H1>
<P>
<h3>Introduction</H3>
<P>
Unlike many other bbs packages, for each node you need only one record. If you
have a relation with a node for one network with costsharing, and other
networks without costsharing you need two records for that node. For each node
you can setup the aka's, mail, files and session handshake.
<p>&nbsp;<p>
<H3>Main setup</H3>
<p>
<pre>
<strong>Sysop name </strong>The name of the system operator.
<strong>Fido aka's </strong>Maximum 20 Fido addresses.
<strong>Dial command </strong>You can put an override here for the normal
dial command. If you leave this empty the
command from the modem setup is used.
<strong>Phone number 1 </strong>An alternative phone number/ip address to dial.
<strong>Phone number 2 </strong>An alternative phone number/ip address to dial.
Use these above commands if the node has
another phone number as mentioned in the
nodelist. If you call this node via TCP/IP
and the IP address can't be resolved by
the nodelist, you may enter an IP address
or hostname here.
<strong>Route via </strong>A route via Fido address. All mail for this
node will be send via this Aka, even mail
and files for other networks. This can be
usefull if this node has internet access
so you can send everything to this node
over the internet.
<strong>Netmail direct </strong>Set "direct" flag in netmail to this node.
<strong>Netmail crash </strong>Send netmail always "crash" to this node.
<strong>Netmail hold </strong>Put mail on "hold" for this node.
<strong>Send notify </strong>Send automatic generated notify messages.
<strong>Language </strong>The language to use (not yet working).
<strong>Deleted </strong>If this node must be deleted.
<strong>No EMSI </strong>Disable EMSI handshake.
<strong>No YooHoo/2U2 </strong>Disable FTSC-0006 handshake.
<strong>No Filerequest </strong>Disable filerquest from this node.
<strong>Don't call </strong>Do not call this node.
<strong>No Hold mail </strong>Only pickup mail if we call, send nothing.
<strong>Pickup primary </strong>Only exchange mail for one Aka.
<strong>No Zmodem </strong>Disable Zmodem protocol.
<strong>No Zedzap </strong>Disable Zedzap protocol.
<strong>No Hydra </strong>Disable Hydra protocol.
<strong>No TCP/IP </strong>Disbale TCP/IP protocol, forces dial only.
</pre>
<P>
<IMG SRC="../images/nodes.gif" width="589" height="343">
<P>&nbsp;<p>
<H3>Mail setup</H3>
<P>
<pre>
<strong>Session pwd </strong>The mailer session password.
<strong>Check PKT pwd </strong>Check password in received .pkt files. If not,
errors or missing passwords are only logged.
If set, errors or missing password are refused
and the .pkt files are renamed to .bad
<strong>UplMgr program </strong>The name of the Areamgr program of this node.
(This doesn't work yet).
<strong>UplMgr passwd </strong>The password for the Areamgr of this node.
<strong>Mail forward </strong>Not in use yet.
<strong>ARCmail comp. </strong>Use ARCmail 0.60 file naming convention for out of zone mail.
<strong>ARCmail a..z </strong>Allow a..z last character for ARCmail filenames.
</pre>
<P>
<IMG SRC="../images/nodes1.gif" width="576" height="344">
<P>&nbsp;<p>
<H3>Mail groups</H3>
<P>
Here you can tag which mail groups are available for this node. Note that all
groups are visible here, even for networks this node has no aka's in. Be
carefull not to allow a node to connect areas from networks he has no aka in.
<P>
<IMG SRC="../images/nodes2.gif" width="589" height="343">
<P>&nbsp;<p>
<H3>File setup</H3>
<P>
<pre>
<strong>Files password </strong>The password for .tic files.
<strong>Mgr password </strong>The password for the Areamgr and Filemgr.
<strong>UplMgr program </strong>The name of the Filemgr progrom of this node.
<strong>UplMgr passwd </strong>The password of the Filemgr if this node.
<strong>UplMgr Add + </strong>Add a "+" in the command to connect areas.
<strong>Incl. message </strong>Send a netmail message for each file to send.
<strong>Send TIC file </strong>Send .tic file to this node.
<strong>Advanced TIC </strong>Send advanced or standard .tic files.
<strong>File forward </strong>Forward TIC files for this node (not yet).
<strong>Billing </strong>Is Costsharing active for this node.
<strong>Bill direct </strong>Send the bill direct or on command.
<strong>Credit </strong>The credit this node has in units.
<strong>Debet </strong>The debet we have with this node (informational).
<strong>Add </strong>Add (or substract) factor to the bill.
<strong>Warn level </strong>The debet level when to write a warning mesage.
<strong>Stop level </strong>The debet level when to stop sending files.
</pre>
<P>
<IMG SRC="../images/nodes3.gif" width="589" height="343">
<P>&nbsp;<p>
<H3>File groups</H3>
<P>
The same story as for mail groups is true for the file groups.
<P>
<IMG SRC="../images/nodes4.gif" width="589" height="343">
<P>&nbsp;<p>
<H3>Statistics</H3>
<P>
In this statistics screen you can see the mail and files flow with this
node. Values are stored for the current week, the previous week, the
current month and previous month and the overall total since you defined
this node. There are actual 12 months of statistics stored in the nodes
record, only 2 are visible.
<P>
<IMG SRC="../images/nodes5.gif" width="589" height="343">
<P>
<A HREF="./"><IMG SRC="../images/larrow.gif" ALT="Back" Border="0" width="40" height="30"> Back to index</A>&nbsp;
<A HREF="../"><IMG SRC="../images/b_arrow.gif" ALT="Home" Border="0" width="33" height="35"> Back to main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>

37
html/setup/oneliner.html Normal file
View File

@@ -0,0 +1,37 @@
<HTML>
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META name="author" lang="en" "content="Michiel Broek">
<META name="copyright" lang="en" content="Copyright Michiel Broek">
<META name="description" lang="en" content="MBSE BBS Manual">
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
<TITLE>MBSE BBS Setup - BBS Setup - Oneliners.</TITLE>
<LINK rel=stylesheet HREF="../manual.css">
</HEAD>
<BODY>
<BLOCKQUOTE>
<h5>Last update 29-Jan-2001</h5>
<P>&nbsp;<P>
<H1>MBSE BBS Setup - BBS Setup - Oneliners.</H1>
<P>
<H3>Oneliners.</H3>
<P>
Oneliners are small quotes that can be random selected and displayed to
your users. From the same database oneliners can be selected and inserted
at the bottom of messages. With the oneliners setup you can edit, add,
delete and import oneliners. Import is done from plain ASCII textfiles,
one quote on each line. The lines should be maximum 70 characters long.
<P>
<IMG SRC="../images/oneliner.gif" width="589" height="343">
<P>
<A HREF="bbs.html"><IMG SRC="../images/larrow.gif" ALT="Back" Border="0" width="40" height="30"> Back to BBS index</A>&nbsp;
<A HREF="./"><IMG SRC="../images/larrow.gif" ALT="Back" Border="0" width="40" height="30"> Back to index</A>&nbsp;
<A HREF="../"><IMG SRC="../images/b_arrow.gif" ALT="Home" Border="0" width="33" height="35"> Back to main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>

55
html/setup/protocol.html Normal file
View File

@@ -0,0 +1,55 @@
<HTML>
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META name="author" lang="en" "content="Michiel Broek">
<META name="copyright" lang="en" content="Copyright Michiel Broek">
<META name="description" lang="en" content="MBSE BBS Manual">
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
<TITLE>MBSE BBS Setup - BBS Setup - Transfer Protocols.</TITLE>
<LINK rel=stylesheet HREF="../manual.css">
</HEAD>
<BODY>
<BLOCKQUOTE>
<h5>Last update 29-Jan-2001</h5>
<P>&nbsp;<P>
<H1>MBSE BBS Setup - BBS Setup - Transfer Protocols.</H1>
<P>
<H3>Introduction.</H3>
<p>
It might look strange that you have to define transfer protocols for the bbs
while for the mailer you don't need to do that. This is historic, ifcico
already had internal protocols and the precessor of the bbs package had external
protocols. Because my priority was make the bbs working it still is that way.
When time comes I will build some of the protocols internal, adding external
protocols will allways be possible.
<P>&nbsp;<p>
<H3>Transfer Protocols Setup.</H3>
<P>
<pre>
<strong>Select Key </strong>The key the user has to press to select this protocol.
<strong>Name </strong>The name of this protocol.
<strong>Upload </strong>The full path and filename and parameters to upload files.
<strong>Download </strong>The full path and filename and parameters to download files.
<strong>Available </strong>If this protocol is available.
<strong>Batching </strong>If this is a batching protocol.
<strong>Bi direct </strong>If this is a bi-directional protocol (Not supported yet).
<strong>Advice </strong>A small advice to the user shown before the transfer starts.
<strong>Efficiency </strong>The efficiency in percent. Has no real meaning.
<strong>Deleted </strong>If this protocol must be deleted.
<strong>Sec. level </strong>The security level a user must have to select this protocol.
</pre>
<P>
<IMG SRC="../images/protocol.gif" width="589" height="343">
<P>
<A HREF="bbs.html"><IMG SRC="../images/larrow.gif" ALT="Back" Border="0" width="40" height="30"> Back to BBS index</A>&nbsp;
<A HREF="./"><IMG SRC="../images/larrow.gif" ALT="Back" Border="0" width="40" height="30"> Back to index</A>&nbsp;
<A HREF="../"><IMG SRC="../images/b_arrow.gif" ALT="Home" Border="0" width="33" height="35"> Back to main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>

29
html/setup/safe.html Executable file
View File

@@ -0,0 +1,29 @@
<HTML>
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META name="author" lang="en" "content="Michiel Broek">
<META name="copyright" lang="en" content="Copyright Michiel Broek">
<META name="description" lang="en" content="MBSE BBS Manual">
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
<TITLE>MBSE BBS Setup - BBS Setup - Safe Cracker Data.</TITLE>
<LINK rel=stylesheet HREF="../manual.css">
</HEAD>
<BODY>
<BLOCKQUOTE>
<h5>Last update 29-Jan-2001</h5>
<P>&nbsp;<P>
<H1>MBSE BBS Setup - BBS Setup - Safe Cracker Data</H1>
<P>
This is meant to edit users personal safe cracker records and to reset
the winner. This is not available yet.
<P>
<A HREF="bbs.html"><IMG SRC="../images/larrow.gif" ALT="Back" Border="0" width="40" height="30"> Back to BBS index</A>&nbsp;
<A HREF="./"><IMG SRC="../images/larrow.gif" ALT="Back" Border="0" width="40" height="30"> Back to index</A>&nbsp;
<A HREF="../"><IMG SRC="../images/b_arrow.gif" ALT="Home" Border="0" width="33" height="35"> Back to main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>

56
html/setup/security.html Normal file
View File

@@ -0,0 +1,56 @@
<HTML>
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META name="author" lang="en" "content="Michiel Broek">
<META name="copyright" lang="en" content="Copyright Michiel Broek">
<META name="description" lang="en" content="MBSE BBS Manual">
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
<TITLE>MBSE BBS Setup - BBS Setup - Security Limits.</TITLE>
<LINK rel=stylesheet HREF="../manual.css">
</HEAD>
<BODY>
<BLOCKQUOTE>
<h5>Last update 29-Jan-2001</h5>
<P>&nbsp;<P>
<H1>MBSE BBS Setup - BBS Setup - Security Limits.</H1>
<P>
<H3>Security limits, introduction.</H3>
<P>
Every BBS needs several security limits to make a difference between several
user groups. These are the twits, regular users and (co-)sysops. If you have
a donation system you will probably have more different levels. Every level a
user can have must have a record in this file. To operate MBSE BBS you need at
least 3 levels, twit with level 0, new users with the level as setup in 1.5.1,
and the sysop level as setup in 1.4.5 As said, for special usergroups you can
add more levels as you need. If a user logs in and has a level in the userbase
you didn't define here, he won't be able to login. Even the twit level needs
some access to be able to throw him out in a nice but friendly way, give him
5 minutes, 1 file to download and no more then 1 Kb so he will understand he
is not wanted. Some defaults are installed during first bbs setup.
<P>&nbsp;<p>
<H3>Limits setup</H3>
<P>
<pre>
<strong>Access level </strong>The access level value.
<strong>Maximum time </strong>The maximum time each day.
<strong>Download Kb. </strong>Maximum Kilobytes download each day.
<strong>Download Files </strong>Maximum files to download each day.
<strong>Description </strong>The description for this level.
<strong>Available </strong>If this level is available.
<strong>Deleted </strong>If this level must be deleted.
</pre>
<p>
<IMG SRC="../images/security.gif" width="589" height="343">
<P>
<A HREF="bbs.html"><IMG SRC="../images/larrow.gif" ALT="Back" Border="0" width="40" height="30"> Back to BBS index</A>&nbsp;
<A HREF="./"><IMG SRC="../images/larrow.gif" ALT="Back" Border="0" width="40" height="30"> Back to index</A>&nbsp;
<A HREF="../"><IMG SRC="../images/b_arrow.gif" ALT="Home" Border="0" width="33" height="35"> Back to main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>

69
html/setup/services.html Normal file
View File

@@ -0,0 +1,69 @@
<HTML>
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META name="author" lang="en" "content="Michiel Broek">
<META name="copyright" lang="en" content="Copyright Michiel Broek">
<META name="description" lang="en" content="MBSE BBS Manual">
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
<TITLE>MBSE BBS Setup - Edit Services.</TITLE>
<LINK rel=stylesheet HREF="../manual.css">
</HEAD>
<BODY>
<BLOCKQUOTE>
<h5>Last update 06-Jun-2001</h5>
<P>&nbsp;<P>
<H1>MBSE BBS Setup - Edit Services.</H1>
<P>
<H3>Introduction.</H3>
<P>
Services are special mail accounts. Netmail addressed to one of these names
will be handled according to the action that is selected. Current implemented
actions are AreaMgr, FileMgr and Email. So if you name a service <strong>
Areamgr</strong> and set the action to <strong>AreaMgr</strong> then an incoming
netmail will be directed to the Areamgr function. If you define a service
<strong>listserv</strong> and set the action to <strong>Email</strong> then
and incoming netmail will be converted to email and send to <strong>listserv</strong>
at your host.<br>
If you should want to run some votemanager on your system you can
do that by creating a service <b>votemgr</b> with the type set to <b>email</b>.
You also need to setup a valid unix user <b>votemgr</b> so that there will be an excisting
mailbox. Then with some external scripts you can process all received messages.
<P>&nbsp;<P>
<H3>Edit Services.</H3>
<P>
<pre>
<strong>Name </strong>The name of the Service.
<strong>Type </strong>Toggle the service type with the spacebar.
<strong>Active </strong>If this service is active.
<strong>Deleted </strong>If this service must be deleted.
</pre>
<P>
Here are some example services:
<P>
<PRE>
UUCP Email
allfix FileMgr
areamgr AreaMgr
fmail AreaMgr
gecho AreaMgr
listserv Email
majordomo Email
mbsebbs Email
mbsebbs-owner Email
mbtic FileMgr
owner-mbsebbs Email
raid FileMgr
</PRE>
Note: the UUCP services is needed if you are gating email!
<P>
<A HREF="./"><IMG SRC="../images/larrow.gif" ALT="Back" Border="0" width="40" height="30"> Back to index</A>&nbsp;
<A HREF="../"><IMG SRC="../images/b_arrow.gif" ALT="Home" Border="0" width="33" height="35"> Back to main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>

37
html/setup/sitedoc.html Normal file
View File

@@ -0,0 +1,37 @@
<HTML>
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META name="author" lang="en" "content="Michiel Broek">
<META name="copyright" lang="en" content="Copyright Michiel Broek">
<META name="description" lang="en" content="MBSE BBS Manual">
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
<TITLE>MBSE BBS Setup - Create Sitedocs.</TITLE>
<LINK rel=stylesheet HREF="../manual.css">
</HEAD>
<BODY>
<BLOCKQUOTE>
<h5>Last update 30-Jan-2001</h5>
<P>&nbsp;<P>
<H1>MBSE BBS Setup - Create Sitedocs.</H1>
<P>
<H3>Create Sitedocs</H3>
<P>
This option creates 3 documents in the doc directory under the home directory
of MBSE BBS, site.doc, xref.doc and stat.doc. Only the file site.doc is more
or less complete, the other 2 are heavily under construction. These three
files are a complete reference of your BBS setup. Especially the site.doc is
a large document, think at least four times before you send it to a printer.
The document xref.doc will contain lists with data from your setup that
depends on eachother. The file stat.doc will be a listing of all statistic
counters that are present in several data files.
<P>
<A HREF="./"><IMG SRC="../images/larrow.gif" ALT="Back" Border="0" width="40" height="30"> Back to index</A>&nbsp;
<A HREF="../"><IMG SRC="../images/b_arrow.gif" ALT="Home" Border="0" width="33" height="35"> Back to main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>

31
html/setup/softinfo.html Normal file
View File

@@ -0,0 +1,31 @@
<HTML>
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META name="author" lang="en" "content="Michiel Broek">
<META name="copyright" lang="en" content="Copyright Michiel Broek">
<META name="description" lang="en" content="MBSE BBS Manual">
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
<TITLE>MBSE BBS Setup - Show Software Information.</TITLE>
<LINK rel=stylesheet HREF="../manual.css">
</HEAD>
<BODY>
<BLOCKQUOTE>
<h5>Last update 30-Jan-2001</h5>
<P>&nbsp;<P>
<H1>MBSE BBS Setup - Show Software Information.</H1>
<P>
<H3>Introduction</H3>
<P>
This screen shows the information about the MBSE BBS software, copyright and
release policy.
<P>
<A HREF="./"><IMG SRC="../images/larrow.gif" ALT="Back" Border="0" width="40" height="30"> Back to index</A>&nbsp;
<A HREF="../"><IMG SRC="../images/b_arrow.gif" ALT="Home" Border="0" width="33" height="35"> Back to main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>

67
html/setup/taskmgr.html Normal file
View File

@@ -0,0 +1,67 @@
<HTML>
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META name="author" lang="en" "content="Michiel Broek">
<META name="copyright" lang="en" content="Copyright Michiel Broek">
<META name="description" lang="en" content="MBSE BBS Manual">
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
<TITLE>MBSE BBS Setup - Task Manager.</TITLE>
<LINK rel=stylesheet HREF="../manual.css">
</HEAD>
<BODY>
<BLOCKQUOTE>
<h5>Last update 07-Jul-2001</h5>
<P>&nbsp;<P>
<H1>MBSE BBS Setup - Task Manager.</H1>
<P>
<H3>Introduction</H3>
<P>
The task manager is the daemon which controls the MBSE BBS. It watches semafore's and spawns
programs in the background. The behaviour is setup in this screen.
<P>
<H3>Edit Task Manager</H3>
<P>
<pre>
<b>Mailout </b>Action for semafore mailout.
<b>Mailin </b>Action for semafore mailin.
<b>Newnews </b>Action for semafore newnews.
<b>Index 1 </b>Nodelist compiler 1 for semafore mbindex.
<b>Index 2 </b>Nodelist compiler 2 for semafore mbindex.
<b>Index 3 </b>Nodelist compiler 3 for semafore mbindex.
<b>Msglink </b>Action for semafore msglink.
<b>Reqindex </b>Action for semafore reqindex.
<b>ISP conn </b>Not in use yet!
<b>ISP disc </b>Not in use yet!
<b>Ping #1 </b>IP address of node to ping to check the internet.
<b>Ping #2 </b>IP address of second node to ping to check the internet.
<b>ISP blks </b>Set to true if you have internet dialup and if it blocks normal dial.
<b>Max Load </b>Max system load until processing is suspended.
<b>ZMH start </b>Start of Zone Mail Hour in UTC time.
<b>ZMH end </b>End of Zone Mail Hour in UTC time.
<b>Debug </b>Enable debug logging.
<b>Max POTS </b>Maximum simultaneous outgoing calls (for now ISDN + POTS + TCP/IP).
<b>Max ISDN </b>Not in use yet!
<b>Max TCP </b>Not in use yet!
</pre>
<P>
Default are the original MBSE commands filled in, but you could also call
shell scripts. As you can see, the task manager is not yet finished.
<P>
The two IP addresses to ping need to be IP addresses, not hostnames. This is the
most reliable way to check the connection. You should enter the IP addresses of
the nameservers of your own ISP here. One of these will always be up, so if one
of these can be reached, the internet connection is assumed to be alive.
<P>
<IMG SRC="../images/taskmgr.gif" Border="0">
<P>
<A HREF="./"><IMG SRC="../images/larrow.gif" ALT="Back" Border="0" width="40" height="30"> Back to index</A>&nbsp;
<A HREF="../"><IMG SRC="../images/b_arrow.gif" ALT="Home" Border="0" width="33" height="35"> Back to main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>

37
html/setup/tic.html Normal file
View File

@@ -0,0 +1,37 @@
<HTML>
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META name="author" lang="en" "content="Michiel Broek">
<META name="copyright" lang="en" content="Copyright Michiel Broek">
<META name="description" lang="en" content="MBSE BBS Manual">
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
<TITLE>MBSE BBS Setup - File Echo's Setup.</TITLE>
<LINK rel=stylesheet HREF="../manual.css">
</HEAD>
<BODY>
<BLOCKQUOTE>
<h5>Last update 29-Jan-2001</h5>
<P>&nbsp;<P>
<H1>MBSE BBS Setup - File Echo's Setup.</H1>
<P>
<H3>File Echo's Setup.</H3>
<P>
The File Echo's Setup is split in the following sections:
<P>
<ol>
<li><A HREF="fegroup.html">File echo groups</a>
<li><A HREF="fileecho.html">File echo areas</A>
<li><A HREF="hatch.html">Hatch manager</a>
<li><A HREF="magic.html">Magic files</a>
</ol>
<A HREF="./"><IMG SRC="../images/larrow.gif" ALT="Back" Border="0" width="40" height="30"> Back to index</A>&nbsp;
<A HREF="../"><IMG SRC="../images/b_arrow.gif" ALT="Home" Border="0" width="33" height="35"> Back to main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>

29
html/setup/timebank.html Executable file
View File

@@ -0,0 +1,29 @@
<HTML>
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META name="author" lang="en" "content="Michiel Broek">
<META name="copyright" lang="en" content="Copyright Michiel Broek">
<META name="description" lang="en" content="MBSE BBS Manual">
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
<TITLE>MBSE BBS Setup - BBS Setup - TimeBank.</TITLE>
<LINK rel=stylesheet HREF="../manual.css">
</HEAD>
<BODY>
<BLOCKQUOTE>
<h5>Last update 29-Jan-2001</h5>
<P>&nbsp;<P>
<H1>MBSE BBS Setup - BBS Setup - TimeBank.</H1>
<P>
This is meant to edit the users personal timebank records. This is not
available yet.
<P>
<A HREF="bbs.html"><IMG SRC="../images/larrow.gif" ALT="Back" Border="0" width="40" height="30"> Back to BBS index</A>&nbsp;
<A HREF="./"><IMG SRC="../images/larrow.gif" ALT="Back" Border="0" width="40" height="30"> Back to index</A>&nbsp;
<A HREF="../"><IMG SRC="../images/b_arrow.gif" ALT="Home" Border="0" width="33" height="35"> Back to main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>

73
html/setup/ttyinfo.html Normal file
View File

@@ -0,0 +1,73 @@
<HTML>
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META name="author" lang="en" "content="Michiel Broek">
<META name="copyright" lang="en" content="Copyright Michiel Broek">
<META name="description" lang="en" content="MBSE BBS Manual">
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
<TITLE>MBSE BBS Setup - TTY Lines.</TITLE>
<LINK rel=stylesheet HREF="../manual.css">
</HEAD>
<BODY>
<BLOCKQUOTE>
<h5>Last update 29-Jan-2001</h5>
<P>&nbsp;<P>
<H1>MBSE BBS Setup - TTY Lines.</H1>
<P>
<h3>Introduction.</H3>
<P>
For each line your bbs has you must setup a tty line. This also includes
console lines (for local login), network lines for internet and lan connections
and X-terminal connections, ISDN lines, and Analogue modem lines. If a call
comes in over a tty you didn't define, that call is refused. So if you are
directly connected to the internet, and have only 5 network tty's defined,
then maximum 5 users are allowed to telnet to your bbs via the internet.
<p>
One thing about the portspeed, this is only needed for devices connected to
serial ports such as modems and external ISDN adapters. For network tty's and
internal ISDN cards this should be set to zero. If you set it to some other value,
things still word but you will get error messages in the logs.
<p>
A note about the EMSI flags, this <u>must</u> match your modem capabilities, if
not dialout will not work correct. It is used to see which line to use to call
a certain node. If you add the X75 flag on an analogue line, your system will try to
call ISDN nodes using an analogue modem. So these are not your nodelist flags as they
may represent combined ISDN and analogue flags but the flags that belong to a modem.
<p>&nbsp;<p>
<H3>Setup a line.</H3>
<p>
<pre>
<strong>Comment </strong>A description for this line.
<strong>TTY device </strong>The tty device name without /dev/
<strong>Phone nr. </strong>The phone number on this line.
<strong>Line Speed </strong>The maximum line speed for this line.
<strong>Fido Flags </strong>The EMSI flags for this line, include your modem flags here!
<strong>Line Type </strong>Can be POTS, ISDN, Network and Local.
<strong>Available </strong>Is this line available for use.
<strong>Auth. log </strong>Not in use yet.
<strong>Honor ZMH </strong>Deny users during ZMH on this line.
<strong>Deleted </strong>If this line must be deleted.
<strong>Callout </strong>Allow calling other systems from this line.
<strong>Portspeed </strong>The "locked" modemspeed, 0 to 4000000 baud, only for serial ports.
<strong>Modemtype </strong>The modem connected to this line.
<strong>EMSI name </strong>The EMSI name presented for this (modem) line.
</pre>
<p>&nbsp;<p>
<H3>Some examples.</H3>
<P>
<IMG SRC="../images/tty.gif" width="589" height="343"><P>
<IMG SRC="../images/tty1.gif" width="576" height="344"><P>
<IMG SRC="../images/tty2.gif" width="589" height="342"><P>
<IMG SRC="../images/tty3.gif" width="589" height="343"><P>
<A HREF="./"><IMG SRC="../images/larrow.gif" ALT="Back" Border="0" width="40" height="30"> Back to index</A>&nbsp;
<A HREF="../"><IMG SRC="../images/b_arrow.gif" ALT="Home" Border="0" width="33" height="35"> Back to main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>

80
html/setup/users.html Normal file
View File

@@ -0,0 +1,80 @@
<HTML>
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META name="author" lang="en" "content="Michiel Broek">
<META name="copyright" lang="en" content="Copyright Michiel Broek">
<META name="description" lang="en" content="MBSE BBS Manual">
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
<TITLE>MBSE BBS Setup - BBS Users.</TITLE>
<LINK rel=stylesheet HREF="../manual.css">
</HEAD>
<BODY>
<BLOCKQUOTE>
<h5>Last update 30-Jan-2001</h5>
<P>&nbsp;<P>
<H1>MBSE BBS Setup - BBS Users.</H1>
<P>
<H3>Introduction.</H3>
<P>
This screen lets you edit some settings of the BBS users. Note that the users
database will never be packed and users will always keep their record number.
If a user is deleted the record will be blanked. New users will get a blank
record if it exists, otherwise the database will be expanded. The reason for
this is the LastRead pointers of the message areas, BBS systems who do it
in another method mostly can't keep track of LastRead pointers and records,
and they mix all users LastRead pointers. Fields that
can be changed by the users themselves are marked with a <b>*</b>.
<P>&nbsp;<P>
<H3>Edit User</H3>
<P>
<pre>
<strong>Full Name </strong>The full (Fidonet) name of the user.
<strong>Handle * </strong>The nickname of the user.
<strong>Location * </strong>The location of the user.
<strong>Address n * </strong>The address of the user (3 lines).
<strong>Voicephone * </strong>The voice phonenumber of the user.
<strong>dataphone * </strong>The data phonenumber of the user.
<strong>Security </strong>The security level of the user.
<strong>Birthdate * </strong>The birthdate of the user DD-MM-YYYY.
<strong>Expirydate </strong>The expiry date of the user DD-MM-YYYY.
<strong>Expiry Sec </strong>The security level the user gets after expiry.
<strong>Unix uid </strong>The unix username of the user.
<strong>Comment </strong>The comment about this user.
<strong>Password * </strong>Change password for this user.
<strong>Sex * </strong>Users sex, male or female.
<strong>Credit </strong>The users credit.
<strong>Protocol * </strong>The selected file transfer protocol.
<strong>Archiver * </strong>The selected archiver.
<strong>Hidden </strong>If the user is hidden from listings etc.
<strong>Hotkeys * </strong>Hotkeys on/off.
<strong>Color * </strong>Color on/off.
<strong>Deleted </strong>User must be deleted.
<strong>No Kill </strong>User can never be deleted.
<strong>Fs Chat * </strong>Use fullscreen chat on/off.
<strong>Locked </strong>Locked out of the BBS.
<strong>Silent * </strong>Do not disturb on/off.
<strong>CLS * </strong>Sent clearscreen codes on/off.
<strong>More * </strong>More prompt on/off.
<strong>Fs Edit * </strong>Use fullscreen editor on/off.
<strong>MailScan * </strong>Scan for new mail at logon on/off.
<strong>Guest </strong>Is this a "guest" account on/off.
<strong>ShowNews * </strong>Show "news" screens on/off.
<strong>NewFiles * </strong>New files scan at logon on/off.
<strong>Ext Info </strong>Send ^aKLUDGES with BlueWave downloads.
<strong>Email </strong>If this user has an email address.
</pre>
<P>
<IMG SRC="../images/users.gif" width="589" height="342">
<P>
<A HREF="./"><IMG SRC="../images/larrow.gif" ALT="Back" Border="0" width="40" height="30"> Back to index</A>&nbsp;
<A HREF="../"><IMG SRC="../images/b_arrow.gif" ALT="Home" Border="0" width="33" height="35"> Back to main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>

52
html/setup/virscan.html Normal file
View File

@@ -0,0 +1,52 @@
<HTML>
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META name="author" lang="en" "content="Michiel Broek">
<META name="copyright" lang="en" content="Copyright Michiel Broek">
<META name="description" lang="en" content="MBSE BBS Manual">
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
<TITLE>MBSE BBS Setup - Virus scanners.</TITLE>
<LINK rel=stylesheet HREF="../manual.css">
</HEAD>
<BODY>
<BLOCKQUOTE>
<h5>Last update 29-Jan-2001</h5>
<P>&nbsp;<P>
<H1>MBSE BBS Setup - virus scanners</H1>
<P>
Once upon a time there was no DOS and no computer virusses. But since DOS was
invented as a small OS which was easily extensible, virus writers saw their
chance to easy spread their hacks. Although running a Linux system is
relative safe, most of the files that you have available on your bbs
are DOS based programs. And before you put them available for download, they
should be checked for virusses. Macro virusses are a relative new danger,
this can also hurt Unix/Linux users.<P>
There are several scanners for Linux available. Default only two of them
are setup. You may consult <A HREF="http://www.openantivirus.org/">
http://www.openantivirus.org</A> for more scanner mentioned in a mini-FAQ
maintained by Rainer Link.
<p>
<b>NAI Virus Scan</b> (uvscan) for Unix (Linux) made by <A HREF="http://www.nai.com">
Network Associates, USA.</A>
Not free for personal use. Uses the same DAT files as for Windows and DOS.
<P>
<strong>AntiVir/Linux</strong> made by <A HREF="http://www.hbedv.com">
H+BEDV Datentechnik GmbH.</A>
Can also be installed in sendmail or Postfix to scan incoming
and outgoing email. This may be a good idea if you run a email gateway.
This version can be registered for personal use.
<P>
As soon as you have made a scanner available in the setup and you receive files
in tic areas where the scan flag is set, then these files will be checked.
As soon as one of the scanners detects a virus the received file will not be imported.
Uploads from users will be checked with the installed virus scanners as well.
<p>
<A HREF="./"><IMG SRC="../images/larrow.gif" ALT="Back" Border="0" width="40" height="30"> Back to index</A>&nbsp;
<A HREF="../"><IMG SRC="../images/b_arrow.gif" ALT="Home" Border="0" width="33" height="35"> Back to main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>