102389 - Simple MAPI does not work if MAPI is not enabled on computer

Status: VERIFIED FIXED

(MailNews Core :: Simple MAPI, defect, P2)

Description

[Tiantian Kong]

If MAPI in not enabled on the computer, ie, 

(1) From Word, no "Mail recipient" shows up from File|Send To
(2) From Excel, no Send shows up in File.
(3) From powerpoint, no "Mail recipient" shows up from File|Send To 

then our simple MAPI feature will not work after selecting NS mail client as the
default client.

Comment 1

[Jaime Rodriguez, Jr.]

how is this different then the way other clients work? At first glance, this 
does not seem like a show stopper to me.

Comment 2

[Krishna Mohan]

Yes.  This is not a show stopper and is a rare case.

Comment 3

[Scott MacGregor]

actually I am in this case. All it takes is a user with just netscape 6 on his
or her machine. Isn't that something we want to target? I'd like to nominate for
reconsideration since this keeps me from using simple mapi. Also, I'm sure
marketing is going to think this is a common case (see John Gable). We can talk
about those reasons at the PDT meeting.

Comment 4

[Scott MacGregor]

*** Bug 102824 has been marked as a duplicate of this bug. ***

Comment 5

[grega]

can we throw a 'check' in the N6 mapi enablement process to verify if the user's
OS environment is mapi enabled?

Comment 6

[Rajiv Dayal]

Yes we can, we can infact enable the OS environment for MAPI support. This needs
changes in the win.ini file. Will take this up after the mapi support branch
landing.

Comment 7

[Tiantian Kong]

System administer needs to update the win.ini file if user is not MAPI enabled. 
We'll fix this at the 2nd stage of sMAPI

Comment 8

[Tiantian Kong]

Deleted nsbranch. Will deal with this in the user guide, etc. Proper fix at the 
2nd stage.

Comment 9

[Scott MacGregor]

tiantian please don't remove nsBranch nominations. If you think it's a minus
please just change it to nsBranch-. by removing the keyword you are making it
hard for us to track whether the bug has been considered for the branch.

btw, unless we feel we can't fix this bug, I strongly believe this should be
fixed on the branch. It keeps me from being able to use simple mapi!!! And per
my comments above, I believe marketing is going to have strong feelings about this.

Comment 10

[Jaime Rodriguez, Jr.]

--> curt

Comment 11

[Tiantian Kong]

Curt: 
Here's the entry for the win.ini file. After Krishna provided this to me, it has 
been working on the test on my win 98.

Scot: 

Please copy these into your win.ini, and let us know if it enabled MAPI for you.  

[Mail] 
MAPI=1 
MAPIX=1 
OLEMessaging=1 
CMC=1 
CMCDLLNAME=mapi.dll 
CMCDLLNAME32=MAPI32.DLL 
MAPIXVER=1.0.0.1 

Comment 12

[Sean Su]

Are you sure it's a win.ini file change and not a windows registry change?  
Win.ini is the old way of doing things and should no longer be touched.  Do we 
know if there are equivalent windows registry keys that will also fix this bug?

Comment 13

[Rajiv Dayal]

Yes this is a win.ini change. We need to update registry key as well as deal
with the mapi32.dll to do so but besides that there are these win.ini entries
that are required too. Most systems should have these entries in the win.ini for
MAPI support. These entries not being there is a rare occurance. So when we put
these entries we should check if they are not already present.

Comment 14

[Curt Patrick (gone)]

Okay, I've got a handle on what it takes to get these setting into win.ini. But
I need more info about what needs to be checked or not before making the
settings.  Rajiv you say we should check first the settings are usually already
set.  Will the values for the keys always be the settings you gave me?  If so,
it is actually easier just to always test them than to check first.  It is just
as much work to check them as to set them.  On the other hand, if we really do
need to check first do we need to check each key individually?  What if some are
set and some are not (that actually was the case on my machine)?  What if some
are set to different values than we desire?

Comment 15

[Curt Patrick (gone)]

Correction to the above: "it is actually easier just to always test them than to
check first" should say "it is actually easier just to always SET them than to
check first".

Comment 16

[Krishna Mohan]

I think the following entries are required to enable MAPI.  It is better to 
check whether these entries are present or not before SET.

[Mail] 
MAPI=1 
MAPIX=1 
CMCDLLNAME32=MAPI32.DLL 

Comment 17

[Krishna Mohan]

The entries are same on XP as well.

Comment 18

[Curt Patrick (gone)]

Attachment: Always creates the [mail] section in win.ini

Comment 19

[Curt Patrick (gone)]

Krishna and I spoke further by phone.  Since we always want these settings to be
made, and they are always the same values I'm going for the "keep it simple"
solution, i.e. I always set the values whether they preexist or not.

Comment 20

[Daniel Veditz [:dveditz]]

