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

Updated documentation

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

331
html/setup/emareas.html
View File

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

117
html/setup/fdb.html
View File

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

14
html/setup/global.html
View File

@@ -1,4 +1,5 @@
<HTML>
<!-- $Id$ -->
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
@@ -11,7 +12,7 @@
</HEAD>
<BODY>
<BLOCKQUOTE>
<h5>Last update 07-Jan-2002</h5>
<h5>Last update 21-Jan-2002</h5>
<P>&nbsp;<P>
<H1>MBSE BBS Setup - Global Setup</H1>
@@ -286,14 +287,14 @@ split will be forced right after the file that passes the 31 KBytes limit.
I use values of 1 KBytes below maximum for overhead such as SEEN-BY and
PATH lines. Values larger then 32 KBytes is not a good idea, recent tests
in May 1999 have shown that your messages will not reach all systems
if they are larger then 32 KBytes. Splitting is used for newsfiles reports
if they are larger then 32 KBytes. Splitting is used for newfiles reports
and gated news articles to Fidonet.
<P>
<h3>1.15. Edit Internet mail and news processing.</h3>
<p>
Email and news is setup here. There are three possible configurations which you
can set with 1.14.11:
can set with 1.15.11:
<ul>
<li><strong>No ISP</strong>. If you don't have any connection to the internet
use this setting. Email will come from the default Fidonet UUCP gate and will be send out
@@ -314,7 +315,9 @@ can set with 1.14.11:
<li><strong>Perm ISP</strong>. If you are permanent connected to the internet
either with a static or dynamic IP address use this option. Use this option
also if you have an UUCP domain and have a dialup UUCP connection. Also
you can use this for dialup if you have your own maildomain.
you can use this for dialup if you have your own maildomain without UUCP,
you will then fetch the mail from a multidrop mailbox (POP or IMAP) and
send the mail using SMTP via the SMTP mailer of your provider.<br>
If you have a dynamic IP address you can still get a DNS name from for
example <A HREF="http://www.dynip.com">dynip.com</A>
Incoming email will come directly from the internet, but if someone sends
@@ -322,6 +325,8 @@ can set with 1.14.11:
<strong>user@yourbbs.domain.org</strong>. Note, the username is their
Unix name.
</ul>
Note: the terms <b>Dial ISP</b> and <b>Perm ISP</b> are not correct, it doesn't
matter how you are connected, it only matters if you have a maildomain or not.
Another word of wisdom from my side, configuration of the internet, ppp, sendmail etc. is not discussed
here, see the HOWTO's and other documentation that exists at <A HREF="http://www.linuxdoc.org">
www.linuxdoc.org</A>, it's all there.
@@ -338,6 +343,7 @@ www.linuxdoc.org</A>, it's all there.
<strong>UUCP aka </strong>The default Fidonet UUCP gate, 2:292/875@fidonet
<strong>Emailmode </strong>The email mode, discussed above
<strong>News mode </strong>Newsfeed mode, INN, rnews or UUCP.
<strong>Articles </strong>The default maximum newsarticles to fetch per group.
<strong>Split at </strong>Gently split newfiles reports after n KBytes (12..60)
<strong>Force at </strong>Force split of newfiles reports after n KBytes (16..63)
<strong>Control ok </strong>Allow news control messages to be gated

127
html/setup/hatch.html
View File

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