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

Converted from CVS

Browse Source
This commit is contained in:
Mercurial Repos
2009-05-15 22:01:56 +02:00
commit b7b0017dd9
900 changed files with 203942 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -0,0 +1,57 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML>
<!-- $Id: archiver.html,v 1.5 2003/11/09 14:46:32 mbroek Exp $ -->
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META NAME="Language" content='en'>
<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>
<div align='right'><h5>Last update 09-Nov-2003</h5></div>
<div align='center'><H1>MBSE BBS Setup - archiver programs</H1></div>
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>
When you configured the sources and build mbse, the configure script searched
for excisting archivers. When mbsetup was run the first time, when mbtask was
started, the archivers found on your system are already configured with the
right paths and enabled.
If you want the refresh the archivers configuration again after you added new
archiver programs, then remove /opt/mbse/etc/archiver.data. Compile the whole
bbs again, start with <code>make clean</code> and <code>./configure</code>.
After you reinstalled the binaries, run <b>mbsetup</b> and the new archivers are
automagic added to the setup. Of course, you can also add new archivers
manually. Archivers that were not originally found but are known, are present in
the setup but are disabled.
<p>
<A HREF="./"><IMG SRC="../images/larrow.png" ALT="Back" Border="0">Back to index</A>&nbsp;
<A HREF="../"><IMG SRC="../images/b_arrow.png" ALT="Home" Border="0">Back to main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>

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

@@ -0,0 +1,40 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML>
<!-- $Id: bbs.html,v 1.5 2003/11/09 14:46:32 mbroek Exp $ -->
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META NAME="Language" content='en'>
<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>
<DIV align=right><h5>Last update 02-Mar-2003</h5></DIV>
<DIV align=center><H1>MBSE BBS Setup - Edit BBS Setup.</H1></DIV>
<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>
</ol>
<A HREF="./"><IMG SRC="../images/larrow.png" ALT="Back" Border="0">Back to index</A>&nbsp;
<A HREF="../"><IMG SRC="../images/b_arrow.png" ALT="Home" Border="0">Back to main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>

46
html/setup/chat.html Normal file
View File

@@ -0,0 +1,46 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML>
<!-- $Id: chat.html,v 1.5 2005/11/16 20:24:46 mbse Exp $ -->
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META NAME="Language" content='en'>
<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 - Internet BBS Chat.</TITLE>
<LINK rel=stylesheet HREF="../manual.css">
</HEAD>
<BODY>
<BLOCKQUOTE>
<div align='right'><h5>Last update 16-Nov-2005</h5></div>
<div align='center'><H1>MBSE BBS Setup - Internet BBS Chat</H1></div>
<H3>Introduction.</H3>
<P>
MBSE BBS has the chat system that can be linked via internet, Internet BBS
Chat (IBC) using the protocol described in FSP-9999.999. With this setup you can
define other BBS systems to link with. To use IBC with other systems you need to
make sure that UDP port 60179 is open on your firewall.
<P>&nbsp;<P>
<H3>Edit systems</H3>
<P>
<pre>
<strong>Comment </strong>The remote BBS name or a comment.
<strong>Server </strong>The Full Qualified Domain Name of the remote.
<strong>Dyn. DNS </strong>Yes if the remote uses a dyndns name.
<strong>Myname </strong>My FQDN (default copied from 1.2.10).
<strong>Password </strong>The password for the link.
<strong>Active </strong>Is the link active.
<strong>Deleted </strong>If this records must be deleted.
<strong>Compress </strong>Use zlib compression on the link (Not yet).
</pre>
<p>
<A HREF="./"><IMG SRC="../images/larrow.png" ALT="Back" Border="0">Back to index</A>&nbsp;
<A HREF="../"><IMG SRC="../images/b_arrow.png" ALT="Home" Border="0">Back to main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>

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

@@ -0,0 +1,47 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML>
<!-- $Id: domains.html,v 1.5 2003/11/09 14:46:32 mbroek Exp $ -->
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META NAME="Language" content='en'>
<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>
<div align='right'><h5>Last update 25-Oct-2001</h5></div>
<div align='center'><H1>MBSE BBS Setup - Edit Domains.</H1></div>
<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.png" Border='0' ALT='Domains example'>
<P>
<A HREF="./"><IMG SRC="../images/larrow.png" ALT="Back" Border="0">Back to index</A>&nbsp;
<A HREF="../"><IMG SRC="../images/b_arrow.png" ALT="Home" Border="0">Back to main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>

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

@@ -0,0 +1,134 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML>
<!-- $Id: emareas.html,v 1.8 2007/10/14 13:30:04 mbse Exp $ -->
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META NAME="Language" content='en'>
<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>
<div align="right"><h5>Last update 14-Oct-2007</h5></div>
<div align="center"><H1>MBSE BBS Setup - Mail Setup -> Mail Areas.</H1></div>
<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>Group </strong>The name of the echomail group.
<strong>Newsgroup </strong>The newsgroup name if you are gating this area.
<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>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.
<strong>Charset </strong>Default characterset for the area
<strong>Active </strong>If this area is active.
<strong>Days Old </strong>The maximum age of the messages before purging.
<strong>Max. Msgs </strong>The maximum messages in this area.
<strong>Articles </strong>The maximum news headers to fetch.
<strong>Netreply </strong>Netmail reply area if this is echomail.
<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>User Del. </strong>Users may delete their own messages.
<strong>Aliases </strong>Allow the use of an Alias.
<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.
<strong>Security </strong>The security flags for downlinks to access this area.
</pre>
<P>
<IMG SRC="../images/emareas.png" alt='Mail areas setup'>
<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 block access to the area in a certain group for a node who has
access to the group you should use the Security flags and also set the correct
security flags for the node.
<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 max. articles
<li>Change bbs security
<li>Change link 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 this in the
message area groups. This has been changed since MBSE BBS version 0.33.19.
<P>
<A HREF="mail.html"><IMG SRC="../images/larrow.png" ALT="Back" Border="0">Back to Mail Setup</A>&nbsp;
<A HREF="./"><IMG SRC="../images/larrow.png" ALT="Back" Border="0">Back to index</A>&nbsp;
<A HREF="../"><IMG SRC="../images/b_arrow.png" ALT="Home" Border="0">Back to main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>

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

@@ -0,0 +1,70 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML>
<!-- $Id: emgroup.html,v 1.9 2006/03/27 20:41:29 mbse Exp $ -->
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META NAME="Language" content='en'>
<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>
<div align="right"><h5>Last update 27-Mar-2006</h5></div>
<div align="center"><H1>MBSE BBS Setup - Mail Setup - Message Groups.</H1></div>
<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. When you have defined a Areas
file and a message is received while you have no area for it, the area will be
created with the defaults that are set in the message area group. This will only
work if you receive a message from the uplink defined in this group, not from
any downlinks.
A note about the <b>Start at</b> area you can define, this may be higher then
your number of areas currently is. As soon as a area is created in this group
the areas database will be expanded so that it fits. Select these values
carefully, make sure you have room for all possible areas in that group and
skip a number of extra areas for future expansion.
<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>Base path </strong>The base for the JAM path without the area name.
<strong>Read sec </strong>The read security for bbs users for auto created areas.
<strong>Write sec </strong>The write security for bbs users for auto created areas.
<strong>Sysop sec </strong>The sysop security for bbs users for auto created areas.
<strong>Link sec </strong>The link security to copy to new created areas.
<strong>Start at </strong>Start area number (lowest) to create new areas.
<strong>Net reply </strong>Netmail reply board for auto created areas.
<strong>Users del </strong>User may delete for auto created areas.
<strong>Aliases </strong>Are aliases allowed in auto created areas.
<strong>Quotes </strong>Append a quote when user writes in auto created areas.
<strong>Active </strong>If this group is active.
<strong>Deleted </strong>If this group must be deleted.
<strong>Auto change </strong>Change areas when running <b>mbfido areas</b>.
<strong>User change </strong>Create/delete areas when users connect/disconnect.
<strong>Use Aka </strong>The Fidonet aka to use.
<strong>Uplink </strong>The Fidonet aka of your uplink.
<strong>Areas </strong>Areas file in the path defined in 1.4.6 screen 2.
<strong>Charset </strong>Default character set to use.
<strong>GoldED grp </strong>Groupnumber for GoldED include file.
</pre>
<P>
<IMG SRC="../images/emgroup.png" alt='Mail groups setup'>
<P>
<A HREF="mail.html"><IMG SRC="../images/larrow.png" ALT="Back" Border="0">Back to Mail Setup</A>&nbsp;
<A HREF="./"><IMG SRC="../images/larrow.png" ALT="Back" Border="0">Back to index</A>&nbsp;
<A HREF="../"><IMG SRC="../images/b_arrow.png" ALT="Home" Border="0">Back to main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>

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

