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

Updated documentation

Browse Source
This commit is contained in:
Michiel Broek 2002-01-21 22:20:54 +00:00
parent 53f739639c
commit 6ebffc9d86
20 changed files with 935 additions and 1006 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
html/Makefile
View File

@ -6,7 +6,7 @@ include ../Makefile.global
H_BASE = basic.html date.html dist.html manual.css \
flow.html postfix.html gwnews.html index.htm ups.html \
install.html intergate.html intro.html invoking.html \
intergate.html intro.html invoking.html \
known_bugs.html mgetty.html routing.html nodelist.html
H_FTSC = ftsc/fsc-0039.html ftsc/fsc-0056.html ftsc/fsc-0087.html \
@ -63,10 +63,10 @@ H_PROGS = programs/import.html programs/mbchat.html \
programs/mbaff.html programs/mbdiff.html \
programs/mbindex.html programs/mbout.html \
programs/mbsetup.html programs/mbuseradd.html \
programs/mball.html programs/mbfbgen.html \
programs/mball.html \
programs/mblang.html programs/mbsebbs.html \
programs/mbstat.html programs/mbpasswd.html \
programs/mbtask.html programs/mbmail.html
programs/mbtask.html
H_SETUP = setup/archiver.html setup/index.htm setup/bbs.html \
setup/bbslist.html setup/language.html setup/oneliner.html \

63
html/basic.html
View File

@ -1,4 +1,5 @@
<HTML>
<!-- $Id$ -->
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
@ -118,11 +119,13 @@ easy to guess of course. The script will then continue again:
<li>The password will be removed from user <strong>bbs</strong> This action
will make changes in /etc/shadow (if you have that) otherwise in /etc/passwd.
On FreeBSD it uses other tools to modify the master database.
On NetBSD you have to do that manually, there are no tools to do that.
<li>If they don't exist in the file /etc/services the services fido, tfido
and binkp will be added.
and binkp will be added.
<li>If they don't exist in the file /etc/inetd.conf the internet protocols
for the mailer will be added. The <strong>inetd</strong> is restarted to
activate the changes.
activate the changes. If your distribution uses xinetd instead of inetd, an
include file for xinetd is added instead.
</ol>
<p>&nbsp;<p>
@ -132,6 +135,7 @@ The last screen of the script is about sanity checks. Perform those checks!
If something is wrong, now is the time to fix it. Don't panic and remember
the backups of the system files that are changed are in /etc with the
extension <strong>.mbse</strong> i.e: those were the original files.
The installation logfile is copied to /opt/mbse.
If everythings is allright, then remove the directory /tmp/mbsebbs-0.33.nn:
<pre>
cd /tmp
@ -142,7 +146,7 @@ rm -Rf mbsebbs-0.33.nn
<h3>Step 4: Install the basic packages.</h3>
<p>
Login as user <b>mbse</b>. Yes, very important, <b>login as user mbse</b>.
While in the home directory unpack the distribution archives:
While in mbse's home directory (/opt/mbse) unpack the distribution archives:
<pre>
tar xfvz /path/to/mbsebbs-0.33.nn.tar.gz
</pre>
@ -158,17 +162,23 @@ make install
exit
</pre>
The last part of the installation procedure shows you the location of the bbs
startup script that is added to your system. Because this is your first
time installation, example menus, textfiles and some databases are installed.
startup script that is added to your system. Remember this one for a moment.
Because this is your first
time installation, example menus and example textfiles are installed.
If they already exist on your systems (when you do an upgrade) they
will not be installed again.
<p>
Now you must start the <b>mbtask</b> daemon by hand by typing <b>/opt/mbse/bin/mbtask</b>.
Check the file <b>/opt/mbse/log/mbtask.log</b> for startup problems. You may notice that
the program <b>mbcico</b> is started everytime, this is not a problem, it simply doesn't work right
now because you haven't configured anything yet. The first time <b>mbtask</b> is
started on your system it will create a lot of new configuration files with
default settings.
Now start the bbs for the first time (still as root) by executing the startup
script you just saw on the screen followed by a space and the word <b>start</b>.
For example:
<pre>
/etc/rc.d/init.d/mbsed start
</pre>
This will start the <b>mbtask</b> daemon.
After that the bbs will be opened for use.
Check the file <b>/opt/mbse/log/mbtask.log</b> for startup problems.
The first time <b>mbtask</b> is started on your system it will create a
lot of new configuration files with default settings.
<p>&nbsp;<p>
<h3>Step 5: (RedHat) startup problems.</h3>
@ -182,13 +192,34 @@ that other new distributions also need the extra minus sign. If that's the
case, please let me know and tell me how I can test what version it is.
<p>&nbsp;<p>
<h3>Step 6: ready.</h3>
<h3>Step 6: Ready.</h3>
<p>
Now the basic environment is finished, the next thing is to <a href="install.html">install</a>
the scripts, examples and configuration.
Now you have shell scripts in ~/etc, most of them are called by cron, some
are called during system startup and shutdown. You also have some default
configuration files, these are ttyinfo, modems, fidonet networks. In the
default (english) directory you now have default menu datafiles and ansi
screens. These are copies of my test system so you have to edit them to
build your own bbs.<br>
Editing ansi screens can be done on a Linux system with
<strong>duhdraw</strong>,
this is available from 2:280/2802 as <strong>duhdraw.tgz</strong> (68 Kbytes).
The binaries are included in this archive, if you compile it yourself
it may give trouble so if the binaries work, use these.<br>
Another editor is available from
<A HREF="http://www.drastic.net/bmdraw/">http://www.drastic.net/bmdraw/</A>,
you can find the tar.gz file in <A
HREF="http://www.drastic.net/bmdraw/files/bmd022.tgz">
http://www.drastic.net/bmdraw/files/bmd022.tgz</A>, it's about 36 Kbytes.
This is also a thedraw clone for Linux. Note, at my system I needed to run it as
root.<br>
You may also want to edit ~/etc/header.txt and ~/etc/footer.txt, these
files are the top and bottom of the newfiles/allfiles listings.
<P>
Now the basic environment is finished, the next thing to do is
<a href="setup/index.htm">configure the bbs</a>.
<P>&nbsp;<P>
<a href="index.htm"><img SRC="images/b_arrow.gif" ALT="Back to Index" BORDER=0 width="33" height="35" ></a>
<a href="index.htm">Back to Index</a>
<a href="index.htm"><img SRC="images/b_arrow.gif" ALT="Back to Index" BORDER=0>Back to Index</a>
</blockquote>
</body>

23
html/dist.html
View File

@ -1,4 +1,5 @@
<HTML>
<!-- $Id$ -->
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
@ -11,7 +12,7 @@
</HEAD>
<BODY>
<BLOCKQUOTE>
<h5>Last update 29-Dec-2001</h5>
<h5>Last update 21-Jan-2002</h5>
<P>&nbsp;<P>
<H1>Unix Distributions.</H1>
@ -23,6 +24,8 @@ Linux is available in several distributions, they all have advantages and
disadvantages for bbs use. Which distribution to pick is very personal.
Since late 2001 a port to FreeBSD is available, from version 0.33.19 this
port is ready to use.
Since januari 2002 a port to NetBSD is available, this version is not ready for
use.<br>
You should also consider the fact if the bbs machine is the same machine on
which you do your daily work on or if you use a seperate system for the bbs.
I will describe the distributions below for use on dedicated bbs computers,
@ -40,17 +43,17 @@ setup for MBSE BBS like Zipslack. Not included is the mgetty package.
<P>
I write this as if these are the same which isn't true of course. From MBSE
BBS's point of view they are almost the same, so that's why I treat them as
the same distributions. For people with little Linux experience these
the same distributions. The E-Smith server and gateway based on Redhat is also
supported.
For people with little Linux experience these
distributions are a good choice if you can spare the diskspace. I haven't
found a simple dedicated setup for the bbs, so the safest way is to install
allmost everything, which is quite simple. This will cost you about 1200 Megs.
Maybe that someone more experienced with these distro's can give more details
on how to build a small server. Please note that from RedHat 6.1 and up the
startup script (/etc/rc.d/init.d/mbsed) is different than before. Maybe
this is needed for Mandrake 6.1 and up too.
on how to build a small server.
<P>&nbsp;<P>
<H3>SuSe</H3>
<H3>SuSE</H3>
<P>
Since SuSE 7.1 the setup scripts are working and tested. Older distro's
might work.
@ -73,6 +76,12 @@ precompiled mgetty packages may not always have Fidonet support compiled in.
You may need to build mgetty yourself if you have an older FreeBSD distribution.
<P>&nbsp;<P>
<H3>NetBSD</H3>
<P>
I use an old Sun Sparcstation 2 with NetBSD 1.5.2. This is more stable then
Linux on Sparc systems. This is still in test, info will follow later.
<P>&nbsp;<P>
<H3>Famous last words...</H3>
<P>
I don't have the diskspace for all kinds of Linux distributions to install
@ -81,7 +90,7 @@ installed. Also, I don't buy every new distro that's available. If you have
a problem with that, just send me the new distro on CD to test by snailmail.
<P>&nbsp;<P>
<A HREF="index.htm"><IMG SRC="images/b_arrow.gif" ALT="Back" border="0"> Go Back</A>
<A HREF="index.htm"><IMG SRC="images/b_arrow.gif" ALT="Back" border="0">Go Back</A>
</BODY>
</HTML>