Comment on attachment 52555 [details] [diff] [review]
Always creates the [mail] section in win.ini

>Index: mail.jst
>===================================================================
>RCS file: /m/src/ns/xpinstall/packager/windows/mail.jst,v

Where's the mozilla tree version?

>+function updateWinIni()
>+{
>+  var fWindows = getFolder("Windows");
>+  var fWinIni  = getWinProfile(fWindows, "win.ini");

I'd prefer
     var fWinIni = getWinProfile(getFolder("Windows"), "win.ini");
but your way works.

>+  fWinIni.writeString("Mail", "MAPI", "1");
>+  fWinIni.writeString("Mail", "MAPIX", "1");
>+  fWinIni.writeString("Mail", "OLEMessaging", "1");
>+  fWinIni.writeString("Mail", "CMC", "1");
>+  fWinIni.writeString("Mail", "CMCDLLNAME", "mapi.dll");
>+  fWinIni.writeString("Mail", "CMCDLLNAME32", "MAPI32.DLL");
>+  fWinIni.writeString("Mail", "MAPIXVER", "1.0.0.1");

Is it seven items or three as a later comment says?  The reference to mapi.dll
seems suspect at least since we don't have one of those, only a mapi32.dll

Comment 21

[Curt Patrick (gone)]

I think I may have misunderstood Krishna about the number of settings needed.  I
thought he was saying that 3 of the 7 that were to be set are required, 4
optional.    I guess that doesn't really make much sense now that I give it a
second thought.  Krishna, are telling me to just set the 3 that you specify in
your 2001-10-08 10:39 message and forget about the other 4 altogether?

Comment 22

[Curt Patrick (gone)]

Attachment: Lean fix for mozilla

Comment 23

[Curt Patrick (gone)]

Attachment: Lean fix for ns

Comment 24

[Curt Patrick (gone)]

Following further discussion with Krisha we determined that only 2 settings need
to be made in win.ini:

[Mail] 
MAPI=1 
CMCDLLNAME32=MAPI32.DLL 

The above patches set these two keys and implement the other coding suggestion
from Dan.

Comment 25

[Sean Su]

Comment on attachment 52620 [details] [diff] [review]
Lean fix for mozilla

r=ssu

Comment 26

[Daniel Veditz [:dveditz]]

Comment on attachment 52620 [details] [diff] [review]
Lean fix for mozilla

sr=dveditz

Comment 27

[Sean Su]

Comment on attachment 52621 [details] [diff] [review]
Lean fix for ns

r=ssu

Comment 28

[Daniel Veditz [:dveditz]]

Comment on attachment 52621 [details] [diff] [review]
Lean fix for ns

sr=dveditz

Comment 29

[Jaime Rodriguez, Jr.]

pls check this into the branch - PDT+

Comment 30

[Curt Patrick (gone)]

Checked in to mozilla, ns both trunk and branch.

Comment 31

[Scott MacGregor]

So I just downloaded this morning's 094 release build and I still have this
problem. After installing NS6, i started it up, made it the default mail client.
Then started up word and i still don't see a send to recipients button in word.
I just have the Send to -> Fax like I mentioned before.....

re-opening...

do I need to restart my computer for this to work? 

Comment 32

[Jaime Rodriguez, Jr.]

*** Bug 104254 has been marked as a duplicate of this bug. ***

Comment 33

[Krishna Mohan]

The fix is present in installation script.  So, if you have installed it you 
should see "[MAPI]" entry in win.ini file.  If you haven't installed and just 
copied the binary files, you may not see these entries.

Comment 34

[Scott MacGregor]

I use the installer when I install new versions. 

I have the following lines in my win.ini file:

[Mail]
MAPI=1
CMCDLLNAME32=MAPI32.DLL

on win2k, word, excel, etc. still aren't listing send to mail recipients as an
option though.

Comment 35

[David :Bienvenu]

Are we all running the same versions of Word? I would think that the newer
versions of word would not look at anything in win.ini, like Sean says. The very
first line of win.ini says "For 16 bit app support".

Comment 36

[Jaime Rodriguez, Jr.]

Everyone I ahve talked to, is using Office 97

Comment 37

[David :Bienvenu]

OK, I found that word97 really is looking at win.ini, but that settings mscott
has there are not sufficient. 

The complete settings below do enable it for me. I don't know which ones aren't
required but I can try removing them one by one

[Mail] 
MAPI=1 
MAPIX=1 
OLEMessaging=1 
CMC=1 
CMCDLLNAME=mapi.dll 
CMCDLLNAME32=MAPI32.DLL 
MAPIXVER=1.0.0.1 

Comment 38

[David :Bienvenu]

OK, I found I need MAPIX=1 as well. Scott's .ini doesn't have that added for
some reason.

Comment 39

[Scott MacGregor]

David, that last one did it for me. I just added:
MAPIX=1

and now MSword is showing me Mail To Recipients.

Comment 40

[Krishna Mohan]

Follow the link below and have a look at the MSDN documentation.  It says MAPIX 
is for full implementation of MAPI.

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/mapi/html/_mapi
1book_determining_which_client_interfaces_are_installed.asp

May we need MAPIX as well. B'cos we are not replacing the dll in the system 
directory if it a smart one.   Typically office application might be determining 
it this way.....

Look into the win.ini file.  (In our case Full MAPI is not there)
Look into the system directory (In our case it is smart dll, which is full mapi)

So, there is a configuration mismatch.  I doubt that is why it is not enabled.

What ever it is, as David says, the soultion might be having MAPIX=1.

Comment 41

[Curt Patrick (gone)]

I can sure add the MAPIX-1 setting to win.ini if that is what is needed.  Is
there any reason why I shouldn't?  i.e., can it hurt anything to add it?

Comment 42

[Curt Patrick (gone)]

Attachment: Adds MAPIX (for mozilla)

Comment 43

[Curt Patrick (gone)]

Attachment: Adds MAPIX (for ns)

Comment 44

[Curt Patrick (gone)]

I went ahead and made up the patches to set MAPIX=1 in win.ini.  If I don't hear
differently I'm going to commit the change once I have r= and sr= reviews.

Comment 45

[Tiantian Kong]

Trix:

Please could you provide a test matrix which will cause the win.ini entry for
MAPI being missing? And verify it once the new patch gets done. 

Please help us to ensure that it'll not be reopened again after the most recent
patch. Thx.

Comment 46

[sol]

From the Microsoft Knowledge Base:

http://support.microsoft.com/support/kb/articles/Q141/0/61.asp

Before you start a Simple Messaging Application Programming Interface (MAPI)
session with a MAPI application, you may need to determine if Simple MAPI is
available on the system.

One way to see if Simple MAPI is available is to check the [Mail] section in the
WIN.INI file for the MAPI entry. This entry will have a value of 1 if Simple
MAPI is installed; 0 if it is not installed. For example, the entry will be the
following if Simple MAPI is available:
[Mail]
MAPI=1 

With the release of MAPI version 1.0, you should also check the MAPIX entry for
the availability of Extended MAPI, CMC entry for Common Mail Calls, and
OLEMessaging for OLE Messaging.

For example, the following entries are for Extended MAPI:
[Mail]
MAPI=1
MAPIX=1
CMC=1
OLEMessaging=1 

Comment 47

[Scott MacGregor]

Curt, I think we want you to wait on checking this new patch in until we are
sure we understand why this flag needs to be added AND if there are potentially
any more flags that 4.7 writes to win.ini that we need to be writing too for mapi.

Comment 48

[Krishna Mohan]

I don't think the following two entries are required for office applications to 
enable the menu item.

CMC=1
OLEMessaging=1 

Comment 49

[Krishna Mohan]

Netscape 4.7 copies just the following entries in the win.in file.
[Mail]
MAPIX=1
MAPI=1

Comment 50

[Scott MacGregor]

cool, then those are the 2 we should set in mozilla too. Thanks for looking that
up Krishna.

Comment 51

[Curt Patrick (gone)]

Attachment: MAPI and MAPIX only (for mozilla)

Comment 52

[Curt Patrick (gone)]

Attachment: MAPI and MAPIX only (for ns)

Comment 53

[Curt Patrick (gone)]

So it looks like everyone is agreed that only MAPI=1 and MAPIX=1 are to be set
in win.ini.  The above two patches do that.

Comment 54

[Sean Su]

Comment on attachment 53229 [details] [diff] [review]
MAPI and MAPIX only (for mozilla)

r=ssu

Comment 55

[Sean Su]

Comment on attachment 53230 [details] [diff] [review]
MAPI and MAPIX only (for ns)

r=ssu

Comment 56

[David :Bienvenu]

Comment on attachment 53230 [details] [diff] [review]
MAPI and MAPIX only (for ns)

sr=bienvenu

Comment 57

[David :Bienvenu]

Comment on attachment 53229 [details] [diff] [review]
MAPI and MAPIX only (for mozilla)

sr=bienvenu

Comment 58

[Krishna Mohan]

I have tested setting MAPI=1 and MAPIX=1 on 98, ME, NT, 2000 and XP.  It is 
enabling the Send menu properly.

Comment 59

[Curt Patrick (gone)]

Committed patches 53229 and 53230 to both trunk and branch.

Comment 60

[Jaime Rodriguez, Jr.]

pls verify this fix with today's branch build asap.

Comment 61

[Tiantian Kong]

I verified this fix on my win NT4.0 with today's branch build. It's working
beautifully. 

Trix is testing on all other platforms.

Comment 62

[Trix Supremo]

verified on 2001-10-15-05-0.9.4 on all win32 supp. platforms.