@@ -0,0 +1,54 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML>
<!-- $Id: fdb.html,v 1.5 2004/03/08 22:25:22 mbroek Exp $ -->
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META NAME="Language" content='en'>
<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>
<div align='right'><h5>Last update 08-Mar-2004</h5></div>
<div align='center'><H1>MBSE BBS Setup - Files Database.</H1></div>
<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.
<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>TIC Area </strong>The name of the tic area the file was received in.
<strong>Magic </strong>The magic name to download/freq this file.
<strong>Uploader </strong>The name of the uploader.
<strong>Times DL </strong>The number of times downloaded from the BBS.
<strong>Password </strong>The password to access this file.
<strong>Deleted </strong>If this file should be deleted.
<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.png" alt='File database setup'>
<P>
<A HREF="./"><IMG SRC="../images/larrow.png" ALT="Back" Border="0">Back to index</A>&nbsp;
<A HREF="../"><IMG SRC="../images/b_arrow.png" ALT="Home" Border="0">Back to main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>

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

@@ -0,0 +1,81 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML>
<!-- $Id: fegroup.html,v 1.9 2004/03/08 22:25:22 mbroek Exp $ -->
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META NAME="Language" content='en'>
<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>
<div align="right"><h5>Last update 08-Mar-2003</h5></div>
<div align="center"><H1>MBSE BBS Setup - File Echo's Setup - File Groups.</H1></div>
<H3>Introduction.</H3>
<P>
File echo groups are to logically divide your file echo's for different
file distribution networks.
This screen also has a lot of fields that are needed for the auto area create.
When a new area is created a bbs download area is made and a new tic area record
is made.
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. If you are connected to the filegate then there is
one area file for all distribution groups. You must then create a file group for
each distribution group, ie. Fidonet, SDS etc. The name of that group must
exactly match the comment field in the group in this setup.
<P>&nbsp;<p>
<H3>File Group Setup.</H3>
<P>
<pre>
<strong>Name </strong>File Echo Group name.
<strong>Comment </strong>The description of that group.
<strong>Base path </strong>The base path for new created areas.
<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 ~/var/arealists).
<strong>Filegate </strong>Is area file in filegate.zxx format or not.
<strong>Banner </strong>Banner file to add to archives.
<strong>Convert </strong>Archiver to convert archive to.
<strong>BBS group </strong>BBS group name.
<strong>New group </strong>New files announce group.
<strong>Active </strong>If this group is active.
<strong>Deleted </strong>If this group must be deleted.
<strong>Start at </strong>New created areas must start at area nr.
<strong>Auto chng </strong>Auto change when running <b>mbfido areas</b>
<strong>User chng </strong>Auto create areas on downlinks requests.
<strong>Replace </strong>Set replace option in new areas.
<strong>Dupecheck </strong>Set Dupecheck option in new areas.
<strong>Secure </strong>Set secure option in new areas.
<strong>Touch </strong>Set Touch filedate option in new areas.
<strong>Virscan </strong>Set virus scanner option in new areas.
<strong>Announce </strong>Set announce files option in new areas.
<strong>Upd magic </strong>Set update magicname option in new areas.
<strong>File ID </strong>Set File ID option in new areas.
<strong>Conv. all </strong>Set convert all option in new areas.
<strong>Send orig </strong>Set send original option in new areas.
<strong>DL sec </strong>Set download security in new areas.
<strong>UP sec </strong>Set upload security in new areas.
<strong>LT sec </strong>Set list security in new areas.
<strong>Upl. area </strong>Set upload area number in new areas.
<strong>Link sec </strong>Set link security to copy to new areas.
</pre>
<p>
<img src="../images/fegroup.png" alt='File echo groups setup'>
<P>
<A HREF="tic.html"><IMG SRC="../images/larrow.png" ALT="Back" Border="0">Back to File Echo's Setup</A>&nbsp;
<A HREF="./"><IMG SRC="../images/larrow.png" ALT="Back" Border="0">Back to index</A>&nbsp;
<A HREF="../"><IMG SRC="../images/b_arrow.png" ALT="Home" Border="0">Back to main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>

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

@@ -0,0 +1,41 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML>
<!-- $Id: fidonet.html,v 1.4 2003/11/09 14:46:32 mbroek Exp $ -->
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META NAME="Language" content='en'>
<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>
<div align='right'><h5>Last update 29-Jan-2001</h5></div>
<div align='center'><H1>MBSE BBS Setup - fidonet Networks</H1></div>
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 not 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.png" alt='Fidonet networks setup'>
<p>
<A HREF="./"><IMG SRC="../images/larrow.png" ALT="Back" Border="0">Back to index</A>&nbsp;
<A HREF="../"><IMG SRC="../images/b_arrow.png" ALT="Home" Border="0">Back to main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>

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

@@ -0,0 +1,96 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML>
<!-- $Id: fileecho.html,v 1.8 2005/08/12 13:26:54 mbse Exp $ -->
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META NAME="Language" content='en'>
<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>
<div align="right"><h5>Last update 12-Aug-2005</h5></div>
<div align="center"><H1>MBSE BBS Setup - File Echo's Setup - TIC Areas.</H1></div>
<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>Security </strong>The security access flags for downlinks.
<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>Touch </strong>Touch rearchived files to the original date.
<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>New SR </strong>Give new node links the status SR instead of S.
<strong>Systems </strong>To the screen with connected systems.
</pre>
<P>
<IMG SRC="../images/fileecho.png" alt='TIC area setup'>
<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>Change security flags
<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>
<A HREF="tic.html"><IMG SRC="../images/larrow.png" ALT="Back" Border="0">Back to File Echo's Setup</A>&nbsp;
<A HREF="./"><IMG SRC="../images/larrow.png" ALT="Back" Border="0">Back to index</A>&nbsp;
<A HREF="../"><IMG SRC="../images/b_arrow.png" ALT="Home" Border="0">Back to main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>

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

@@ -0,0 +1,57 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML>
<!-- $Id: filefind.html,v 1.6 2007/03/05 12:25:19 mbse Exp $ -->
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META NAME="Language" content='en'>
<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>
<div align='right'><h5>Last update 05-Mar-2007</h5></div>
<div align='center'><H1>MBSE BBS Setup - Filefind Areas.</H1></div>
<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>The language to use for the reply.
<strong>Template </strong>The name of the macro template file.
<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>CHRS kludge </strong>The CHRS kludge and encoding to use.
<strong>Keywrd len </strong>The minimum keyword length allowed in search.
</pre>
<P>
<IMG SRC="../images/filefind.png" alt='Filefind setup'>
<P>
<A HREF="./"><IMG SRC="../images/larrow.png" ALT="Back" Border="0">Back to index</A>&nbsp;
<A HREF="../"><IMG SRC="../images/b_arrow.png" ALT="Home" Border="0">Back to main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>

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

@@ -0,0 +1,78 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML>
<!-- $Id: files.html,v 1.8 2005/08/11 21:10:03 mbse Exp $ -->
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META NAME="Language" content='en'>
<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>
<div align='right'><h5>Last update 11-Aug-2005</h5></div>
<div align='center'><H1>MBSE BBS Setup - BBS Setup - File Areas.</H1></div>
<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.
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>
If you change the path in an existing area, all files in that area are automatic
moved to the new location.
<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>Available </strong>If this area is available. If you make an available
area unavailable the area is checked if there are
downloadable files in that area. If so, you can't remove
the area. If there are none you will be asked if you are
sure. After the area is made unavailable, the record is
filled with reasonable default values.
<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>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>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.png" alt='File areas setup'>
<P>
<A HREF="bbs.html"><IMG SRC="../images/larrow.png" ALT="Back" Border="0">Back to BBS index</A>&nbsp;
<A HREF="./"><IMG SRC="../images/larrow.png" ALT="Back" Border="0">Back to index</A>&nbsp;
<A HREF="../"><IMG SRC="../images/b_arrow.png" ALT="Home" Border="0">Back to main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>

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