18
html/flow.html
View File

@ -1,4 +1,5 @@
<HTML>
<!-- $Id$ -->
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
@ -11,7 +12,7 @@
</HEAD>
<BODY>
<BLOCKQUOTE>
<h5>Last update 29-Dec-2001</h5>
<h5>Last update 21-Jan-2002</h5>
<P>&nbsp;<P>
<H1>Running a BBS under Unix.</H1>
@ -75,12 +76,13 @@ the session is ended and mgetty takes over the line again.
Note that they never can get a Unix shell unless you install a <b>door</b>
in the bbs that calls a shell for them.
<P>
There are probably more accounts on your system that can callin, <b>mbse</b> is
such an account, this is the MBSE BBS maintenance account. This user will
get the shell prompt. Use good passwords for shell accounts, and never change
your setup so that the <b>root</b> user can directly login except from the console.
If you need root access, login as <b>mbse</b> and type <b>su</b> at the prompt to become
root. You might consider installing SSH on your system for remote maintenance.
Because for dialin with mgetty the mblogin program is used and not the normal
login program, only bbs users can login. All other users including <b>root</b> are
denied access.
You might consider installing SSH on your system for remote maintenance.
<p>
It is also possible to install the mblogin program as the login program for
telnet users if you are directly connected to the internet.
<P>&nbsp;<P>
<H3>A PPP call is detected.</H3>
@ -165,7 +167,7 @@ If you want to use X11 on your bbs, you need more ram and a faster CPU or a
separate machine via a lan and export the display to that machine.
<P>&nbsp;<P>
<A HREF="index.htm"><IMG SRC="images/b_arrow.gif" ALT="Back" Border="0" width="33" height="35"> Go Back</A>
<A HREF="index.htm"><IMG SRC="images/b_arrow.gif" ALT="Back" Border="0">Go Back</A>
</BLOCKQUOTE>
</BODY>
</HTML>

BIN
html/images/fdb.gif
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 8.2 KiB

After

Width:  |  Height:  |  Size: 9.9 KiB

6
html/index.htm
View File

@ -1,4 +1,5 @@
<HTML>
<!-- $Id$ -->
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
@ -15,7 +16,7 @@
<h1>MBSE BBS System Guide v0.33.19</h1>
<HR>
<h5>Last update 07-Jan-2002</h5><BR><P>
<h5>Last update 21-Jan-2002</h5><BR><P>
<h3><a NAME="top"></a>Introduction</h3>
@ -41,7 +42,6 @@
<li><a href="flow.html">Running a BBS under Linux</a></li>
<li><a href="dist.html">Which distribution to use</a></li>
<li><a href="basic.html">Basic installation MBSE BBS</a></li>
<li><a href="install.html">Finishing installation of MBSE BBS</a></li>
<li><a href="setup/index.htm">Configuring the bbs with mbsetup</a></li>
<ol>
<li><A HREF="setup/global.html">Edit Global configuration</a>
@ -96,13 +96,11 @@
<li><a href="programs/mbchat.html">mbchat, Sysop to user chat utility</a></li>
<li><a href="programs/mbcico.html">mbcico, The Fidonet mailer ala ifcico</a></li>
<li><a href="programs/mbdiff.html">mbdiff, Nodelist difference processor</a></li>
<li><a href="programs/mbfbgen.html">mbfbgen, FileBase generator utility</a></li>
<li><a href="programs/mbfido.html">mbfido, Fidonet mail and files procesor</a></li>
<li><a href="programs/mbfile.html">mbfile, Files database maintenance program</a></li>
<li><a href="programs/mbindex.html">mbindex, Nodelist index compiler</a></li>
<li><a href="programs/mblang.html">mblang, Language datafile compiler</a></li>
<li><a href="programs/mblogin.html">mblogin, Unix login replacement</a></li>
<li><a href="programs/mbmail.html">mbmail, Mail Transport Agent for email</a></li>
<li><a href="programs/mbmon.html">mbmon, The monitor program</a></li>
<li><a href="programs/mbmsg.html">mbmsg, The messagebase utility program</a></li>
<li><a href="programs/mbout.html">mbout, The mailer outbound program</a></li>

54
html/install.html
View File

@ -1,54 +0,0 @@
<HTML>
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META name="author" lang="en" content="Michiel Broek">
<META name="copyright" lang="en" content="Copyright Michiel Broek">
<META name="description" lang="en" content="MBSE BBS Manual">
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
<TITLE>Running a BBS under Linux.</TITLE>
<LINK rel=stylesheet HREF="manual.css">
</HEAD>
<BODY>
<BLOCKQUOTE>
<h5>Last update 03-Jul-2001</h5>
<P>&nbsp;<P>
<HTML>
<HEAD>
<TITLE>Installing the BBS.</TITLE>
</HEAD>
<h1 ALIGN="CENTER">Installing the BBS.</h1>
<h3>Installing the BBS.</h3>
<p>
Now you have shell scripts in ~/etc, most of them are called by cron, some
are called during system startup and shutdown. You also have some default
configuration files, these are ttyinfo, modems, fidonet networks. In the
default (english) directory you now have default menu datafiles and ansi
screens. These are copies of my test system so you have to edit them to
build your own bbs.<br>
Editing ansi screens can be done on a Linux system with <strong>duhdraw</strong>,
this is available from 2:280/2802 as <strong>duhdraw.tgz</strong> (68 Kbytes).
The binaries are included in this archive, if you compile it yourself
it may give trouble so if the binaries work, use these.<br>
Another editor is available from
<A HREF="http://www.drastic.net/bmdraw/">http://www.drastic.net/bmdraw/</A>,
you can find the tar.gz file in <A HREF="http://www.drastic.net/bmdraw/files/bmd022.tgz">
http://www.drastic.net/bmdraw/files/bmd022.tgz</A>, it's about 36 Kbytes.
This is also a thedraw clone for Linux. Note, at my system I needed to run it as root.<br>
You may also want to edit ~/etc/header.txt and ~/etc/footer.txt, these
files are the top and bottom of the newfiles/allfiles listings.
<p>
<h3>the next step.</h3>
<p>
The next step is the <a href="setup/index.htm">setup</a> of the bbs.
<P>
<A HREF="index.htm"><IMG SRC="images/b_arrow.gif" ALT="Back to Index" Border="0" width="33" height="35">Back to Index</A>
</blockquote>
</BODY>
</HTML>

12
html/intro.html
View File

@ -1,4 +1,5 @@
<HTML>
<!-- $Id$ -->
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
@ -11,20 +12,19 @@
</HEAD>
<BODY>
<BLOCKQUOTE>
<h5>Last update 28-Jan-2001</h5>
<h5>Last update 21-Jan-2002</h5>
<P>&nbsp;<P>
<H1>Introduction to MBSE BBS.</H1>
<P>
<H3>Distribution.</H3>
<P>
There are only five official distribution sites for the mbse bbs package. They are:
There are only four official distribution sites for the mbse bbs package. They are:
<OL>
<LI><A HREF="http://mbse.sourceforge.net">http://mbse.sourceforge.net</A> Primary site
<LI><A HREF="http://mbse.freezer-burn.org">http://mbse.freezer-burn.org</A> Mirror site
<LI><A HREF="http://www.telematique.org/mbse">http://www.telematique.org/mbse</A> Mirror site
<LI>fidonet node 2:280/2802 (+31-255-515973).
<LI>fidonet node 2:280/2801 (+31-255-533858).
<LI>fidonet node 2:280/2801 (+31-255-536577).
</OL>
If you find mbse bbs on another site it may be out of date. I have no control over these sites.
New versions of mbse bbs are announced in the fidonet area LINUX_BBS. On the official fidonet
@ -87,12 +87,12 @@ the date format.
<H3>Future plans.</H3>
<P>
Plans are to complete integrate news, email, www and chat into MBSE BBS. It
Plans are to completly integrate www and chat into MBSE BBS. It
should work for browsers about the same as with ANSI character terminals.
<P>&nbsp;<P>
<A HREF="index.htm"><IMG SRC="images/b_arrow.gif" ALT="Back" Border="0" width="33" height="35"> Go Back</A>
<A HREF="index.htm"><IMG SRC="images/b_arrow.gif" ALT="Back" Border="0">Go Back</A>
</BLOCKQUOTE>
</BODY>
</HTML>

9
html/known_bugs.html
View File

@ -1,4 +1,5 @@
<HTML>
<!-- $Id$ -->
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
@ -11,7 +12,7 @@
</HEAD>
<BODY>
<BLOCKQUOTE>
<h5>Last update 28-Jan-2001</h5>
<h5>Last update 21-Jan-2002</h5>
<P>&nbsp;<P>
<H1>MBSE BBS - Known bugs.</H1>
<P>
@ -20,18 +21,16 @@ There are always more bugs, but these are known....
<UL>
<LI>Reading of function keys in mbsebbs doesn't work always good, especially on
slow links and over PPP.
slow links and over PPP. This is not a MBSE BBS problem.
<LI>Memory leaks in mbfido during mailtoss.
<LI>Problems with D'Bridge [1a] mailers.
<LI>Sometimes binkp sessions hang on sending files during bidirectional transfers.
<LI>mbsetup crashes at several places if in system aka's the domain name is 12 characters long.
</UL>
<A HREF="index.htm"><IMG SRC="images/b_arrow.gif" ALT="Back" Border="0" width="33" height="35"> Go Back</A>
<A HREF="index.htm"><IMG SRC="images/b_arrow.gif" ALT="Back" Border="0">Go Back</A>
</BODY>
</HTML>

