MHS driver for Microsoft Mail

Summary

    Microsoft mail API (MAPI) is Microsoft's strategic direction for message
system independence.  MS MAIL and several other Microsoft products such as
Visual Basic, Schedule +, EForms, etc., use MAPI to access the back end
services.

    Novell customers using Microsoft products have asked for MHS to be one of
those back end services.  This driver is a short term tactical solution to
meet these demands.  It enables MS Mail customer to use MHS as the back end
service.

Key Messages and Positioning

    1.  This product is in response to Novell customers' demands to support
existing MS-Mail over MHS transport and a clean way to transition from
MS-Mail to native MHS applications.

    2.  Novell customers are best served by well integrated MHS applications.
This product represents the best level of integration Novell can provide
given Microsoft's intermediate architecture including all aspects of NetWare
integration such as administration and management.  It allows MS Mail
customers to introduce high quality e-mail native MHS applications eg.
DaVinci, Beyond, CE QuickMail into their environments, while retaining their
full investment in MS-Mail software and user training.

    3.  This product is not an endorsement of MS-Mail, but a recognition that
customers have invested in MS-Mail and require a way to benefit from the use
of the rich Global MHS facilities without having to introduce a gateway into
the environment.  It provides MS Mail with the benefits of NetWare's
integrated messaging and directory services.

    4.  Novell intends to provide maintenance support of this driver until
such time that it becomes obsolete by the introduction of MAPI.  Because
0-pump solutions are developed to specific versions of MS Mail, Novell will
work closely with Microsoft to ensure that future 0-pump based versions of MS
Mail are supported.

    5.  The Microsoft 0-pump architecture is specific to particular versions
of MS-Mail for Windows only.  As such, this solution can not provide direct
MHS access for MS-Mail users on the Macintosh or DOS.  Users with MS Mail on
these platforms must utilize a gateway in order to maintain connectivity with
the MS Mail for Windows based users.  Alternatively, they can run native MHS
applications on DOS and Macintosh.

    6.  A gateway must be deployed for transition over a period of time while
preserving the connectivity between MS-Mail transport based users and MHS
transport based users.  This gateway has been developed by a 3rd party and is
available for beta test.


MHS Driver for Microsoft Mail

Installation Instructions
Beta Release 2 dated Oct 8, '93
Overview:

    Enclosed is a Windows DLL driver that enables your MS Mail Windows
application to use Novell MHS as a native transport.

    The enclosed DLL requires installation of Novell's NetWare Global MHS
(GMHS) or NetWare Basic MHS (BMHS) on your NetWare server.  Basic MHS is
included in NetWare 3.12 OS.  Please refer to the MHS documentation for more
information.

    The enclosed DLL also supports other Simple MAPI based products, such as
Microsoft's Electronic Forms, Schedule+, and Visual Basic.  Note that
complete testing has not been done on these products.

    This driver also delivers extract file facility of Global MHS or Basic
MHS to MS Mail.  This information is used for the address book.  It contains
the names of users and distribution lists in your organization.

    All features (except shared folders) that were available with the
existing MSMail transport are available with this MHS driver.  Please let us
know if shared folders is a required function in your corporation.

    This DLL supports MS Mail for Windows natively on MHS.  The DOS and
Macintosh versions of MS Mail require a gateway to communicate between MS
Mail Post Office and Global MHS.  Alternatively, those platforms can use a
native MHS application from one of the several applications available for
those platforms.  Please let us know if you need a beta for the gateway
product.


Features: 

Context Sensitive Help Fully Automated Installation Program.
PIF file support for Remote MHS users to run RMHS in a window.  
Supports MAPI 0 (All functions are supported except shared folders).  
Supports Basic MHS & Global MHS (All MSMail features are fully exploited).  
Adds Blind Carbon Copy to the compose form of MSMail.  
Supports fast drill down search for addresses.  
Supports return, read, delivery & non-delivery receipts.  
MS "Switcher" (MAILDRV.EXE) compatible.
Preserves existing MSMail messages by importing them to new MHS mailbag.  
Supports connectivity to other MHS applications on DOS/ Macintosh/ Unix.  
Supports connectivity to SMTP, SNADS, and X.400 through add-on GMHS modules.


Preserving Existing Mail Messages:

    Before installing this driver, enter MSMail and choose the export option
from the File menu.  Export all of the folders you are interested in keeping.
After installing and selecting the MHS driver, you can import the folders to
the new mailbag.  The new default mailbag is "MS_MHS.MMF"

For Alpha and Beta 1 users:

    Please make sure all existing files are Read/ Write, or the MS Mail
System Selector will give error.

    Always, select the Novell MHS Transport using the Mail System Selector
everytime you run setup.  Doing this updates the MSMAIL.INI file.  Please
double-click on Novell MHS Transport to do this.

    FAILURE TO RESELECT MHS DRIVER (EVEN IF IT ALREADY INDICATES MHS MAIL)
WILL RESULT IN AN OBSOLETE MSMAIL.INI FILE

Preparation before Installing:

Step #1 : 	Connect your PC to a NetWare server running GMHS or BMHS.
Step #2 : 	Backup your MSMail mailbag and your Windows directory.
Step #3 : 	Map a drive to the MHS tree on your NetWare server.
		Set the MV environment variable to this directory.
		for example:	
			MAP M:=server/SYS:\
			SET MV=M:\

Setup Instructions

Step #1 : 	Start Windows

Step #2 : 	Make sure MSMail is installed properly.

Step #3 : 	Put MHS driver disk in drive A:.