@@ -0,0 +1,439 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML>
<!-- $Id: global.html,v 1.40 2007/03/01 19:12:55 mbse Exp $ -->
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META NAME="Language" content='en'>
<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>
<div align="right"><h5>Last update 01-Mar-2007</h5></div>
<div align="center"><H1>MBSE BBS Setup - Global Setup</H1></div>
In this setup you can edit all global settings for MBSE BBS. All sections will
be discussed below.
<P>
<h3>1.1. Fidonet Aka's.</h3>
<p>
Here you can enter 40 fidonet addresses. These are 5d addresses. Make sure you
group the different zone's together, strange things will happen if you don't
group them.
<p>
<h3>1.2. Edit Registration Info.</H3>
<P>
<pre>
<strong>BBS Name </strong>The name of your BBS
<strong>Maildomain </strong>Your internet mail domain name (or system host.domain.com
if you don't have a maildomain).
<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>OLR id </strong>The packet name for Offline mail downloads.
<strong>Comment </strong>A comment line for your BBS
<strong>Origin </strong>The default origin line for echomail
<strong>Newuser </strong>The default username &quot;bbs&quot; for new users.
<strong>My FQDN </strong>My real internet Full Qualified Domain Name.
</pre>
A note abou the last item, My FQDN. This <b>MUST</b> be the name that is
returned with <code>nslookup 1.2.3.4</code> (use your internet IP adress there)
if you have a fixed IP address. Systems that are on a dynamic IP address and use
some sort of dyndns service <b>may</b> put that dyndns FQDN in there. Using this will
cause the other system to do twice as much dns resolve actions, so use this only
when needed. Another note, what you put in here has nothing to do with mail or
mail domains, that needs to be in the second option of this screen. The My FQDN
field is used by the Internet BBS Chatserver (IBC) to allow bbs systems to build
a chat network.
<P>
<h3>1.3. 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>Debug logfile </strong>The name of the debug logfile
<strong>Mgr logfile </strong>The name of the area-/filemgr logfile
<strong>Default menu </strong>The name of the default main menu
<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.4. Edit Global Paths</H3>
<P>
<pre>
<strong>Home dirs </strong>The path to the users home directories
<strong>FTP base </strong>The FTP base path, ie. /opt/mbse/ftp/pub
<strong>Arealists </strong>The path where area lists and filebone lists are stored
<strong>Ext. edit </strong>The full path and filename to the external editor
<strong>Rules dir </strong>The path to the directory to store area rules
<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
<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>Out queue </strong>The outbound queue for temporary files
<strong>*.msgs </strong>A netmail directory from where *.msg mails are tossed
These are *.msg files can be created by several doors. (Not in use yet)
<strong>Bad TIC's </strong>Where bad TIC files are saved
<strong>TIC queue </strong>Where TIC files for downlinks are kept
<strong>TMail DOS </strong>The T-Mail 8.3 (short) base path (empty = disable)
<strong>TMail Win </strong>The T-Mail long filename base path (empty = disable)
</pre>
If you fill in the DOS path then the DOS path and Unix path are translated
to DOS paths in the flo files for outbound mail sessions. You only need this if
another mailer uses the outbound that doesn't understand Unix paths.
The DOS path is a fake, but it must match the other mailer.
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.
<P>
<h3>1.5. 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 &lt;Enter&gt;
<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.
<strong>Simult. logins </strong>Maximum simultaneous logins allowed, 0 is unlimited, 1 is adviced.
<strong>Child priority </strong>Subproces nice priority, 0=high, 15=low CPU load.
<strong>Filesystem sync </strong>Call sync before and after execute.
<strong>Default language </strong>Default language (English).
</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, ext3, reiserfs, msdos and vfat partitions
are checked. The lowest free diskspace found counts. Default is 10 MB.
<p>
The Child priority sets the nice value for example zip/unzip, virus scanners
etc. Modern fast hardware will do fine with a low setting, older (pre PII)
hardware may need 15 to prevent a too heavy CPU load.
<p>
The filesystem sync setting is to call sync before and after the execute call,
such as when unzip is called. Almost all GNU/Linux systems need this because GNU/Linux
uses asynchronous directory changes. Since Linux 2.5.19 it should be possible to
mount filesystems synchronous. If this setting is No on asynchronous filesystems
mail and files can get corrupted. XxxxBSD systems use synchronous directory
updates and don't need this switch. If you don't know what all this is about,
leave this to the default setting.
<p>
Choice of default language. English is the best choice because that is the only
language that is complete in the default installation. In the user setup another
language may be used, the language set here is then used as a backup.
<p>
<h3>1.6. User flag Descriptions.</h3>
<p>
In this menu you can give the 32 users flags a meaningfull description.
<p>
<h3>1.7. 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 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>Ask user for his/her home address
<strong>Give email </strong>Give new users email access (default is yes)
<strong>Ask Screenlen </strong>Ask new users to set their screen length
<strong>Do newmail check </strong>Yes/No or Ask new user if for newmail check at logon
<strong>Do newfiles check </strong>Yes/No or Ask new user if for newfiles check at logon
</pre>
<p>
<h3>1.8. Text Colors.</h3>
<p>
Several prompts use different colors. They can be changed with the following
menu.
<P>
<IMG SRC="../images/mbsetup1.6.png" alt='Colors setup'>
<IMG SRC="../images/mbsetup1.6.S.png" alt='Colors setup'>
<P>
<h3>1.9. Sysop paging</h3>
<p>
For sysop chat a protocol is used to communicate with the mbtask daemon which
has a very simple IRC like chatserver. For sysop/user chat a forced channel
with the name #sysop is used.
<pre>
<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>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
</pre><p>
<h3>1.10. 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>Loc resp </strong>Respond to local created filefind messages
<strong>Plus all </strong>Allow filemgr +all command
<strong>Notify </strong>Allow filemgr notify=on/off command
<strong>Passwd </strong>Allow filemgr/areamgr 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>
When you change one of the <b>Allow filemgr</b> settings, you also need to edit
the file /opt/mbse/english/macro/filemgr.help to reflect the new settings.
Default all these switches are set to Yes.
<p>
<h3>1.11. 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 GNU/Linux and they
should run on all GNU/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)
<strong>Plus all </strong>Allow areamgr +all command
<strong>Notify </strong>Allow areamgr notify=on/off command
<strong>Passwd </strong>Allow areamgr/filemgr passwd command
<strong>Pause </strong>Allow areamgr pause/resume commands
</pre><p>
When you change one of the <b>Allow areamgr</b> settings, you also need to edit
the file /opt/mbse/english/macro/areamgr.help to reflect the new settings.
Default all these switches are set to Yes.
<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 newfiles reports
and gated news articles to Fidonet.
<P>
<h3>1.12. 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.12.11:
<ul>
<li><strong>No internet</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.n280.z2.fidonet.org</strong> Note, the username is their
Unix name when sending email.
<li><strong>No maildomain</strong>. If have internet but don't have your own
maildomain (most dialup systems) 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.n280.z2.fidonet.org</strong> Incoming email comes from
the default Fidonet UUCP gate.
Note, the username is their Unix name.
If you have your own maildomain, don't use this option, use the next option:
<li><strong>Own maildomain</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 have a dialup UUCP connection. Also
you can use this for dialup if you have your own maildomain without UUCP,
you will then fetch the mail from a multidrop mailbox (POP or IMAP) and
send the mail using SMTP via the SMTP mailer of your provider.<br>
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 and yourbbs.domain.org must be an existing internet domain.
</ul>
A 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>POP3 user@domain </strong>Use user@domain to login in the POP3 server
<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>Articles </strong>The default maximum newsarticles to fetch per group.
<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.13. Allfiles and Newfiles lists.</h3>
<p>
These are the settings that affect the generation of newfiles and allfiles reports.
<pre>
<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.14. 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. The setting of TCP/IP flags is important too, this
gives the information what this system will do. If you only enter IBN as TCP/IP
flags then the system will only call IBN nodes (binkp). The default is
XX,CM and TCP/IP systems (internet) should use the XX,CM,IBN,IFC flags.
If you cannot do TCP/IP connections, leave TCP/IP "phone" empty. The three
TCP/IP fields are used to give your system information via EMSI or binkp to
the other nodes.
<pre>
<strong>Mailer logl. </strong>The logging level for mailer sessions
<strong>TCP/IP "phone" </strong>The TCP/IP "phone" number (IP address or domain name)
<strong>TCP/IP flags </strong>The TCP/IP capability flags for TCP/IP sessions
<strong>TCP/IP speed </strong>The TCP/IP linespeed
<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 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 MD5 </strong>Disable binkp MD5 passwords
<strong>Zero Locks OK </strong>Allow zero byte lockfiles from another OS
<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.15. 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>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>Hist. limit </strong>Limit the number of mailhistory.html lines, 0 is unlimited.
</pre>
<P>
<h3>1.16. Manager flag Descriptions.</h3>
<p>
In this menu you can give the 32 area-/filemgr flags a meaningfull description.
<p>
<A HREF="./"><IMG SRC="../images/larrow.png" ALT="Back" Border="0">Back to index</A>
<A HREF="../"><IMG SRC="../images/b_arrow.png" ALT="Home" Border="0">Back to main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>

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

@@ -0,0 +1,65 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML>
<!-- $Id: hatch.html,v 1.5 2003/11/09 14:46:32 mbroek Exp $ -->
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META NAME="Language" content='en'>
<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>
<div align='right'><h5>Last update 10-May-2002</h5></div>
<div align='center'><H1>MBSE BBS Setup - File Echo's Setup - Hatch Manager.</H1></div>
<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>
The filenames to hatch may be long filenames as long as there are no spaces in
it. In the TIC file a short filename will be created for the old style tic
processors. The long filename is inserted in the TIC file as well. The short
filenames are created in the same way as windows does.
<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
upper or lowercase letters. Except for the "@" the test is
case sensitive.
<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.png" alt='Hatch manager setup'>
<P>
<A HREF="tic.html"><IMG SRC="../images/larrow.png" ALT="Back" Border="0">Back to File Echo's Setup</A>&nbsp;
<A HREF="./"><IMG SRC="../images/larrow.png" ALT="Back" Border="0">Back to index</A>&nbsp;
<A HREF="../"><IMG SRC="../images/b_arrow.png" ALT="Home" Border="0">Back to main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>

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

