Updated documentation
This commit is contained in:
Michiel Broek
parent
53f739639c
commit
6ebffc9d86
@ -6,7 +6,7 @@ include ../Makefile.global
|
|||||||
|
|
||||||
H_BASE = basic.html date.html dist.html manual.css \
|
H_BASE = basic.html date.html dist.html manual.css \
|
||||||
flow.html postfix.html gwnews.html index.htm ups.html \
|
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
|
known_bugs.html mgetty.html routing.html nodelist.html
|
||||||
|
|
||||||
H_FTSC = ftsc/fsc-0039.html ftsc/fsc-0056.html ftsc/fsc-0087.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/mbaff.html programs/mbdiff.html \
|
||||||
programs/mbindex.html programs/mbout.html \
|
programs/mbindex.html programs/mbout.html \
|
||||||
programs/mbsetup.html programs/mbuseradd.html \
|
programs/mbsetup.html programs/mbuseradd.html \
|
||||||
programs/mball.html programs/mbfbgen.html \
|
programs/mball.html \
|
||||||
programs/mblang.html programs/mbsebbs.html \
|
programs/mblang.html programs/mbsebbs.html \
|
||||||
programs/mbstat.html programs/mbpasswd.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 \
|
H_SETUP = setup/archiver.html setup/index.htm setup/bbs.html \
|
||||||
setup/bbslist.html setup/language.html setup/oneliner.html \
|
setup/bbslist.html setup/language.html setup/oneliner.html \
|
||||||
|
|||||||
@ -1,4 +1,5 @@
|
|||||||
<HTML>
|
<HTML>
|
||||||
|
<!-- $Id$ -->
|
||||||
<HEAD>
|
<HEAD>
|
||||||
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
|
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
|
||||||
<META http-equiv="Content-Style-Type" content="text/css">
|
<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
|
<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.
|
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 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
|
<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
|
<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
|
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>
|
</ol>
|
||||||
<p> <p>
|
<p> <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
|
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
|
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.
|
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:
|
If everythings is allright, then remove the directory /tmp/mbsebbs-0.33.nn:
|
||||||
<pre>
|
<pre>
|
||||||
cd /tmp
|
cd /tmp
|
||||||
@ -142,7 +146,7 @@ rm -Rf mbsebbs-0.33.nn
|
|||||||
<h3>Step 4: Install the basic packages.</h3>
|
<h3>Step 4: Install the basic packages.</h3>
|
||||||
<p>
|
<p>
|
||||||
Login as user <b>mbse</b>. Yes, very important, <b>login as user mbse</b>.
|
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>
|
<pre>
|
||||||
tar xfvz /path/to/mbsebbs-0.33.nn.tar.gz
|
tar xfvz /path/to/mbsebbs-0.33.nn.tar.gz
|
||||||
</pre>
|
</pre>
|
||||||
@ -158,17 +162,23 @@ make install
|
|||||||
exit
|
exit
|
||||||
</pre>
|
</pre>
|
||||||
The last part of the installation procedure shows you the location of the bbs
|
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
|
startup script that is added to your system. Remember this one for a moment.
|
||||||
time installation, example menus, textfiles and some databases are installed.
|
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
|
If they already exist on your systems (when you do an upgrade) they
|
||||||
will not be installed again.
|
will not be installed again.
|
||||||
<p>
|
<p>
|
||||||
Now you must start the <b>mbtask</b> daemon by hand by typing <b>/opt/mbse/bin/mbtask</b>.
|
Now start the bbs for the first time (still as root) by executing the startup
|
||||||
Check the file <b>/opt/mbse/log/mbtask.log</b> for startup problems. You may notice that
|
script you just saw on the screen followed by a space and the word <b>start</b>.
|
||||||
the program <b>mbcico</b> is started everytime, this is not a problem, it simply doesn't work right
|
For example:
|
||||||
now because you haven't configured anything yet. The first time <b>mbtask</b> is
|
<pre>
|
||||||
started on your system it will create a lot of new configuration files with
|
/etc/rc.d/init.d/mbsed start
|
||||||
default settings.
|
</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> <p>
|
<p> <p>
|
||||||
|
|
||||||
<h3>Step 5: (RedHat) startup problems.</h3>
|
<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.
|
case, please let me know and tell me how I can test what version it is.
|
||||||
<p> <p>
|
<p> <p>
|
||||||
|
|
||||||
<h3>Step 6: ready.</h3>
|
<h3>Step 6: Ready.</h3>
|
||||||
<p>
|
<p>
|
||||||
Now the basic environment is finished, the next thing is to <a href="install.html">install</a>
|
Now you have shell scripts in ~/etc, most of them are called by cron, some
|
||||||
the scripts, examples and configuration.
|
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> <P>
|
<P> <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>
|
</blockquote>
|
||||||
</body>
|
</body>
|
||||||
|
|||||||
@ -1,4 +1,5 @@
|
|||||||
<HTML>
|
<HTML>
|
||||||
|
<!-- $Id$ -->
|
||||||
<HEAD>
|
<HEAD>
|
||||||
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
|
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
|
||||||
<META http-equiv="Content-Style-Type" content="text/css">
|
<META http-equiv="Content-Style-Type" content="text/css">
|
||||||
@ -11,7 +12,7 @@
|
|||||||
</HEAD>
|
</HEAD>
|
||||||
<BODY>
|
<BODY>
|
||||||
<BLOCKQUOTE>
|
<BLOCKQUOTE>
|
||||||
<h5>Last update 29-Dec-2001</h5>
|
<h5>Last update 21-Jan-2002</h5>
|
||||||
<P> <P>
|
<P> <P>
|
||||||
|
|
||||||
<H1>Unix Distributions.</H1>
|
<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.
|
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
|
Since late 2001 a port to FreeBSD is available, from version 0.33.19 this
|
||||||
port is ready to use.
|
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
|
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.
|
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,
|
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>
|
<P>
|
||||||
I write this as if these are the same which isn't true of course. From MBSE
|
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
|
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
|
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
|
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.
|
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
|
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
|
on how to build a small server.
|
||||||
startup script (/etc/rc.d/init.d/mbsed) is different than before. Maybe
|
|
||||||
this is needed for Mandrake 6.1 and up too.
|
|
||||||
<P> <P>
|
<P> <P>
|
||||||
|
|
||||||
<H3>SuSe</H3>
|
<H3>SuSE</H3>
|
||||||
<P>
|
<P>
|
||||||
Since SuSE 7.1 the setup scripts are working and tested. Older distro's
|
Since SuSE 7.1 the setup scripts are working and tested. Older distro's
|
||||||
might work.
|
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.
|
You may need to build mgetty yourself if you have an older FreeBSD distribution.
|
||||||
<P> <P>
|
<P> <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> <P>
|
||||||
|
|
||||||
<H3>Famous last words...</H3>
|
<H3>Famous last words...</H3>
|
||||||
<P>
|
<P>
|
||||||
I don't have the diskspace for all kinds of Linux distributions to install
|
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.
|
a problem with that, just send me the new distro on CD to test by snailmail.
|
||||||
<P> <P>
|
<P> <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>
|
</BODY>
|
||||||
</HTML>
|
</HTML>
|
||||||
|
|
||||||
|
|||||||
@ -1,4 +1,5 @@
|
|||||||
<HTML>
|
<HTML>
|
||||||
|
<!-- $Id$ -->
|
||||||
<HEAD>
|
<HEAD>
|
||||||
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
|
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
|
||||||
<META http-equiv="Content-Style-Type" content="text/css">
|
<META http-equiv="Content-Style-Type" content="text/css">
|
||||||
@ -11,7 +12,7 @@
|
|||||||
</HEAD>
|
</HEAD>
|
||||||
<BODY>
|
<BODY>
|
||||||
<BLOCKQUOTE>
|
<BLOCKQUOTE>
|
||||||
<h5>Last update 29-Dec-2001</h5>
|
<h5>Last update 21-Jan-2002</h5>
|
||||||
<P> <P>
|
<P> <P>
|
||||||
|
|
||||||
<H1>Running a BBS under Unix.</H1>
|
<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>
|
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.
|
in the bbs that calls a shell for them.
|
||||||
<P>
|
<P>
|
||||||
There are probably more accounts on your system that can callin, <b>mbse</b> is
|
Because for dialin with mgetty the mblogin program is used and not the normal
|
||||||
such an account, this is the MBSE BBS maintenance account. This user will
|
login program, only bbs users can login. All other users including <b>root</b> are
|
||||||
get the shell prompt. Use good passwords for shell accounts, and never change
|
denied access.
|
||||||
your setup so that the <b>root</b> user can directly login except from the console.
|
You might consider installing SSH on your system for remote maintenance.
|
||||||
If you need root access, login as <b>mbse</b> and type <b>su</b> at the prompt to become
|
<p>
|
||||||
root. You might consider installing SSH on your system for remote maintenance.
|
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> <P>
|
<P> <P>
|
||||||
|
|
||||||
<H3>A PPP call is detected.</H3>
|
<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.
|
separate machine via a lan and export the display to that machine.
|
||||||
<P> <P>
|
<P> <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>
|
</BLOCKQUOTE>
|
||||||
</BODY>
|
</BODY>
|
||||||
</HTML>
|
</HTML>
|
||||||
|
|||||||
Binary file not shown.
|
Before Width: | Height: | Size: 8.2 KiB After Width: | Height: | Size: 9.9 KiB |
@ -1,4 +1,5 @@
|
|||||||
<HTML>
|
<HTML>
|
||||||
|
<!-- $Id$ -->
|
||||||
<HEAD>
|
<HEAD>
|
||||||
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
|
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
|
||||||
<META http-equiv="Content-Style-Type" content="text/css">
|
<META http-equiv="Content-Style-Type" content="text/css">
|
||||||
@ -15,7 +16,7 @@
|
|||||||
<h1>MBSE BBS System Guide v0.33.19</h1>
|
<h1>MBSE BBS System Guide v0.33.19</h1>
|
||||||
<HR>
|
<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>
|
<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="flow.html">Running a BBS under Linux</a></li>
|
||||||
<li><a href="dist.html">Which distribution to use</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="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>
|
<li><a href="setup/index.htm">Configuring the bbs with mbsetup</a></li>
|
||||||
<ol>
|
<ol>
|
||||||
<li><A HREF="setup/global.html">Edit Global configuration</a>
|
<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/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/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/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/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/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/mbindex.html">mbindex, Nodelist index compiler</a></li>
|
||||||
<li><a href="programs/mblang.html">mblang, Language datafile 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/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/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/mbmsg.html">mbmsg, The messagebase utility program</a></li>
|
||||||
<li><a href="programs/mbout.html">mbout, The mailer outbound program</a></li>
|
<li><a href="programs/mbout.html">mbout, The mailer outbound program</a></li>
|
||||||
|
|||||||
@ -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> <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>
|
|
||||||
|
|
||||||
@ -1,4 +1,5 @@
|
|||||||
<HTML>
|
<HTML>
|
||||||
|
<!-- $Id$ -->
|
||||||
<HEAD>
|
<HEAD>
|
||||||
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
|
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
|
||||||
<META http-equiv="Content-Style-Type" content="text/css">
|
<META http-equiv="Content-Style-Type" content="text/css">
|
||||||
@ -11,20 +12,19 @@
|
|||||||
</HEAD>
|
</HEAD>
|
||||||
<BODY>
|
<BODY>
|
||||||
<BLOCKQUOTE>
|
<BLOCKQUOTE>
|
||||||
<h5>Last update 28-Jan-2001</h5>
|
<h5>Last update 21-Jan-2002</h5>
|
||||||
<P> <P>
|
<P> <P>
|
||||||
<H1>Introduction to MBSE BBS.</H1>
|
<H1>Introduction to MBSE BBS.</H1>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<H3>Distribution.</H3>
|
<H3>Distribution.</H3>
|
||||||
<P>
|
<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>
|
<OL>
|
||||||
<LI><A HREF="http://mbse.sourceforge.net">http://mbse.sourceforge.net</A> Primary site
|
<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://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/2802 (+31-255-515973).
|
||||||
<LI>fidonet node 2:280/2801 (+31-255-533858).
|
<LI>fidonet node 2:280/2801 (+31-255-536577).
|
||||||
</OL>
|
</OL>
|
||||||
If you find mbse bbs on another site it may be out of date. I have no control over these sites.
|
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
|
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>
|
<H3>Future plans.</H3>
|
||||||
<P>
|
<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.
|
should work for browsers about the same as with ANSI character terminals.
|
||||||
<P> <P>
|
<P> <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>
|
</BLOCKQUOTE>
|
||||||
</BODY>
|
</BODY>
|
||||||
</HTML>
|
</HTML>
|
||||||
|
|||||||
@ -1,4 +1,5 @@
|
|||||||
<HTML>
|
<HTML>
|
||||||
|
<!-- $Id$ -->
|
||||||
<HEAD>
|
<HEAD>
|
||||||
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
|
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
|
||||||
<META http-equiv="Content-Style-Type" content="text/css">
|
<META http-equiv="Content-Style-Type" content="text/css">
|
||||||
@ -11,7 +12,7 @@
|
|||||||
</HEAD>
|
</HEAD>
|
||||||
<BODY>
|
<BODY>
|
||||||
<BLOCKQUOTE>
|
<BLOCKQUOTE>
|
||||||
<h5>Last update 28-Jan-2001</h5>
|
<h5>Last update 21-Jan-2002</h5>
|
||||||
<P> <P>
|
<P> <P>
|
||||||
<H1>MBSE BBS - Known bugs.</H1>
|
<H1>MBSE BBS - Known bugs.</H1>
|
||||||
<P>
|
<P>
|
||||||
@ -20,18 +21,16 @@ There are always more bugs, but these are known....
|
|||||||
|
|
||||||
<UL>
|
<UL>
|
||||||
<LI>Reading of function keys in mbsebbs doesn't work always good, especially on
|
<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>Memory leaks in mbfido during mailtoss.
|
||||||
|
|
||||||
<LI>Problems with D'Bridge [1a] mailers.
|
<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.
|
<LI>mbsetup crashes at several places if in system aka's the domain name is 12 characters long.
|
||||||
</UL>
|
</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>
|
</BODY>
|
||||||
</HTML>
|
</HTML>
|
||||||
|
|
||||||
|
|||||||
@ -1,4 +1,5 @@
|
|||||||
<HTML>
|
<HTML>
|
||||||
|
<!-- $Id$ -->
|
||||||
<HEAD>
|
<HEAD>
|
||||||
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
|
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
|
||||||
<META http-equiv="Content-Style-Type" content="text/css">
|
<META http-equiv="Content-Style-Type" content="text/css">
|
||||||
@ -11,7 +12,7 @@
|
|||||||
</HEAD>
|
</HEAD>
|
||||||
<BODY>
|
<BODY>
|
||||||
<BLOCKQUOTE>
|
<BLOCKQUOTE>
|
||||||
<h5>Last update 07-Jan-2002</h5>
|
<h5>Last update 21-Jan-2002</h5>
|
||||||
<P> <P>
|
<P> <P>
|
||||||
|
|
||||||
<h1>MBSE BBS Programs.</h1>
|
<h1>MBSE BBS Programs.</h1>
|
||||||
@ -24,7 +25,6 @@
|
|||||||
<li><A HREF="mbchat.html">mbchat, Sysop to user chat utility</A>
|
<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="mbcico.html">mbcico, The Fidonet mailer ala ifcico</A>
|
||||||
<li><A HREF="mbdiff.html">mbdiff, Nodelist difference processor</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="mbfido.html">mbfido, Fidonet mail and files procesor</A>
|
||||||
<li><A HREF="mbfile.html">mbfile, Files database maintenance program</A>
|
<li><A HREF="mbfile.html">mbfile, Files database maintenance program</A>
|
||||||
<li><A HREF="mbindex.html">mbindex, Nodelist index compiler</A>
|
<li><A HREF="mbindex.html">mbindex, Nodelist index compiler</A>
|
||||||
|
|||||||
@ -1,222 +1,263 @@
|
|||||||
<HTML>
|
<HTML>
|
||||||
<HEAD>
|
<!-- $Id$ -->
|
||||||
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
|
<HEAD>
|
||||||
<META http-equiv="Content-Style-Type" content="text/css">
|
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
|
||||||
<META name="author" lang="en" "content="Michiel Broek">
|
<META http-equiv="Content-Style-Type" content="text/css">
|
||||||
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
<META name="author" lang="en" content="Michiel Broek">
|
||||||
<META name="description" lang="en" content="MBSE BBS Manual">
|
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
||||||
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
<META name="description" lang="en" content="MBSE BBS Manual">
|
||||||
<TITLE>MBSE BBS Programs - mbcico - The Fidonet mailer.</TITLE>
|
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
||||||
<LINK rel=stylesheet HREF="../manual.css">
|
<TITLE>MBSE BBS Programs - mbcico - The Fidonet mailer.</TITLE>
|
||||||
</HEAD>
|
<LINK rel=stylesheet HREF="../manual.css">
|
||||||
<BODY>
|
</HEAD>
|
||||||
<BLOCKQUOTE>
|
<BODY>
|
||||||
<h5>Last update 30-Jan-2001</h5>
|
<BLOCKQUOTE>
|
||||||
<P> <P>
|
<h5>Last update 21-Jan-2002</h5>
|
||||||
|
<P> <P>
|
||||||
<H1>mbcico - The Fidonet mailer.</H1>
|
|
||||||
|
<H1>mbcico - The Fidonet mailer.</H1>
|
||||||
<P>
|
|
||||||
This is work in progress....
|
<P>
|
||||||
<P>
|
This is work in progress....
|
||||||
|
<P>
|
||||||
<h3>Synopsis.</H3>
|
|
||||||
<P>
|
<h3>Synopsis.</H3>
|
||||||
<code>-r<role> -a<inetaddr> <node> ...</code><br>
|
<P>
|
||||||
<code>-r 0|1 </code>1 - master, o - slave [0]<br>
|
<code>-r<role> -a<inetaddr> <node> ...</code><br>
|
||||||
<code>-n<phone> </code>forced phone number<br>
|
<code>-r 0|1 </code>1 - master, o - slave [0]<br>
|
||||||
<code>-l<ttydevice> </code>forced tty device<br>
|
<code>-n<phone> </code>forced phone number<br>
|
||||||
<code>-t<tcpmode> </code>telnet TCP/IP mode, must be one of ifc|itn|ibn, forces TCP/IP<br>
|
<code>-l<ttydevice> </code>forced tty device<br>
|
||||||
<code>-a<inetaddr> </code>supply internet hostname if not in nodelist<br>
|
<code>-t<tcpmode> </code>telnet TCP/IP mode, must be one of ifc|itn|ibn, forces TCP/IP<br>
|
||||||
<code> <node> </code>should be in domain form, e.g. f11.n22.z3
|
<code>-a<inetaddr> </code>supply internet hostname if not in nodelist<br>
|
||||||
(this implies master mode)<br>
|
<code> <node> </code>should be in domain form, e.g. f11.n22.z3
|
||||||
<code>-h </code>show this help message<br>
|
(this implies master mode)<br>
|
||||||
<br>
|
<code>-h </code>show this help message<br>
|
||||||
or: <code>mbcico tsync|yoohoo|**EMSI_INQC816|-t ibn|-t ifc|-t itn</code> (this implies slave mode)
|
<br>
|
||||||
<P> <P>
|
or: <code>mbcico tsync|yoohoo|**EMSI_INQC816|-t ibn|-t ifc|-t itn</code> (this implies slave mode)
|
||||||
|
<P> <P>
|
||||||
<H3>Description.</H3>
|
|
||||||
<P>
|
<H3>Description.</H3>
|
||||||
<strong>mbcico</strong> stands for MBse "Internet - Fidonet Copy In /Copy Out",
|
<P>
|
||||||
this is a FidoNet(r) compatible transport agent. It is based on <strong>
|
<strong>mbcico</strong> stands for MBse "Internet - Fidonet Copy In /Copy Out",
|
||||||
ifcico</strong> written by Eugene G. Crosser, <crosser@average.org>,
|
this is a FidoNet(r) compatible transport agent. It is based on <strong>
|
||||||
2:5020/230@FidoNet. I changed the name of the program to make the difference
|
ifcico</strong> written by Eugene G. Crosser, <crosser@average.org>,
|
||||||
between <strong>ifcico</strong> and <strong>mbcico</strong>. Nowadays it is
|
2:5020/230@FidoNet. I changed the name of the program to make the difference
|
||||||
quite different then ifcico.
|
between <strong>ifcico</strong> and <strong>mbcico</strong>. Nowadays it is
|
||||||
<P>
|
quite different then ifcico.
|
||||||
Currently it supports FTS-0001, YooHoo/2U2 and EMSI handshake protocols,
|
<P>
|
||||||
Xmodem, Telink, Modem7, Hydra, SEAlink with and without overdrive and
|
Currently it supports FTS-0001, YooHoo/2U2 and EMSI handshake protocols,
|
||||||
crash recovery, Bark file and update requests, WaZoo protocols: DietIFNA,
|
Xmodem, Telink, Modem7, Hydra, SEAlink with and without overdrive and
|
||||||
plain Zmodem (aka ZedZip, EMSI flag "ZMO") and ZedZap, WaZoo file and
|
crash recovery, Bark file and update requests, WaZoo protocols: DietIFNA,
|
||||||
update requests (nodelist flag should be XA). WaZoo file and update requests
|
plain Zmodem (aka ZedZip, EMSI flag "ZMO") and ZedZap, WaZoo file and
|
||||||
do also work with FTS-0001 sessions, this is supported by several well known DOS
|
update requests (nodelist flag should be XA). WaZoo file and update requests
|
||||||
mailers also.
|
do also work with FTS-0001 sessions, this is supported by several well known DOS
|
||||||
Password protected requests and update requests are implemented (but not
|
mailers also.
|
||||||
yet full tested).
|
Password protected requests and update requests are implemented (but not
|
||||||
<P>
|
yet full tested).
|
||||||
There is also a special protocol optimized to use over TCP/IP connections,
|
<P>
|
||||||
contributed by Stanislav Voronyi <stas@uanet.kharkov.ua>, it is
|
There is also a special protocol optimized to use over TCP/IP connections,
|
||||||
identiefied by EMSI proto code TCP (not registered) and nodelist flag IFC.
|
contributed by Stanislav Voronyi <stas@uanet.kharkov.ua>, it is
|
||||||
The default port is 60179. There is a telnet variant on this, the default
|
identiefied by EMSI proto code TCP (not registered) and nodelist flag IFC.
|
||||||
port is 23, and nodelist flag is ITN. The telnet variant is written by
|
The default port is 60179. There is a telnet variant on this, the default
|
||||||
T. Tanaka.
|
port is 23, and nodelist flag is ITN. The telnet variant is written by
|
||||||
<P>
|
T. Tanaka.
|
||||||
There is also a <strong>Binkp</strong> implementation, this is a
|
<P>
|
||||||
bi-directional TCP/IP protocol.
|
There is also a <strong>Binkp</strong> implementation, this is a
|
||||||
This protocol is prefferred over the IFC protocol because it is
|
bi-directional TCP/IP protocol.
|
||||||
more efficient. Nodelist flag is IBN, the default port is 24554, and the
|
This protocol is prefferred over the IFC protocol because it is
|
||||||
nodelist request flag is XX. This Binkp implementation supports multiple
|
more efficient. Nodelist flag is IBN, the default port is 24554, and the
|
||||||
batches, however this is only tested against another <strong>mbcico.</strong>
|
nodelist request flag is XX. This Binkp implementation supports multiple
|
||||||
I don't know if any other mailer supports this option, but it is documented
|
batches, however this is only tested against another <strong>mbcico.</strong>
|
||||||
in the spec's.
|
I don't know if any other mailer supports this option, but it is documented
|
||||||
<P>
|
in the spec's.
|
||||||
Outbound directory structure is BinkleyTerm compatible, with domains and
|
<P>
|
||||||
point subdirectories (full 5d). There are separate "protected" and
|
Outbound directory structure is BinkleyTerm compatible, with domains and
|
||||||
"unprotected" inbound directories for the incoming sessions with the nodes
|
point subdirectories (full 5d). There are separate "protected" and
|
||||||
that are in your setup. Files received during outbound sessions are always
|
"unprotected" inbound directories for the incoming sessions with the nodes
|
||||||
stored in the "protected" inbound.
|
that are in your setup. Files received during outbound sessions are always
|
||||||
<P>
|
stored in the "protected" inbound.
|
||||||
"Magic" file request processors are executable files placed in the "magic"
|
<P>
|
||||||
directory. If a request is made for a file with matching name, the
|
"Magic" file request processors are executable files placed in the "magic"
|
||||||
executable from the "magic" directory is run, and its stdout output is mailed
|
directory. If a request is made for a file with matching name, the
|
||||||
to the requestor. Full requestor's address, in the form of "John Smith of
|
executable from the "magic" directory is run, and its stdout output is mailed
|
||||||
1:234/56/7" is passed to the executable in the command line. Non-executable
|
to the requestor. Full requestor's address, in the form of "John Smith of
|
||||||
files in the magic directory contain the full names to magic filenames. The
|
1:234/56/7" is passed to the executable in the command line. Non-executable
|
||||||
magic NODELIST can thus point to the full path and filename of your latest
|
files in the magic directory contain the full names to magic filenames. The
|
||||||
nodelist. These magic names are automatic maintained by the <strong>mbfido</strong>
|
magic NODELIST can thus point to the full path and filename of your latest
|
||||||
program when the magic name is set in the .tic file that you receive.
|
nodelist. These magic names are automatic maintained by the <strong>mbfido</strong>
|
||||||
<P>
|
program when the magic name is set in the .tic file that you receive.
|
||||||
To run <strong>mbcico</strong> in master mode, you need to make dialout
|
<P>
|
||||||
devices read/writeable for <strong>mbcico</strong>, and do the same for
|
To run <strong>mbcico</strong> in master mode, you need to make dialout
|
||||||
the directory where your uucp locks are created (usually /var/locks).
|
devices read/writeable for <strong>mbcico</strong>, and do the same for
|
||||||
<P> <P>
|
the directory where your uucp locks are created (usually /var/locks).
|
||||||
|
<P> <P>
|
||||||
<h3>Answer Mode.</h3>
|
|
||||||
<P>
|
<h3>Answer Mode.</h3>
|
||||||
To make <strong>mbcico</strong> work in answer mode, you need <strong>
|
<P>
|
||||||
mgetty</strong> written by Gert Doering. <strong>mbcico</strong> must be
|
To make <strong>mbcico</strong> work in answer mode, you need <strong>
|
||||||
started with one of the following parameters:
|
mgetty</strong> written by Gert Doering. <strong>mbcico</strong> must be
|
||||||
<P><PRE>
|
started with one of the following parameters:
|
||||||
FTS-0001 call: "/opt/mbse/bin/mbcico tsync"
|
<P><PRE>
|
||||||
FTS-0006 call: "/opt/mbse/bin/mbcico yoohoo"
|
FTS-0001 call: "/opt/mbse/bin/mbcico tsync"
|
||||||
EMSI call: "/opt/mbse/bin/mbcico **EMSI_....."
|
FTS-0006 call: "/opt/mbse/bin/mbcico yoohoo"
|
||||||
</PRE><P>
|
EMSI call: "/opt/mbse/bin/mbcico **EMSI_....."
|
||||||
In the latter case the received EMSI packet should be passed whitout trailing
|
</PRE><P>
|
||||||
CR). To make this work <strong>mgetty</strong> must be compiled with the
|
In the latter case the received EMSI packet should be passed whitout trailing
|
||||||
-DFIDO option. Other getty programs might work.
|
CR). To make this work <strong>mgetty</strong> must be compiled with the
|
||||||
<P>
|
-DFIDO option. Other getty programs might work.
|
||||||
To answer TCP/IP calls the following lines should be added to /etc/inetd.conf:
|
<P>
|
||||||
<P><PRE>
|
To answer TCP/IP calls the following lines should be added to /etc/inetd.conf:
|
||||||
binkd stream tcp nowait mbse /opt/mbse/bin/mbcico mbcico -t ibn
|
<P><PRE>
|
||||||
tfido stream tcp nowait mbse /opt/mbse/bin/mbcico mbcico -t itn
|
binkd stream tcp nowait mbse /opt/mbse/bin/mbcico mbcico -t ibn
|
||||||
fido stream tcp nowait mbse /opt/mbse/bin/mbcico mbcico -t ifc
|
tfido stream tcp nowait mbse /opt/mbse/bin/mbcico mbcico -t itn
|
||||||
</PRE><P>
|
fido stream tcp nowait mbse /opt/mbse/bin/mbcico mbcico -t ifc
|
||||||
In the file /etc/services the following lines must be present:
|
</PRE><P>
|
||||||
<P><PRE>
|
If your system uses xinetd the file /etc/xinetd.d/mbsebbs could be:
|
||||||
binkd 24554/tcp # mbcico IBN mode
|
<P><PRE>
|
||||||
tfido 60177/tcp # mbcico ITN mode
|
#:MBSE BBS services are defined here.
|
||||||
fido 60179/tcp # mbcico IFC mode
|
|
||||||
mbse 60180/tcp # MBSE BBS deamon
|
service binkp
|
||||||
</PRE><P>
|
{
|
||||||
In this case I installed the ITN mode at port 60177 instead of 23 like most
|
socket_type = stream
|
||||||
sysops do.
|
protocol = tcp
|
||||||
<P> <P>
|
wait = no
|
||||||
|
user = mbse
|
||||||
|
instances = 10
|
||||||
<h3>Master Mode.</h3>
|
server = /opt/mbse/bin/mbcico
|
||||||
<P>
|
server_args = -t ibn
|
||||||
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
|
service tfido
|
||||||
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
|
socket_type = stream
|
||||||
<strong>poll</strong> request in the outbound. Be carefull.
|
protocol = tcp
|
||||||
The taskmanager <strong>mbtask</strong> will start calling <strong>mbcico -r1</strong>
|
wait = no
|
||||||
if it has seen the <b>scanout</b> semafore. After all calls are completed <b>mbcico</b>
|
user = mbse
|
||||||
will remove the <b>scanout</b> semafore.
|
instances = 10
|
||||||
During ZMH all non-compressed mail is send. File requests in the outbound do not
|
server = /opt/mbse/bin/mbcico
|
||||||
force calling a system. If you make a filerequest, you must also make a
|
server_args = -t itn
|
||||||
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
|
service fido
|
||||||
called a random dialdelay is used with each call except for internet calls.
|
{
|
||||||
<P> <P>
|
socket_type = stream
|
||||||
|
protocol = tcp
|
||||||
<h3>Environment.</H3>
|
wait = no
|
||||||
<P>
|
user = mbse
|
||||||
In order to run the mbcico you need to set one global environment variable
|
instances = 10
|
||||||
<strong>$MBSE_ROOT</strong>
|
server = /opt/mbse/bin/mbcico
|
||||||
This variable must point to the root of the bbs directoy structure.
|
server_args = -t ifc
|
||||||
<P> <P>
|
}
|
||||||
|
</PRE><P>
|
||||||
<H3>Return Codes.</H3>
|
In the file /etc/services the following lines must be present:
|
||||||
<P>
|
<P><PRE>
|
||||||
<pre>
|
binkd 24554/tcp # mbcico IBN mode
|
||||||
0 - No errors
|
tfido 60177/tcp # mbcico ITN mode
|
||||||
1..32 - Linux errors, SIGHUP, SIGKILL, etc.
|
fido 60179/tcp # mbcico IFC mode
|
||||||
101 - No dialout ports available.
|
mbse 60180/tcp # MBSE BBS deamon
|
||||||
102 - Dial failed (no CONNECT or TCP connection failed).
|
</PRE><P>
|
||||||
103 - Could not reset the modem (no OK).
|
In this case I installed the ITN mode at port 60177 instead of 23 like most
|
||||||
104 - System is locked.
|
sysops do.
|
||||||
105 - not used?
|
<P> <P>
|
||||||
106 - Nodelist lookup failed.
|
|
||||||
107 - Call prohibited by config options.
|
|
||||||
108 - Phone number unavailable.
|
<h3>Master Mode.</h3>
|
||||||
109 - No matching ports defined.
|
<P>
|
||||||
110 - Tried to call a CM system outside ZMH.
|
To make <strong>mbcico</strong> scan for pending outbound mail and do
|
||||||
111..129 - Session failures (not defined).
|
appropriate calls, start it with <strong>-r1</strong> flag. It will check
|
||||||
130 - Could not establish session, system is marked undialable.
|
for Zone Mail Hour, outside ZMH only crash mail is delivered. Mail to
|
||||||
</pre>
|
non-CM systems is only send when mail has the Immedidate status.
|
||||||
These codes are also stored in status files for nodes, with the extension
|
Poll request are always honnored, even to non-CM systems if there is a
|
||||||
of ".sts". These are small datafiles containing three decimal numbers.
|
<strong>poll</strong> request in the outbound. Be carefull.
|
||||||
<ol>
|
The taskmanager <strong>mbtask</strong> will start calling <strong>mbcico -r1</strong>
|
||||||
<li>Time retry code, this is the last call attempt time. This is an unsigned
|
if it has seen the <b>scanout</b> semafore. After all calls are completed <b>mbcico</b>
|
||||||
long representing the number of seconds since the epoch.
|
will remove the <b>scanout</b> semafore.
|
||||||
<li>Retries, this is the number of consequtive call attempts made that returned
|
During ZMH all non-compressed mail is send. File requests in the outbound do not
|
||||||
"call failed" or other errors. This field is zeroed when the call succeeds and
|
force calling a system. If you make a filerequest, you must also make a
|
||||||
when a new "poll" is created. If the value is 30, the node won't be called
|
poll for that node to really start the request. You can also force a call
|
||||||
anymore.
|
by entering <strong>mbcico f2802.n280.z2</strong> on the commandline.
|
||||||
<li>Code, this is the return code of the last attempt.
|
Only one call is made then and there is no dial delay. If <b>mbcico -r1</b> is
|
||||||
</ol>
|
called a random dialdelay is used with each call except for internet calls.
|
||||||
<p> <p>
|
<P><B>Note:</B> you should not call nodes with mbcico directly, let
|
||||||
|
<b>mbtask</b> do the calling.
|
||||||
<h3>Configuration.</H3>
|
If you want to call a node make a <a href="mbout.html">poll</a> command.
|
||||||
<P>
|
<P> <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
|
<h3>Environment.</H3>
|
||||||
that problem. This will produce huge logfiles, but also a lot of information.
|
<P>
|
||||||
Important flags are Device IO, EMSI debug, File forward, Locking, Outboundscan
|
In order to run the mbcico you need to set one global environment variable
|
||||||
and Session.
|
<strong>$MBSE_ROOT</strong>
|
||||||
<P> <P>
|
This variable must point to the root of the bbs directoy structure.
|
||||||
|
<P> <P>
|
||||||
<h3>Bugs.</H3>
|
|
||||||
<P>
|
<H3>Return Codes.</H3>
|
||||||
Incoming calls from McMail mailers, McMail is quite hasty
|
<P>
|
||||||
to establish an EMSI session, and times out in less than a second. So
|
<pre>
|
||||||
if your system is heavy loaded, or not too fast, McMail cannot connect
|
0 - No errors
|
||||||
with your system. This is a known problem with McMail 1.0 and older,
|
1..32 - Linux errors, SIGHUP, SIGKILL, etc.
|
||||||
later versions are ok.
|
101 - No dialout ports available.
|
||||||
<P> <P>
|
102 - Dial failed (no CONNECT or TCP connection failed).
|
||||||
|
103 - Could not reset the modem (no OK).
|
||||||
<H3>Authors.</H3>
|
104 - System is locked.
|
||||||
<P>
|
105 - not used?
|
||||||
<pre>
|
106 - Nodelist lookup failed.
|
||||||
Eugene G. Crosser <crosser@average.org> Orginal ifcico.
|
107 - Call prohibited by config options.
|
||||||
Stanislav Voronyi <stas@uanet.kharkov.ua> TCP/IP code.
|
108 - Phone number unavailable.
|
||||||
T. Tanaka Telnet mode.
|
109 - No matching ports defined.
|
||||||
Martin Junius Rewrite of opentcp().
|
110 - Tried to call a CM system outside ZMH.
|
||||||
Omen Technology Inc Zmodem protocol.
|
111..129 - Session failures (not defined).
|
||||||
Arjen G. Lentz, Joaquim H. Homrighausen Hydra transfer protocol.
|
130 - Could not establish session, system is marked undialable.
|
||||||
Cristof Meerwald Implementation of Hydra in ifcico.
|
</pre>
|
||||||
P. Saratxaga Tty driver code, yoohoo extensions.
|
These codes are also stored in status files for nodes, with the extension
|
||||||
Dima Maloff Binkp protocol.
|
of ".sts". These are small datafiles containing three decimal numbers.
|
||||||
Michiel Broek Rewrite for MBSE BBS.
|
<ol>
|
||||||
</pre>
|
<li>Time retry code, this is the last call attempt time. This is an unsigned
|
||||||
<P>
|
long representing the number of seconds since the epoch.
|
||||||
|
<li>Retries, this is the number of consequtive call attempts made that returned
|
||||||
<A HREF="index.htm"><IMG SRC="../images/larrow.gif" ALT="Index" Border="0" width="40" height="30"> Back to index</A>
|
"call failed" or other errors. This field is zeroed when the call succeeds and
|
||||||
<A HREF="../index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Main" Border="0" width="33" height="35"> Back to Main index</A>
|
when a new "poll" is created. If the value is 30, the node won't be called
|
||||||
</BLOCKQUOTE>
|
anymore.
|
||||||
</BODY>
|
<li>Code, this is the return code of the last attempt.
|
||||||
</HTML>
|
</ol>
|
||||||
|
<p> <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> <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> <P>
|
||||||
|
|
||||||
|
<H3>Authors.</H3>
|
||||||
|
<P>
|
||||||
|
<pre>
|
||||||
|
Eugene G. Crosser <crosser@average.org> Orginal ifcico.
|
||||||
|
Stanislav Voronyi <stas@uanet.kharkov.ua> 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>
|
||||||
|
<A HREF="../index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Main" Border="0">Back to Main index</A>
|
||||||
|
</BLOCKQUOTE>
|
||||||
|
</BODY>
|
||||||
|
</HTML>
|
||||||
|
|
||||||
|
|||||||
@ -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> <P>
|
|
||||||
|
|
||||||
<H1>mbfbgen - FileBase Generator</H1>
|
|
||||||
<P>
|
|
||||||
|
|
||||||
<H3>Synopsis.</H3>
|
|
||||||
<P>
|
|
||||||
<code><strong>mbfbgen</strong></code>
|
|
||||||
<P> <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> <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>
|
|
||||||
<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>
|
|
||||||
|
|
||||||
@ -1,260 +1,270 @@
|
|||||||
<HTML>
|
<HTML>
|
||||||
<HEAD>
|
<!-- $Id$ -->
|
||||||
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
|
<HEAD>
|
||||||
<META http-equiv="Content-Style-Type" content="text/css">
|
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
|
||||||
<META name="author" lang="en" "content="Michiel Broek">
|
<META http-equiv="Content-Style-Type" content="text/css">
|
||||||
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
<META name="author" lang="en" content="Michiel Broek">
|
||||||
<META name="description" lang="en" content="MBSE BBS Manual">
|
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
||||||
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
<META name="description" lang="en" content="MBSE BBS Manual">
|
||||||
<TITLE>MBSE BBS Programs - mbfido - The Fidonet mail and files processor.</TITLE>
|
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
||||||
<LINK rel=stylesheet HREF="../manual.css">
|
<TITLE>MBSE BBS Programs - mbfido - The Fidonet mail and files processor.</TITLE>
|
||||||
</HEAD>
|
<LINK rel=stylesheet HREF="../manual.css">
|
||||||
<BODY>
|
</HEAD>
|
||||||
<BLOCKQUOTE>
|
<BODY>
|
||||||
<h5>Last update 10-Jul-2001</h5>
|
<BLOCKQUOTE>
|
||||||
<P> <P>
|
<h5>Last update 21-Jan-2002</h5>
|
||||||
|
<P> <P>
|
||||||
<H1>mbfido, the fidonet mail and files processor.</H1>
|
|
||||||
<P>
|
<H1>mbfido, the fidonet mail and files processor.</H1>
|
||||||
|
<P>
|
||||||
<h3>Synopsis.</H3>
|
|
||||||
<P>
|
<h3>Synopsis.</H3>
|
||||||
<code>mbfido [command(s)] <options></code>
|
<P>
|
||||||
<P> <P>
|
<code>mbfido [command(s)] <options></code>
|
||||||
|
<P> <P>
|
||||||
<H3>Description.</H3>
|
|
||||||
<P>
|
<H3>Description.</H3>
|
||||||
<strong>mbfido</strong>
|
<P>
|
||||||
is the program to process fidonet mail and files. In order to run mbfido
|
<strong>mbfido</strong>
|
||||||
you must first start <strong>mbtask</strong>,
|
is the program to process fidonet mail and files. In order to run mbfido
|
||||||
this is the deamon which controls all bbs activities. To prevent that
|
you must first start <strong>mbtask</strong>,
|
||||||
<strong>mbfido</strong> will run more than once at the same time a lock
|
this is the deamon which controls all bbs activities. To prevent that
|
||||||
is placed in the protected inbound with the pid of the running
|
<strong>mbfido</strong> will run more than once at the same time a lock
|
||||||
<strong>mbfido</strong> program. The gateway to and from internet is also
|
is placed in the protected inbound with the pid of the running
|
||||||
handled by <strong>mbfido</strong>.
|
<strong>mbfido</strong> program. The gateway to and from internet is also
|
||||||
<P> <P>
|
handled by <strong>mbfido</strong>.
|
||||||
|
<P> <P>
|
||||||
<H3>Specifications.</H3>
|
|
||||||
<p>
|
<H3>Specifications.</H3>
|
||||||
The recognized mail packets are type 2+ following the FSC-0039 standard with
|
<p>
|
||||||
a fallback to the old stone age packets.
|
The recognized mail packets are type 2+ following the FSC-0039 standard with
|
||||||
Can handle messages of maximum 429467295 bytes, or less if you have less
|
a fallback to the old stone age packets.
|
||||||
memory available, the practical limit is about 1 Meg. Note that most mailprocessors
|
Can handle messages of maximum 429467295 bytes, or less if you have less
|
||||||
are only guaranteed to work to maximum 16 KBytes.
|
memory available, the practical limit is about 1 Meg. Note that most mailprocessors
|
||||||
Recent experiments in the LINUX echo show that this is still true,
|
are only guaranteed to work to maximum 16 KBytes.
|
||||||
although most tossers seem to process mail up to 32 KBytes.
|
Recent experiments in the LINUX echo show that this is still true,
|
||||||
<P> <P>
|
although most tossers seem to process mail up to 32 KBytes.
|
||||||
|
<P> <P>
|
||||||
<H3>Tossing Mail.</H3>
|
|
||||||
<P>
|
<H3>Tossing Mail.</H3>
|
||||||
First make sure you have the necessary message areas in your setup. At least
|
<P>
|
||||||
you need the badmail and dupemail areas and a netmail area for each network
|
First make sure you have the necessary message areas in your setup. At least
|
||||||
you participate in. If you don't create badmail and dupemail areas then
|
you need the badmail and dupemail areas and a netmail area for each network
|
||||||
bad (unknown area etc) and dupes are lost and you cannot check the reason why.
|
you participate in. If you don't create badmail and dupemail areas then
|
||||||
If you don't create the netmail areas for each network, then netmail to your
|
bad (unknown area etc) and dupes are lost and you cannot check the reason why.
|
||||||
system will dissapear. It is not possible to "retoss" the badmail yet after
|
If you don't create the netmail areas for each network, then netmail to your
|
||||||
you have created any missing echomail areas.
|
system will dissapear. It is not possible to "retoss" the badmail yet after
|
||||||
<P>
|
you have created any missing echomail areas.
|
||||||
To prevent .pkt name collision the toss of incoming mail is done in parts.
|
<P>
|
||||||
The first run is to process all uncompressed mailpackets and add mail to the
|
To prevent .pkt name collision the toss of incoming mail is done in parts.
|
||||||
outbound. Then each compressed ARCmail archive will be uncompressed and
|
The first run is to process all uncompressed mailpackets and add mail to the
|
||||||
processed and mail will be imported and forwarded as necessary. During all
|
outbound. Then each compressed ARCmail archive will be uncompressed and
|
||||||
these passes all filenames are sorted by date and time, the oldest files are
|
processed and mail will be imported and forwarded as necessary. During all
|
||||||
processed first.
|
these passes all filenames are sorted by date and time, the oldest files are
|
||||||
<P>
|
processed first.
|
||||||
The recognized mail packets are type 2+ following the FSC-0039 standard with
|
<P>
|
||||||
a fallback to the old stone age packets. The packets are checked for being
|
The recognized mail packets are type 2+ following the FSC-0039 standard with
|
||||||
addressed to one of your own aka's and for a correct password. The
|
a fallback to the old stone age packets. The packets are checked for being
|
||||||
password check may be switched off in the nodes setup. After all the packet
|
addressed to one of your own aka's and for a correct password. The
|
||||||
header checks the messages will be extracted from the packet file.
|
password check may be switched off in the nodes setup. After all the packet
|
||||||
<P>
|
header checks the messages will be extracted from the packet file.
|
||||||
When messages are extracted from the packets, the date format is checked for
|
<P>
|
||||||
Year2000 bugs from other tossers. Several checks are done by ideas of Tobias
|
When messages are extracted from the packets, the date format is checked for
|
||||||
Ernst of 2:2476/418. It is also possible to run the <strong>pktdate</strong>
|
Year2000 bugs from other tossers. Several checks are done by ideas of Tobias
|
||||||
utility before each packet will be processed. Whatever date format us used in
|
Ernst of 2:2476/418. It is also possible to run the <strong>pktdate</strong>
|
||||||
the original message, <strong>mbfido</strong> will always rewrite the date
|
utility before each packet will be processed. Whatever date format us used in
|
||||||
field in the right FTS-0001 format.
|
the original message, <strong>mbfido</strong> will always rewrite the date
|
||||||
<P>
|
field in the right FTS-0001 format.
|
||||||
If the message is a netmail the message is checked for DOMAIN, INTL, FMPT and
|
<P>
|
||||||
TOPT kludges so that full 4d or 5d addressing will be possible. Then a check
|
If the message is a netmail the message is checked for DOMAIN, INTL, FMPT and
|
||||||
is done if this netmail is addressed to one of our aka's. If it's addressed to
|
TOPT kludges so that full 4d or 5d addressing will be possible. Then a check
|
||||||
"sysop" or "postmaster" the name is replaced with the sysop's name. If the
|
is done if this netmail is addressed to one of our aka's. If it's addressed to
|
||||||
message is addressed to one of the names defined in the service setup, that
|
"sysop" or "postmaster" the name is replaced with the sysop's name. If the
|
||||||
mail will be handled by the service manager, ie. given to areamgr, filemgr or
|
message is addressed to one of the names defined in the service setup, that
|
||||||
send further as email to your local system.
|
mail will be handled by the service manager, ie. given to areamgr, filemgr or
|
||||||
<BR>
|
send further as email to your local system.
|
||||||
Then the message is checked if it is addressed to an existing bbs user, and if
|
<BR>
|
||||||
so it will be imported into the netmail area of the main zone of the bbs.
|
Then the message is checked if it is addressed to an existing bbs user, and if
|
||||||
If it's not addressed to a bbs user, the message will be readdressed to the
|
so it will be imported into the netmail area of the main zone of the bbs.
|
||||||
sysop. If the message is not for one of our aka's the message will be put in the
|
If it's not addressed to a bbs user, the message will be readdressed to the
|
||||||
mailqueue for further routing.
|
sysop. If the message is not for one of our aka's the message will be put in the
|
||||||
<P>
|
mailqueue for further routing.
|
||||||
If the message is a echomail message it will be checked for being a duplicate by
|
<P>
|
||||||
storing the CRC32 value of the AREA: line, message subject, origin line,
|
If the message is a echomail message it will be checked for being a duplicate by
|
||||||
message date and msgid kludge and testing if that CRC32 value exists in the
|
storing the CRC32 value of the AREA: line, message subject, origin line,
|
||||||
echomail duplicate database. If there is no msgid in the message, the whole
|
message date and msgid kludge and testing if that CRC32 value exists in the
|
||||||
message body will be include to complete the CRC32 dupe check.
|
echomail duplicate database. If there is no msgid in the message, the whole
|
||||||
Also the existance of the echomail area is checked and the node must be linked to that area.
|
message body will be include to complete the CRC32 dupe check.
|
||||||
If the message is not in a passthru area and is not a duplicate it
|
Also the existance of the echomail area is checked and the node must be linked to that area.
|
||||||
is finally imported in the message base.
|
If the message is not in a passthru area and is not a duplicate it
|
||||||
After that is the message will be forwarded to downlinks
|
is finally imported in the message base.
|
||||||
by adding the message to the mailqueue.
|
After that is the message will be forwarded to downlinks
|
||||||
<P> <P>
|
by adding the message to the mailqueue.
|
||||||
|
<P> <P>
|
||||||
<h3>Adding mail to the outbound.</h3>
|
|
||||||
<P>
|
<h3>Adding mail to the outbound.</h3>
|
||||||
Adding mail to the outbound is done in two passes. The first pass is to put all
|
<P>
|
||||||
outgoing mail into the ~/tmp directory, these files are named z.n.n.p.ext
|
Adding mail to the outbound is done in two passes. The first pass is to put all
|
||||||
The extension can be qqq for packed mail, nnn for normal unpacked mail, hhh for
|
outgoing mail into the ~/tmp directory, these files are named z.n.n.p.ext
|
||||||
hold unpacked mail and ccc for crash unpacked mail. Adding mail to this tmp
|
The extension can be qqq for packed mail, nnn for normal unpacked mail, hhh for
|
||||||
directory can allways be done, even if one of the nodes you are adding mail
|
hold unpacked mail and ccc for crash unpacked mail. Adding mail to this tmp
|
||||||
for is having a mail session with your system. This is a safe operation.<br>
|
directory can allways be done, even if one of the nodes you are adding mail
|
||||||
In the second pass, these temp files are really added to the outbound, but
|
for is having a mail session with your system. This is a safe operation.<br>
|
||||||
only if the destination node is not locked, ie. there is no current mailsession
|
In the second pass, these temp files are really added to the outbound, but
|
||||||
with that node. If there is a mail session going, these temp files will stay in
|
only if the destination node is not locked, ie. there is no current mailsession
|
||||||
the temp directory and are added to the outbound in a later run of
|
with that node. If there is a mail session going, these temp files will stay in
|
||||||
<strong>mbfido</strong>. If adding the mail to the outbound succeeds
|
the temp directory and are added to the outbound in a later run of
|
||||||
the temporary file is removed.
|
<strong>mbfido</strong>. If adding the mail to the outbound succeeds
|
||||||
<P> <P>
|
the temporary file is removed.
|
||||||
|
<P> <P>
|
||||||
<H3>Alias file.</H3>
|
|
||||||
<P>
|
<H3>Alias file.</H3>
|
||||||
If the file /opt/mbse/etc/aliases exists, mbfido will try to fetch ftn-style
|
<P>
|
||||||
aliases from there.
|
If the file /opt/mbse/etc/aliases exists, mbfido will try to fetch ftn-style
|
||||||
If "from" address of a message from FidoNet matches <b>right</b> side
|
aliases from there.
|
||||||
of some entry in alias file, then the Reply-To: header is created
|
If "from" address of a message from FidoNet matches <b>right</b> side
|
||||||
in the RFC message with the name part taken from the left side of the
|
of some entry in alias file, then the Reply-To: header is created
|
||||||
sysalis entry and domain part taken from myfqdn (below). E.g., if a
|
in the RFC message with the name part taken from the left side of the
|
||||||
fidonet message comes from "John Smith of 1:234/567.89@fidonet" and
|
sysalis entry and domain part taken from myfqdn (below). E.g., if a
|
||||||
there is an entry in the sysalias file:
|
fidonet message comes from "John Smith of 1:234/567.89@fidonet" and
|
||||||
<pre>
|
there is an entry in the sysalias file:
|
||||||
"jsmith: John.Smith@p89.f567.n234.z1.fidonet.org"
|
<pre>
|
||||||
</pre>
|
"jsmith: John.Smith@p89.f567.n234.z1.fidonet.org"
|
||||||
and Domain name value is "mbse.nl", then the resulting message will
|
</pre>
|
||||||
contain a line: "Reply-To: jsmith@mbse.nl".
|
and Domain name value is "mbse.nl", then the resulting message will
|
||||||
<P> <P>
|
contain a line: "Reply-To: jsmith@mbse.nl".
|
||||||
|
<P> <P>
|
||||||
<H3>Commands.</H3>
|
|
||||||
<P>
|
<H3>Commands.</H3>
|
||||||
<code><strong>mbfido</strong> notify <nodes></code>
|
<P>
|
||||||
This command will send notify messages to all nodes in your setup which
|
<code><strong>mbfido</strong> mail <recipient></code>
|
||||||
have the notify option set to on. If you enter nodes as option you may use
|
This command is used by your MTA to deliver email addressed to for example
|
||||||
wilcards, ie 2:*/* to send messages to all nodes in zone 2. If you specify
|
Michiel_Broek@f2802.n280.z2.fidonet.org
|
||||||
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
|
<P>
|
||||||
just send to all your links the information about their setup. Each node
|
<code><strong>mbmail</strong> <recipient></code>
|
||||||
will receive a status report for files and mail, and area list for all
|
This is the same as above.
|
||||||
file areas and mail areas to each aka a node has, and a flow report for
|
|
||||||
mail for each aka.
|
<P>
|
||||||
<P>
|
<code><strong>mbfido</strong> notify <nodes></code>
|
||||||
<code><strong>mbfido</strong> roll</code>
|
This command will send notify messages to all nodes in your setup which
|
||||||
This command will only do something if a new week or month has begun.
|
have the notify option set to on. If you enter nodes as option you may use
|
||||||
If this is true the statistic records in several databases are updated.
|
wilcards, ie 2:*/* to send messages to all nodes in zone 2. If you specify
|
||||||
You should run this command each midnight from cron to be sure that this when it is
|
exactly one node, messages will be generated even if that node has the
|
||||||
time to do so. This command is always executed before one of the scan, toss or tic commands so
|
notify function off. From cron you should not specify any nodes, this will
|
||||||
if you don't do this in cron, it will still happen.
|
just send to all your links the information about their setup. Each node
|
||||||
<P>
|
will receive a status report for files and mail, and area list for all
|
||||||
<code><strong>mbfido</strong> scan</code>
|
file areas and mail areas to each aka a node has, and a flow report for
|
||||||
Scan for new messages entered at the bbs or by other utilities. If the file
|
mail for each aka.
|
||||||
~/tmp/echomail.jam or ~/tmp/netmail.jam exists,
|
<P>
|
||||||
mbfido will only scan the messages in areas which are
|
<code><strong>mbfido</strong> roll</code>
|
||||||
pointed at in this file. This is a lot faster then a full mailscan.
|
This command will only do something if a new week or month has begun.
|
||||||
If it is not present, all messagebases are scanned
|
If this is true the statistic records in several databases are updated.
|
||||||
to see if there is a new message. If you specify
|
You should run this command each midnight from cron to be sure that this when it is
|
||||||
<strong>-full</strong> on the commandline a full messagebase scan is forced.
|
time to do so. This command is always executed before one of the scan, toss or tic commands so
|
||||||
It is wise to do this sometimes, on my bbs I run this once a day.
|
if you don't do this in cron, it will still happen.
|
||||||
<P>
|
<P>
|
||||||
<code><strong>mbfido</strong> tag</code>
|
<code><strong>mbfido</strong> scan</code>
|
||||||
The command will create tag- and areas files in the doc directory for each group of
|
Scan for new messages entered at the bbs or by other utilities. If the file
|
||||||
mail and files.
|
~/tmp/echomail.jam or ~/tmp/netmail.jam exists,
|
||||||
<P>
|
mbfido will only scan the messages in areas which are
|
||||||
<code><strong>mbfido</strong> test</code>
|
pointed at in this file. This is a lot faster then a full mailscan.
|
||||||
This is for testing of the mail routing. In the source "tracker.c" I have
|
If it is not present, all messagebases are scanned
|
||||||
included a list of nodes that will be tested. This is for development only,
|
to see if there is a new message. If you specify
|
||||||
but it might be handy for you to test your netmail routing.
|
<strong>-full</strong> on the commandline a full messagebase scan is forced.
|
||||||
<P>
|
It is wise to do this sometimes, on my bbs I run this once a day.
|
||||||
<code><strong>mbfido</strong> tic</code>
|
<P>
|
||||||
Process incoming files accompanied with .tic control files. Several actions can
|
<code><strong>mbfido</strong> tag</code>
|
||||||
take place on the incoming file before they are imported in the BBS areas.
|
The command will create tag- and areas files in the doc directory for each group of
|
||||||
Options are rearchiving, replacing banners (with your add), check for DOS
|
mail and files.
|
||||||
viruses, running scripts for certain filename patterns, send these files to
|
<P>
|
||||||
other nodes etc. All options can be defined for each area. If as a result from
|
<code><strong>mbfido</strong> test</code>
|
||||||
one of the actions there are new files hatched, for example after processing
|
This is for testing of the mail routing. In the source "tracker.c" I have
|
||||||
a nodelist difference file which created a new nodelist, the .tic processing
|
included a list of nodes that will be tested. This is for development only,
|
||||||
will start again, until there is really nothing more to do.
|
but it might be handy for you to test your netmail routing.
|
||||||
<P>
|
<P>
|
||||||
<code><strong>mbfido</strong> toss</code>
|
<code><strong>mbfido</strong> tic</code>
|
||||||
Toss incoming fidonet netmail and or echomail. By default mail in the protected
|
Process incoming files accompanied with .tic control files. Several actions can
|
||||||
inbound directory will be processed, uncompressed .pkt files and compressed
|
take place on the incoming file before they are imported in the BBS areas.
|
||||||
arcmail bundles are recognized, filename case doesn't matter.
|
Options are rearchiving, replacing banners (with your add), check for DOS
|
||||||
<P>
|
viruses, running scripts for certain filename patterns, send these files to
|
||||||
<code><b>mbfido</b> news</code> Scan all defined newsgroups for new newsarticles.
|
other nodes etc. All options can be defined for each area. If as a result from
|
||||||
New articles are fetched from the newsserver and stored in your messagebase and
|
one of the actions there are new files hatched, for example after processing
|
||||||
send to your up- and downlinks. This is for use with an NNTP gateway.
|
a nodelist difference file which created a new nodelist, the .tic processing
|
||||||
<P>
|
will start again, until there is really nothing more to do.
|
||||||
<code><strong>mbfido</strong> uucp</code>
|
<P>
|
||||||
This will read a standard a newsbatch from stdin and gate the articles
|
<code><strong>mbfido</strong> toss</code>
|
||||||
to Fidonet and the local message base. This is for use with an UUCP gateway, this
|
Toss incoming fidonet netmail and or echomail. By default mail in the protected
|
||||||
mode should be called by uuxqt. The newsbatch may be compressed or uncompressed or
|
inbound directory will be processed, uncompressed .pkt files and compressed
|
||||||
a single news article.
|
arcmail bundles are recognized, filename case doesn't matter.
|
||||||
<P>
|
<P>
|
||||||
<code><strong>mbnews</strong></code>
|
<code><b>mbfido</b> news</code> Scan all defined newsgroups for new newsarticles.
|
||||||
This is an alternative to <strong>mbfido uucp -quiet</strong>.
|
New articles are fetched from the newsserver and stored in your messagebase and
|
||||||
<P> <P>
|
send to your up- and downlinks. This is for use with an NNTP gateway.
|
||||||
|
<P>
|
||||||
<h3>Options.</h3>
|
<code><strong>mbfido</strong> uucp</code>
|
||||||
<P>
|
This will read a standard a newsbatch from stdin and gate the articles
|
||||||
<code><strong>mbfido</strong> [command] -nocrc</code>
|
to Fidonet and the local message base. This is for use with an UUCP gateway, this
|
||||||
Disable CRC checking of incoming TIC files. Only use this if you know what
|
mode should be called by uuxqt. The newsbatch may be compressed or uncompressed or
|
||||||
you are doing.
|
a single news article.
|
||||||
<P>
|
<P>
|
||||||
<code><strong>mbfido</strong> scan -full</code>
|
<code><strong>mbnews</strong></code>
|
||||||
Force scanning of all message bases for new entered mail. You need this if
|
This is an alternative to <strong>mbfido uucp -quiet</strong>.
|
||||||
mail in entered with other editors then from mbse. Also, running it once a
|
<P> <P>
|
||||||
day is adviced to catch any missed messages.
|
|
||||||
<P>
|
<h3>Options.</h3>
|
||||||
<code><strong>mbfido</strong> news -learn</code>
|
<P>
|
||||||
Scan the newsserver for news articles, and update the news dupes database only.
|
<code><strong>mbfido</strong> [command] -nocrc</code>
|
||||||
Use this switch if you start using mbfido to gate news articles for the first time.
|
Disable CRC checking of incoming TIC files. Only use this if you know what
|
||||||
Articles will not be gated with this switch, mbfido will just learn which articles
|
you are doing.
|
||||||
already exist. Normally you only need to use this switch once.
|
<P>
|
||||||
<P>
|
<code><strong>mbfido</strong> scan -full</code>
|
||||||
<code><strong>mbfido</strong> [command] -nodupe</code>
|
Force scanning of all message bases for new entered mail. You need this if
|
||||||
Disable checking for duplicate's. Normally you should not use this switch.
|
mail in entered with other editors then from mbse. Also, running it once a
|
||||||
This switch doesn't work with the news command, only for echomail and tic files.
|
day is adviced to catch any missed messages.
|
||||||
<P>
|
<P>
|
||||||
<code><strong>mbfido</strong> [command] -quiet</code>
|
<code><strong>mbfido</strong> news -learn</code>
|
||||||
Quiet mode, all output to the current tty is supressed. Use this flag if
|
Scan the newsserver for news articles, and update the news dupes database only.
|
||||||
you toss mail from a script (started by cron) after mail is received.
|
Use this switch if you start using mbfido to gate news articles for the first time.
|
||||||
<P>
|
Articles will not be gated with this switch, mbfido will just learn which articles
|
||||||
<code><strong>mbfido</strong> toss -a</code> Toss mail and allow to autocreate
|
already exist. Normally you only need to use this switch once.
|
||||||
new message areas. See the <A HREF="../setup/emareas.html"> message area setup</A>
|
<P>
|
||||||
how to set this up.
|
<code><strong>mbfido</strong> [command] -nodupe</code>
|
||||||
<code><strong>mbfido</strong> toss -unsecure</code>
|
Disable checking for duplicate's. Normally you should not use this switch.
|
||||||
Toss mail without checking if the echomail is for your own system en without
|
This switch doesn't work with the news command, only for echomail and tic files.
|
||||||
checking if the sending node is connected to your system. Nodes who are
|
<P>
|
||||||
excluded from a certain echo, can stil not enter messages in that echo.
|
<code><strong>mbfido</strong> [command] -quiet</code>
|
||||||
<P>
|
Quiet mode, all output to the current tty is supressed. Use this flag if
|
||||||
<code><strong>mbfido</strong> [command] -unprotect</code>
|
you toss mail from a script (started by cron) after mail is received.
|
||||||
Toss from the unprotected inbound directory. The default is to toss from the
|
<P>
|
||||||
protected inbound directory.
|
<code><strong>mbfido</strong> toss -a</code> Toss mail and allow to autocreate
|
||||||
<P> <P>
|
new message areas. See the <A HREF="../setup/emareas.html"> message area setup</A>
|
||||||
|
how to set this up.
|
||||||
<h3>Environment.</H3>
|
<code><strong>mbfido</strong> toss -unsecure</code>
|
||||||
<P>
|
Toss mail without checking if the echomail is for your own system en without
|
||||||
In order to run the bbs you need to set one global environment variable
|
checking if the sending node is connected to your system. Nodes who are
|
||||||
<strong>$MBSE_ROOT</strong>
|
excluded from a certain echo, can stil not enter messages in that echo.
|
||||||
This variable must point to the root of the bbs directoy structure.
|
<P>
|
||||||
<P> <P>
|
<code><strong>mbfido</strong> [command] -unprotect</code>
|
||||||
|
Toss from the unprotected inbound directory. The default is to toss from the
|
||||||
<h3>Bugs.</H3>
|
protected inbound directory.
|
||||||
<P>
|
<P> <P>
|
||||||
There are still bugs, this program is under development.
|
|
||||||
<P>
|
<h3>Environment.</H3>
|
||||||
|
<P>
|
||||||
<A HREF="index.htm"><IMG SRC="../images/larrow.gif" ALT="Index" Border="0" width="40" height="30"> Back to index</A>
|
In order to run the bbs you need to set one global environment variable
|
||||||
<A HREF="../index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Main" Border="0" width="33" height="35"> Back to Main index</A>
|
<strong>$MBSE_ROOT</strong>
|
||||||
</BLOCKQUOTE>
|
This variable must point to the root of the bbs directoy structure.
|
||||||
</BODY>
|
<P> <P>
|
||||||
</HTML>
|
|
||||||
|
<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>
|
||||||
|
<A HREF="../index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Main" Border="0">Back to Main index</A>
|
||||||
|
</BLOCKQUOTE>
|
||||||
|
</BODY>
|
||||||
|
</HTML>
|
||||||
|
|
||||||
|
|||||||
@ -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> <P>
|
|
||||||
|
|
||||||
<H1>mbmail - Mail User Agent for the email gate.</H1>
|
|
||||||
<P>
|
|
||||||
|
|
||||||
<H3>Synopsys.</H3>
|
|
||||||
<code><strong>mbmail</strong> -r<addr> -g<grade> -c<charset> -b <recip></code>
|
|
||||||
<P> <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<addr> -g<grade> -c<charset> -b <recip></code>
|
|
||||||
The -r<addr> 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<grade> is the packet flavor. This
|
|
||||||
can be one of the characters n, c or h which means normal, crash or hold. The -c<charset> will
|
|
||||||
force a certain characterset. Normally this will be automatic set. The -b switch disables splitting
|
|
||||||
of long messages. The <recip> 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>
|
|
||||||
<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>
|
|
||||||
|
|
||||||
@ -1,4 +1,5 @@
|
|||||||
<HTML>
|
<HTML>
|
||||||
|
<!-- $Id$ -->
|
||||||
<HEAD>
|
<HEAD>
|
||||||
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
|
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
|
||||||
<META http-equiv="Content-Style-Type" content="text/css">
|
<META http-equiv="Content-Style-Type" content="text/css">
|
||||||
@ -11,7 +12,7 @@
|
|||||||
</HEAD>
|
</HEAD>
|
||||||
<BODY>
|
<BODY>
|
||||||
<BLOCKQUOTE>
|
<BLOCKQUOTE>
|
||||||
<h5>Last update 07-Jan-2002</h5>
|
<h5>Last update 21-Jan-2002</h5>
|
||||||
<P> <P>
|
<P> <P>
|
||||||
|
|
||||||
<H1>mbpasswd - The password wrapper.</H1>
|
<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.
|
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>
|
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
|
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.
|
program and if you do, the password for a user are not in sync anymore.
|
||||||
<P> <P>
|
<P> <P>
|
||||||
|
|
||||||
|
|||||||
@ -1,8 +1,9 @@
|
|||||||
<HTML>
|
<HTML>
|
||||||
|
<!-- $Id$ -->
|
||||||
<HEAD>
|
<HEAD>
|
||||||
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
|
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
|
||||||
<META http-equiv="Content-Style-Type" content="text/css">
|
<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="copyright" lang="en" content="Copyright Michiel Broek">
|
||||||
<META name="description" lang="en" content="MBSE BBS Manual">
|
<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">
|
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
||||||
@ -11,7 +12,7 @@
|
|||||||
</HEAD>
|
</HEAD>
|
||||||
<BODY>
|
<BODY>
|
||||||
<BLOCKQUOTE>
|
<BLOCKQUOTE>
|
||||||
<h5>Last update 09-Nov-2001</h5>
|
<h5>Last update 21-Jan-2002</h5>
|
||||||
<P> <P>
|
<P> <P>
|
||||||
|
|
||||||
<H1>mbsebbs - The main BBS program</H1>
|
<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,
|
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.
|
unless you have turned this feature off in the setup.
|
||||||
<P>
|
<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.
|
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.
|
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
|
If the users Date of Birth is invalid, he is forced to enter the right
|
||||||
Date of Birth.
|
Date of Birth.
|
||||||
The next check is to see if the user has passed the expiry date, this is a
|
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
|
If the environment variable <strong>CALLER_ID</strong> is present, a log entry
|
||||||
will be made with the caller id.
|
will be made with the caller id.
|
||||||
<P>
|
<P>
|
||||||
If the environment variable <strong>LOGNAME</strong> is present and it is not
|
The environment variable <strong>LOGNAME</strong> must contain the unix
|
||||||
<strong>bbs</strong> then it is assumed that it is a Unixmode login of the
|
username. This is set by the <b>mblogin</b> program.
|
||||||
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>.
|
|
||||||
<P> <P>
|
<P> <P>
|
||||||
|
|
||||||
|
|
||||||
<A HREF="index.htm"><IMG SRC="../images/larrow.gif" ALT="Index" Border="0" width="40" height="30"> Back to index</A>
|
<A HREF="index.htm"><IMG SRC="../images/larrow.gif" ALT="Index" Border="0">Back to index</A>
|
||||||
<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/b_arrow.gif" ALT="Main" Border="0">Back to Main index</A>
|
||||||
</BLOCKQUOTE>
|
</BLOCKQUOTE>
|
||||||
</BODY>
|
</BODY>
|
||||||
</HTML>
|
</HTML>
|
||||||
|
|||||||
@ -1,164 +1,167 @@
|
|||||||
<HTML>
|
<HTML>
|
||||||
<HEAD>
|
<!-- $Id$ -->
|
||||||
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
|
<HEAD>
|
||||||
<META http-equiv="Content-Style-Type" content="text/css">
|
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
|
||||||
<META name="author" lang="en" "content="Michiel Broek">
|
<META http-equiv="Content-Style-Type" content="text/css">
|
||||||
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
<META name="author" lang="en" content="Michiel Broek">
|
||||||
<META name="description" lang="en" content="MBSE BBS Manual">
|
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
||||||
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
<META name="description" lang="en" content="MBSE BBS Manual">
|
||||||
<TITLE>MBSE BBS Setup - Mail Setup - Mail Areas.</TITLE>
|
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
||||||
<LINK rel=stylesheet HREF="../manual.css">
|
<TITLE>MBSE BBS Setup - Mail Setup - Mail Areas.</TITLE>
|
||||||
</HEAD>
|
<LINK rel=stylesheet HREF="../manual.css">
|
||||||
<BODY>
|
</HEAD>
|
||||||
<BLOCKQUOTE>
|
<BODY>
|
||||||
<h5>Last update 08-Jun-2001</h5>
|
<BLOCKQUOTE>
|
||||||
<P> <P>
|
<h5>Last update 21-Jan-2002</h5>
|
||||||
|
<P> <P>
|
||||||
<H1>MBSE BBS Setup - Mail Setup -> Mail Areas.</H1>
|
|
||||||
<P>
|
<H1>MBSE BBS Setup - Mail Setup -> Mail Areas.</H1>
|
||||||
|
<P>
|
||||||
<H3>Introduction.</H3>
|
|
||||||
<P>
|
<H3>Introduction.</H3>
|
||||||
Mail areas have fixed area numbers, just like file areas. But if you want you
|
<P>
|
||||||
can move areas.
|
Mail areas have fixed area numbers, just like file areas. But if you want you
|
||||||
Some offline readers don't like changing the area numbers. All areas can
|
can move areas.
|
||||||
be of the following types: local, netmail, echomail and news. If you gate
|
Some offline readers don't like changing the area numbers. All areas can
|
||||||
news and echomail in the same area, then select echomail
|
be of the following types: local, netmail, echomail and news. If you gate
|
||||||
if this area is a Fidonet area, select news if this area is a Usenet news area.
|
news and echomail in the same area, then select echomail
|
||||||
<P>
|
if this area is a Fidonet area, select news if this area is a Usenet news area.
|
||||||
There is a global setup tool, if you are in the main message area setup screen then
|
<P>
|
||||||
you can choose the Global command. This will allow you to do bulk changes on areas
|
There is a global setup tool, if you are in the main message area setup screen then
|
||||||
selected by the mail groups. Options are delete connection, add new connection,
|
you can choose the Global command. This will allow you to do bulk changes on areas
|
||||||
replace connection, change connection status, change days old for purge, change
|
selected by the mail groups. Options are delete connection, add new connection,
|
||||||
maximum messages for purge, change user security, change aka to use, change origin line,
|
replace connection, change connection status, change days old for purge, change
|
||||||
change netmail reply board and delete message area.
|
maximum messages for purge, change user security, change aka to use, change origin line,
|
||||||
<P> <P>
|
change netmail reply board and delete message area.
|
||||||
|
<P> <P>
|
||||||
<H3>Message Area Setup.</H3>
|
|
||||||
<P>
|
<H3>Message Area Setup.</H3>
|
||||||
<pre>
|
<P>
|
||||||
<strong>Area Name </strong>The description of the area.
|
<pre>
|
||||||
<strong>Area Tag </strong>The echomail area tag.
|
<strong>Area Name </strong>The description of the area.
|
||||||
<strong>Newsgroup </strong>The newsgroup name if you are gating this area.
|
<strong>Area Tag </strong>The echomail area tag.
|
||||||
<strong>Moderator </strong>Leave this blank for now!
|
<strong>Newsgroup </strong>The newsgroup name if you are gating this area.
|
||||||
<strong>JAM base </strong>The path and name of the JAM message base without extension.
|
<strong>Moderator </strong>Leave this blank for now!
|
||||||
<strong>Origin </strong>The origin line to add to echomail messages.
|
<strong>JAM base </strong>The path and name of the JAM message base without extension.
|
||||||
<strong>Fido Aka </strong>The Fidonet aka for this area.
|
<strong>Origin </strong>The origin line to add to echomail messages.
|
||||||
<strong>QWK name </strong>The name of the area for OffLine Readers.
|
<strong>Fido Aka </strong>The Fidonet aka for this area.
|
||||||
<strong>Group </strong>The name of the echomail group.
|
<strong>QWK name </strong>The name of the area for OffLine Readers.
|
||||||
<strong>Distrib. </strong>Leave this blank for now!
|
<strong>Group </strong>The name of the echomail group.
|
||||||
<strong>Area Type </strong>Local, Netmail, Echomail or News.
|
<strong>Distrib. </strong>Leave this blank for now!
|
||||||
<strong>Msg Kinds </strong>Private/Public, Private, Public, Read Only, FTN moderated, Usenet Moderated
|
<strong>Area Type </strong>Local, Netmail, Echomail or News.
|
||||||
<strong>FTN chars </strong>FTN characterset, not in use yet, defaults to IBMPC 2
|
<strong>Msg Kinds </strong>Private/Public, Private, Public, Read Only, FTN moderated, Usenet Moderated
|
||||||
<strong>RFC chars </strong>RFC characterset, not in use yet, defaults tp LATIN-1 2
|
<strong>FTN chars </strong>FTN characterset, not in use yet, defaults to IBMPC 2
|
||||||
<strong>Days Old </strong>The maximum age of the messages before purging.
|
<strong>RFC chars </strong>RFC characterset, not in use yet, defaults tp LATIN-1 2
|
||||||
<strong>Max. Msgs </strong>The maximum messages in this area.
|
<strong>Days Old </strong>The maximum age of the messages before purging.
|
||||||
<strong>Netreply </strong>Netmail reply area if this is echomail.
|
<strong>Max. Msgs </strong>The maximum messages in this area.
|
||||||
<strong>Active </strong>If this area is active.
|
<strong>Articles </strong>The maximum news headers to fetch.
|
||||||
<strong>User Del. </strong>Users may delete their own messages.
|
<strong>Netreply </strong>Netmail reply area if this is echomail.
|
||||||
<strong>Read Sec. </strong>The security level to read messages.
|
<strong>Active </strong>If this area is active.
|
||||||
<strong>Write Sec. </strong>The security level to write messages.
|
<strong>User Del. </strong>Users may delete their own messages.
|
||||||
<strong>Sysop Sec. </strong>The security level to do sysop actions.
|
<strong>Read Sec. </strong>The security level to read messages.
|
||||||
<strong>Aliases </strong>Allow the use of an Alias.
|
<strong>Write Sec. </strong>The security level to write messages.
|
||||||
<strong>Random org </strong>Create random origin lines (Oneliner database).
|
<strong>Sysop Sec. </strong>The security level to do sysop actions.
|
||||||
<strong>Quotes </strong>Add a random quote under new messages (Oneliner database).
|
<strong>Aliases </strong>Allow the use of an Alias.
|
||||||
<strong>Mandatory </strong>If this area is mandatory for downlinks.
|
<strong>Random org </strong>Create random origin lines (Oneliner database).
|
||||||
<strong>UnSecure </strong>Don't check link address during toss (Dangerous!).
|
<strong>Quotes </strong>Add a random quote under new messages (Oneliner database).
|
||||||
<strong>OLR Default </strong>Switch area default on for OLR users.
|
<strong>Mandatory </strong>If this area is mandatory for downlinks.
|
||||||
<strong>OLR Forced </strong>Area is always on for OLR users.
|
<strong>UnSecure </strong>Don't check link address during toss (Dangerous!).
|
||||||
<strong>Connections </strong>This will take you to the screen to edit up and downlinks.
|
<strong>OLR Default </strong>Switch area default on for OLR users.
|
||||||
</pre>
|
<strong>OLR Forced </strong>Area is always on for OLR users.
|
||||||
<P>
|
<strong>Connections </strong>This will take you to the screen to edit up and downlinks.
|
||||||
|
</pre>
|
||||||
<IMG SRC="../images/emareas.gif" width="587" height="342">
|
<P>
|
||||||
<P> <P>
|
|
||||||
|
<IMG SRC="../images/emareas.gif">
|
||||||
<H3>Edit connection</H3>
|
<P> <P>
|
||||||
<P>
|
|
||||||
<pre>
|
<H3>Edit connection</H3>
|
||||||
<strong>Aka </strong>The network address.
|
<P>
|
||||||
<strong>Send to </strong>Export mail to this node.
|
<pre>
|
||||||
<strong>Recv from </strong>Import mail form this node.
|
<strong>Aka </strong>The network address.
|
||||||
<strong>Pause </strong>The node is temporary disconnected.
|
<strong>Send to </strong>Export mail to this node.
|
||||||
<strong>Excluded </strong>The node is disconnected by the sysop.
|
<strong>Recv from </strong>Import mail form this node.
|
||||||
<strong>Delete </strong>Delete this connection.
|
<strong>Pause </strong>The node is temporary disconnected.
|
||||||
</pre>
|
<strong>Excluded </strong>The node is disconnected by the sysop.
|
||||||
<P>
|
<strong>Delete </strong>Delete this connection.
|
||||||
A note about the excluded switch. This can be used to disconnect a node
|
</pre>
|
||||||
from the area by moderator request. AreaMgr requests from that node
|
<P>
|
||||||
for this area are not processed anymore, he cannot disconnect this area
|
A note about the excluded switch. This can be used to disconnect a node
|
||||||
and reconnect. If you want to prevent a node to connect the area while
|
from the area by moderator request. AreaMgr requests from that node
|
||||||
he is not connected, you should manually connect the node and then set
|
for this area are not processed anymore, he cannot disconnect this area
|
||||||
the Excluded flag to yes. However, the status of this flag is reported to the
|
and reconnect. If you want to prevent a node to connect the area while
|
||||||
node in the notify messages, so this action is not invisible.
|
he is not connected, you should manually connect the node and then set
|
||||||
<P> <P>
|
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> <P>
|
||||||
<H3>Global Commands.</H3>
|
|
||||||
<P>
|
|
||||||
From menu 9.2 you can enter the global commands menu. In this menu you can:
|
<H3>Global Commands.</H3>
|
||||||
<ol>
|
<P>
|
||||||
<li>Delete connection
|
From menu 9.2 you can enter the global commands menu. In this menu you can:
|
||||||
<li>Add new connection
|
<ol>
|
||||||
<li>Replace connection
|
<li>Delete connection
|
||||||
<li>Change connection status
|
<li>Add new connection
|
||||||
<li>Change days old
|
<li>Replace connection
|
||||||
<li>Change max. messages
|
<li>Change connection status
|
||||||
<li>Change security
|
<li>Change days old
|
||||||
<li>Change aka to use
|
<li>Change max. messages
|
||||||
<li>Change origin line
|
<li>Change max. articles
|
||||||
<li>Change netmail reply
|
<li>Change security
|
||||||
<li>Delete message area
|
<li>Change aka to use
|
||||||
</ol>
|
<li>Change origin line
|
||||||
After you have selected the action you want and added the items to do, you will see
|
<li>Change netmail reply
|
||||||
a screen were you can select message area groups. You can then tag one or more
|
<li>Delete message area
|
||||||
groups and press enter when you are done. Then you have one chance to perform the
|
</ol>
|
||||||
actions or to bail out. All areas matching in that group are affected by your
|
After you have selected the action you want and added the items to do, you will see
|
||||||
changes. If you are not happy with the result, don't save the database and no
|
a screen were you can select message area groups. You can then tag one or more
|
||||||
harm is done. The file mbsetup.log shows all affected areas.
|
groups and press enter when you are done. Then you have one chance to perform the
|
||||||
<P> <P>
|
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.
|
||||||
<H3>Automatic area creation.</H3>
|
<P> <P>
|
||||||
<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:
|
<H3>Automatic area creation.</H3>
|
||||||
<pre>
|
<P>
|
||||||
1. Area Name Area autocreada:
|
If you want to use the automatic area creation you have to define a fictitious
|
||||||
2. FTN area DEFAULT
|
area tagged 'DEFAULT' with the options you want for new areas like this:
|
||||||
3. Newsgroup
|
<pre>
|
||||||
4. Moderator
|
1. Area Name Area autocreada:
|
||||||
5. JAM base /var/spool/mbse/mail/
|
2. FTN area DEFAULT
|
||||||
6. Origin Parolas BBX. Por fin.
|
3. Newsgroup
|
||||||
7. Fido Aka 0:0/0@ 22. Sysop Sec. 100
|
4. Moderator
|
||||||
8. QWK name 15. Days Old 40 23. Aliases No
|
5. JAM base /var/spool/mbse/mail/
|
||||||
9. Group AUTOCREADAS 16. Max. Msgs 1000 24. Quotes No
|
6. Origin Parolas BBX. Por fin.
|
||||||
10. Distrib. 17. Netreply 0 25. Mandatory No
|
7. Fido Aka 0:0/0@ 22. Sysop Sec. 100
|
||||||
11. Area Type Echomail 18. Active Yes 26. UnSecure No
|
8. QWK name 15. Days Old 40 23. Aliases No
|
||||||
12. Msg Kinds Public 19. User Del. Yes 27. OLR Default No
|
9. Group AUTOCREADAS 16. Max. Msgs 1000 24. Quotes No
|
||||||
13. FTN chars IBMPC 2 20. Read Sec. 5 28. OLR Forced No
|
10. Distrib. 17. Netreply 0 25. Mandatory No
|
||||||
14. RFC chars LATIN-1 2 21. Write Sec. 5 29. Connections
|
11. Area Type Echomail 18. Active Yes 26. UnSecure No
|
||||||
</pre>
|
12. Msg Kinds Public 19. User Del. Yes 27. OLR Default No
|
||||||
The FTN area's Tag must be 'DEFAULT' exactly. Connections will be left blank. Fill
|
13. FTN chars IBMPC 2 20. Read Sec. 5 28. OLR Forced No
|
||||||
the remaining options with your defaults for the new areas.
|
14. RFC chars LATIN-1 2 21. Write Sec. 5 29. Connections
|
||||||
If Fido AKA has not been filled in, the best fitting AKA according to the origin of
|
</pre>
|
||||||
the message will be used from the configuration.<BR>
|
The FTN area's Tag must be 'DEFAULT' exactly. Connections will be left blank. Fill
|
||||||
<P>
|
the remaining options with your defaults for the new areas.
|
||||||
Areas will be created as is laid out in this template, the tag of a new area
|
If Fido AKA has not been filled in, the best fitting AKA according to the origin of
|
||||||
will be added to the name and base path, the new tag will be placed in the tag
|
the message will be used from the configuration.<BR>
|
||||||
and qwk name (truncating it if needed).
|
<P>
|
||||||
Only the node from which the new area is received will be added in connections.
|
Areas will be created as is laid out in this template, the tag of a new area
|
||||||
<P>
|
will be added to the name and base path, the new tag will be placed in the tag
|
||||||
You will need to change the setup, menu 18, item 2, to change the command
|
and qwk name (truncating it if needed).
|
||||||
'mbfido tic toss'. Add the -a parameter if you want the automatic
|
Only the node from which the new area is received will be added in connections.
|
||||||
creation of areas to work when importing received mail.
|
<P>
|
||||||
So the commandline would be like <b>/opt/mbse/bin/mbfido tic toss web -a -quiet</b>.
|
You will need to change the setup, menu 18, item 2, to change the command
|
||||||
<P>
|
'mbfido tic toss'. Add the -a parameter if you want the automatic
|
||||||
|
creation of areas to work when importing received mail.
|
||||||
<A HREF="mail.html"><IMG SRC="../images/larrow.gif" ALT="Back" Border="0" width="40" height="30"> Back to Mail Setup</A>
|
So the commandline would be like <b>/opt/mbse/bin/mbfido tic toss web -a -quiet</b>.
|
||||||
<A HREF="./"><IMG SRC="../images/larrow.gif" ALT="Back" Border="0" width="40" height="30"> Back to index</A>
|
<P>
|
||||||
<A HREF="../"><IMG SRC="../images/b_arrow.gif" ALT="Home" Border="0" width="40" height="30"> Back to main index</A>
|
|
||||||
</BLOCKQUOTE>
|
<A HREF="mail.html"><IMG SRC="../images/larrow.gif" ALT="Back" Border="0">Back to Mail Setup</A>
|
||||||
</BODY>
|
<A HREF="./"><IMG SRC="../images/larrow.gif" ALT="Back" Border="0">Back to index</A>
|
||||||
</HTML>
|
<A HREF="../"><IMG SRC="../images/b_arrow.gif" ALT="Home" Border="0">Back to main index</A>
|
||||||
|
</BLOCKQUOTE>
|
||||||
|
</BODY>
|
||||||
|
</HTML>
|
||||||
|
|
||||||
|
|||||||
@ -1,58 +1,59 @@
|
|||||||
<HTML>
|
<HTML>
|
||||||
<HEAD>
|
<!-- $Id$ -->
|
||||||
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
|
<HEAD>
|
||||||
<META http-equiv="Content-Style-Type" content="text/css">
|
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
|
||||||
<META name="author" lang="en" "content="Michiel Broek">
|
<META http-equiv="Content-Style-Type" content="text/css">
|
||||||
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
<META name="author" lang="en" content="Michiel Broek">
|
||||||
<META name="description" lang="en" content="MBSE BBS Manual">
|
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
||||||
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
<META name="description" lang="en" content="MBSE BBS Manual">
|
||||||
<TITLE>MBSE BBS Setup - Files Database.</TITLE>
|
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
||||||
<LINK rel=stylesheet HREF="../manual.css">
|
<TITLE>MBSE BBS Setup - Files Database.</TITLE>
|
||||||
</HEAD>
|
<LINK rel=stylesheet HREF="../manual.css">
|
||||||
<BODY>
|
</HEAD>
|
||||||
<BLOCKQUOTE>
|
<BODY>
|
||||||
<h5>Last update 30-Jan-2001</h5>
|
<BLOCKQUOTE>
|
||||||
<P> <P>
|
<h5>Last update 21-Jan-2002</h5>
|
||||||
|
<P> <P>
|
||||||
<H1>MBSE BBS Setup - Files Database.</H1>
|
|
||||||
<P>
|
<H1>MBSE BBS Setup - Files Database.</H1>
|
||||||
|
<P>
|
||||||
<H3>Introduction.</H3>
|
|
||||||
<P>
|
<H3>Introduction.</H3>
|
||||||
This option allows you to manually edit the files in the files database.
|
<P>
|
||||||
The option to edit the file description is not present at this moment, but
|
This option allows you to manually edit the files in the files database.
|
||||||
will be when I have the time. The basic file entries can't be changed.
|
The option to edit the file description is not present at this moment, but
|
||||||
<P> <P>
|
will be when I have the time. The basic file entries can't be changed.
|
||||||
|
<P> <P>
|
||||||
<H3>Edit File.</H3>
|
|
||||||
<P>
|
<H3>Edit File.</H3>
|
||||||
<pre>
|
<P>
|
||||||
<strong>FileName </strong>The 8.3 filename of the file.
|
<pre>
|
||||||
<strong>Long fn </strong>The long filename of the file, not in use yet.
|
<strong>FileName </strong>The 8.3 filename of the file.
|
||||||
<strong>FileSize </strong>The size of the file in bytes.
|
<strong>Long fn </strong>The long filename of the file.
|
||||||
<strong>FileDate </strong>The real date of the file.
|
<strong>FileSize </strong>The size of the file in bytes.
|
||||||
<strong>Last DL. </strong>The date of the last download of the file.
|
<strong>FileDate </strong>The real date of the file.
|
||||||
<strong>Upl.Date </strong>The upload date.
|
<strong>Last DL. </strong>The date of the last download of the file.
|
||||||
<strong>Uploader </strong>The name of the uploader.
|
<strong>Upl.Date </strong>The upload date.
|
||||||
<strong>Times DL </strong>The number of times downloaded from the BBS.
|
<strong>Uploader </strong>The name of the uploader.
|
||||||
<strong>Times FTP </strong>Not in use yet.
|
<strong>Times DL </strong>The number of times downloaded from the BBS.
|
||||||
<strong>Times Req </strong>The number of times requested by mailer.
|
<strong>Times FTP </strong>Not in use yet.
|
||||||
<strong>Password </strong>The password to access this file.
|
<strong>Times Req </strong>The number of times requested by mailer.
|
||||||
<strong>Cost </strong>Not in use yet.
|
<strong>Password </strong>The password to access this file.
|
||||||
<strong>Free </strong>If this file is free for download.
|
<strong>Cost </strong>Not in use yet.
|
||||||
<strong>Deleted </strong>If this file should be deleted.
|
<strong>Free </strong>If this file is free for download.
|
||||||
<strong>Missing </strong>If this file is missing on disk.
|
<strong>Deleted </strong>If this file should be deleted.
|
||||||
<strong>No Kill </strong>Don't delete this file with <strong>mbfile</strong>
|
<strong>Missing </strong>If this file is missing on disk.
|
||||||
<strong>Announced </strong>If this file is ever announced as new.
|
<strong>No Kill </strong>Don't delete this file with <strong>mbfile</strong>
|
||||||
</pre>
|
<strong>Announced </strong>If this file is ever announced as new.
|
||||||
<P>
|
</pre>
|
||||||
|
<P>
|
||||||
<IMG SRC="../images/fdb.gif" width="589" height="343">
|
|
||||||
<P>
|
<IMG SRC="../images/fdb.gif">
|
||||||
|
<P>
|
||||||
<A HREF="./"><IMG SRC="../images/larrow.gif" ALT="Back" Border="0" width="40" height="30"> Back to index</A>
|
|
||||||
<A HREF="../"><IMG SRC="../images/b_arrow.gif" ALT="Home" Border="0" width="33" height="35"> Back to main index</A>
|
<A HREF="./"><IMG SRC="../images/larrow.gif" ALT="Back" Border="0">Back to index</A>
|
||||||
</BLOCKQUOTE>
|
<A HREF="../"><IMG SRC="../images/b_arrow.gif" ALT="Home" Border="0">Back to main index</A>
|
||||||
</BODY>
|
</BLOCKQUOTE>
|
||||||
</HTML>
|
</BODY>
|
||||||
|
</HTML>
|
||||||
|
|
||||||
|
|||||||
@ -1,4 +1,5 @@
|
|||||||
<HTML>
|
<HTML>
|
||||||
|
<!-- $Id$ -->
|
||||||
<HEAD>
|
<HEAD>
|
||||||
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
|
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
|
||||||
<META http-equiv="Content-Style-Type" content="text/css">
|
<META http-equiv="Content-Style-Type" content="text/css">
|
||||||
@ -11,7 +12,7 @@
|
|||||||
</HEAD>
|
</HEAD>
|
||||||
<BODY>
|
<BODY>
|
||||||
<BLOCKQUOTE>
|
<BLOCKQUOTE>
|
||||||
<h5>Last update 07-Jan-2002</h5>
|
<h5>Last update 21-Jan-2002</h5>
|
||||||
<P> <P>
|
<P> <P>
|
||||||
|
|
||||||
<H1>MBSE BBS Setup - Global Setup</H1>
|
<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
|
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
|
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
|
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.
|
and gated news articles to Fidonet.
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<h3>1.15. Edit Internet mail and news processing.</h3>
|
<h3>1.15. Edit Internet mail and news processing.</h3>
|
||||||
<p>
|
<p>
|
||||||
Email and news is setup here. There are three possible configurations which you
|
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>
|
<ul>
|
||||||
<li><strong>No ISP</strong>. If you don't have any connection to the internet
|
<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
|
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
|
<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
|
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
|
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
|
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>
|
example <A HREF="http://www.dynip.com">dynip.com</A>
|
||||||
Incoming email will come directly from the internet, but if someone sends
|
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
|
<strong>user@yourbbs.domain.org</strong>. Note, the username is their
|
||||||
Unix name.
|
Unix name.
|
||||||
</ul>
|
</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
|
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">
|
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.
|
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>UUCP aka </strong>The default Fidonet UUCP gate, 2:292/875@fidonet
|
||||||
<strong>Emailmode </strong>The email mode, discussed above
|
<strong>Emailmode </strong>The email mode, discussed above
|
||||||
<strong>News mode </strong>Newsfeed mode, INN, rnews or UUCP.
|
<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>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>Force at </strong>Force split of newfiles reports after n KBytes (16..63)
|
||||||
<strong>Control ok </strong>Allow news control messages to be gated
|
<strong>Control ok </strong>Allow news control messages to be gated
|
||||||
|
|||||||
@ -1,61 +1,66 @@
|
|||||||
<HTML>
|
<HTML>
|
||||||
<HEAD>
|
<!-- $Id$ -->
|
||||||
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
|
<HEAD>
|
||||||
<META http-equiv="Content-Style-Type" content="text/css">
|
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
|
||||||
<META name="author" lang="en" "content="Michiel Broek">
|
<META http-equiv="Content-Style-Type" content="text/css">
|
||||||
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
<META name="author" lang="en" content="Michiel Broek">
|
||||||
<META name="description" lang="en" content="MBSE BBS Manual">
|
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
||||||
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
<META name="description" lang="en" content="MBSE BBS Manual">
|
||||||
<TITLE>MBSE BBS Setup - File Echo's Setup - Hatch Manager.</TITLE>
|
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
||||||
<LINK rel=stylesheet HREF="../manual.css">
|
<TITLE>MBSE BBS Setup - File Echo's Setup - Hatch Manager.</TITLE>
|
||||||
</HEAD>
|
<LINK rel=stylesheet HREF="../manual.css">
|
||||||
<BODY>
|
</HEAD>
|
||||||
<BLOCKQUOTE>
|
<BODY>
|
||||||
<h5>Last update 30-Jan-2001</h5>
|
<BLOCKQUOTE>
|
||||||
<P> <P>
|
<h5>Last update 21-Jan-2002</h5>
|
||||||
|
<P> <P>
|
||||||
<H1>MBSE BBS Setup - File Echo's Setup - Hatch Manager.</H1>
|
|
||||||
<P>
|
<H1>MBSE BBS Setup - File Echo's Setup - Hatch Manager.</H1>
|
||||||
|
<P>
|
||||||
<H3>Introduction.</H3>
|
|
||||||
<P>
|
<H3>Introduction.</H3>
|
||||||
Hatch files is nothing more than entering a new file into a file echo. That
|
<P>
|
||||||
file is searched for on your system in a specific directory with a certain
|
Hatch files is nothing more than entering a new file into a file echo. That
|
||||||
filemask. This can be for example a new created nodelist or an allfiles listing.
|
file is searched for on your system in a specific directory with a certain
|
||||||
Everytime <strong>mbfido tic</strong> is run it will scan for files defined
|
filemask. This can be for example a new created nodelist or an allfiles listing.
|
||||||
in this setup. If such a file is found, a special .tic file is written and
|
Everytime <strong>mbfido tic</strong> is run it will scan for files defined
|
||||||
stored in the mailers inbound directory. When the <strong>mbfido</strong>
|
in this setup. If such a file is found, a special .tic file is written and
|
||||||
starts processing .tic files, that new hatched file will be processed as if
|
stored in the mailers inbound directory. When the <strong>mbfido</strong>
|
||||||
it was received form another system. To let this work, you obviously need
|
starts processing .tic files, that new hatched file will be processed as if
|
||||||
an existing TIC area.
|
it was received form another system. To let this work, you obviously need
|
||||||
<P> <P>
|
an existing TIC area.<P>
|
||||||
|
The filenames to hatch may be long filenames as long as there are no spaces in
|
||||||
<H3>Hatch Manager Setup.</H3>
|
it. In the TIC file a short filename will be created for the old style tic
|
||||||
<P>
|
processors. The long filename is inserted in the TIC file as well. The short
|
||||||
<pre>
|
filenames are created in the same way as windows does.
|
||||||
<strong>Mask </strong>The path and filename mask to search for.
|
<P> <P>
|
||||||
"?" matches any character, "#" matches digits and "@" matches
|
|
||||||
alpha characters. Don't use "*", this doesn't work!
|
<H3>Hatch Manager Setup.</H3>
|
||||||
<strong>Area </strong>The area to hatch this file in.
|
<P>
|
||||||
<strong>Replace </strong>The filename to replace, ie. "nodelist.z*"
|
<pre>
|
||||||
<strong>Magic </strong>The filerequest magic name, ie. "nodelist"
|
<strong>Mask </strong>The path and filename mask to search for.
|
||||||
<strong>Desc </strong>The description of the file, %12 in the description
|
"?" matches any character, "#" matches digits and "@" matches
|
||||||
means copy the 12th character of the name in place.
|
alpha characters. Don't use "*", this doesn't work!
|
||||||
<strong>Dupe </strong>Check for duplicates.
|
<strong>Area </strong>The area to hatch this file in.
|
||||||
<strong>Active </strong>If this area is active.
|
<strong>Replace </strong>The filename to replace, ie. "nodelist.z*"
|
||||||
<strong>Deleted </strong>If this area must be deleted.
|
<strong>Magic </strong>The filerequest magic name, ie. "nodelist"
|
||||||
<strong>Days </strong>The days in the week to scan for this file.
|
<strong>Desc </strong>The description of the file, %12 in the description
|
||||||
<strong>Month </strong>The dates in the month to scan for this file.
|
means copy the 12th character of the name in place.
|
||||||
</pre>
|
<strong>Dupe </strong>Check for duplicates.
|
||||||
<P>
|
<strong>Active </strong>If this area is active.
|
||||||
|
<strong>Deleted </strong>If this area must be deleted.
|
||||||
<IMG SRC="../images/hatch.gif" width="589" height="343">
|
<strong>Days </strong>The days in the week to scan for this file.
|
||||||
<P>
|
<strong>Month </strong>The dates in the month to scan for this file.
|
||||||
|
</pre>
|
||||||
<A HREF="tic.html"><IMG SRC="../images/larrow.gif" ALT="Back" Border="0" width="40" height="30"> Back to File Echo's Setup</A>
|
<P>
|
||||||
<A HREF="./"><IMG SRC="../images/larrow.gif" ALT="Back" Border="0" width="40" height="30"> Back to index</A>
|
|
||||||
<A HREF="../"><IMG SRC="../images/b_arrow.gif" ALT="Home" Border="0" width="33" height="35"> Back to main index</A>
|
<IMG SRC="../images/hatch.gif">
|
||||||
</BLOCKQUOTE>
|
<P>
|
||||||
</BODY>
|
|
||||||
</HTML>
|
<A HREF="tic.html"><IMG SRC="../images/larrow.gif" ALT="Back" Border="0">Back to File Echo's Setup</A>
|
||||||
|
<A HREF="./"><IMG SRC="../images/larrow.gif" ALT="Back" Border="0">Back to index</A>
|
||||||
|
<A HREF="../"><IMG SRC="../images/b_arrow.gif" ALT="Home" Border="0">Back to main index</A>
|
||||||
|
</BLOCKQUOTE>
|
||||||
|
</BODY>
|
||||||
|
</HTML>
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user