4
html/programs/index.htm
View File

@ -1,4 +1,5 @@
<HTML>
<!-- $Id$ -->
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
@ -11,7 +12,7 @@
</HEAD>
<BODY>
<BLOCKQUOTE>
<h5>Last update 07-Jan-2002</h5>
<h5>Last update 21-Jan-2002</h5>
<P>&nbsp;<P>
<h1>MBSE BBS Programs.</h1>
@ -24,7 +25,6 @@
<li><A HREF="mbchat.html">mbchat, Sysop to user chat utility</A>
<li><A HREF="mbcico.html">mbcico, The Fidonet mailer ala ifcico</A>
<li><A HREF="mbdiff.html">mbdiff, Nodelist difference processor</A>
<li><A HREF="mbfbgen.html">mbfbgen, FileBase Generator utility</A>
<li><A HREF="mbfido.html">mbfido, Fidonet mail and files procesor</A>
<li><A HREF="mbfile.html">mbfile, Files database maintenance program</A>
<li><A HREF="mbindex.html">mbindex, Nodelist index compiler</A>

485
html/programs/mbcico.html
View File

@ -1,222 +1,263 @@
<HTML>
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META name="author" lang="en" "content="Michiel Broek">
<META name="copyright" lang="en" content="Copyright Michiel Broek">
<META name="description" lang="en" content="MBSE BBS Manual">
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
<TITLE>MBSE BBS Programs - mbcico - The Fidonet mailer.</TITLE>
<LINK rel=stylesheet HREF="../manual.css">
</HEAD>
<BODY>
<BLOCKQUOTE>
<h5>Last update 30-Jan-2001</h5>
<P>&nbsp;<P>
<H1>mbcico - The Fidonet mailer.</H1>
<P>
This is work in progress....
<P>
<h3>Synopsis.</H3>
<P>
<code>-r&lt;role&gt; -a&lt;inetaddr&gt; &lt;node&gt; ...</code><br>
<code>-r 0|1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</code>1 - master, o - slave [0]<br>
<code>-n&lt;phone&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</code>forced phone number<br>
<code>-l&lt;ttydevice&gt;&nbsp;</code>forced tty device<br>
<code>-t&lt;tcpmode&gt;&nbsp;&nbsp;&nbsp;</code>telnet TCP/IP mode, must be one of ifc|itn|ibn, forces TCP/IP<br>
<code>-a&lt;inetaddr&gt;&nbsp;&nbsp;</code>supply internet hostname if not in nodelist<br>
<code> &lt;node&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</code>should be in domain form, e.g. f11.n22.z3
(this implies master mode)<br>
<code>-h&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</code>show this help message<br>
<br>
&nbsp;or: <code>mbcico tsync|yoohoo|**EMSI_INQC816|-t ibn|-t ifc|-t itn</code> (this implies slave mode)
<P>&nbsp;<P>
<H3>Description.</H3>
<P>
<strong>mbcico</strong> stands for MBse "Internet - Fidonet Copy In /Copy Out",
this is a FidoNet(r) compatible transport agent. It is based on <strong>
ifcico</strong> written by Eugene G. Crosser, &lt;crosser@average.org&gt;,
2:5020/230@FidoNet. I changed the name of the program to make the difference
between <strong>ifcico</strong> and <strong>mbcico</strong>. Nowadays it is
quite different then ifcico.
<P>
Currently it supports FTS-0001, YooHoo/2U2 and EMSI handshake protocols,
Xmodem, Telink, Modem7, Hydra, SEAlink with and without overdrive and
crash recovery, Bark file and update requests, WaZoo protocols: DietIFNA,
plain Zmodem (aka ZedZip, EMSI flag "ZMO") and ZedZap, WaZoo file and
update requests (nodelist flag should be XA). WaZoo file and update requests
do also work with FTS-0001 sessions, this is supported by several well known DOS
mailers also.
Password protected requests and update requests are implemented (but not
yet full tested).
<P>
There is also a special protocol optimized to use over TCP/IP connections,
contributed by Stanislav Voronyi &lt;stas@uanet.kharkov.ua&gt;, it is
identiefied by EMSI proto code TCP (not registered) and nodelist flag IFC.
The default port is 60179. There is a telnet variant on this, the default
port is 23, and nodelist flag is ITN. The telnet variant is written by
T. Tanaka.
<P>
There is also a <strong>Binkp</strong> implementation, this is a
bi-directional TCP/IP protocol.
This protocol is prefferred over the IFC protocol because it is
more efficient. Nodelist flag is IBN, the default port is 24554, and the
nodelist request flag is XX. This Binkp implementation supports multiple
batches, however this is only tested against another <strong>mbcico.</strong>
I don't know if any other mailer supports this option, but it is documented
in the spec's.
<P>
Outbound directory structure is BinkleyTerm compatible, with domains and
point subdirectories (full 5d). There are separate "protected" and
"unprotected" inbound directories for the incoming sessions with the nodes
that are in your setup. Files received during outbound sessions are always
stored in the "protected" inbound.
<P>
"Magic" file request processors are executable files placed in the "magic"
directory. If a request is made for a file with matching name, the
executable from the "magic" directory is run, and its stdout output is mailed
to the requestor. Full requestor's address, in the form of "John Smith of
1:234/56/7" is passed to the executable in the command line. Non-executable
files in the magic directory contain the full names to magic filenames. The
magic NODELIST can thus point to the full path and filename of your latest
nodelist. These magic names are automatic maintained by the <strong>mbfido</strong>
program when the magic name is set in the .tic file that you receive.
<P>
To run <strong>mbcico</strong> in master mode, you need to make dialout
devices read/writeable for <strong>mbcico</strong>, and do the same for
the directory where your uucp locks are created (usually /var/locks).
<P>&nbsp;<P>
<h3>Answer Mode.</h3>
<P>
To make <strong>mbcico</strong> work in answer mode, you need <strong>
mgetty</strong> written by Gert Doering. <strong>mbcico</strong> must be
started with one of the following parameters:
<P><PRE>
FTS-0001 call: "/opt/mbse/bin/mbcico tsync"
FTS-0006 call: "/opt/mbse/bin/mbcico yoohoo"
EMSI call: "/opt/mbse/bin/mbcico **EMSI_....."
</PRE><P>
In the latter case the received EMSI packet should be passed whitout trailing
CR). To make this work <strong>mgetty</strong> must be compiled with the
-DFIDO option. Other getty programs might work.
<P>
To answer TCP/IP calls the following lines should be added to /etc/inetd.conf:
<P><PRE>
binkd stream tcp nowait mbse /opt/mbse/bin/mbcico mbcico -t ibn
tfido stream tcp nowait mbse /opt/mbse/bin/mbcico mbcico -t itn
fido stream tcp nowait mbse /opt/mbse/bin/mbcico mbcico -t ifc
</PRE><P>
In the file /etc/services the following lines must be present:
<P><PRE>
binkd 24554/tcp # mbcico IBN mode
tfido 60177/tcp # mbcico ITN mode
fido 60179/tcp # mbcico IFC mode
mbse 60180/tcp # MBSE BBS deamon
</PRE><P>
In this case I installed the ITN mode at port 60177 instead of 23 like most
sysops do.
<P>&nbsp;<P>
<h3>Master Mode.</h3>
<P>
To make <strong>mbcico</strong> scan for pending outbound mail and do
appropriate calls, start it with <strong>-r1</strong> flag. It will check
for Zone Mail Hour, outside ZMH only crash mail is delivered. Mail to
non-CM systems is only send when mail has the Immedidate status.
Poll request are always honnored, even to non-CM systems if there is a
<strong>poll</strong> request in the outbound. Be carefull.
The taskmanager <strong>mbtask</strong> will start calling <strong>mbcico -r1</strong>
if it has seen the <b>scanout</b> semafore. After all calls are completed <b>mbcico</b>
will remove the <b>scanout</b> semafore.
During ZMH all non-compressed mail is send. File requests in the outbound do not
force calling a system. If you make a filerequest, you must also make a
poll for that node to really start the request. You can also force a call
by entering <strong>mbcico f2802.n280.z2</strong> on the commandline.
Only one call is made then and there is no dial delay. If <b>mbcico -r1</b> is
called a random dialdelay is used with each call except for internet calls.
<P>&nbsp;<P>
<h3>Environment.</H3>
<P>
In order to run the mbcico you need to set one global environment variable
<strong>$MBSE_ROOT</strong>
This variable must point to the root of the bbs directoy structure.
<P>&nbsp;<P>
<H3>Return Codes.</H3>
<P>
<pre>
0 - No errors
1..32 - Linux errors, SIGHUP, SIGKILL, etc.
101 - No dialout ports available.
102 - Dial failed (no CONNECT or TCP connection failed).
103 - Could not reset the modem (no OK).
104 - System is locked.
105 - not used?
106 - Nodelist lookup failed.
107 - Call prohibited by config options.
108 - Phone number unavailable.
109 - No matching ports defined.
110 - Tried to call a CM system outside ZMH.
111..129 - Session failures (not defined).
130 - Could not establish session, system is marked undialable.
</pre>
These codes are also stored in status files for nodes, with the extension
of ".sts". These are small datafiles containing three decimal numbers.
<ol>
<li>Time retry code, this is the last call attempt time. This is an unsigned
long representing the number of seconds since the epoch.
<li>Retries, this is the number of consequtive call attempts made that returned
"call failed" or other errors. This field is zeroed when the call succeeds and
when a new "poll" is created. If the value is 30, the node won't be called
anymore.
<li>Code, this is the return code of the last attempt.
</ol>
<p>&nbsp;<p>
<h3>Configuration.</H3>
<P>
The behaviour of mbcico can be configured with <strong>mbsetup</strong>,
section 1.16 If something doesn't do what you want, set the debug on for
that problem. This will produce huge logfiles, but also a lot of information.
Important flags are Device IO, EMSI debug, File forward, Locking, Outboundscan
and Session.
<P>&nbsp;<P>
<h3>Bugs.</H3>
<P>
Incoming calls from McMail mailers, McMail is quite hasty
to establish an EMSI session, and times out in less than a second. So
if your system is heavy loaded, or not too fast, McMail cannot connect
with your system. This is a known problem with McMail 1.0 and older,
later versions are ok.
<P>&nbsp;<P>
<H3>Authors.</H3>
<P>
<pre>
Eugene G. Crosser &lt;crosser@average.org&gt; Orginal ifcico.
Stanislav Voronyi &lt;stas@uanet.kharkov.ua&gt; TCP/IP code.
T. Tanaka Telnet mode.
Martin Junius Rewrite of opentcp().
Omen Technology Inc Zmodem protocol.
Arjen G. Lentz, Joaquim H. Homrighausen Hydra transfer protocol.
Cristof Meerwald Implementation of Hydra in ifcico.
P. Saratxaga Tty driver code, yoohoo extensions.
Dima Maloff Binkp protocol.
Michiel Broek Rewrite for MBSE BBS.
</pre>
<P>
<A HREF="index.htm"><IMG SRC="../images/larrow.gif" ALT="Index" Border="0" width="40" height="30"> Back to index</A>&nbsp;
<A HREF="../index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Main" Border="0" width="33" height="35"> Back to Main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>
<HTML>
<!-- $Id$ -->
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META name="author" lang="en" content="Michiel Broek">
<META name="copyright" lang="en" content="Copyright Michiel Broek">
<META name="description" lang="en" content="MBSE BBS Manual">
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
<TITLE>MBSE BBS Programs - mbcico - The Fidonet mailer.</TITLE>
<LINK rel=stylesheet HREF="../manual.css">
</HEAD>
<BODY>
<BLOCKQUOTE>
<h5>Last update 21-Jan-2002</h5>
<P>&nbsp;<P>
<H1>mbcico - The Fidonet mailer.</H1>
<P>
This is work in progress....
<P>
<h3>Synopsis.</H3>
<P>
<code>-r&lt;role&gt; -a&lt;inetaddr&gt; &lt;node&gt; ...</code><br>
<code>-r 0|1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</code>1 - master, o - slave [0]<br>
<code>-n&lt;phone&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</code>forced phone number<br>
<code>-l&lt;ttydevice&gt;&nbsp;</code>forced tty device<br>
<code>-t&lt;tcpmode&gt;&nbsp;&nbsp;&nbsp;</code>telnet TCP/IP mode, must be one of ifc|itn|ibn, forces TCP/IP<br>
<code>-a&lt;inetaddr&gt;&nbsp;&nbsp;</code>supply internet hostname if not in nodelist<br>
<code> &lt;node&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</code>should be in domain form, e.g. f11.n22.z3
(this implies master mode)<br>
<code>-h&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</code>show this help message<br>
<br>
&nbsp;or: <code>mbcico tsync|yoohoo|**EMSI_INQC816|-t ibn|-t ifc|-t itn</code> (this implies slave mode)
<P>&nbsp;<P>
<H3>Description.</H3>
<P>
<strong>mbcico</strong> stands for MBse "Internet - Fidonet Copy In /Copy Out",
this is a FidoNet(r) compatible transport agent. It is based on <strong>
ifcico</strong> written by Eugene G. Crosser, &lt;crosser@average.org&gt;,
2:5020/230@FidoNet. I changed the name of the program to make the difference
between <strong>ifcico</strong> and <strong>mbcico</strong>. Nowadays it is
quite different then ifcico.
<P>
Currently it supports FTS-0001, YooHoo/2U2 and EMSI handshake protocols,
Xmodem, Telink, Modem7, Hydra, SEAlink with and without overdrive and
crash recovery, Bark file and update requests, WaZoo protocols: DietIFNA,
plain Zmodem (aka ZedZip, EMSI flag "ZMO") and ZedZap, WaZoo file and
update requests (nodelist flag should be XA). WaZoo file and update requests
do also work with FTS-0001 sessions, this is supported by several well known DOS
mailers also.
Password protected requests and update requests are implemented (but not
yet full tested).
<P>
There is also a special protocol optimized to use over TCP/IP connections,
contributed by Stanislav Voronyi &lt;stas@uanet.kharkov.ua&gt;, it is
identiefied by EMSI proto code TCP (not registered) and nodelist flag IFC.
The default port is 60179. There is a telnet variant on this, the default
port is 23, and nodelist flag is ITN. The telnet variant is written by
T. Tanaka.
<P>
There is also a <strong>Binkp</strong> implementation, this is a
bi-directional TCP/IP protocol.
This protocol is prefferred over the IFC protocol because it is
more efficient. Nodelist flag is IBN, the default port is 24554, and the
nodelist request flag is XX. This Binkp implementation supports multiple
batches, however this is only tested against another <strong>mbcico.</strong>
I don't know if any other mailer supports this option, but it is documented
in the spec's.
<P>
Outbound directory structure is BinkleyTerm compatible, with domains and
point subdirectories (full 5d). There are separate "protected" and
"unprotected" inbound directories for the incoming sessions with the nodes
that are in your setup. Files received during outbound sessions are always
stored in the "protected" inbound.
<P>
"Magic" file request processors are executable files placed in the "magic"
directory. If a request is made for a file with matching name, the
executable from the "magic" directory is run, and its stdout output is mailed
to the requestor. Full requestor's address, in the form of "John Smith of
1:234/56/7" is passed to the executable in the command line. Non-executable
files in the magic directory contain the full names to magic filenames. The
magic NODELIST can thus point to the full path and filename of your latest
nodelist. These magic names are automatic maintained by the <strong>mbfido</strong>
program when the magic name is set in the .tic file that you receive.
<P>
To run <strong>mbcico</strong> in master mode, you need to make dialout
devices read/writeable for <strong>mbcico</strong>, and do the same for
the directory where your uucp locks are created (usually /var/locks).
<P>&nbsp;<P>
<h3>Answer Mode.</h3>
<P>
To make <strong>mbcico</strong> work in answer mode, you need <strong>
mgetty</strong> written by Gert Doering. <strong>mbcico</strong> must be
started with one of the following parameters:
<P><PRE>
FTS-0001 call: "/opt/mbse/bin/mbcico tsync"
FTS-0006 call: "/opt/mbse/bin/mbcico yoohoo"
EMSI call: "/opt/mbse/bin/mbcico **EMSI_....."
</PRE><P>
In the latter case the received EMSI packet should be passed whitout trailing
CR). To make this work <strong>mgetty</strong> must be compiled with the
-DFIDO option. Other getty programs might work.
<P>
To answer TCP/IP calls the following lines should be added to /etc/inetd.conf:
<P><PRE>
binkd stream tcp nowait mbse /opt/mbse/bin/mbcico mbcico -t ibn
tfido stream tcp nowait mbse /opt/mbse/bin/mbcico mbcico -t itn
fido stream tcp nowait mbse /opt/mbse/bin/mbcico mbcico -t ifc
</PRE><P>
If your system uses xinetd the file /etc/xinetd.d/mbsebbs could be:
<P><PRE>
#:MBSE BBS services are defined here.
service binkp
{
socket_type = stream
protocol = tcp
wait = no
user = mbse
instances = 10
server = /opt/mbse/bin/mbcico
server_args = -t ibn
}
service tfido
{
socket_type = stream
protocol = tcp
wait = no
user = mbse
instances = 10
server = /opt/mbse/bin/mbcico
server_args = -t itn
}
service fido
{
socket_type = stream
protocol = tcp
wait = no
user = mbse
instances = 10
server = /opt/mbse/bin/mbcico
server_args = -t ifc
}
</PRE><P>
In the file /etc/services the following lines must be present:
<P><PRE>
binkd 24554/tcp # mbcico IBN mode
tfido 60177/tcp # mbcico ITN mode
fido 60179/tcp # mbcico IFC mode
mbse 60180/tcp # MBSE BBS deamon
</PRE><P>
In this case I installed the ITN mode at port 60177 instead of 23 like most
sysops do.
<P>&nbsp;<P>
<h3>Master Mode.</h3>
<P>
To make <strong>mbcico</strong> scan for pending outbound mail and do
appropriate calls, start it with <strong>-r1</strong> flag. It will check
for Zone Mail Hour, outside ZMH only crash mail is delivered. Mail to
non-CM systems is only send when mail has the Immedidate status.
Poll request are always honnored, even to non-CM systems if there is a
<strong>poll</strong> request in the outbound. Be carefull.
The taskmanager <strong>mbtask</strong> will start calling <strong>mbcico -r1</strong>
if it has seen the <b>scanout</b> semafore. After all calls are completed <b>mbcico</b>
will remove the <b>scanout</b> semafore.
During ZMH all non-compressed mail is send. File requests in the outbound do not
force calling a system. If you make a filerequest, you must also make a
poll for that node to really start the request. You can also force a call
by entering <strong>mbcico f2802.n280.z2</strong> on the commandline.
Only one call is made then and there is no dial delay. If <b>mbcico -r1</b> is
called a random dialdelay is used with each call except for internet calls.
<P><B>Note:</B> you should not call nodes with mbcico directly, let
<b>mbtask</b> do the calling.
If you want to call a node make a <a href="mbout.html">poll</a> command.
<P>&nbsp;<P>
<h3>Environment.</H3>
<P>
In order to run the mbcico you need to set one global environment variable
<strong>$MBSE_ROOT</strong>
This variable must point to the root of the bbs directoy structure.
<P>&nbsp;<P>
<H3>Return Codes.</H3>
<P>
<pre>
0 - No errors
1..32 - Linux errors, SIGHUP, SIGKILL, etc.
101 - No dialout ports available.
102 - Dial failed (no CONNECT or TCP connection failed).
103 - Could not reset the modem (no OK).
104 - System is locked.
105 - not used?
106 - Nodelist lookup failed.
107 - Call prohibited by config options.
108 - Phone number unavailable.
109 - No matching ports defined.
110 - Tried to call a CM system outside ZMH.
111..129 - Session failures (not defined).
130 - Could not establish session, system is marked undialable.
</pre>
These codes are also stored in status files for nodes, with the extension
of ".sts". These are small datafiles containing three decimal numbers.
<ol>
<li>Time retry code, this is the last call attempt time. This is an unsigned
long representing the number of seconds since the epoch.
<li>Retries, this is the number of consequtive call attempts made that returned
"call failed" or other errors. This field is zeroed when the call succeeds and
when a new "poll" is created. If the value is 30, the node won't be called
anymore.
<li>Code, this is the return code of the last attempt.
</ol>
<p>&nbsp;<p>
<h3>Configuration.</H3>
<P>
The behaviour of mbcico can be configured with <strong>mbsetup</strong>,
section 1.17 If something doesn't do what you want, set the debug on for
that problem. This will produce huge logfiles, but also a lot of information.
Important flags are Device IO, EMSI debug, File forward, Locking, Outboundscan
and Session.
<P>&nbsp;<P>
<h3>Bugs.</H3>
<P>
Incoming calls from McMail mailers, McMail is quite hasty
to establish an EMSI session, and times out in less than a second. So
if your system is heavy loaded, or not too fast, McMail cannot connect
with your system. This is a known problem with McMail 1.0 and older,
later versions are ok.
<P>&nbsp;<P>
<H3>Authors.</H3>
<P>
<pre>
Eugene G. Crosser &lt;crosser@average.org&gt; Orginal ifcico.
Stanislav Voronyi &lt;stas@uanet.kharkov.ua&gt; TCP/IP code.
T. Tanaka Telnet mode.
Martin Junius Rewrite of opentcp().
Omen Technology Inc Zmodem protocol.
Arjen G. Lentz, Joaquim H. Homrighausen Hydra transfer protocol.
Cristof Meerwald Implementation of Hydra in ifcico.
P. Saratxaga Tty driver code, yoohoo extensions.
Dima Maloff Binkp protocol.
Michiel Broek Rewrite for MBSE BBS.
</pre>
<P>
<A HREF="index.htm"><IMG SRC="../images/larrow.gif" ALT="Index" Border="0">Back to index</A>&nbsp;
<A HREF="../index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Main" Border="0">Back to Main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>