@@ -0,0 +1,79 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML>
<!-- $Id: index.htm,v 1.8 2007/03/01 19:12:56 mbse Exp $ -->
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META NAME="Language" content='en'>
<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>
<DIV align=right><h5>Last update 01-Mar-2007</h5></DIV>
<DIV align=center><h1>MBSE BBS Setup Guide</h1></DIV>
<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.png" alt='mbsetup'>
<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="oneliner.html">Edit Oneliners</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="route.html">Edit Routing Table</A>
<li><A HREF="chat.html">Edit Internet BBS Chat</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.png" ALT="Back" border="0">Back to index</A>
</BLOCKQUOTE>
</BODY>
</HTML>

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

@@ -0,0 +1,66 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML>
<!-- $Id: language.html,v 1.8 2007/02/17 12:14:19 mbse Exp $ -->
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META NAME="Language" content='en'>
<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>
<div align='right'><h5>Last update 17-Feb-2007</h5></div>
<div align='center'><H1>MBSE BBS Setup - BBS Setup - Language Setup.</H1></div>
<H3>Language introduction.</H3>
<P>
You need to define at least one language, this is the default language.
The ISO language code of the dfeault language needs to be the same as in the
global setup 1.5.24 and should be set to <b>en</b>.
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. It is therefore wise to name all menus, macro templates and
textfiles the same for all languages used.
When you setup the languages for the first time, entries for English, Dutch,
Spanish, Galego, German, French and Chinese languages are created.
<p>
And important note about the ISO code, don't change this. And if you do,
then you <em>must</em> change the directory name under <code>/opt/mbse/share/int</code>
to the same name as the code here. For example for the <b>en</b> code the system
expects the following paths and files:
<p>
<pre>
/opt/mbse/share/int/language.en
/opt/mbse/share/int/menus/en/*.mnu
/opt/mbse/share/int/txtfiles/en/*.ans
/opt/mbse/share/int/txtfiles/en/*.asc
/opt/mbse/share/int/macro/en/*
</pre>
<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>ISO code </strong>The 2 letter ISO code of the language.
<strong>Available </strong>If this language is available.
<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.png" alt='Language setup'>
<P>
<A HREF="bbs.html"><IMG SRC="../images/larrow.png" ALT="Back" Border="0">Back to BBS index</A>&nbsp;
<A HREF="./"><IMG SRC="../images/larrow.png" ALT="Back" Border="0">Back to index</A>&nbsp;
<A HREF="../"><IMG SRC="../images/b_arrow.png" ALT="Home" Border="0">Back to main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>

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

@@ -0,0 +1,76 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML>
<!-- $Id: magic.html,v 1.5 2003/11/09 14:46:32 mbroek Exp $ -->
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META NAME="Language" content='en'>
<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>
<div align='right'><h5>Last update 10-May-2002</h5></div>
<div align='center'><H1>MBSE BBS Setup - File Echo's Setup - Magics Files Setup.</H1></div>
<H3>Introduction.</H3>
<P>
Magics are special actions that you can perform on 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.
If you use the execute command, you can only execute commands that are in the
directory $MBSE_ROOT/bin, ie. /opt/mbse/bin.
<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 upper or lowercase letter.
Except for the "@" the test is case sensitive.
<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.png" alt='Magic setup'>
<P>
<A HREF="tic.html"><IMG SRC="../images/larrow.png" ALT="Back" Border="0">Back to File Echo's Setup</A>&nbsp;
<A HREF="./"><IMG SRC="../images/larrow.png" ALT="Back" Border="0">Back to index</A>&nbsp;
<A HREF="../"><IMG SRC="../images/b_arrow.png" ALT="Home" Border="0">Back to main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>

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

@@ -0,0 +1,34 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML>
<!-- $Id: mail.html,v 1.4 2003/11/09 14:46:32 mbroek Exp $ -->
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META NAME="Language" content='en'>
<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>
<div align='right'><h5>Last update 29-Jan-2001</h5></div>
<div align='center'><H1>MBSE BBS Setup - Mail Setup.</H1></div>
<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.png" ALT="Back" Border="0">Back to index</A>&nbsp;
<A HREF="../"><IMG SRC="../images/b_arrow.png" ALT="Home" Border="0">Back to main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>

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

@@ -0,0 +1,88 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML>
<!-- $Id: modems.html,v 1.4 2003/11/09 14:46:32 mbroek Exp $ -->
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META NAME="Language" content='en'>
<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>
<div align='right'><h5>Last update 29-Jan-2001</h5></div>
<div align='center'><H1>MBSE BBS Setup - Modem types</H1></div>
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 &amp;D2 or &amp;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.png" alt='Modems setup'>
<P>
<A HREF="./"><IMG SRC="../images/larrow.png" ALT="Back" Border="0">Back to index</A>&nbsp;
<A HREF="../"><IMG SRC="../images/b_arrow.png" ALT="Home" Border="0">Back to main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>

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

@@ -0,0 +1,53 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML>
<!-- $Id: newfiles.html,v 1.5 2007/03/05 12:25:20 mbse Exp $ -->
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META NAME="Language" content='en'>
<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>
<div align='right'><h5>Last update 05-Mar-2007</h5></div>
<div align='center'><H1>MBSE BBS Setup - Newfiles Reports.</H1></div>
<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>New groups </strong>The screen to define the groups to include.
<strong>CHRS kludge </strong>The CHRS kludge an encoding to use.
</pre>
<P>
<IMG SRC="../images/newfiles.png" alt='Newfiles reports'>
<P>
<A HREF="./"><IMG SRC="../images/larrow.png" ALT="Back" Border="0">Back to index</A>&nbsp;
<A HREF="../"><IMG SRC="../images/b_arrow.png" ALT="Home" Border="0">Back to main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>

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

@@ -0,0 +1,48 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML>
<!-- $Id: newgroups.html,v 1.4 2003/11/09 14:46:32 mbroek Exp $ -->
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META NAME="Language" content='en'>
<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>
<div align='right'><h5>Last update 30-Jan-2001</h5></div>
<div align='center'><H1>MBSE BBS Setup - Newfiles Groups.</H1></div>
<H3>Introduction</H3>
<P>
The newfiles groups 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.png" alt='Newfiles groups setup'>
<P>
<A HREF="./"><IMG SRC="../images/larrow.png" ALT="Back" Border="0">Back to index</A>&nbsp;
<A HREF="../"><IMG SRC="../images/b_arrow.png" ALT="Home" Border="0">Back to main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>

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

@@ -0,0 +1,415 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML>
<!-- $Id: nodes.html,v 1.23 2005/08/21 14:03:34 mbse Exp $ -->
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META NAME="Language" content='en'>
<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>
<div align=right><h5>Last update 21-Aug-2005</h5></div>
<div align=center><H1>MBSE BBS Setup - Fidonet nodes.</H1></div>
<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. There are ten
screens for each node.
<p>&nbsp;<p>
<H3>1. Edit general setup</H3>
<p>
This screen has the general information for the node. The contact info fields are
just for private use, these fields are only used in this screen. The Outbox dir is for
files to sent to the node, all file you put in there will be sent to the remote if
user mbse has read/write access to the file. Only real files are allowed, not symlinks etc.
<p><table>
<tr><th nowrap align=left valign=top>Sysop name</th><td>The name of the system
operator. The name entered here is used in Areamgr and Filemgr messages etc.</td></tr>
<tr><th nowrap align=left valign=top>Outbox dir</th><td>Private extra outbound
directory for this node. Any file dropped into this directory will be sent to
the node and removed after it is sent.</td></tr>
<tr><th nowrap align=left valign=top>Pvt. phone</th><td>Contact info, node private
phone.</td></tr>
<tr><th nowrap align=left valign=top>Pvt. fax</th><td>Contact info, node private
fax.</td></tr>
<tr><th nowrap align=left valign=top>Pvt. cellphone</th><td>Contact info, node
cellphone (GSM).</td></tr>
<tr><th nowrap align=left valign=top>Pvt. e-mail</th><td>Contact info, node e-mail
address.</td></tr>
<tr><th nowrap align=left valign=top>Pvt. remark</th><td>Contact info, node
remark.</td></tr>
<tr><th nowrap align=left valign=top>Route via</th><td>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. Note that to force calling this node
via internetr, ISDN or pots can also be done by using nodelist flags override. See
section 3. This setting is more usefull to force routing via another node or
aka.</td></tr>
<tr><th nowrap align=left valign=top>Netmail direct</th><td>Set "direct" flag in
netmail to this node.</td></tr>
<tr><th nowrap align=left valign=top>Netmail crash</th><td>Send netmail always "crash"
to this node.</td></tr>
<tr><th nowrap align=left valign=top>Netmail hold</th><td>Put mail on "hold" for this
node.</td></tr>
<tr><th nowrap align=left valign=top>Pack mail</th><td>Should net- and echomail be packed in
arcmail archives.</td></tr>
<tr><th nowrap align=left valign=top>Send notify</th><td>Send automatic generated
notify messages.</td></tr>
<tr><th nowrap align=left valign=top>Language</th><td>The language to use for areamgr
msgs.</td></tr>
<tr><th nowrap align=left valign=top>Deleted</th><td>If this node must be
deleted.</td></tr>
</table>
<P>
<IMG SRC="../images/nodes1.png" alt='Nodes setup'>
<P>&nbsp;<p>
<H3>2. Edit nodes aka's</H3>
<p>
In this screen you can setup 20 aka's for the node.
<p>
<IMG SRC="../images/nodes2.png" alt="Nodes aka's setup">
<P>&nbsp;<p>
<H3>3. Edit node session</H3>
<p>
In this screen you can setup the session defaults.
<p><table>
<tr><th nowrap align=left valign=top>Session passwd</th><td>This is the mailer
session password.</td></tr>
<tr><th nowrap align=left valign=top>Dial command</th><td>You can put an
override here for the normal dial command. If you leave this empty the command
from the modem setup is used.</td></tr>
<tr><th nowrap align=left valign=top>Phone number 1</th><td>An alternative phone
number to dial.</td></tr>
<tr><th nowrap align=left valign=top>Phone number 2</th><td>An alternative phone
number to dial. Use these above commands if the node has another
phone number as mentioned in the nodelist.</td></tr>
<tr><th nowrap align=left valign=top>Nodelist flags</th><td>Override for the
nodelist flags, the nodelist flags are completly ignored if you enter something
here so make sure all flags you need are here. All aka's of this node will use
the same flags. This can be usefull to force calling this node via the
internet and to force a certain protocol.</td></tr>
<tr><th nowrap align=left valign=top>Inet hostname</th><td>The FQDN hostname or
IP address of this node. This replaces the original system name from the
nodelist and this is then used to make the internet TCP/IP connection. This can
be usefull if the FQDN is not present in the nodelist.</td></tr>
<tr><th nowrap align=left valign=top>Outbound sess.</th><td>Outbound session
method, choices are <b>Direct</b> and <b>Directory</b>. Direct means normal
classic mailer connections. Directory means that everything is put in a
directory from which the other node can fetch the mail and files using ftp
protocol.</td></tr>
<tr><th nowrap align=left valign=top>Inbound sess.</th><td>Inbound session
method, choices are <b>Direct</b> and <b>Directory</b>. Direct means normal
classic mailer connections. Directory means that inbound mail and files are
expected in a directory were it is stored by the node using ftp
protocol.</td></tr>
<tr><th nowrap align=left valign=top>No EMSI</th><td>Disable EMSI
handshake.</td></tr>
<tr><th nowrap align=left valign=top>No YooHoo/2U2</th><td>Disable FTSC-0006
handshake.</td></tr>
<tr><th nowrap align=left valign=top>No Filerequest</th><td>Disable filerequest
from this node.</td></tr>
<tr><th nowrap align=left valign=top>Don't call</th><td>Do not call this
node.</td></tr>
<tr><th nowrap align=left valign=top>8.3 names</th><td>Set this if the node only
accepts 8.3 filenames.</td></tr>
<tr><th nowrap align=left valign=top>No PLZ</th><td>Disable PLZ compression on
outgoing calls with the binkp protocol.</td></tr>
<tr><th nowrap align=left valign=top>No GZ/BZ2</th><td>Disable GZ and BZ2
compression on outgoing calls with the binkp protocol.</td></tr>
<tr><th nowrap align=left valign=top>No Zmodem</th><td>Disable Zmodem
protocol.</td></tr>
<tr><th nowrap align=left valign=top>No Zedzap</th><td>Disable Zedzap
protocol.</td></tr>
<tr><th nowrap align=left valign=top>No Hydra</th><td>Disable Hydra
protocol.</td></tr>
<tr><th nowrap align=left valign=top>Binkp CRC32</th><td>Enable CRC32 file
transfer checks.</td></tr>
<tr><th nowrap align=left valign=top>Binkp old esc</th><td>Some systems followed
the wrong character escape method as published in FSP-1011 revision 3. For these
systems turn this flag on or you won't be able to send long filenames with
spaces in the name or other special characters. Such known systems are Argus and
Irex upto 2.29. Others may exist, even some older mbse versions.
<tr><th nowrap align=left valign=top>No binkp/1.1</th><td>Irex from version 2.24
at least upto 2.29 have a buggy binkp/1.1 implementation. Set this to Yes for
nodes that use one of these Irex versions and the binkp session will fall back
to the binkp/1.0 protocol.</td></tr>
<tr><th nowrap align=left valign=top>Ign. Hold</th><td>Ignore the nodelist flags
Hold or Down. Set this only if you want to call a node that is Down or Hold and
you know that you can connect it.</td></tr>
</table>
<p>
<IMG SRC="../images/nodes3.png" alt="Nodes session setup">
<P>&nbsp;<p>
<H3>4. Edit node - mail processing</H3>
<P>
<p><table>
<tr><th nowrap align=left valign=top>PKT password</th><td>The password to insert
in .pkt files.</td></tr>
<tr><th nowrap align=left valign=top>Check PKT pwd</th><td>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</td></tr>
<tr><th nowrap align=left valign=top>Mail forward</th><td>Not in use
yet.</td></tr>
<tr><th nowrap align=left valign=top>ARCmail comp.</th><td>Use ARCmail 0.60 file
naming convention for out of zone mail.</td></tr>
<tr><th nowrap align=left valign=top>ARCmail a..z</th><td>Allow a..z last
character for ARCmail filenames.</td></tr>
</table>
<P>
<IMG SRC="../images/nodes4.png" alt='Nodes mail setup'>
<P>&nbsp;<p>
<H3>5. Edit 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/nodes5.png" alt='Nodes mail groups'>
<P>&nbsp;<p>
<H3>6. File setup</H3>
<P>
<p><table>
<tr><th nowrap align=left valign=top>Files password</th><td>The password for
.tic files.</td></tr>
<tr><th nowrap align=left valign=top>Incl. message</th><td>Send a netmail
message for each file to send.</td></tr>
<tr><th nowrap align=left valign=top>Send TIC file</th><td>Send .tic file to
this node.</td></tr>
<tr><th nowrap align=left valign=top>Advanced TIC</th><td>Send advanced or
standard .tic files.</td></tr>
<tr><th nowrap align=left valign=top>Advanced SB</th><td>Send advanced Seen-By
lines, some systems can't handle this!</td></tr>
<tr><th nowrap align=left valign=top>To line in TIC</th><td>Send the To line in
the ticfile. Some braindead systems will forward this line instead of processing
it and then the next system in the line will fail.</td></tr>
<tr><th nowrap align=left valign=top>File forward</th><td>Forward TIC files for
this node (not yet).</td></tr>
</table>
<P>
<IMG SRC="../images/nodes6.png" alt='Nodes files setup'>
<P>&nbsp;<p>
<H3>7. File groups</H3>
<P>
The same story as for mail groups is true for the file groups.
<P>
<IMG SRC="../images/nodes7.png" alt='Nodes files groups'>
<P>&nbsp;<p>
<H3>8. Directory session</H3>
<P>
Setup in this screen is needed if you selected Inbound and or Outbound session
as Directory session. The node is then getting and bringing mail using the ftp
protocol and no normal mailer connects are being used anymore.
This may be a good solution for points, they only need a simple mailreader and a
tosser. The mail is transferred by the <b>mbfido</b> program, during the toss or
tic command after the normal inbound is processed <b>mbfido</b> will look for nodes inbound
directories to process. When mail is added to the outbound, mail for nodes with
directory sessions is not stored in the normal Binley Style Outbound but in the
session outbound directory.<br>
You need to setup a ftp account for this node and the best thing is to
set this up so that the other node is forced in a chroot environment, ie. make
it so that the node only sees his own directories and cannot leave that. The ftp
account needs to be a member of group bbs because mbfido needs access to the
files as well as the node. The nodes account needs also to be a member of group
bbsftp for the chroot environment.
The node needs umask 002 so that files that he puts
there will have group read/write access. During toss mbfido also stores the
files with group read/write access so that the node can remove the files when he
has fetched all files. Directory locking is supported and is compatible with
other mailers that support ftp. Here is a small sample of protftp.conf for use
with directory sessions:
<pre>
# This is /etc/proftpd.conf for use with mbsebbs ftp mail
# sessions and anonymous ftp access.
# It assumes that you have a user/group "nobody" and "ftp"
# for normal/anonymous operation.
# It also assumes you have a group bbsftp were ftp mail users
# must be a member of.
#
ServerName "Seaport ProFTPD server"
ServerType inetd
DefaultServer on
#
# Port 21 is the standard FTP port.
Port 21
# Umask 002 is to force new dirs and files to be group writable.
Umask 002
#
# To prevent DoS attacks, set the maximum number of child processes
# to 30.
MaxInstances 30
#
# Set the user and group that the server normally runs at.
User nobody
Group nogroup
#
SystemLog /var/log/proftpd
TransferLog /var/log/xferlog
#
# Anonymous ftp and members of group bbsftp have a chroot environment.
DefaultRoot ~ bbsftp
#
# Normally, we want files to be overwriteable.
&lt;Directory /*&gt;
AllowOverwrite on
&lt;/Directory&gt;
#
# A basic anonymous FTP server configuration.
# To enable this, remove the user ftp from /etc/ftpusers.
&lt;Anonymous ~ftp&gt;
RequireValidShell off
User ftp
Group ftp
# We want clients to be able to login with "anonymous" as well as "ftp"
UserAlias anonymous ftp
#
# Limit the maximum number of anonymous logins
MaxClients 50
#
# We want 'welcome.msg' displayed at login, and '.message' displayed
# in each newly chdired directory.
DisplayLogin welcome.msg
DisplayFirstChDir .welcome
DisplayReadme README
#
# Display .dotfiles and .dirs
LsDefaultOptions "-a"
#
# Limit WRITE everywhere in the anonymous chroot
&lt;Limit WRITE&gt;
DenyAll
&lt;/Limit&gt;
#
# An upload directory that allows storing files but not retrieving
# or creating directories.
&lt;Directory incoming/*&gt;
&lt;Limit READ&gt;
DenyAll
&lt;/Limit&gt;
&lt;Limit STOR&gt;
AllowAll
&lt;/Limit&gt;
&lt;/Directory&gt;
#
&lt;/Anonymous&gt;
</pre>
Here are some examples to create an account, first create the extra group
bbsftp:
<pre>
groupadd bbsftp
</pre>
Then create accounts like this:
<pre>
useradd -g bbs -G bbsftp -d /opt/mbse/var/bbsftp/irex -s /bin/bash -c "FTP Mail account" irex
</pre>
Then give the node a password for the ftp login. Note that this account has a
shell, proftpd needs a valid shell to allow access. If the node tries to telnet
to your bbs he can't login with this account if you use <b>mblogin</b>, this is
because the node is not in the bbs userfile. If you system allows it, the node
can access the shell using rlogin or ssh.<br>
Now the items to setup for the directory sessions:
<p><table>
<tr><th nowrap align=left valign=top colspan=2>Outbound settings</th></tr>
<tr><th nowrap align=left valign=top>Files path</th><td>The path were to store
the outbound mail and files.</td></tr>
<tr><th nowrap align=left valign=top>Check for lock</th><td>If we need to check
for a lockfile before adding files.</td></tr>
<tr><th nowrap align=left valign=top>Wait clear lock</th><td>Wait for the lock
to clear if present or not. If set to yes and there is a lock created by the
node then mbfido will wait for maximum 10 minutes for the lock to disappear. If
set to no, mbfido skips this node and will add mail and files at a later time.
<tr><th nowrap align=left valign=top>Check lockfile</th><td>The full filename
and path of the lockfile to check for.</td></tr>
<tr><th nowrap align=left valign=top>Create lock</th><td>If mbfido should create
a lock during the time it will add mail and files.</td></tr>
<tr><th nowrap align=left valign=top>Create lockfile</th><td>The full filename
and path of the lockfile to create.</td></tr>
<tr><th nowrap align=left valign=top colspan=2>Inbound settings</th></tr>
<tr><th nowrap align=left valign=top>Files path</th><td>The path from were to
get the inbound mail and files.</td></tr>
<tr><th nowrap align=left valign=top>Check for lock</th><td>If we need to check
for a lockfile before getting files.</td></tr>
<tr><th nowrap align=left valign=top>Wait clear lock</th><td>Wait for the lock
to clear if present or not. If set to yes and there is a lock created by the
node then mbfido will wait for maximum 10 minutes for the lock to disappear. If
set to no, mbfido skips this node and will scan this directory at a later time.
<tr><th nowrap align=left valign=top>Check lockfile</th><td>The full filename
and path of the lockfile to check for.</td></tr>
<tr><th nowrap align=left valign=top>Create lock</th><td>If mbfido should create
a lock during the time it will get mail and files.</td></tr>
<tr><th nowrap align=left valign=top>Create lockfile</th><td>The full filename
and path of the lockfile to create.</td></tr>
</table>
<P>
<IMG SRC="../images/nodes8.png" alt='Nodes directory setup'>
<P>&nbsp;<P>
<H3>9. Security</H3>
<P>
This will set the security bits for the node. These bits can be used to give
access or deny access to certain echomail areas or tic file areas. Default bit 1
is set for each node.
<P>
<IMG SRC="../images/nodes9.png" alt='Nodes security setup'>
<P>
<H3>10. Area and File managers</H3>
<P>
This screen sets names and passwords of the uplink managers, also our own
password is set here.
<p><table>
<tr><th nowrap align=left valign=top>Uplink AreaMgr program</th><td>The name of the
Areamgr program of this node. This could be AreaFix, AreaMgr etc.</td></tr>
<tr><th nowrap align=left valign=top>Uplink AreaMgr passowrd</th><td>The password for the
Areamgr of this node.</td></tr>
<tr><th nowrap align=left valign=top>Uplink AreaMgr is BBBS</th><td>If the uplink uses BBBS software set this
to Yes.</td></tr>
<tr><th nowrap align=left valign=top>Uplink FilMgr program</th><td>The name of the
Filemgr progrom of this node. This could be FileMgr, Allfix, Raid etc.</td></tr>
<tr><th nowrap align=left valign=top>Uplink FileMgr password</th><td>The password of the
Filemgr if this node.</td></tr>
<tr><th nowrap align=left valign=top>Uplink FileMgr is BBBS</th><td>If the plink
uses BBBS set this to Yes.</td></tr>
<tr><th nowrap align=left valign=top>Our Area/Filemgr passwd</th><td>Our own
Area/Filemgr password for this node to send to our node.</td></tr>
</table>
<P>
<IMG SRC="../images/nodes10.png" alt="Nodes managers setup">
<P>
<H3>11. 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/nodes11.png" alt='Nodes statistics'>
<P>
<A HREF="./"><IMG SRC="../images/larrow.png" ALT="Back" Border="0">Back to index</A>&nbsp;
<A HREF="../"><IMG SRC="../images/b_arrow.png" ALT="Home" Border="0">Back to main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>

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

@@ -0,0 +1,36 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML>
<!-- $Id: oneliner.html,v 1.4 2003/11/09 14:46:32 mbroek Exp $ -->
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META NAME="Language" content='en'>
<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>
<div align='right'><h5>Last update 29-Jan-2001</h5></div>
<div align='center'><H1>MBSE BBS Setup - BBS Setup - Oneliners.</H1></div>
<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.png" alt='oneliners setup'>
<P>
<A HREF="bbs.html"><IMG SRC="../images/larrow.png" ALT="Back" Border="0">Back to BBS index</A>&nbsp;
<A HREF="./"><IMG SRC="../images/larrow.png" ALT="Back" Border="0">Back to index</A>&nbsp;
<A HREF="../"><IMG SRC="../images/b_arrow.png" ALT="Home" Border="0">Back to main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>

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

@@ -0,0 +1,75 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML>
<!-- $Id: protocol.html,v 1.6 2004/11/28 15:19:26 mbse Exp $ -->
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META NAME="Language" content='en'>
<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>
<div align='right'><h5>Last update 28-Nov-2004</h5></div>
<div align='center'><H1>MBSE BBS Setup - BBS Setup - File Transfer Protocols.</H1></div>
<H3>Introduction.</H3>
<p>
MBSE BBS has Xmodem, Ymodem, Ymodem-1K, Ymodem-G, Zmodem and Zmodem-8K (aka
ZedZap) build in. In addition some external protocols are added to the setup but
they are disabled by default. When the bbs is started the first time, a set of
default protocols is created. The code used is based on the code from lrzsz
package wich is based in the original code written by Chuck Forsberg.
<p>
Ymodem is receiver driven. That means if the user has selected plain Ymodem at
the bbs and
his local client is using Ymodem-G and when the user starts a download, the files are
sent with Ymodem-G and not with plain Ymodem. With the same configuation an
upload will be sent with plain Ymodem. With downloads, the Ymodem at the bbs
will use what the client wants: 128 or 1K data blocks, crc of checksum, normal or
streaming Ymodem-G.
<p>
Zmodem is transmitter driven. That means if the user has selected Zmodem-8K at
the bbs and his local client is using normal Zmodem and when the user starts a
download, the download is sent with Zmodem-8K. With the same configuration an
upload will be sent with plain Zmodem. With uploads, the Zmodem at the bbs
doesn't care what is being used, it will adapt to the client program.
<p>
These days (2004) nobody should use Xmodem anymore but when I wrote Ymodem you
also get Xmodem because they are the same. Only with Xmodem the user has to
type in the filename to both sides. If you enable it you are on your own and you
may need to change the sources to make it really work because I didn't add
typing in the filename at the bbs. Also, Xmodem is restricted to 8.3 filenames
and the bbs uses long filenames.
<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>Internal </strong>If this is internal or external protocol.
<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>
Some fields cannot be changed when this is an internal protocol, they are
hardcoded.
<P>
<IMG SRC="../images/protocol.png" alt='File transfer protocols'>
<P>
<A HREF="bbs.html"><IMG SRC="../images/larrow.png" ALT="Back" Border="0">Back to BBS index</A>&nbsp;
<A HREF="./"><IMG SRC="../images/larrow.png" ALT="Back" Border="0">Back to index</A>&nbsp;
<A HREF="../"><IMG SRC="../images/b_arrow.png" ALT="Home" Border="0">Back to main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>

71
html/setup/route.html Normal file
View File

@@ -0,0 +1,71 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML>
<!-- $Id: route.html,v 1.3 2003/11/09 14:46:32 mbroek Exp $ -->
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META NAME="Language" content='en'>
<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 Routing Table.</TITLE>
<LINK rel=stylesheet HREF="../manual.css">
</HEAD>
<BODY>
<BLOCKQUOTE>
<div align=right><h5>Last update 25-Oct-2001</h5></div>
<div align=center><H1>MBSE BBS Setup - Edit Routing Table.</H1></div>
<H3>Introduction.</H3>
<P>
First an important note: normal nodes, hubs and hosts should not need this to
setup. MBSE is smart enough to do normal netmail routing using the nodelist.
There are cases when you might need this, for example if you are a RC or if you
have special routing arrangements via internet nodes. Think at least twice
before adding entries here. You can always use the <b>mbfido test</b> command to
check if the standard routing is enough. You should also check to see what you have
done with <b>mbfido test</b> if the entries in this table do what you expect
them to do.
During route tests it is wise to temporary switch on extra debug logging
with mbsetup menu 1.5.16.17 and check the information in the logfile, there is a
lot of information about the descisions that are made.
<P>
When you edit a route table, the entries you add might not be in the right
order, this will be done after you leave the editor. Sorting is done in order of
zone, exact nodes first, then globals. If you end the routing table with a global
route, ie. to All zones, then the standard routing isn't used anymore and only
the table is consulted. This might not be needed, most likely is that you only
need to add the routes to the non-standard nodes. The table is processed from
the first entry to the last and stops when an entry matches. If there was no
match, the default routing will be used.
<P>&nbsp;<P>
<H3>Edit Routing Table.</H3>
<P>
When you open the table you see something like this:<P>
<IMG SRC="../images/route1.png" ALT="Routing table" Border="0">
<P>
The edit screen looks like this:<P>
<IMG SRC="../images/route2.png" ALT="Routing editor" Border="0">
<pre>
<strong>Mask </strong>The destination mask to test for.
<strong>Action </strong>Route to, Direct or Default.
<strong>Dest addr </strong>The destination node in case of Route to.
<strong>Active </strong>If this rule is active.
<strong>Deleted </strong>If this rule must be deleted.
</pre>
<P>
If the Action is <b>Route to</b> then all mail matching the Mask will be routed
to the node setup in Dest addr. This node must be present in your setup.
If the Mask is <b>Direct</b> then mail to node node(s) matching the Mask will be
sent direct, not routed. If the action is <b>Default</b> then the nodes matching
the Mask will use the standard default routing. More actions will be added
later.
<P>
<A HREF="./"><IMG SRC="../images/larrow.png" ALT="Back" Border="0">Back to index</A>&nbsp;
<A HREF="../"><IMG SRC="../images/b_arrow.png" ALT="Home" Border="0">Back to main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>

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

@@ -0,0 +1,57 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML>
<!-- $Id: security.html,v 1.5 2003/11/09 14:46:32 mbroek Exp $ -->
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META NAME="Language" content='en'>
<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>
<div align='right'><h5>Last update 09-Feb-2002</h5></div>
<div align='center'><H1>MBSE BBS Setup - BBS Setup - Security Limits.</H1></div>
<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.7.1,
and the sysop level as setup in 1.5.4 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. If set to zero, the user gets 24 hours a day.
<strong>Download Kb. </strong>Maximum Kilobytes download each day, zero is unlimited.
<strong>Download Files </strong>Maximum files to download each day, zero is unlimited.
<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>
So if you completly want to disable a users ratio's, set Maximum time, Download
Kb and Download files to zero. A users session is still limited to 24 hours.
<p>
<IMG SRC="../images/security.png" alt='Security setup'>
<P>
<A HREF="bbs.html"><IMG SRC="../images/larrow.png" ALT="Back" Border="0">Back to BBS index</A>&nbsp;
<A HREF="./"><IMG SRC="../images/larrow.png" ALT="Back" Border="0">Back to index</A>&nbsp;
<A HREF="../"><IMG SRC="../images/b_arrow.png" ALT="Home" Border="0">Back to main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>

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

@@ -0,0 +1,59 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML>
<!-- $Id: services.html,v 1.6 2003/11/09 14:46:32 mbroek Exp $ -->
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META NAME="Language" content='en'>
<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>
<div align='right'><h5>Last update 25-Oct-2001</h5></div>
<div align='center'><H1>MBSE BBS Setup - Edit Services.</H1></div>
<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 the <strong>listserv</strong>
account at your host.<br>
<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
mbtic FileMgr
raid FileMgr
</PRE>
Note: the UUCP services is needed if you are gating email!
<P>
<A HREF="./"><IMG SRC="../images/larrow.png" ALT="Back" Border="0">Back to index</A>&nbsp;
<A HREF="../"><IMG SRC="../images/b_arrow.png" ALT="Home" Border="0">Back to main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>

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

@@ -0,0 +1,36 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML>
<!-- $Id: sitedoc.html,v 1.5 2004/04/09 18:31:23 mbroek Exp $ -->
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META NAME="Language" content='en'>
<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>
<div align='right'><h5>Last update 09-Apr-2004</h5></div>
<div align='center'><H1>MBSE BBS Setup - Create Sitedocs.</H1></div>
<H3>Create Sitedocs</H3>
<P>
This option creates everal documents in the share/doc and share/doc/html
directories under the home directory of MBSE BBS. In the first directory is a
file called site.doc that is formatted to print. In the html directory are
a lot of html pages with cross reference links. Since these pages contain
confidentional information of your users and links, you should not make these
html pages public available, but you can browse these with a browser with open
file and point to /opt/mbse/share/html/index.html.
<P>
<A HREF="./"><IMG SRC="../images/larrow.png" ALT="Back" Border="0">Back to index</A>&nbsp;
<A HREF="../"><IMG SRC="../images/b_arrow.png" ALT="Home" Border="0">Back to main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>

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

@@ -0,0 +1,30 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML>
<!-- $Id: softinfo.html,v 1.4 2003/11/09 14:46:32 mbroek Exp $ -->
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META NAME="Language" content='en'>
<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>
<div align='right'><h5>Last update 30-Jan-2001</h5></div>
<div align='center'><H1>MBSE BBS Setup - Show Software Information.</H1></div>
<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.png" ALT="Back" Border="0">Back to index</A>&nbsp;
<A HREF="../"><IMG SRC="../images/b_arrow.png" ALT="Home" Border="0">Back to main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>

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

@@ -0,0 +1,68 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML>
<!-- $Id: taskmgr.html,v 1.9 2004/05/19 20:46:12 mbse Exp $ -->
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META NAME="Language" content='en'>
<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>
<div align='right'><h5>Last update 19-May-2004</h5></div>
<div align='center'><H1>MBSE BBS Setup - Task Manager.</H1></div>
<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. It also watches the outbound to see if there are
nodes to call.
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>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>Max TCP </b>Maximum simultaneous outgoing calls over the internet.
<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.
</pre>
<P>
Default are the original MBSE commands filled in, but you could also call
shell scripts.
<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. The
status of the internet connection is used to decide if it is allowed (and
possible) to call TCP/IP nodes. Calling these nodes is not depending on ZMH
unless the destination is not a CM node.<br>
The <b>max load</b> setting decides at which system load point processing of background
tasks will be suspended. The default value should be allright for machines slower then 200
MHz or with low ram. On faster machines you may set this value higher.
<P>
<IMG SRC="../images/taskmgr.png" Border="0" alt='Taskmanager setup'>
<P>
<A HREF="./"><IMG SRC="../images/larrow.png" ALT="Back" Border="0">Back to index</A>&nbsp;
<A HREF="../"><IMG SRC="../images/b_arrow.png" ALT="Home" Border="0">Back to main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>

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

@@ -0,0 +1,36 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML>
<!-- $Id: tic.html,v 1.4 2003/11/09 14:46:32 mbroek Exp $ -->
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META NAME="Language" content='en'>
<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>
<div align='right'><h5>Last update 29-Jan-2001</h5></div>
<div align='center'><H1>MBSE BBS Setup - File Echo's Setup.</H1></div>
<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.png" ALT="Back" Border="0">Back to index</A>&nbsp;
<A HREF="../"><IMG SRC="../images/b_arrow.png" ALT="Home" Border="0">Back to main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>

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

@@ -0,0 +1,68 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML>
<!-- $Id: ttyinfo.html,v 1.6 2005/10/08 19:16:27 mbse Exp $ -->
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META NAME="Language" content='en'>
<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>
<div align='right'><h5>Last update 08-Oct-2005</h5></div>
<div align='center'><H1>MBSE BBS Setup - TTY Lines.</H1></div>
<h3>Introduction.</H3>
<P>
For each modem or ISDN line your bbs has you must setup a tty line.
This also includes console lines (for local login). Since version 0.81.0
you don't need to setup network lines anymore, these are now buildin.
If a call comes in over a (modem or ISDN) tty you didn't define, that call is refused.
<p>
One thing about the portspeed, this is only needed for devices connected to
serial ports such as modems and external ISDN adapters.
For internal ISDN cards this should be set to zero. If you set it to some other value,
things still work 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>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.png" ALT="Overview of tty ports"><P>
<IMG SRC="../images/tty1.png" ALT="A analogue modem port at COM1"><P>
<IMG SRC="../images/tty2.png" ALT="A ISDN channel"><P>
<A HREF="./"><IMG SRC="../images/larrow.png" ALT="Back" Border="0">Back to index</A>&nbsp;
<A HREF="../"><IMG SRC="../images/b_arrow.png" ALT="Home" Border="0">Back to main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>

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

@@ -0,0 +1,106 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML>
<!-- $Id: users.html,v 1.9 2005/11/08 21:03:09 mbse Exp $ -->
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META NAME="Language" content='en'>
<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>
<div align='right'><h5>Last update 08-Nov-2005</h5></div>
<div align='center'><H1>MBSE BBS Setup - BBS Users.</H1></div>
<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 in the second screen.
<P>&nbsp;<P>
<H3>Edit User</H3>
<P>
<pre>
<strong>Full Name </strong>The full (Fidonet) name of the user.
<strong>Security </strong>The security level of the user.
<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>Displays the unix name of the user.
<strong>1st login </strong>Displays the date of the first login.
<strong>Last login </strong>Displays the date of the last login.
<strong>Pwdchange </strong>Displays the date of the last password change.
<strong>Credit </strong>The users credit.
<strong>Hidden </strong>If the user is hidden from listings etc.
<strong>Deleted </strong>User must be deleted.
<strong>No Kill </strong>User can never be deleted.
<strong>Comment </strong>The comment about this user.
<strong>Locked </strong>Locked out of the BBS.
<strong>Guest </strong>Is this a "guest" account on/off.
<strong>Ext Info </strong>Send ^aKLUDGES with BlueWave downloads.
<strong>Email </strong>If this user has an email address.
<strong>Calls </strong>Displays the number of calls.
<strong>Downlds </strong>Displays the number of downloads.
<strong>Down Kb </strong>Displays the number of Kilobytes downloaded.
<strong>Uploads </strong>Displays the number of uploads.
<strong>Upload Kb </strong>Displays the number of Kilobytes uploaded.
<strong>Posted </strong>Displays the number of messages posted.
<strong>Time left </strong>Show the time left in minuts and reset the time.
<strong>Screen 2 </strong>Go to next setup screen.
</pre>
Watch out when changing the unix userid of the user, you need to change the
system password file and the users home directory manually.
<P>
<IMG SRC="../images/users.png" alt='User editor'>
<P>
<H3>Edit User Private Settings</H3>
<P>
<pre>
<strong>Handle </strong>The nickname of the user.
<strong>Location </strong>The location of the user.
<strong>Address 1 </strong>The address of the user line 1.
<strong>Address 2 </strong>The address of the user line 2.
<strong>Address 3 </strong>The address of the user line 3.
<strong>Voicephone </strong>The voice phonenumber of the user.
<strong>dataphone </strong>The data phonenumber of the user.
<strong>Birthdate </strong>The birthdate of the user DD-MM-YYYY.
<strong>Password </strong>Change password for this user.
<strong>Sex </strong>Users sex, male or female.
<strong>Protocol </strong>The selected file transfer protocol.
<strong>Archiver </strong>The selected archiver.
<strong>Charset </strong>The users preffered character set.
<strong>Screenlen </strong>The length (lines) of the users screen.
<strong>Language </strong>The language the user uses.
<strong>Hotkeys </strong>Hotkeys on/off.
<strong>Color </strong>Color on/off.
<strong>Fs Chat </strong>Fullscreen Chat on/off.
<strong>Silent </strong>Do not disturb on/off.
<strong>CLS </strong>Sent clearscreen codes on/off.
<strong>More </strong>More prompt on/off.
<strong>Editor </strong>Select message editor.
<strong>MailScan </strong>Scan for new mail at logon on/off.
<strong>ShowNews </strong>Show "news" screens on/off.
<strong>NewFiles </strong>New files scan at logon on/off.
<strong>Emacs </strong>Use Emacs (or Wordstar) FS edit shortcut keys.
</pre>
<P>
<IMG SRC="../images/users2.png" alt='User editor'>
<P>
<A HREF="./"><IMG SRC="../images/larrow.png" ALT="Back" Border="0">Back to index</A>&nbsp;
<A HREF="../"><IMG SRC="../images/b_arrow.png" ALT="Home" Border="0">Back to main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>

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

@@ -0,0 +1,105 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML>
<!-- $Id: virscan.html,v 1.10 2008/02/17 21:51:44 mbse Exp $ -->
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META NAME="Language" content='en'>
<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>
<div align='right'><h5>Last update 17-Feb-2008</h5></div>
<div align='center'><H1>MBSE BBS Setup - virus scanners</H1></div>
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 GNU/Linux system is
relative safe, most of the files that you have available on your bbs
are DOS/Windows 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 GNU/Linux available. Default only four of them
are setup. You may consult <A HREF="http://www.openantivirus.org/">
http://www.openantivirus.org</A> for more scanners mentioned in a mini-FAQ
maintained by Rainer Link.
<p>
When you configured the sources and build mbse, the configure script searched
for excisting scanners. When mbsetup was run the first time, when mbtask was
started, the scanners found on your system are already configured with the
right paths and enabled.
<P>
The following scanners are default installed in the setup:
<p>
<UL>
<LI><b>NAI Virus Scan</b> (uvscan) for Unix (GNU/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.
<LI><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.
<LI><strong>F-PROT</strong> available from <A
HREF="http://www.frisk.is">http://www.frisk.is</A>. There is a free version for personal use.
<LI><strong>Clam AntiVirus</strong> is a GNU licensed virus scanner for Unix. It
is available from <A HREF="http://www.clamav.net">www.clamav.net</A>. It has one
slight disadvantage over other scanners (or just the opposite), when it tests a
file with the Eicar testvirus signature it will report that and triggers the
virus detection. This happens with NAI DAT files.
</UL>
<P>
As soon as you have made one 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>&nbsp;<p>
<H3>Stream scanners</H3>
<P>
A new feature is stream scanning. In this setup you need a virus scanner loaded as a daemon and it
must listen to a TCP/IP port to receive commands and data to scan. Currently this is only implemented
for ClamAV, but F-Prot may follow. First you need a machine where <b>clamd</b> is running, this
can be a remote machine but of course also the bbs machine itself. ClamAV needs to be configured
so that it listens to a TCP/IP port, and depending on other things on the local socket too.
Recent versions of ClamAV can do both together. Change your <code>/etc/clamav/clamd.conf</code> to
contain the following lines:
<pre>
# Path to a local socket file the daemon will listen on.
# Default: disabled (must be specified by a user)
LocalSocket /var/run/clamav/clamd
# Remove stale socket after unclean shutdown.
# Default: no
#FixStaleSocket yes
# TCP port address.
# Default: no
TCPSocket 3310
# TCP address.
# By default we bind to INADDR_ANY, probably not wise.
# Enable the following to provide some degree of protection
# from the outside world.
# Default: no
#TCPAddr 127.0.0.1
</pre>
I left the comment for the TCPaddr, but it's up to you to protect the clamd server. After you
restart <b>clamd</b> test the connection with <code>telnet host.where.clamd.runs 3310</code>,
type VERSION followed by a return and you should see the ClamAV version. If that works, you can enable
the ClamAV stream scanner in mbsetup and disable the old commandline scanner.<BR>
So why would you use this. It's about 10 times faster then the commandline scanner.
<P>
<A HREF="./"><IMG SRC="../images/larrow.png" ALT="Back" Border="0">Back to index</A>&nbsp;
<A HREF="../"><IMG SRC="../images/b_arrow.png" ALT="Home" Border="0">Back to main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>