Chapter 4
Customizing Advanced Features
This chapter describes how to perform advanced customizations. It also provides HTML files and their location and details on features that are fully customizable for the Messenger Express user interface.
This chapter contains the following sections:
Advanced Customization Overview
In addition to the Messenger Express features discussed in Chapter 2 "Customizing General Features," and Chapter 3 "Customizing User Interface Features," many others are fully customizable. However, to take advantage of these features, an in-depth knowledge of JavaScript is required. In addition, migration problems might be encountered, for example, when attempting to reconfigure JavaScript files.
|
Note
|
This chapter does not provide code samples for the advanced customizations. Also, an advanced knowledge of JavaScript and HTML is assumed.
|
Messenger Express User Interface Customizable Features
Table 4-1 shows the features of the Messenger Express user interface that are fully customizable.
Table 4-1 Messenger Express User Interface Customizable Features
|
Features
|
Files
|
|
Attachments
|
attach_fs.html
|
|
Collection of mail from another server
|
collect_fs.html
|
|
Message composition
|
comp_fs.html
|
|
Folder management tab
|
fldr_fs.html
|
|
Addresses search
|
ldap_fs.html
|
|
Mailbox management tab
|
mbox_fs.html
|
|
Message management tab
|
msg_fs.html
|
|
Personalize option management
|
opts_fs.html
|
|
Return receipt
|
receipt_fs.html
|
|
Subscribe Folders
|
subscribe_fs.html
|
|
Search Messages
|
searchmsg_fs.html
|
|
Emoticon
|
emoticons.html
|
Attachments
You can modify the following attachments options:
Browse button
Attach, Cancel, Help buttons
HTML File Mapping
The HTML file that controls the attachment related features is attach_fs.html.
Collect Mail from Another Server
You can modify the following when collecting mail from another server:
POP server name (text field)
POP user ID (text field)
Password (text field)
Delete messages from server (select button)
Save to folder (list box)
Collect, Cancel, and Help (button)
HTML File Mapping
The HTML file that controls the mail collection feature is collect_fs.html.
Message Composition
The message composition feature enables basic mail functions. You can modify the following message composition options:
Compose new message
Reply to the sender
Reply to all recipients of the message including the sender
Forward message to others
Move message to folder
Delete message
Navigate through messages using Prev or Next icon.
HTML File Mapping
The HTML file that controls the message composition feature is msg_fs.html.
Folder Management Tab
The folder management tab enables access to server-side folders. You can modify the following folder management tab options:
Update content of folder
Create new folder
Rename folder
Share folder
Delete existing folder
HTML File Mapping
The HTML file that controls the folder management tab feature is fldr_fs.html.
Address Search
The address search feature enables the management of address search in LDAP directories. You can modify the following address search options:
Search for people in the selected search directory (list box)
Insert full name (text field)
Contain field (text field)
Search, Close (buttons)
To, Cc, Bcc (buttons)
HTML File Mapping
The HTML file that controls the address search feature is lookup_fs.html.
Mailbox Management Tab
The mailbox management tab enables access to a mailbox. You can modify the following mailbox management tab options:
Get new message
Compose new message
Search for message
Move message to selected folder
Delete message
Undelete message
Select message
Select all messages
Collect external messages
HTML File Mapping
The HTML file that controls the mailbox management tab feature is mbox_fs.html.
Personal Option Management (Options Tab)
You can modify the following Options tab options:
Account summary
Personal information - change personal information
Password - change and reset password
Settings
Appearance
Vacation message - set vacation message
Delegated administrator
HTML File Mapping
The HTML file that controls the options tab features is opts_fs.html.
Return Receipt
The return receipt feature enables the management of return receipts.
HTML File Mapping
The file that controls the return receipt feature is receipt_fs.html.
Customization of Users' Default LDAP Attributes
The Messenger Express server loads a default set of LDAP attributes for a user at the start of a session. These attributes are as follows:
|
cn
|
|
givenName
|
|
mail
|
|
mailAlternateAddress
|
|
mailAutoReplyMode
|
|
mailAutoReplySubject
|
|
mailAutoReplyText
|
|
mailAutoReplyTextInternal
|
|
mailAutoReplyTimeout
|
|
mailDeliveryOption
|
|
mailForwardingAddress
|
|
mailQuota,mailMsgQuota
|
|
preferredLanguage
|
|
sn
|
|
uid
|
|
vacationEndDate
|
|
vacationStartDate
|
You might want to obtain other customized LDAP attributes from the server. For example, an ISP might have a custom LDAP attribute assigned to all users called myuserclass. This attribute could denote different types of users that access services, including Messenger Express. Possible values for this attribute are "regular" and "vip".
Depending on the type of user (that is, the value of the myuserclass LDAP attribute), different advertisement are presented to the user when they log into Messenger Express (Messenger Express is customized to display banner advertisement). If the customized client has access to the myuserclass LDAP attribute, the type of user can be determined and the relevant banner advertisement for that user type is displayed.
To obtain other customized LDAP attributes from the server, use configutil to modify the service.http.extrauserldapattrs configuration parameter. The attributes are read-only by default. If the customer wants to modify an attribute using the Messenger Express code, that attribute needs to be marked read-write by appending the suffix w.
The example below assumes the customer wants to display banner advertisements depending on the class of the user and that the client program allows the user to edit a link to a home page:
configutil -l -o service.http.extrauserldapattrs -v "myuserclass,homepage:w "
Domain Specific Customization
This section describes how to customize the Messenger Express client interface for each domain.
You can perform the following tasks to customize the Messenger Express client interface:
Create a directory with the domain name under server-root/html directory.
Populate this directory with the customized versions of the files from the original directory hierarchy.
-
For example, assume that you have a domain called siroe. To change the icon for siroe domain, add a new icon in the imx directory of siroe.com and change the reference to it in main.js file:
|
html/...
|
// default interface
|
|
html/imx/...
|
// default interface
|
|
html/en/...
|
// default interface
|
|
html/siroe.com/main.js
|
// refers to imx/bottle.gif
|
|
html/siroe.com/imx/bottle.gif
|
|
After login, the server refers the user agent to pick the file main.html which is located in the domain/lang directory. The main.html file contains relative references to the rest of the interface. The client requests all the files that make the interface in the directory. If these files exist, then they are displayed otherwise there is fallback to the default setup files.
-
If you have many domains and only a few distinct `brands' then you can use links to make the server use the correct version:
|
html/...
|
// default interface
|
|
html/sesta.com/...
|
// customized interface for brand 1
|
|
html/varrius.com -> sesta.com
|
// default interface
|
Domain From URL
The server listens to all IP addresses and can still present a customized interface before login occurs. It does this by looking at the URL and determines if it contains a known domain presenting a per domain login screen.
For example, for the per domain login screen: http://webmail.sesta.com/, the server sends the page from the location: html/sesta.com/en/default.html.
In this case a user does not have to append @domain to the username to login.