61
html/programs/mbfbgen.html
View File

@ -1,61 +0,0 @@
<HTML>
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META name="author" lang="en" "content="Michiel Broek">
<META name="copyright" lang="en" content="Copyright Michiel Broek">
<META name="description" lang="en" content="MBSE BBS Manual">
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
<TITLE>MBSE BBS Programs - mbfbgen - FileBase Generato.</TITLE>
<LINK rel=stylesheet HREF="../manual.css">
</HEAD>
<BODY>
<BLOCKQUOTE>
<h5>Last update 30-Jan-2001</h5>
<P>&nbsp;<P>
<H1>mbfbgen - FileBase Generator</H1>
<P>
<H3>Synopsis.</H3>
<P>
<code><strong>mbfbgen</strong></code>
<P>&nbsp;<P>
<H3>Description.</H3>
<P>
<strong>mbfbgen</strong> is used to import filebase areas from CD-ROM. This
util works like <strong>fbgen</strong> which is known to RA users. It reads
the file <strong>files.bbs</strong> to get the filenames and descriptions
to build the filedatabase.
<P>
To import a filebase you must setup the area with <strong>mbsetup</strong>.
If you are really importing from a CD that will stay mounted on your system
you must set <strong>CDrom</strong> to yes. If the files.bbs file is not in the
directory were the files are, but somewere else on the CD, you must fill in
the field <strong>Files.bbs</strong> in the edit file area screen.
If the files.bbs file is in the same directory together with the files, you may
leave that field blank.
It is handy to use a closed range of file areas.
Once you are ready with the setup start <strong>mbfbgen</strong>, enter the
start and end area numbers, the uploader name, and the import will start.
This can last quite long as from each file the 32 bits CRC is calculated
that will be stored in the filedatabase. When <strong>mbfbgen</strong> is
finished, run <strong>mbfile index</strong> to recreate the filerequest index
file.
<P>&nbsp;<P>
<H3>Environmet.</H3>
<P>
In order to run <strong>fbgen</strong> you must set the global variable
<strong>$MBSE_ROOT</strong>. This variable must point to the root directory
of the bbs structure. The main configuration file <strong>config.data</strong>
must be present in the ~/etc directory.
<P>
<A HREF="index.htm"><IMG SRC="../images/larrow.gif" ALT="Index" Border="0" width="40" height="30"> Back to index</A>&nbsp;
<A HREF="../index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Main" Border="0" width="33" height="35"> Back to Main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>

