home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Network Support Encyclopedia 96-1
/
novell-nsepro-1996-1-cd2.iso
/
download
/
netware
/
msml20.exe
/
NOTE.TX_
/
NOTE.TX
Wrap
Text File
|
1995-05-19
|
21KB
|
565 lines
NOVELL TECHNICAL INFORMATION DOCUMENT
TITLE: NetWare MHS Driver for Microsoft Mail
DOCUMENT ID: TID200037
DOCUMENT REVISION: B
DATE: 17FEB94
ALERT STATUS: Yellow
INFORMATION TYPE: Symptom Solution
README FOR: MSMAIL.EXE
NOVELL PRODUCT and VERSION:
NetWare Global MHS 2.0
NetWare Basic MHS
NetWare Remote MHS 2.0
ABSTRACT:
The NetWare MHS Driver for Microsoft Mail (MS Mail) product is provided in
response to Novell and Microsoft customers' requirements to support their
existing MS Mail installations over an MHS transport and provide a clean way
of transition from MS Mail to native MHS applications.
──────────────────────────────────────────────────────────────────────────────
DISCLAIMER
THE ORIGIN OF THIS INFORMATION MAY BE INTERNAL OR EXTERNAL TO NOVELL. NOVELL
MAKES EVERY EFFORT WITHIN ITS MEANS TO VERIFY THIS INFORMATION. HOWEVER, THE
INFORMATION PROVIDED IN THIS DOCUMENT IS FOR YOUR INFORMATION ONLY. NOVELL
MAKES NO EXPLICIT OR IMPLIED CLAIMS TO THE VALIDITY OF THIS INFORMATION.
──────────────────────────────────────────────────────────────────────────────
SYMPTOM
MS Mail spelling feature generates an
"...error loading spelling dictionary..." when using within
WORD.
OR
I want MS Mail to share the same Spelling Dictionary as my
Microsoft Office Apps.
SOLUTION
Make MS Mail use the same spelling dictionary as WORD and other
Microsoft Office applications. In addition to providing
consistency across applications it will spare resources.
Edit WIN.INI and MSMAIL.INI which should both be under the
WINDOWS directory. Find the [MS Proofing Tools] section in both
files. Typically the sections would have at least the following
lines:
WIN.INI:
[MS Proofing Tools]
Custom Dict 1=C:\WINWORD\CUSTOM.DIC
Spelling 1033,0=C:\WINDOWS\MSAPPS\PROOF\MSSPEL2.DLL,C:\WINDOWS\MSAPPS\PROOF\MSSP2_EN.LEX
Custom Dict (Mail)=C:\MSMAIL\CUSTOM.DIC
Spelling (Mail) 1033,0=C:\WINDOWS\MSAPPS\PROOF\MSSPELL.DLL,C:\WINDOWS\MSAPPS\PROOF\MSSP_AM.LEX
MSMAIL.INI
[MS Proofing Tools]
Spelling=Spelling (Mail) 1033,0
Custom Dict=Custom Dict (Mail)
As the WIN.INI file shows there are two spelling DLLs (MSSPEL2
and MSSPELL) and two dictionaries (C:\WINWORD\CUSTOM.DIC and
C:\MSMAIL\CUSTOM.DIC). The entries in the MSMAIL.INI file are pointing
to the appropriate entries in the WIN.INI file (ie. the right hand
side of the '=', in the MSMAIL.INI entries correspond to the
left hand side of the '=' in the WIN.INI entries). This points us to
the dictionary and DLL being used. In order for MS Mail to share the
same dictionary and DLL with Microsoft Office, just change the pointers
as shown below:
New MSMAIL.INI
[MS Proofing Tools]
Spelling=Spelling 1033,0
Custom Dict=Custom Dict 1
SYMPTOM
The MS Mail spelling feature becomes unselected.
SOLUTION
To correct this, select Mail Options and reselect the option "Check
spelling of messages before sending," and save before exiting the menu.
Each time you select the MHS transport in the Mail System Selector, your
MS Mail login password is cleared. Select Mail Options in MS Mail, and
select Change Password to reenter your password.
The default MS Mail message storage file is in directory <drive>:\Windows
(Example: c:\Windows). To change this, select Mail Options, select
Server and modify the message storage field to point to the desired
location.
SYMPTOM
The address book does not work.
SOLUTION
First verify STEP 1.
If and only if STEP 1 is completely correct do STEP 2.
STEP 1.
See the Setup instructions. Most likely, the preferred application name
is wrong. Ask your administrator to verify it.
Next check your MHS long and short user names. They must match the long
and short name created by the server administrator. Again, ask your
administrator to verify the MHS names.
Check the MHS path you specified. It must be set to the parent directory
of the MHS directory structure. You can check this by mapping to the
directory and seeing if it contains the directory ..\mhs.
Example: G:\apps\mhs\mail\users
In this example, the MHS path would be G:\apps, which is the parent
directory of the MHS directory structure.
CAUTION:
if your MHS Path is of the form <Server>\<VOL>:<PATH>
it will not be understood from MSMail. It must be set
to <Drive Letter>:<PATH>.
STEP 2.
Give all users the "FILE SCAN" right to
..\MHS\MAIL\PUBLIC\SMF-NS.XRT file (in addition to the "READ"
right that users already have).
In order to do this once for all users use the FILER. On
NetWare 4 "[public]" already has the read right to the file,
also add the "FILE SCAN" right.
On NetWare 3 do the same to the group "Everyone".
SYMPTOM
Users cannot run RMHS from MSMail.
SOLUTION
Ensure Remote MHS is installed at your workstation. The RMHS path must
be set to the parent of the MHS directory on your PC. If your
administrator has decided not to use the RMHS path setting in the server
options dialog, you must set the MV environment variable before starting
MS Windows.
Example: set MV=G:\apps (see the previous example)
SYMPTOM
When users try to create an address, the only address type is "CUSTOM
ADDRESS." Where is the "MHS ADDRESS"?
SOLUTION
This usually 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 or your administrator has not enabled the creation of the
extract file. You can type in the addresses manually or you can save
them in the private address book using custom addressing.
If you are running Remote MHS and do not have the company extract file,
obtain it from your MHS administrator. It will simplify your addressing.
Please refer to NetWare Remote MHS user documentation for instructions.
SYMPTOM
User's cannot use the menu driven method to create an address.
SOLUTION
Please read the MS Mail users guide for full details. Be sure to choose
the option "MHS address," instead of the custom address.
SYMPTOM
User's cannot get Schedule+ to work.
SOLUTION
Verify that the SCHDPLUS.INI file in the Windows subdirectory contains
the line "scheduletransport = TRNANY." This is a replacement .DLL file
that patches Schedule+ application.
Also verify that the file TRNANY.DLL is in the windows\system
subdirectory.
SYMPTOM
User's cannot enter addresses that are not in their address book.
SOLUTION
Use the exact syntax shown in the following example to enter addresses
that are not in the address book:
Example:
To send a message to "John Jones@engineering.acme," type the following:
[mhs:John Jones @ engineering.acme]
Note: Addresses within the square brackets ([ ]) can be separated by
commas. However, MS Mail style addresses are separated with semicolons
(;) outside the square brackets.
SYMPTOM
User's cannot share calendars in Schedule+.
SOLUTION
That feature is a hard-coded feature of Schedule+ application. Microsoft
may address this in an upcoming version to support the 0 pump
architecture.
SYMPTOM
User's cannot see the same people they previously had in their address
book.
SOLUTION
Verify that the administrator has provided the extract file that contains
all the names in the MHS directory. The administrator must also enable
directory synchronization on the MHS network to keep this address book up
to date.
SYMPTOM
User's lost all mail they had before the conversion.
SOLUTION
The mail was not exported before the conversion or was not imported after
the conversion. Use the selector to reenable the old Microsoft
transport. Export the folders, then use the selector to invoke the
Novell MHS Mail transport. Now, import these folders.
Note that if you switch between transports to use both, you will have
different mail folders. This is because the NetWare MHS transport and
the standard MS Mail transport use different mailboxes.
SYMPTOM
Microsoft Office 4.x Applications report my logon name to be
invalid, when I choose "Send" or "Add Routing Slip".
SOLUTION
Some applications in the Microsoft Office attempt to validate
your session with the mail service. The driver attempts to
provide this by checking your logon name with your fullname
in the public address book. Ensure your logon name is your
fullname or a substring of that fullname.
SYMPTOM
How can I get mail for my account under different name?
SOLUTION
If a user has other accounts on the MHS server and wants to access mail
for those accounts, they will have to modify the entries for user (such
as long name or short name) in the MSMAIL.INI file in the Windows
subdirectory.
Self-Extracting File Name: MSMAIL.EXE Revision: B
Files Included Size Date Time
\
MSMAIL.TXT (This File)
BCC.DLL 10688 01-04-93 12:00a
FILES.INI 116 09-01-93 12:00a
SETUP.EXE 24624 03-23-92 12:00a
SETUP.LST 537 12-02-93 12:00a
MSMAIL.INI 1313 12-25-93 12:00a
NOTE.DOC 26867 02-11-94 12:04p
NOTE.TXT 21420 02-11-94 12:04p
TRNANY.DLL 5057 04-26-93 12:00a
MAILDRV.EXE 23840 04-06-93 12:00a
MAILDRV.HLP 14980 04-06-93 12:00a
MHSDRVR.INF 1768 02-07-94 4:15p
MHSDRVR.MST 5064 10-07-93 12:00a
MHSMAIL.DLL 112208 12-25-93 12:00a
MHSMAIL.HLP 15459 12-02-93 12:00a
_MSTEST.EXE 89504 03-23-92 12:00a
MSCOMSTF.DLL 74528 03-23-92 12:00a
MSCUISTF.DLL 15504 12-13-93 12:00a
MSDETECT.INC 22097 03-23-92 12:00a
MSDETSTF.DLL 24544 03-23-92 12:00a
MSINSSTF.DLL 65440 03-23-92 12:00a
MSSHLSTF.DLL 14928 03-23-92 12:00a
MSUILSTF.DLL 6144 03-23-92 12:00a
SCHDPLUS.INI 155 09-01-93 12:00a
SETUPAPI.INC 55620 03-23-92 12:00a
Installation Instructions:
Supported Configurations:
Both NetWare MHS and MS Mail postoffice support the separation of
messaging applications such as electronic mail, calendaring, and forms
processing from the messaging transport that does the message routing and
delivery. Hence, it is possible to move from the standard Microsoft
postoffice and messaging transport system to the NetWare MHS messaging
transport system by deploying this MHS driver for MS Mail.
Restrictions:
■ Because Microsoft's 0 pump architecture is specific to Microsoft
Windows, the DOS and Macintosh versions of MS Mail are not supported
with this product.
■ This software must be installed with the NetWare MHS products
supporting the SMF v71 API. It does not support NetWare MHS 1.5 or
prior versions.
■ The shared folder feature of MS Mail and the shared calendar feature
for MS Schedule+ are not supported.
Install:
An automatic Setup program is available to install the software at the
user's MS Windows workstation. Before beginning to install this driver
software, the administrator must install Global MHS, Basic MHS, or remote
MHS. The administrator then needs to set up MS Mail.
3.1 If MS Mail is already installed:
This procedure will preserve your existing MS mail messages.
1. Before installing the MHS driver, enter MS Mail and choose the
export option from the File menu.
2. Export all of the folders you are interested in keeping.
3. After installing and selecting the MHS driver, you can import these
folders to the new mailbag. The new default message file is
"MS_MHS.MMF" located in the Windows subdirectory by default.
4. Install the MHS driver with the setup instructions after preserving
existing mail.
3.2 If MS Mail is not installed
■ If you have purchased the LAN version of Microsoft Mail, install the
product following the manufacturer's instructions to obtain the MS
Mail for Windows client software. You only need to install the
Windows client and need not install server programs.
■ When you are prompted to install server programs, choose DONE from
the menu.
■ If you have purchased MS Mail Remote for Windows, install the
product following the manufacturer's instructions. You do not need
to install the transfer disk. When you are prompted for the
transfer disk, select CANCEL on the menu.
■ If you have purchased Microsoft Office or Microsoft Windows for
Workgroups, you only need to install the MS Mail client software.
Install the MHS driver by following the setup instructions.
3.3 Setup Instructions:
1. Connect your PC to a NetWare server running NetWare Global MHS or
NetWare Basic MHS.
2. Backup your MS Mail mailbox and your MS Windows directory.
3. Map a drive to the parent directory of the MHS tree on your NetWare
server. Set the MV environment variable to this directory.
Example:
If MHS is installed under the APPS directory on the SYS: volume,
then do the following:
MAP M:=<server>/SYS:\apps
SET MV=M:\apps
4. Start MS Windows
5. Make sure MS Mail is installed and functioning properly.
6. Put the NetWare MHS driver for MS Mail disk in the A: drive (or map
a drive to the MHS driver software location).
7. From Program Manager, select the File Menu, then select Run.
On the command line, enter <drive letter>:SETUP
Example: A:SETUP
(The MHS driver copies to appropriate MS Windows directories.)
8. Setup will start the MS Mail selector program. If it does not,
invoke the mail system selector by double-clicking on the new icon.
Note that Microsoft Mail Remote comes with its own selector. Use
the selector supplied by this driver software.
Note: If you have a prior copy of MHS driver for MS Mail, make sure
that all existing files in your MS Windows subdirectory are
Read/Write or the MS Mail System Selector will give error.
9. Double-click on the "Novell MHS Mail" choice. After a few moments
the selection will move to the "current" choice box.
Note: Always select the Novell MHS Mail transport using the Mail
system selector every time setup is run. Doing this updates the
MSMAIL.INI file located in the Windows subdirectory by default. If
you do not select the MHS driver after this installation, your prior
driver remains in effect as the installed driver.
10. Exit the program and start MS Mail.
11. Type in a name and a password (optional). The password protects the
mailbox from someone copying it and reading it.
Note: When MS Mail is invoked for the first time after installing
the MHS driver, you will see the following error message displayed
twice:
MESSAGE
Can't find MHS tree structure
Ignore this message. It will disappear after the MHS driver is
configured as described in the next two steps.
12. Select the Mail menu, Options option, and select the server button.
13. Enter your long (SMF-71) name.
Example: Joseph Smith@Sales.Acme
Enter your short name (8 characters or less: A-Z, 0-9, $-#).
Example: Jsmith
Enter the path to the parent directory of the MHS tree.
Example: <server>\sys:\apps). Also refer to step 3.
Enter your preferred application as defined in MHS.
To ensure mail is delivered to the correct mailbox, this choice must
have been set as the preferred application in MHS administration.
Fill out the rest of the form as you like, most are preference
settings.
14. Click OK, and exit MS Mail.
15. Restart MS Mail.
16. 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 12.
If linking to Global MHS, verify that NGMEXTRC.NLM module has been
loaded on the NetWare Global MHS server.
If using Basic MHS, the synchronizing of users is automatic.
If using Remote MHS, copy the extract file from your network
(\MHS\MAIL\PUBLIC\SMF_NS.XRT) to the same location on your Remote
MHS installation.
17. If the user has exported their folders before conversion, import
them back into the new MHS mailbag by selecting the File menu of MS
Mail.
If you have questions on the NetWare MHS Driver for Microsoft Mail,
call Novell Technical Support at 1-800-NETWARE or 801-429-5588.
For the Novell Messaging Hotline, dial 1-408-577-8989
Solution Specifics:
■The MHS driver is Microsoft 0 pump architecture compliant:
All functions (except shared folders) are supported
■The MHS driver is SMF v71 API compliant:
It supports NetWare Global MHS, NetWare Remote MHS and NetWare Basic
MHS.
It also supports all Global MHS protocol modules. Thus, a MS Mail
user gains the full capabilities to address and exchange mail with
SMTP, SNADS, and X.400 users when those modules are loaded.
■Centralized administration:
All configuration data can be set within MS Mail.
■Fully automated setup and install program.
■Comprehensive context sensitive help.
■Blind Carbon Copy (Bcc) added to the compose form of MS Mail.
■MS "Switcher" (MAILDRV.EXE) compatible:
Allows the user to select the MHS transport or standard MS Mail
transport.
■NetWare MHS features of return-receipts, delivery-receipts and
non-delivery receipts are fully implemented.
■Preserve existing mail messages:
Existing MS mail messages can be imported to new MHS mailbox.
Trademarks
NetWare, the N design, and Novell are registered trademarks and NetWare
Remote MHS, NetWare Global MHS, and NetWare Basic MHS are trademarks of
Novell, Inc. NetWire is a service mark of Novell, Inc.
Microsoft and Windows are registered trademarks and Visual Basic,
Schedule+, EForms are trademarks of Microsoft Corporation. Mac and
Macintosh are registered trademarks of Apple Computer Inc.
All other trademarks and registered trademarks are owned by their
respective corporations.
Copyright (C) 1994 Novell, Inc. All rights reserved. No part of this
publication may be reproduced, photocopied, stored in a retrieval system,
transmitted or translated into any language without the express written
consent of the publisher.
Novell, Inc.
2180 Fortune Drive
San Jose, CA 95131, U.S.A.
NetWare MHS Driver for Microsoft Mail
Release Note - January 1994
Novell Messaging Hotline: 1-408-577-8989