Set Common Mail preferences
To enable user mail preferences such as signatures and the default text style used to compose mail, you define the appropriate properties in a property extension database.
You can configure the following user mail preferences:
ibm-lwpPIMMailSignatureType Whether the signature contains rich text or plain content ibm-lwpPIMMailSignature Actual content of the signature ibm-lwpPIMMailIncludeMsgSignature Whether to include the signature in e-mail messages ibm-lwpMsgMailComposeWithPlainText Whether to compose e-mail messages using rich text or plain text by default For detailed instructions on setting up a property extension database and defining parameters, see the appropriate topic for your operating system
For example configuring a property extension database on Windows.
Keep in mind that add each parameter one at a time. For example, after you set up the property extension database and propagate security changes open the wkplc.properties file, add the first required parameter, save the updated file, and then run the task to add the property. Repeat this process for each parameter that you want to add.
- Define ibm-lwpPIMMailSignatureType as follows:
la.propertyName=ibm-lwpPIMMailSignatureType la.dataType=String la.EntityType=PersonAccount la.mltiValued=false- Define ibm-lwpPIMMailSignature as follows:
la.propertyName=ibm-lwpPIMMailSignature la.dataType=String la.EntityType=PersonAccount la.mltiValued=false- Define ibm-lwpPIMMailIncludeMsgSignature as follows:
la.propertyName=ibm-lwpPIMMailIncludeMsgSignature la.dataType=int la.EntityType=PersonAccount la.mltiValued=false- Define ibm-lwpMsgMailComposeWithPlainText as follows:
la.propertyName=bm-lwpMsgMailComposeWithPlainText la.dataType=int la.EntityType=PersonAccount la.mltiValued=false
Parent topic
Configure the Common Mail portletNext topic:
Enabling Spell Checker in the Common Mail portlet