530
html/programs/mbfido.html
View File

@ -1,260 +1,270 @@
<HTML>
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META name="author" lang="en" "content="Michiel Broek">
<META name="copyright" lang="en" content="Copyright Michiel Broek">
<META name="description" lang="en" content="MBSE BBS Manual">
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
<TITLE>MBSE BBS Programs - mbfido - The Fidonet mail and files processor.</TITLE>
<LINK rel=stylesheet HREF="../manual.css">
</HEAD>
<BODY>
<BLOCKQUOTE>
<h5>Last update 10-Jul-2001</h5>
<P>&nbsp;<P>
<H1>mbfido, the fidonet mail and files processor.</H1>
<P>
<h3>Synopsis.</H3>
<P>
<code>mbfido [command(s)] &lt;options&gt;</code>
<P>&nbsp;<P>
<H3>Description.</H3>
<P>
<strong>mbfido</strong>
is the program to process fidonet mail and files. In order to run mbfido
you must first start <strong>mbtask</strong>,
this is the deamon which controls all bbs activities. To prevent that
<strong>mbfido</strong> will run more than once at the same time a lock
is placed in the protected inbound with the pid of the running
<strong>mbfido</strong> program. The gateway to and from internet is also
handled by <strong>mbfido</strong>.
<P>&nbsp;<P>
<H3>Specifications.</H3>
<p>
The recognized mail packets are type 2+ following the FSC-0039 standard with
a fallback to the old stone age packets.
Can handle messages of maximum 429467295 bytes, or less if you have less
memory available, the practical limit is about 1 Meg. Note that most mailprocessors
are only guaranteed to work to maximum 16 KBytes.
Recent experiments in the LINUX echo show that this is still true,
although most tossers seem to process mail up to 32 KBytes.
<P>&nbsp;<P>
<H3>Tossing Mail.</H3>
<P>
First make sure you have the necessary message areas in your setup. At least
you need the badmail and dupemail areas and a netmail area for each network
you participate in. If you don't create badmail and dupemail areas then
bad (unknown area etc) and dupes are lost and you cannot check the reason why.
If you don't create the netmail areas for each network, then netmail to your
system will dissapear. It is not possible to "retoss" the badmail yet after
you have created any missing echomail areas.
<P>
To prevent .pkt name collision the toss of incoming mail is done in parts.
The first run is to process all uncompressed mailpackets and add mail to the
outbound. Then each compressed ARCmail archive will be uncompressed and
processed and mail will be imported and forwarded as necessary. During all
these passes all filenames are sorted by date and time, the oldest files are
processed first.
<P>
The recognized mail packets are type 2+ following the FSC-0039 standard with
a fallback to the old stone age packets. The packets are checked for being
addressed to one of your own aka's and for a correct password. The
password check may be switched off in the nodes setup. After all the packet
header checks the messages will be extracted from the packet file.
<P>
When messages are extracted from the packets, the date format is checked for
Year2000 bugs from other tossers. Several checks are done by ideas of Tobias
Ernst of 2:2476/418. It is also possible to run the <strong>pktdate</strong>
utility before each packet will be processed. Whatever date format us used in
the original message, <strong>mbfido</strong> will always rewrite the date
field in the right FTS-0001 format.
<P>
If the message is a netmail the message is checked for DOMAIN, INTL, FMPT and
TOPT kludges so that full 4d or 5d addressing will be possible. Then a check
is done if this netmail is addressed to one of our aka's. If it's addressed to
"sysop" or "postmaster" the name is replaced with the sysop's name. If the
message is addressed to one of the names defined in the service setup, that
mail will be handled by the service manager, ie. given to areamgr, filemgr or
send further as email to your local system.
<BR>
Then the message is checked if it is addressed to an existing bbs user, and if
so it will be imported into the netmail area of the main zone of the bbs.
If it's not addressed to a bbs user, the message will be readdressed to the
sysop. If the message is not for one of our aka's the message will be put in the
mailqueue for further routing.
<P>
If the message is a echomail message it will be checked for being a duplicate by
storing the CRC32 value of the AREA: line, message subject, origin line,
message date and msgid kludge and testing if that CRC32 value exists in the
echomail duplicate database. If there is no msgid in the message, the whole
message body will be include to complete the CRC32 dupe check.
Also the existance of the echomail area is checked and the node must be linked to that area.
If the message is not in a passthru area and is not a duplicate it
is finally imported in the message base.
After that is the message will be forwarded to downlinks
by adding the message to the mailqueue.
<P>&nbsp;<P>
<h3>Adding mail to the outbound.</h3>
<P>
Adding mail to the outbound is done in two passes. The first pass is to put all
outgoing mail into the ~/tmp directory, these files are named z.n.n.p.ext
The extension can be qqq for packed mail, nnn for normal unpacked mail, hhh for
hold unpacked mail and ccc for crash unpacked mail. Adding mail to this tmp
directory can allways be done, even if one of the nodes you are adding mail
for is having a mail session with your system. This is a safe operation.<br>
In the second pass, these temp files are really added to the outbound, but
only if the destination node is not locked, ie. there is no current mailsession
with that node. If there is a mail session going, these temp files will stay in
the temp directory and are added to the outbound in a later run of
<strong>mbfido</strong>. If adding the mail to the outbound succeeds
the temporary file is removed.
<P>&nbsp;<P>
<H3>Alias file.</H3>
<P>
If the file /opt/mbse/etc/aliases exists, mbfido will try to fetch ftn-style
aliases from there.
If "from" address of a message from FidoNet matches <b>right</b> side
of some entry in alias file, then the Reply-To: header is created
in the RFC message with the name part taken from the left side of the
sysalis entry and domain part taken from myfqdn (below). E.g., if a
fidonet message comes from "John Smith of 1:234/567.89@fidonet" and
there is an entry in the sysalias file:
<pre>
"jsmith: John.Smith@p89.f567.n234.z1.fidonet.org"
</pre>
and Domain name value is "mbse.nl", then the resulting message will
contain a line: "Reply-To: jsmith@mbse.nl".
<P>&nbsp;<P>
<H3>Commands.</H3>
<P>
<code><strong>mbfido</strong> notify &lt;nodes&gt;</code>
This command will send notify messages to all nodes in your setup which
have the notify option set to on. If you enter nodes as option you may use
wilcards, ie 2:*/* to send messages to all nodes in zone 2. If you specify
exactly one node, messages will be generated even if that node has the
notify function off. From cron you should not specify any nodes, this will
just send to all your links the information about their setup. Each node
will receive a status report for files and mail, and area list for all
file areas and mail areas to each aka a node has, and a flow report for
mail for each aka.
<P>
<code><strong>mbfido</strong> roll</code>
This command will only do something if a new week or month has begun.
If this is true the statistic records in several databases are updated.
You should run this command each midnight from cron to be sure that this when it is
time to do so. This command is always executed before one of the scan, toss or tic commands so
if you don't do this in cron, it will still happen.
<P>
<code><strong>mbfido</strong> scan</code>
Scan for new messages entered at the bbs or by other utilities. If the file
~/tmp/echomail.jam or ~/tmp/netmail.jam exists,
mbfido will only scan the messages in areas which are
pointed at in this file. This is a lot faster then a full mailscan.
If it is not present, all messagebases are scanned
to see if there is a new message. If you specify
<strong>-full</strong> on the commandline a full messagebase scan is forced.
It is wise to do this sometimes, on my bbs I run this once a day.
<P>
<code><strong>mbfido</strong> tag</code>
The command will create tag- and areas files in the doc directory for each group of
mail and files.
<P>
<code><strong>mbfido</strong> test</code>
This is for testing of the mail routing. In the source "tracker.c" I have
included a list of nodes that will be tested. This is for development only,
but it might be handy for you to test your netmail routing.
<P>
<code><strong>mbfido</strong> tic</code>
Process incoming files accompanied with .tic control files. Several actions can
take place on the incoming file before they are imported in the BBS areas.
Options are rearchiving, replacing banners (with your add), check for DOS
viruses, running scripts for certain filename patterns, send these files to
other nodes etc. All options can be defined for each area. If as a result from
one of the actions there are new files hatched, for example after processing
a nodelist difference file which created a new nodelist, the .tic processing
will start again, until there is really nothing more to do.
<P>
<code><strong>mbfido</strong> toss</code>
Toss incoming fidonet netmail and or echomail. By default mail in the protected
inbound directory will be processed, uncompressed .pkt files and compressed
arcmail bundles are recognized, filename case doesn't matter.
<P>
<code><b>mbfido</b> news</code> Scan all defined newsgroups for new newsarticles.
New articles are fetched from the newsserver and stored in your messagebase and
send to your up- and downlinks. This is for use with an NNTP gateway.
<P>
<code><strong>mbfido</strong> uucp</code>
This will read a standard a newsbatch from stdin and gate the articles
to Fidonet and the local message base. This is for use with an UUCP gateway, this
mode should be called by uuxqt. The newsbatch may be compressed or uncompressed or
a single news article.
<P>
<code><strong>mbnews</strong></code>
This is an alternative to <strong>mbfido uucp -quiet</strong>.
<P>&nbsp;<P>
<h3>Options.</h3>
<P>
<code><strong>mbfido</strong> [command] -nocrc</code>
Disable CRC checking of incoming TIC files. Only use this if you know what
you are doing.
<P>
<code><strong>mbfido</strong> scan -full</code>
Force scanning of all message bases for new entered mail. You need this if
mail in entered with other editors then from mbse. Also, running it once a
day is adviced to catch any missed messages.
<P>
<code><strong>mbfido</strong> news -learn</code>
Scan the newsserver for news articles, and update the news dupes database only.
Use this switch if you start using mbfido to gate news articles for the first time.
Articles will not be gated with this switch, mbfido will just learn which articles
already exist. Normally you only need to use this switch once.
<P>
<code><strong>mbfido</strong> [command] -nodupe</code>
Disable checking for duplicate's. Normally you should not use this switch.
This switch doesn't work with the news command, only for echomail and tic files.
<P>
<code><strong>mbfido</strong> [command] -quiet</code>
Quiet mode, all output to the current tty is supressed. Use this flag if
you toss mail from a script (started by cron) after mail is received.
<P>
<code><strong>mbfido</strong> toss -a</code> Toss mail and allow to autocreate
new message areas. See the <A HREF="../setup/emareas.html"> message area setup</A>
how to set this up.
<code><strong>mbfido</strong> toss -unsecure</code>
Toss mail without checking if the echomail is for your own system en without
checking if the sending node is connected to your system. Nodes who are
excluded from a certain echo, can stil not enter messages in that echo.
<P>
<code><strong>mbfido</strong> [command] -unprotect</code>
Toss from the unprotected inbound directory. The default is to toss from the
protected inbound directory.
<P>&nbsp;<P>
<h3>Environment.</H3>
<P>
In order to run the bbs you need to set one global environment variable
<strong>$MBSE_ROOT</strong>
This variable must point to the root of the bbs directoy structure.
<P>&nbsp;<P>
<h3>Bugs.</H3>
<P>
There are still bugs, this program is under development.
<P>
<A HREF="index.htm"><IMG SRC="../images/larrow.gif" ALT="Index" Border="0" width="40" height="30"> Back to index</A>&nbsp;
<A HREF="../index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Main" Border="0" width="33" height="35"> Back to Main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>
<HTML>
<!-- $Id$ -->
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META name="author" lang="en" content="Michiel Broek">
<META name="copyright" lang="en" content="Copyright Michiel Broek">
<META name="description" lang="en" content="MBSE BBS Manual">
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
<TITLE>MBSE BBS Programs - mbfido - The Fidonet mail and files processor.</TITLE>
<LINK rel=stylesheet HREF="../manual.css">
</HEAD>
<BODY>
<BLOCKQUOTE>
<h5>Last update 21-Jan-2002</h5>
<P>&nbsp;<P>
<H1>mbfido, the fidonet mail and files processor.</H1>
<P>
<h3>Synopsis.</H3>
<P>
<code>mbfido [command(s)] &lt;options&gt;</code>
<P>&nbsp;<P>
<H3>Description.</H3>
<P>
<strong>mbfido</strong>
is the program to process fidonet mail and files. In order to run mbfido
you must first start <strong>mbtask</strong>,
this is the deamon which controls all bbs activities. To prevent that
<strong>mbfido</strong> will run more than once at the same time a lock
is placed in the protected inbound with the pid of the running
<strong>mbfido</strong> program. The gateway to and from internet is also
handled by <strong>mbfido</strong>.
<P>&nbsp;<P>
<H3>Specifications.</H3>
<p>
The recognized mail packets are type 2+ following the FSC-0039 standard with
a fallback to the old stone age packets.
Can handle messages of maximum 429467295 bytes, or less if you have less
memory available, the practical limit is about 1 Meg. Note that most mailprocessors
are only guaranteed to work to maximum 16 KBytes.
Recent experiments in the LINUX echo show that this is still true,
although most tossers seem to process mail up to 32 KBytes.
<P>&nbsp;<P>
<H3>Tossing Mail.</H3>
<P>
First make sure you have the necessary message areas in your setup. At least
you need the badmail and dupemail areas and a netmail area for each network
you participate in. If you don't create badmail and dupemail areas then
bad (unknown area etc) and dupes are lost and you cannot check the reason why.
If you don't create the netmail areas for each network, then netmail to your
system will dissapear. It is not possible to "retoss" the badmail yet after
you have created any missing echomail areas.
<P>
To prevent .pkt name collision the toss of incoming mail is done in parts.
The first run is to process all uncompressed mailpackets and add mail to the
outbound. Then each compressed ARCmail archive will be uncompressed and
processed and mail will be imported and forwarded as necessary. During all
these passes all filenames are sorted by date and time, the oldest files are
processed first.
<P>
The recognized mail packets are type 2+ following the FSC-0039 standard with
a fallback to the old stone age packets. The packets are checked for being
addressed to one of your own aka's and for a correct password. The
password check may be switched off in the nodes setup. After all the packet
header checks the messages will be extracted from the packet file.
<P>
When messages are extracted from the packets, the date format is checked for
Year2000 bugs from other tossers. Several checks are done by ideas of Tobias
Ernst of 2:2476/418. It is also possible to run the <strong>pktdate</strong>
utility before each packet will be processed. Whatever date format us used in
the original message, <strong>mbfido</strong> will always rewrite the date
field in the right FTS-0001 format.
<P>
If the message is a netmail the message is checked for DOMAIN, INTL, FMPT and
TOPT kludges so that full 4d or 5d addressing will be possible. Then a check
is done if this netmail is addressed to one of our aka's. If it's addressed to
"sysop" or "postmaster" the name is replaced with the sysop's name. If the
message is addressed to one of the names defined in the service setup, that
mail will be handled by the service manager, ie. given to areamgr, filemgr or
send further as email to your local system.
<BR>
Then the message is checked if it is addressed to an existing bbs user, and if
so it will be imported into the netmail area of the main zone of the bbs.
If it's not addressed to a bbs user, the message will be readdressed to the
sysop. If the message is not for one of our aka's the message will be put in the
mailqueue for further routing.
<P>
If the message is a echomail message it will be checked for being a duplicate by
storing the CRC32 value of the AREA: line, message subject, origin line,
message date and msgid kludge and testing if that CRC32 value exists in the
echomail duplicate database. If there is no msgid in the message, the whole
message body will be include to complete the CRC32 dupe check.
Also the existance of the echomail area is checked and the node must be linked to that area.
If the message is not in a passthru area and is not a duplicate it
is finally imported in the message base.
After that is the message will be forwarded to downlinks
by adding the message to the mailqueue.
<P>&nbsp;<P>
<h3>Adding mail to the outbound.</h3>
<P>
Adding mail to the outbound is done in two passes. The first pass is to put all
outgoing mail into the ~/tmp directory, these files are named z.n.n.p.ext
The extension can be qqq for packed mail, nnn for normal unpacked mail, hhh for
hold unpacked mail and ccc for crash unpacked mail. Adding mail to this tmp
directory can allways be done, even if one of the nodes you are adding mail
for is having a mail session with your system. This is a safe operation.<br>
In the second pass, these temp files are really added to the outbound, but
only if the destination node is not locked, ie. there is no current mailsession
with that node. If there is a mail session going, these temp files will stay in
the temp directory and are added to the outbound in a later run of
<strong>mbfido</strong>. If adding the mail to the outbound succeeds
the temporary file is removed.
<P>&nbsp;<P>
<H3>Alias file.</H3>
<P>
If the file /opt/mbse/etc/aliases exists, mbfido will try to fetch ftn-style
aliases from there.
If "from" address of a message from FidoNet matches <b>right</b> side
of some entry in alias file, then the Reply-To: header is created
in the RFC message with the name part taken from the left side of the
sysalis entry and domain part taken from myfqdn (below). E.g., if a
fidonet message comes from "John Smith of 1:234/567.89@fidonet" and
there is an entry in the sysalias file:
<pre>
"jsmith: John.Smith@p89.f567.n234.z1.fidonet.org"
</pre>
and Domain name value is "mbse.nl", then the resulting message will
contain a line: "Reply-To: jsmith@mbse.nl".
<P>&nbsp;<P>
<H3>Commands.</H3>
<P>
<code><strong>mbfido</strong> mail &lt;recipient&gt;</code>
This command is used by your MTA to deliver email addressed to for example
Michiel_Broek@f2802.n280.z2.fidonet.org
<P>
<code><strong>mbmail</strong> &lt;recipient&gt;</code>
This is the same as above.
<P>
<code><strong>mbfido</strong> notify &lt;nodes&gt;</code>
This command will send notify messages to all nodes in your setup which
have the notify option set to on. If you enter nodes as option you may use
wilcards, ie 2:*/* to send messages to all nodes in zone 2. If you specify
exactly one node, messages will be generated even if that node has the
notify function off. From cron you should not specify any nodes, this will
just send to all your links the information about their setup. Each node
will receive a status report for files and mail, and area list for all
file areas and mail areas to each aka a node has, and a flow report for
mail for each aka.
<P>
<code><strong>mbfido</strong> roll</code>
This command will only do something if a new week or month has begun.
If this is true the statistic records in several databases are updated.
You should run this command each midnight from cron to be sure that this when it is
time to do so. This command is always executed before one of the scan, toss or tic commands so
if you don't do this in cron, it will still happen.
<P>
<code><strong>mbfido</strong> scan</code>
Scan for new messages entered at the bbs or by other utilities. If the file
~/tmp/echomail.jam or ~/tmp/netmail.jam exists,
mbfido will only scan the messages in areas which are
pointed at in this file. This is a lot faster then a full mailscan.
If it is not present, all messagebases are scanned
to see if there is a new message. If you specify
<strong>-full</strong> on the commandline a full messagebase scan is forced.
It is wise to do this sometimes, on my bbs I run this once a day.
<P>
<code><strong>mbfido</strong> tag</code>
The command will create tag- and areas files in the doc directory for each group of
mail and files.
<P>
<code><strong>mbfido</strong> test</code>
This is for testing of the mail routing. In the source "tracker.c" I have
included a list of nodes that will be tested. This is for development only,
but it might be handy for you to test your netmail routing.
<P>
<code><strong>mbfido</strong> tic</code>
Process incoming files accompanied with .tic control files. Several actions can
take place on the incoming file before they are imported in the BBS areas.
Options are rearchiving, replacing banners (with your add), check for DOS
viruses, running scripts for certain filename patterns, send these files to
other nodes etc. All options can be defined for each area. If as a result from
one of the actions there are new files hatched, for example after processing
a nodelist difference file which created a new nodelist, the .tic processing
will start again, until there is really nothing more to do.
<P>
<code><strong>mbfido</strong> toss</code>
Toss incoming fidonet netmail and or echomail. By default mail in the protected
inbound directory will be processed, uncompressed .pkt files and compressed
arcmail bundles are recognized, filename case doesn't matter.
<P>
<code><b>mbfido</b> news</code> Scan all defined newsgroups for new newsarticles.
New articles are fetched from the newsserver and stored in your messagebase and
send to your up- and downlinks. This is for use with an NNTP gateway.
<P>
<code><strong>mbfido</strong> uucp</code>
This will read a standard a newsbatch from stdin and gate the articles
to Fidonet and the local message base. This is for use with an UUCP gateway, this
mode should be called by uuxqt. The newsbatch may be compressed or uncompressed or
a single news article.
<P>
<code><strong>mbnews</strong></code>
This is an alternative to <strong>mbfido uucp -quiet</strong>.
<P>&nbsp;<P>
<h3>Options.</h3>
<P>
<code><strong>mbfido</strong> [command] -nocrc</code>
Disable CRC checking of incoming TIC files. Only use this if you know what
you are doing.
<P>
<code><strong>mbfido</strong> scan -full</code>
Force scanning of all message bases for new entered mail. You need this if
mail in entered with other editors then from mbse. Also, running it once a
day is adviced to catch any missed messages.
<P>
<code><strong>mbfido</strong> news -learn</code>
Scan the newsserver for news articles, and update the news dupes database only.
Use this switch if you start using mbfido to gate news articles for the first time.
Articles will not be gated with this switch, mbfido will just learn which articles
already exist. Normally you only need to use this switch once.
<P>
<code><strong>mbfido</strong> [command] -nodupe</code>
Disable checking for duplicate's. Normally you should not use this switch.
This switch doesn't work with the news command, only for echomail and tic files.
<P>
<code><strong>mbfido</strong> [command] -quiet</code>
Quiet mode, all output to the current tty is supressed. Use this flag if
you toss mail from a script (started by cron) after mail is received.
<P>
<code><strong>mbfido</strong> toss -a</code> Toss mail and allow to autocreate
new message areas. See the <A HREF="../setup/emareas.html"> message area setup</A>
how to set this up.
<code><strong>mbfido</strong> toss -unsecure</code>
Toss mail without checking if the echomail is for your own system en without
checking if the sending node is connected to your system. Nodes who are
excluded from a certain echo, can stil not enter messages in that echo.
<P>
<code><strong>mbfido</strong> [command] -unprotect</code>
Toss from the unprotected inbound directory. The default is to toss from the
protected inbound directory.
<P>&nbsp;<P>
<h3>Environment.</H3>
<P>
In order to run the bbs you need to set one global environment variable
<strong>$MBSE_ROOT</strong>
This variable must point to the root of the bbs directoy structure.
<P>&nbsp;<P>
<h3>Bugs.</H3>
<P>
There are still bugs, this program is under development.
<P>
<A HREF="index.htm"><IMG SRC="../images/larrow.gif" ALT="Index" Border="0">Back to index</A>&nbsp;
<A HREF="../index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Main" Border="0">Back to Main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>

