File URL Namespace
File URL Namespace
This content is no longer actively maintained. It is provided as is, for anyone who may still be using these technologies, with no warranties or claims of accuracy with regard to the most recent product version or service release. ExOLEDB registers with the OLE DB RootBinder to support both a public and private namespace in local Exchange private and public stores. Both namespaces are prefixed by "file://./backofficestorage". This is staticit cannot be changed by system administration or any other means. The public namespace is:
This is for all public folder databases, including the default MAPI public folder database. DomainName specifies the fully qualified domain name for the organization. TopLevelFolder specifies the top folder in a folder tree for a particular MDB. For example:
Folder trees outside of the default MAPI public folder are not visible to Microsoft® Outlook® 2000 and prior MAPI clients.
The private namespace is:
This namespace is for all private databases. The UserName string is the part of the address string that comes before the "@" of the user's proxy address. For example:
The store will notify the ExOLEDB provider when a new database is created. Also, a directory listing at the "file://./backofficestorage" level will return the list of organizations. A directory listing at the "file://./backofficestorage/DomainName" will return the list of top level folders for the specified domain or organization, including the static "MBX" string, which represents private mailboxes. A directory listing at the "file://./backofficestorage/DomainName/MBX" will return an empty listto preserve mailbox privacy. However, a directory listing of a specific user, such as "file://./backofficestorage/DomainName/MBX/UserName", will give a list of the top-level folders within the IPM sub-tree (for example, Inbox, Outbox, Deleted Items, and so on). You can change to any of these directories and continue to navigate down the folder hierarchy.
Access to a user's NON-IPM sub-tree is via the URL "file://./backofficestorage/DomainName/MBX/UserName/NON_IPM_SUBTREE". The NON-IPM sub-tree is not visible in a directory listing of a user mailbox. The only way to access the NON-IPM sub-tree is to explicitly change the directory to the NON-IPM folder. After you bind to the NON-IPM folder, you can get a directory listing of the folders under the NON-IPM folder for a particular user.
Access to the top level of a public NON-IPM sub-tree is similar via the URL "file://./backofficestorage/DomainName/TopLevelFolderName/NON_IPM_SUBTREE". The behavior is the same as described for private databases.
Here are some additional examples for further clarification:
- Browse to file://./backofficestorage/DomainName/
Result: List of top-level folders plus an MBX folder.
- Browse to file://./backofficestorage/DomainName/TopLevelFolder1
Result: List of folders under TopLevelFolder1.
- Browse to file://./backofficestorage/DomainName/ where DomainName doesn't exist
Result: MBX folder.
- Browse to file://./backofficestorage/DomainName/MBX where DomainName does or doesn't exist
Result: Empty directory.
- Browse to file://./backofficestorage/DomainName/TopLevelFolder1 where DomainName doesn't exist
Result: Command fails.
- Browse to file://./backofficestorage/DomainName/MBX/User/NON-IPM-SUBTREE
Result: Lists the top-level folders in the NON-IPM-SUBTREE for this user. The NON-IPM-SUBTREE is not visible in a normal directory listing of //./backofficestorage/DomainName/MBX/UserName. You must specify the NON-IPM-SUBTREE explicitly to get its contents.
- Browse to file://./backofficestorage/DomainName/TopLevelFolder1/NON-IPM-SUBTREE
Result: Lists the top-level folders in the NON-IPM-SUBTREE for TopLevelFolder1.