I was doing a quantify run, getting a build instrumented, and I noticed these two DLLs flash by (mozilla trunk build, pull 12am Jan 11, running with a completely default mozilla profile [brand new]). bin/msgbsutl.dll bin/components/msgMapi.dll I thought there was a bug about splitting up localstore.rdf or somehow otherwise deferring the loading of mailnews dlls during a browser-only startup, but I can't find it right now. But the msgMapi.dll is obviously a new thing [that it is loaded at startup]. So, are we going to defer the loading of these DLLs?

reassigning to rajiv. I'm not sure if these are required to load or not or if there's a way to prevent them from loading for someone who doesn't have this turned on.

Since MAPI uses MS COM for IPC, the MAPI support exe class object in Mozilla needs to be registered with OLE during startup. Thus it is required that msgMapi.dll is loaded during startup or else the MAPI client applications will not be able to connect to Mozilla for a MAPI call.

So, if I explicitly do not want to use MAPI ... user_pref("mailnews.default_mail_client", false); // is that the right pref? ... I must still load and register as a MAPI client, because ...? Or am I missing something obvious here.

Second jrgm. Also even when mapi is enabled, the code to register should be small and trivial enough to be in the application rather than in the dll, thus preventing the load of the dll on startup.

This bug is partially identical to bug 106087.

MASS-CHANGE: This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614

MASS-CHANGE: This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago. Because of this, we're resolving the bug as EXPIRED. If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component. Query tag for this change: EXPIRED-20100420