47
html/programs/mbmail.html
View File

@ -1,47 +0,0 @@
<HTML>
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META name="author" lang="en" "content="Michiel Broek">
<META name="copyright" lang="en" content="Copyright Michiel Broek">
<META name="description" lang="en" content="MBSE BBS Manual">
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
<TITLE>MBSE BBS Programs - mbmail - Mail User Agent for the email gate.</TITLE>
<LINK rel=stylesheet HREF="../manual.css">
</HEAD>
<BODY>
<BLOCKQUOTE>
<h5>Last update 10-Apr-2001</h5>
<P>&nbsp;<P>
<H1>mbmail - Mail User Agent for the email gate.</H1>
<P>
<H3>Synopsys.</H3>
<code><strong>mbmail</strong> -r&lt;addr&gt; -g&lt;grade&gt; -c&lt;charset&gt; -b &lt;recip&gt;</code>
<P>&nbsp;<P>
<H3>Description.</H3>
<P>
<strong>mbmail</strong>
is the Mail User Agent that should be called by your Internet mailer to deliver
mail to Fidonet systems. This program must always run as user <strong>mbse</strong> so
your mailer must be capable of doing so. The Postfix mailer I use can do that.
<P>
<H3>Commandline options.</H3>
<P>
<code><strong>mbfile</strong> -r&lt;addr&gt; -g&lt;grade&gt; -c&lt;charset&gt; -b &lt;recip&gt;</code>
The -r&lt;addr&gt; is the address to route the packet to. This should normal be set by
the Internet mailer to one of your aka's. The -g&lt;grade&gt; is the packet flavor. This
can be one of the characters n, c or h which means normal, crash or hold. The -c&lt;charset&gt; will
force a certain characterset. Normally this will be automatic set. The -b switch disables splitting
of long messages. The &lt;recip&gt; are one or more recipients for the message. The message itself is
read from stdin.
<P>
<A HREF="index.htm"><IMG SRC="../images/larrow.gif" ALT="Index" Border="0" width="40" height="30"> Back to index</A>&nbsp;
<A HREF="../index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Main" Border="0" width="33" height="35"> Back to Main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>

