No Search Capability when Outlook in OCL mode

RESOLVED EXPIRED

Status

SeaMonkey
MailNews: Address Book & Contacts
RESOLVED EXPIRED
16 years ago
7 years ago

People

(Reporter: John Marmion, Unassigned)

Tracking

(Blocks: 1 bug)

Trunk
x86
Windows 2000
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

16 years ago
Outlook can be configured in Internet-only mode with a local Address Book (OIL)
or as a Corporate/WorkGroup Client using a local Address Book (OCL). Mozilla is
capable of accessing these Outlook Address Books dynamically. In the latter
case, no data is returned using the quick search or advanced search in Mozilla.
This problem is inherent in the MAPI implementation of Outlook in this mode. The
Search capabilities of Outlook itself in this mode are very limited in
comparison to the OIL mode. Nevertheless, Mozilla can employ the proxy search
capabilities to return Data.
(Reporter)

Updated

16 years ago
Depends on: 111968, 118119
(Reporter)

Comment 1

15 years ago
I recently had another look at this. MAPI uses a Restriction() to return data.
The error code MAPI_E_TOO_COMPLEX (0x80040117) appears to be always returned no
matter  how simple I create a query. The Outlook UI appears to support a very
limited query capability using the DisplayName attribute and the "contains"
operator. Nevertheless, I have been unable to implement this limited search
capability.
mass re-assign.
Assignee: racham → sspitzer

Updated

14 years ago
Blocks: 213274
Product: Browser → Seamonkey

Updated

12 years ago
Assignee: sspitzer → mail
QA Contact: nbaca → addressbook

Comment 3

8 years ago
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
Status: NEW → UNCONFIRMED

Comment 4

7 years ago
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
Status: UNCONFIRMED → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.