Step #4 : 	From Program Manager, select the File Menu, then select 
			run "A:SETUP"
            (The MHS driver copies to appropriate windows directories)

Step #5 : 	Start Mail System Selector by double-clicking on the new icon.
		(If for some reason it isn't running, SETUP will start it)

Step #6 : 	Double-click on the "Novell MHS Mail" choice. After a few moments
         		the selection should move to the "current" choice box.

Step #7 : 	Exit the program and start MSMail.

Step #8 : 	Type in a name and a password (optional). This protects the mailbag
          		from someone copying it and reading it.

Step #9 : 	Select the Mail menu, Options option and select the server button.

Step #10: 	Enter your full MHS name.  This  is also known as your MHS name.
		A sample full MHS name might be 
				"Joseph Smith@Sales.Acme".
		For information on full MHS names and the other information 
		see your MHS documentation. 

		Enter your short name (8 chars or less).  This name is also known
		as your MHS short name.  A sample short name is "JSMITH@Acme".

		Enter the path to your MHS directory tree, (e.g., M:\ ).  Use
		the drive letter in the "SET MV=" command in Step #3 of Preparation. 

        Enter your preferred application as defined in MHS.  
        Fill out the rest of the form as you like, most are preference settings

Step #11: 	Click OK, and exit MSMail.

Step #12: 	Restart MSMail.

Step #13: 	Select the Mail menu. Select Address Book. If you see your company
          	address book, you are set up correctly, if not, go back 
			to step 9. 
		    Also verify that the NGMEXTRC.NLM is loaded (for GMHS servers). 

Step #14: 	Install all other Mail-Enabled apps, such as Sched+, Eforms, etc.



COMMON PROBLEMS

Can't send mail :
	Does the address book work ?  If not, see step 10 of the installation 
	instructions. for GMHS installations, make sure that NGMEXTRC.NLM 
	is loaded at the GMHS server. 

	Most likely, the preferred application name is wrong. 
	Ask your administrator to verify it.


Can't receive mail :
	Check your SHORT USER NAME. It must match exactly. 
	Again, ask your administrator to verify it. Check the mhs path. 
	It should be set to the directory that contains the mhs 
    directory structure.
		Ex:   G:\stuff\mhs\mail\users\public\send

	In this example, it should be G:\STUFF, the home for mhs directory.


GPI Error or Mailspool Error:
	This is most probably a legitimate driver bug. Follow the
	step below and then report the problem immediately.

	Did this occur while a message was downloading? This can be
	verified by noticing a small mail slot icon in the lower right corner. 
	If it is visible with a downward arrow, the answer is yes.

	Return to DOS and set your default directory to your MHS inbox.
	Ex:  	F:
		cd \mhs\mail\users\myshortname\mhs

	Type in "dir *."  Write the first matching file name and rename it to  .BAD

	Restart mail and see if everything works.  If so send offending
	mail message (with attachments) to us so we can fix the driver.
	(Ask your administrator for assistance if necessary)

	If the downward arrow wasn't visible, try to determine what exactly
	was happening at that moment. Were you uploading a message? 
	Were you logging in? Were you creating a personal group ?

	Please try to duplicate the problem again.  If it re-occurrs, please 
    notify us immediately with a detailed description of how we can 
    duplicate it.


I can't type in addresses directly :
	Yes it can be done.  Make sure you follow the syntax exactly.
	Ex:  You want to send a message to "running bear @ engineering.novell"
	Then type in the following:
		[mhs:running bear @ engineering.novell]

	Remember to separate multiple addresses with a semicolon (;).
	The commas don't work.


I can't use the menu driven method to create an address:
	Please read the MSMail users guide. Full details are in that book.
	Be sure to choose the option "MHS address" not custom address.


When I go to create an address, the only address type is "CUSTOM ADDRESS".
Where is the "MHS ADDRESS"?
	This usually is restricted to laptops and occurs when the company address 
	book is not found. This implies that you are not logged in or do not 
    have a drive mapped to the mail server. This is a "feature" of MSMail. 
    We can work around it by putting a copy of the extract in RMHS directory.


I can't get Schedule+ to work, Is it supported? :
	Yes it is supported. Make sure the transport line in the schdplus.ini 
    file points to trnany.  This is a replacement .dll file that patches 
    Schedule+. Make sure trnany.dll is in the windows\system directory.


Why can't I share calendars in Schedule+ :
	We will be supporting that version when it is released by Microsoft.


Can't run RMHS from MSMail :
	Did you purchase and install Remote MHS?  This is a separate product.
	The RMHS path should be set to the parent of the MHS directory
	on your laptop. (See above)
	If your adminstrator has decided not to use the RMHS path setting
	in the server options dialog, you must set the MV environment 
	variable before starting Windows
	Ex:  C:> set mv=c:\stuff (see above)

	RMHS allows users to pick up mail while they are on the road, and it is
	fully integrated with MSMail.  Ask your administrator for a copy.


Beta Support

Call Novell Technical Support (800-NETWARE or 801-429-5588).
For official beta customers, this is a no-charge call, 
if you identify yourself as a MHS driver for Microsoft beta customer. 

If there are problems with this, please send a fax to 
Attn. Manoj Goel at fax# 408 433 9827 or send an email to 
	MHS:	manoj@novell
	SMTP:	manoj@novell.com

    There are several places where information and updates to supplementary
files for GMHS, such as modem definition files, will be available.  These
locations include Novell's anonymous FTP site at ftp.novell.com, 
LIBRARY@NOVELL, the NetWire forum on CompuServe, and Novell Technical Support.