5
html/programs/mbpasswd.html
View File

@ -1,4 +1,5 @@
<HTML>
<!-- $Id$ -->
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
@ -11,7 +12,7 @@
</HEAD>
<BODY>
<BLOCKQUOTE>
<h5>Last update 07-Jan-2002</h5>
<h5>Last update 21-Jan-2002</h5>
<P>&nbsp;<P>
<H1>mbpasswd - The password wrapper.</H1>
@ -34,7 +35,7 @@ bbs when an existing user changes his password. If you as sysop use
His password under Unix is then always the same as his password in the bbs program.
This is necessary for the user to be able to get his email using the pop3 protocol.<P>
You never need to run <strong>mbpasswd</strong> by hand, in fact it is protected so that only
members of group <b>bbs</b> are allowed to use it. User <b>mbse</b> can use thsi
members of group <b>bbs</b> are allowed to use it. User <b>mbse</b> can use this
program and if you do, the password for a user are not in sync anymore.
<P>&nbsp;<P>

29
html/programs/mbsebbs.html
View File

@ -1,8 +1,9 @@
<HTML>
<!-- $Id$ -->
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
<META name="author" lang="en" "content=Michiel Broek">
<META name="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">
@ -11,7 +12,7 @@
</HEAD>
<BODY>
<BLOCKQUOTE>
<h5>Last update 09-Nov-2001</h5>
<h5>Last update 21-Jan-2002</h5>
<P>&nbsp;<P>
<H1>mbsebbs - The main BBS program</H1>
@ -43,18 +44,8 @@ If this tty is not available or is not in your setup, the user is kicked
out. If he is allowed to login, a message is shown at which port he is on,
unless you have turned this feature off in the setup.
<P>
If a user logs in the first check is if he/she has a Unix account or not.
Unix users bypass the login prompt. Other users will get the normal prompt
the same way DOS based bbs programs do. At that time it is checked if the
user has IEMSI capabilities, if that is true, IEMSI login will be tried.
If the user is not known, the newuser procedure begins.
<P>
If the user login is successfull, his favourite language will be loaded.
Then it is checked if the user is the Sysop, if so, the Sysop flag is set.
If the user has a blank password, he is asked to create a new password.
Next it is checked if the user has an Unix account, if not he is forced to
create a Unix account. This situation can exist after switching to MBSE BBS
and you have converted your old userbase to the userbase for MBSE BBS.
If the users Date of Birth is invalid, he is forced to enter the right
Date of Birth.
The next check is to see if the user has passed the expiry date, this is a
@ -139,19 +130,13 @@ will be made with the connect speed.
If the environment variable <strong>CALLER_ID</strong> is present, a log entry
will be made with the caller id.
<P>
If the environment variable <strong>LOGNAME</strong> is present and it is not
<strong>bbs</strong> then it is assumed that it is a Unixmode login of the
user who's Unixname is in the <strong>LOGNAME</strong> environment variable.
This variable is set by the /bin/login program, so users that telnet to your
bbs or login via <strong>mgetty</strong> and login with their Unixname will
set this. If the <strong>LOGNAME</strong> is <strong>bbs</strong> then the
user is prompted to enter his Fidonet style name. By the way, you can change
that default <b>bbs</b> username with <b>mbsetup</b>.
The environment variable <strong>LOGNAME</strong> must contain the unix
username. This is set by the <b>mblogin</b> program.
<P>&nbsp;<P>
<A HREF="index.htm"><IMG SRC="../images/larrow.gif" ALT="Index" Border="0" width="40" height="30"> Back to index</A>&nbsp;
<A HREF="../index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Main" Border="0" width="33" height="35"> Back to Main index</A>
<A HREF="index.htm"><IMG SRC="../images/larrow.gif" ALT="Index" Border="0">Back to index</A>&nbsp;
<A HREF="../index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Main" Border="0">Back to Main index</A>
</BLOCKQUOTE>
</BODY>
</HTML>

