After the introduction of Exchange 2010 RTM, many developers –especially on Sharepoint – complained that Microsoft had dropped Web Parts support. Web Parts are small pieces of (Exchange) content which you can incorporate in your own (Sharepoint) application or personalized web page using customized URLs. The source of this content can the mailbox of the authenticated user or other mailboxes to which that user has sufficient permissions.
For example, in Exchange 2007 you can access a web part showing your weekly Exchange calendar using the following URL:
Now in Exchange 2010 RTM this didn’t work anymore. Luckily, with SP1 Web Parts were reinstated. Calling a Web Part through an URL always starts with https://<FQDN>/owa, followed by one or more of the following parameters:
- SMTP address – This overrides the mailbox to open by specifying the SMTP address associated with the mailbox you want to access, e.g. email@example.com. This parameter always needs to be specified first as part of the location, i.e. it’s not a parameter;
- cmd – Must be used present when not specifying a specific mailbox and it’s assigned value should be “contents”. This parameter makes sure the Web Part is shown and not the full OWA interface;
- id (optional) – opens a specific folder by specifying its PR_ENTRY_ID value;
- fpath (optional) – specifies mailbox folder to display starting from the root folder, e.g. projects/2010. Note that when you specify Inbox you might encounter issues because of user’s localization settings, i.e. “Postvak IN” (Dutch) instead of Inbox;
- module (optional) – specifies one of the standard folders to open, preventing localization issues. Possible values are Inbox, Calendar, Contacts, Tasks or Publicfolders;
- view (optional) – Configure the view depending on the folder. For example, for calendar you can specify monthly, weekly or daily; for Inbox view you can specify a few sort options.
- d, m, y (optional) – Allows you to specify a date for the calendar view;
- part (optional) – When specifying part=1, the Web Part will be shown using reduced UI to make it more compact.
Note that when constructing the URL you need to comply with URL encoding rules, so replace a space with %20 and a slash with %2f for example. More information on this subject here. Also, use “?” before the first parameter and “&” between any additional parameters.
Open a monthly view of our calendar:
Open our Inbox:
Open our inbox with a reduced UI (to fit it in smaller spaces):
Access the Projects folder located in the root of another mailbox:
For those unfamiliar with this Web Part functionality, be sure to check it out as it allows you to easily integrate Exchange information in your application or website. More detailed information on using Outlook Web App Web Parts check here. For those running Exchange 2007, this information is located here (there are some minor differences).
Hi, is it possible to link to a public folder like https:///firstname.lastname@example.org/?cmd=contents&fpath=projects&module=publicfolders. Cheers!
Or try https://../public/[folder]/?cmd=contents?part=1
I have used http://10.11.72.27/exchange/chris.foster/inbox/?cmd=contents&module=inbox&part=1 on a sharepoint 2010 server to access a Outlook 2003 mailbox. I want to change where my name is chris.foster to %username% (of the logged on user) so that each user goes to their mailbox. %username% and dont work. I am using IE9 and the page is in sharepoint 2010. by taking out a username before the inbox doesn’t work. Many thanks
Pingback: Dave Stork's IMHO : Thoughts on “VMware Zimbra vs. Microsoft Exchange”
Pingback: Thoughts on "VMware Zimbra vs Microsoft Exchange" | EighTwOne (821)
Pingback: Thoughts on “VMware Zimbra vs. Microsoft Exchange” | Dave Stork's IMHO
Pingback: Thoughts on “VMware Zimbra vs. Microsoft Exchange” » Dave Stork's IMHO