Common Mail portlet reference

Portal, Express Beta Version 6.1
Operating systems: i5/OS, Linux,Windows

Common Mail portlet reference

Administrators can configure the Common Mail portlet for mail servers that use IMAP4 protocol. In addition to basic mail support, the portlet also supports features such as an inline rich text editor for message creation and editing, and a spell checker.

The Common Mail portlet is found on the Welcome > Messaging page.

Using the Common Mail portlet

The Common Mail portlet requires that you select Configure (first, click the down arrow in the portlet title bar) and then click the wrench icon. This displays a second configuration screen that is IMAP server-specific and contains these sections:

Source: This section allows you to specify the default incoming and outgoing server for users, whether to use a secure connection for connections to the mail server, whether to only display subscribed IMAP folders, and whether to allow or prevent users from changing the mail source when they select Personalize. Note: If you are an administrator, you see the command Edit Shared Settings instead of Personalize. This command works the same as Personalize except that your changes apply to all users of the instance of the portlet whose settings you are editing, up until the time a user decides to personalize the portlet. Use caution when editing shared settings. For more information, see the topic on configuration levels for portlets.

Authentication: This section allows you to specify which credential slot to store authentication information in. Note: Make sure that you when you create credential slots, you type identifying text in the Description field on the Select Vault page for each vault slot. In configure mode for the Common Mail portlet, the Credential vault slot field does not display vault slots that do not have descriptions.

Features: This section allows you to select features to make available or unavailable to users, such as the rich text editor and the ability to attach files.

The Common Mail portlet supports Web Services for Remote Portlets (WSRP). See the topic on setting up the Common Mail portlet as a remote portlet.

Test assumptions

The Common Mail portlet assumes that a supported back-end system has been configured according to system specifications.

Client requirements

This portlet supports browsers and devices capable of rendering HTML markup. The following table provides detailed information.

Minimum requirements for HTML
Markup level	HTML 4.0 Transitional
Java™ applet	None
JavaScript™	1.30
<iframe>	No
Style sheets	Portal styles
Software	The Common Mail portlet is compatible with the specific Web browser software releases listed in the WebSphere Portal Express detailed system requirements.
Accessibility	Yes

Deployment/installation

The Common Mail portlet is installed automatically as part of WebSphere Portal Express installation.

Configuration parameters

Most configuration options for this portlet are set using configure mode. In configure mode, keep the following in mind:

If you enable features for users, log out and log back in to see the changes in the portlet.

You must specify the fully qualified host name of the server. Additionally, users that have access to change the server by using Edit Shared Settings or Personalize must specify the server's fully qualified host name.

The following configuration parameters are available in this portlet.

Parameter	Value
wsrp_remote_portlet	Specifies whether the portlet is supported as a remote WSRP service. This parameter does not exist by default; the administrator must add it to the portlet instance. Example: `true`
CPP_PassHttpCookies	Allows the portlet to work with third-party authentication software such as Computer Associates eTrust SiteMinder by specifying custom cookies. Separate multiple cookie names with a semicolon. This parameter does not exist by default; the administrator must add it to the portlet instance. Example: `cookie1;cookie2`
CPP_PassHttpHeaders	Allows the administrator to specify additional request headers. Separate multiple headers with a semicolon. This parameter does not exist by default; the administrator must add it to the portlet instance. Example: `header1;header2`

Parameter

Value

wsrp_remote_portlet

Specifies whether the portlet is supported as a remote WSRP service.

This parameter does not exist by default; the administrator must add it to the portlet instance.

Example: true

CPP_PassHttpCookies

Allows the portlet to work with third-party authentication software such as Computer Associates eTrust SiteMinder by specifying custom cookies. Separate multiple cookie names with a semicolon.

This parameter does not exist by default; the administrator must add it to the portlet instance.

Example: cookie1;cookie2

CPP_PassHttpHeaders

Allows the administrator to specify additional request headers. Separate multiple headers with a semicolon.

This parameter does not exist by default; the administrator must add it to the portlet instance.

Example: header1;header2

Parent topic: Domino portlets reference Related concepts
Configuration levels for portlets Related tasks
Set up the Common Mail portlet as a remote portlet Related information

WebSphere Portal detailed system requirements Portlet authentication IBM Support Web accessibility

Library | Support | Terms of use |