nitromike2006 wrote:Thanks CCS for the lead in the Manual.
@everyone
Read that if you run Vircom TCP 2.10-14 (2.10e) you need to use MHS (Novell) to get the SMTP stuff to work. Having read about that, first question is where to obtain MHS from? Looked on Novell's site and Google and no luck finding it (presumably for DOS). Is there such an animal? **OR** Is the MHS some kind of add on for MBBS 6.25?
Hopefully someone can enlighten me on this?
Thanks,
Mike
it's in my wg2. ah, thats why it don't work in mbbs 6, ha! I have a idea now. wg uses a different message system. hmm, wonder if I can compile
those moduals of my wg2 for my mbbs 6?
Setting Up The Major BBS for Global MHS 2.0
-------------------------------------------
We suggest the BBS Sysop and the LAN Administrator both read this
file and Chapter 13 of The Major BBS System Operations Manual before
making any changes on either side. Schedules permitting, both of you
should be present on both sides of this installation.
The procedure for configuring Global MHS is similar to the procedure
for configuring MHS 1.5 as described in System Operations Manual,
but there are a few places where Global's configuration will differ.
For one, note that Global MHS supports a "long name" and a "short name"
for gateways, workgroups, and users. You should always create names
which fit into SHORT name fields, and use the precise same name strings
for long name fields as well.
On the MHS side
---------------
First, the LAN Administrator needs to create an MHS gateway for the BBS.
Specify that this is an SMF-70 gateway.
Create a default workgroup for it with the same name as the gateway.
Create a user with a name of "MBBS" on the gateway.
Create a user's workgroup for it with the same name as the gateway's
default workgroup.
Specify a gateway command in the form:
-F<outbound message directory> (no spaces)
Example: -FG:\FROMBBS
On The Major BBS side
---------------------
Follow the steps in Chapter 13 of The Major BBS System Operations
Manual for configuring the BBS to work with MHS, with this exception:
In step 6, do NOT copy the file SMFSEND.EXE into INPOST.EXE. Do NOT.
Instead, copy the Galacticomm-supplied INPOST.EXE into the gateway's
PUBLIC directory.
In Configuration Options (#4 on the Introductory Menu), be sure that
option GTWNME contains the gateway's name.
In Configuration Options (#4 on the Introductory Menu), be sure that
option OUTFIL contains the full drive:\path of the outbound
file attachments subdirectory (PARCEL). See page 183 in The Major BBS
System Operations Manual.
Dedicating an MHS gateway host
------------------------------
Finally, set up a LAN workstation (a third machine, not the BBS computer
nor a Novell file server) to act as a dedicated MHS gateway host.
On this workstation run the Novell-supplied GWDEMON.EXE program
(see the Netware Global Messaging Administration manual for more details
on GWDEMON). This workstation must have the same network drive mappings
as the BBS computer. You may want to create a network account
specifically for the BBS and have both the BBS computer and the GWDEMON
computer log in as that same user.
As an example, consider the following MHS setup:
Root workgroup: Gcomm
Default workgroup: Eng (Eng.Gcomm)
Gateway name: BBSGate
Default workgroup: BBSGate (BBSGate.Gcomm)
A user named:
MBBS@BBSGate.Gcomm
The directory structures (as seen from both the BBS computer and the
GWDEMON host computer) are as follows:
MHS directory: H:\MHS
Gateway directory: H:\MHS\MAIL\GATES\BBSGATE
Outgoing message directory: G:\FROMBBS
Outgoing attachment directory: G:\FROMBBS\PARCEL
Incoming message directory: G:\INTOBBS
Incoming attachment directory: G:\INTOBBS\PARCEL
The Galacticomm-supplied INPOST.EXE, OUTPOST.EXE and BBSPCFG.EXE
(and the file OUTPOST.CFG created by BBSPCFG) all reside in:
H:\MHS\MAIL\GATES\BBSGATE\PUBLIC
and the BBS's offline Configuration options are set to:
GTWNME: BBSGate
OUTMSG: G:\FROMBBS
OUTFIL: G:\FROMBBS\PARCEL
INMSG: G:\INTOBBS
Setup Checklist Example
--------------- -------
The MHS gateway configuration should:
1 - have the same short and long gateway names BBSGate
2 - have a gateway command in the form
-F<outbound message directory> (no spaces) -FG:\FROMBBS
3 - have a default workgroup with the same short
and long names as the gateway BBSGate.Gcomm
4 - be declared as an SMF-70 gateway
5 - have a user declared on the gateway, in the
default workgroup, named MBBS
MBBS@BBSGate.Gcomm
The gateway directory should:
6 - have a child subdirectory named PUBLIC which
contains INPOST.EXE, OUTPOST.EXE and BBSPCFG.EXE
The LAN Administrator should:
7 - run BBSPCFG in the PUBLIC directory, enter the
BBS's inbound and outbound message directories
8 - then OUTPOST.CFG will be in the PUBLIC directory
On the BBS, in Configuration Options (#4 from the Introductory Menu):
9 - ALWMHS = YES
10 - OUTMSG = outbound message directory G:\FROMBBS
11 - OUTFIL = outbound parcel directory G:\FROMBBS\PARCEL
12 - INMSG = inbound message directory G:\INTOBBS
13 - GTWNME = MHS gateway name BBSGate
The BBS computer should:
14 - be logged into the network
15 - have Read/Write/Create/Erase/Modify/Filescan
access to the inbound and outbound message
directories
The GWDEMON computer should:
16 - be logged into the network
17 - have same drive mappings as BBS computer
18 - have Read/Write/Create/Erase/Modify/Filescan
access to the BBS inbound and outbound message
directories
19 - have Read/Write/Create/Erase/Modify/Filescan
access to the gateway directory and all
sub-directories under the gateway directory
20 - have a line in its AUTOEXEC.BAT setting the
environment variable MV to the MHS directory
(a trailing backslash is always required)