Sun Java System Messaging Server 6.3 Administration Guide

ProcedureTo Configure Message Types

To configure a message type, use the configutil utility to set the store.messagetype parameter values that define and identify the message type.

  1. Enable message types by setting the store.messagetype.enable parameter to on.

    This configutil parameter allows the message store to identify and manipulate message types. You must set this parameter before you can configure an individual message type.

    For example, enter the following command:


    configutil -o store.messagetype.enable -v 1
  2. Define and identify the message type by setting the store.messagetype.x parameter.

    The variable x identifies this particular message type in the message store. The variable x must be an integer greater than zero and less than 64. You can define up to 63 message types by iteratively configuring this parameter with unique integers.

    You define the value of the message type with a text string that describes the type.

    For example, to define a text message type, you could enter the following command:


    configutil -o store.messagetype.1 -v text/plain

    To define a voice message type, you could enter the following command:


    configutil -o store.messagetype.2 -v multipart/voice-message
  3. Provide a flag name for the message type by setting the store.messagetype.x.flagname parameter.

    This parameter creates a unique flag that identifies the message type. The flag is automatically set whenever a message of this type first arrives in the message store and remains associated with the message until it is purged. The flag name value is a text string that describes the message type. It does not have to be the same as the value set with the store.messagetype.x parameter.

    The variable x is the integer ID of the message type defined with the store.messagetype.x parameter.

    For example, to define flag names for the message types configured in the preceding step, enter the following commands:


    configutil -o store.messagetype.1.flagname -v text
    
    configutil -o store.messagetype.2.flagname -v voice_message
  4. Configure a quota root name for the message type by setting the store.messagetype.x.quotaroot parameter.

    This parameter enables the quota function to identify and manage a quota root for this message type. The parameter value is a name—a text string that describes the message type. It does not have to be the same as the value set with the store.messagetype.x parameter.

    The variable x is the integer ID of the message type defined with the store.messagetype.x parameter.

    When this parameter is configured, you can set a quota that applies to the specified message type. For more information, see 20.7.4 Administering Quotas by Message Type.

    For example, to enable the use of quota roots for the message types configured in the preceding steps, enter the following commands:


    configutil -o store.messagetype.1.quotaroot -v text
    
    configutil -o store.messagetype.2.quotaroot -v voice
  5. To configure an alternate header field for identifying the message type, set the store.messagetype.header parameter.

    By default, the message store reads the Content-Type header field to determine the message type. Configure the store.messagetype.header parameter only if you want to use a different header field for identifying the message type. The value of this parameter is a text string.

    For example, to use a field called X-Message-Type, enter the following command:


    configutil -o store.messagetype.header -v X-Message-Type