331
html/setup/emareas.html
View File

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

117
html/setup/fdb.html
View File

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

14
html/setup/global.html
View File

@ -1,4 +1,5 @@
<HTML>
<!-- $Id$ -->
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
@ -11,7 +12,7 @@
</HEAD>
<BODY>
<BLOCKQUOTE>
<h5>Last update 07-Jan-2002</h5>
<h5>Last update 21-Jan-2002</h5>
<P>&nbsp;<P>
<H1>MBSE BBS Setup - Global Setup</H1>
@ -286,14 +287,14 @@ split will be forced right after the file that passes the 31 KBytes limit.
I use values of 1 KBytes below maximum for overhead such as SEEN-BY and
PATH lines. Values larger then 32 KBytes is not a good idea, recent tests
in May 1999 have shown that your messages will not reach all systems
if they are larger then 32 KBytes. Splitting is used for newsfiles reports
if they are larger then 32 KBytes. Splitting is used for newfiles reports
and gated news articles to Fidonet.
<P>
<h3>1.15. Edit Internet mail and news processing.</h3>
<p>
Email and news is setup here. There are three possible configurations which you
can set with 1.14.11:
can set with 1.15.11:
<ul>
<li><strong>No ISP</strong>. If you don't have any connection to the internet
use this setting. Email will come from the default Fidonet UUCP gate and will be send out
@ -314,7 +315,9 @@ can set with 1.14.11:
<li><strong>Perm ISP</strong>. If you are permanent connected to the internet
either with a static or dynamic IP address use this option. Use this option
also if you have an UUCP domain and have a dialup UUCP connection. Also
you can use this for dialup if you have your own maildomain.
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
@ -322,6 +325,8 @@ can set with 1.14.11:
<strong>user@yourbbs.domain.org</strong>. Note, the username is their
Unix name.
</ul>
Note: the terms <b>Dial ISP</b> and <b>Perm ISP</b> are not correct, it doesn't
matter how you are connected, it only matters if you have a maildomain or not.
Another word of wisdom from my side, configuration of the internet, ppp, sendmail etc. is not discussed
here, see the HOWTO's and other documentation that exists at <A HREF="http://www.linuxdoc.org">
www.linuxdoc.org</A>, it's all there.
@ -338,6 +343,7 @@ www.linuxdoc.org</A>, it's all there.
<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

127
html/setup/hatch.html
View File

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