Release 5.2
A86653-01
 Library |
 Solution Area |
 Index |
| Oracle eMail Server Administrator's Guide Release 5.2 A86653-01 |
|
You can configure many process parameters to customize your eMail Server system. See Chapter 9, "Managing Processes", for more information about managing processes and changing process parameters.
The following process parameters, discussed in this chapter, are available:
There are some parameters that are available for all types of processes. For example, name and instance are common parameters or properties that describe each registered process instance. Schedules that specify when and how long the process run are also parameters that are common to all process types.
The following parameters are properties that describe the processes. You can specify these properties when you register a process instance, or you can modify them later, if necessary.
OOMGR provides initial values for these common process parameters. However, OOMGR does not maintain inherited defaults for them. Therefore, default and instance-level settings do not apply to the common parameters.
Schedule parameters determine when and for how long a process runs. The four time parameters are grouped into records called time slices that each represent one or more hours of a day.
Each process can have between 1 and 24 time slices. You can specify one time slice that covers 24 hours, or multiple time slices that each represent one or more hours. However, the time slices you define for each process must cover exactly 24 hours.
Each time slices consists of three or four parameters, depending on whether the process is active during the time interval the time slice covers. The following parameters are available:
Some processes do not use schedules because they are constantly available. The protocol server processes (IMAP4SRV, IOLISTENER, and POP3SRV) run whenever a client makes a connection. Likewise, the LDAP server processes (IOLDAP, IOODSSYNC, and ODSIOSYNC) run whenever the directories are updated and require synchronization. If you set schedules for these processes, they will be ignored.
| Parameter | Description and Values |
|---|---|
|
|
This parameter is reserved for future use. |
|
|
Specifies how attachments are presented to the recipient. Adheres to RFC1806 syntax and semantics. Valid values:
Default value: |
|
|
Default character set for text objects. Valid values: Refer to "Configuring the Gateway for Multibyte Support" for a complete list of available character sets. Default Value: |
|
|
Default transfer encoding method for binary body parts when none is specified. Not case sensitive. Valid values: Standard transfer encoding methods are base64, quoted-printable, 7bit, 8bit, and binary. Non-standard encoding methods can also be used. "Configuring the Method for Encoding MIME Content" for more information about these values. Default value: |
|
|
Defines the content transfer encoding method used to encode text body parts of outbound messages. Valid values: Standard transfer encoding methods are base64, quoted-printable, 7bit, 8bit, and binary. Non-standard encoding methods can also be used. "Configuring the Method for Encoding MIME Content" for more information about these values. Default value: |
|
|
Type ID for the default attachment type for unmapped MIME type attachments on inbound messages. Also used if attachment type converter or decoder for content transfer encoding fails. "Creating a MIME Attachment Map" for a list of attachment Type IDs. Default value: |
|
|
Specifies whether the gateway should automatically decode the data encoded with UUENCODE. Valid values: Default value: |
|
|
Specifies whether the gateway should encode binary data. It creates RFC-1521 compliant messages, but for 8-bit body parts, the gateway codes and specifies a content-Transfer-Encoding: x-uuencode header. Valid values: Default value: |
|
|
String attached to incomplete eMail Server sender address (addresses that do not contain @ or !) and unqualified receipt addresses. Default value: |
|
|
"Using Server Process Logs" for information about locating and reading log files. Valid values:
Default value: |
|
|
Adds the gateway name to each inbound address so that the receiver can reply automatically. If you have created a rewriting rule that performs this function, do not use this parameter. Valid values: Default value: |
|
|
Type ID for the default eMail Server attachment type for unmapped MIME types on inbound messages. Also the attachment type used if an attachment type converter of decoder for content transfer encoding fails. "Creating a MIME Attachment Map" for a list of attachment Type IDs. Default value: |
|
store_body |
Specifies whether the gateway should store the body parts encoded, decoded, or both. Valid values:
If this is set to If this is set to 4 (store S/MIME), then messages are encoded, all others are decoded.
If this is set to Default value: |
|
|
Specifies whether the gateway should store the message shell with the body part information. Valid values: Default value: |
|
|
Specifies whether to remove the recipient prefix from the Reply-to and Sender name fields. For example, UNIX: user.com becomes user.com. Valid values: Default value: |
|
|
Specifies whether to remove qualified domain identifiers from the Reply-to, Sender, and Recipient fields. If Valid values: Default value: |
The LDAP server processes synchronize directory data between the eMail Server directory and Oracle Internet Directory, or any other LDAP directory. Each of these processes have specific parameters that you can configure to define how the processes work.
The forward synchronization server has a new parameter called the MIGRATED_OBJECT_TYPE, that specifies the object type to be synchronized for a particular instance of the server. In the performance perspective, the new version of the server also manipulates the database table IOLM_SYNCLOG to significantly shorten the process time.
In the new version of the server, an administrator can specify one of the following object types to synchronize for a particular instance of the server in the newly added parameter. The available object types are:
If an administrator wants to synchronize all object types for a particular instance of the server, they can leave the parameter value to null. The following is an example of running two instances of forward synchronization server.
When two instances of the forward synchronization servers are running at the same time with instance=1 picks up all object types, while instance=2 picks up ONLY `dl'. With the new version of the server, in order to prevent deadlock, instance=1 server is supposed to pick up all objects. However, before doing it, instance=1 server checks if any other instance of the server is picking up any particular object type for synchronization. If so, instance=1 server picks up all object types EXCEPT the one(s) that are being processed by other instance(s). In this example, instance=1 server picks up all object types EXCEPT object type `dl' because instance=2 server is set to pick up object type `dl'.
Another new feature in the new version of the server is manipulationof the database table IOLM_SYNCLOG. Everytime a migration operation(INSERT, UPDATE, or DELETE) is performed, one row is inserted into the database table IOLM_SYNCLOG.
Considering the following situation: for a particular object, an INSERT operation, multiple (say, 10 of them) UPDATE operations, and a DELETE operation rows have been inserted into the IOLM_SYNCLOG table before an instance of the server wakes up and performs the synchronization. With the enhancement, the forward synchronization server first looks at the IOLM_SYNCLOG table to see if some rows can be trimmed off before performing the migration.
In this example, because an INSERT and a DELETE operation for a particular object exists at the same time, the server shouldn't really have to do anything except deleting all the rows for the particular object in the IOLM_SYNCLOG table.
The followings are the situations and the corresponding solutions that
can actually save the process time:
These few case could significantly reduce the process time, especially when the case that a DL will get updated so often within a certain period of time.
The following forward synchronization parameters are available:
The following reverse synchronization parameters are available:
The messaging server processes perform the basic functions of handling messages and information in the eMail Server system. Each of these processes has specific parameters that you can configure to define how the processes work.
The following collector process parameters are available:
| Parameter | Description and Values |
|---|---|
|
|
Specifies the number of days message billing data is kept. Valid Values: Default value: |
|
|
Specifies whether the process removes unneeded internal replicator items. Valid values:
Default value: |
|
|
Number of days to retain calendar events. Valid Values: Default value: |
|
|
Number of days to retain internal log messages. Valid Values: Default value: |
|
|
"Using Server Process Logs" for information about locating and reading log files. Valid values:
Default value: |
|
|
Specifies whether this process collects unreferenced messages. Valid values: Default value: |
|
|
Specifies whether this process removes expired messages. Valid values: Default value: |
|
|
Specifies whether this process identifies unreferenced messages. Valid values: Default value: |
|
|
Specifies whether the collector process will be running in the Oracle Parallel Server environment. If this parameter is enabled, then the collector only processes messages originating from the same node. Enabling this parameter can increase performance, but is not required.See Also:: Oracle Parallel Server documentation for more information about this environment Valid values: Default value: |
|
|
Specifies how many days queue statistics will be kept in the system. Specifying a shorter number of days may save some disk space, but specifying a longer number of days will give you a more accurate view of the system snapshot from the monitor/statistics server process. Valid values: Default value: |
|
|
Specifies whether to remove original recipient information from existing messages by the collector process. This parameter should be kept at the default value of 0. If your system's postman delivery is slow due to frequently receiving messages with a large recipient list, then you can turn on this option to improve system performance. Valid values:
Default value: |
|
|
Specifies whether this process cleans up obsolete registration entries of eMail Server processes in the database as a result of an abnormal shutdown. Valid values: Default value: |
|
|
Specifies how many days the replication log will be kept in the system. The replication log keeps track of changes to directory entries and other information that needs to be replicated. If the replicator process is not running for an extended period, then you might want to increase the number of days this log is kept so that the replicator can process the information when it is running again. If the replicator process runs regularly, then it should be sufficient to use the default value. Valid values: Default value: |
|
|
Specifies whether this process cleans up events. Valid values: Default value: |
|
|
Enabling this parameter means that the collector process will clean up all Oracle ConText search cache data. Valid values: Default value: |
|
|
Specifies whether this process cleans up inactive database shadow processes. Valid values:
Default Value: |
|
|
Relevant only if this process runs on a node containing the V1-V2 gateway. Specifies whether this process collects V1 garbage messages, or if this process runs on the V1-V2 gateway node. Valid values:
Default value: |
The guardian process, ofcguard, does not have parameters to set.
The following monitor process parameters are available:
| Parameter | Description and Values |
|---|---|
|
|
"Using Server Process Logs" for information about locating and reading log files. Valid values:
Default value: |
|
|
Subject line for a "No problem" report. Default value: |
|
|
Specifies who receives no-problem notifications. The account name in this field receives reports when the monitor does not find any problems. Valid values: Default value: |
|
|
Subject line for a problem report. Default value: |
|
|
Specifies who receives problem notifications. The account name in this field receives reports of any problems the monitor finds. Valid values: Default value: |
The following postman process parameters are available:
| Parameter | Description and Values |
|---|---|
|
|
Number of days between automatic replies being generated from a recipient to the same sender, preventing the problem of multiple automatic messages to one user.
For example, suppose Amy Johnson is on vacation for a week and sets up an Auto Reply message. Any message sent to her or to groups or lists of which she is a member triggers the Auto Reply message. The value of Valid values: Default value: |
|
|
Specifies whether delivery statistics information is collected. This information is used by the statistics server for a detailed statistics gathering. Setting this parameter may slow down postman process performance because of the additional work being done by the process.See Also:: "Scripts for Message-Billing Data Collection" for more information Valid values: Default value: |
|
|
Specifies whether this process handles messages destined for local users. Valid values: Default value: |
|
|
"Using Server Process Logs" for information about locating and reading log files. Valid values:
Default value: |
|
|
This parameter is reserved for future use. |
|
|
This parameter is reserved for future use. |
|
|
Specifies whether the postman process will be running in the Oracle Parallel Server environment. If this parameter is enabled, then the postman only processes messages originating from the same node. You should enable this parameter to increase performance if every OPS node has the same number of postman processes running. If you disable this parameter, then you will have more flexibility in which processes are running on which nodes, but there will be a decrease in performance.See Also:: Oracle Parallel Server documentation for more information about this environment Valid values: Default value: |
|
|
Specifies who receives problem notifications when a message is returned to the sender, and when a message is placed in the Dead Message queue. The account name in this field receives reports of any problems the monitor finds. Valid values: Default value: |
|
|
Specifies whether billing information should be collected whenever a message is received. Setting this parameter may slow down postman process performance because of the additional work being done by the process.See Also:: "Scripts for Message-Billing Data Collection" for more information. Valid values:
Default value: |
|
|
Specifies whether this process handles messages destined for remote users. Valid values: Default value: |
|
|
Number of days a message remains in an outbound queue to a remote node. If the message is not delivered within this time period, then the postman returns it to the sender. Valid values: Default value: |
|
|
Number of postman cycles this process waits before checking the route table for updated or new routing information. The postman also checks the route table each time you start or refresh this process. Valid values: Default value: |
|
|
Number of days a message is held in this node's Dead Message queue before the collector removes it. Valid values: Default value: |
|
|
Specifies whether billing information should be collected whenever a message is sent. Setting this parameter may slow down postman process performance because of the additional work being done by the process.See Also:: "Scripts for Message-Billing Data Collection" for more information. Valid values:
Default value: |
|
|
Specifies whether this process acts as a V1-V2 gateway. Valid values: Default value: |
|
|
Maximum number of messages sent at one time through the V1-V2 gateway from Oracle Mail to eMail Server. Valid values: Default value: |
|
|
Size in bytes of the postman's allocated work buffer. This buffer is set aside for the postman when you start eMail Server and determines the number of messages a postman process can handle simultaneously. Valid values: Default value: |
Postman processes can perform local delivery and remote delivery of new e-mail. You might decide to register two instances of the postman process and configure them as follows:
The following replicator process parameters are available:
| Parameter | Description and Values |
|---|---|
|
|
"Using Server Process Logs" for information about locating and reading log files. Valid values:
Default value: |
|
|
Number of minutes between creating packages. Valid values: Default value: |
|
|
Maximum number of data records in replog before creating a package. Valid values: Default value: |
|
|
Maximum number of data records per package created by this replicator. Valid values: Default value: |
|
|
Maximum number of attempts to deliver a given package. Valid values: Default value: |
|
|
Number of minutes between package delivery attempts. Valid values: Default value: |
You should not register more than one replicator process on a node because the replicator must process packages sequentially, and multiple replicator processes could cause the packages to get out of order.
During the day when your users are sending messages back and forth and performing other eMail Server tasks, you probably want your replicator processes to respond quickly to any directory changes you make and not clog the network with large packages of information. To achieve these goals:
log_scan_interval to a short time, about five minutes, to make sure that directory changes are propagated quickly.
max_package_size to 200 objects to avoid network problems.
When you process large directory updates at night, such as synchronizing with a large system, your goal is speed. In this situation, try the following parameter settings:
log_scan_interval to 15 or 20 minutes to let information build up in the replog.
max_log_scan_size to at least half the size of the maximum packet to create large packages of directory information.
max_package_size to 400 to 600 objects for smaller servers, or 1000 to 2000 objects for larger servers to move the information through the eMail Server system efficiently.
When you are installing a new node, you should temporarily change the parameters for the replicator processes on the SCN or DCN of the domain to which the new node will subscribe. In this situation your goal is speedy delivery of the directory information the new node requires. You are not as concerned with reliability because:
The recommended parameter changes during node installation are:
max_package_size to 1000 objects to speed up the transfer.
max_retry_attempt to 2 to let you handle problems after two attempts to send the same package.
retry_interval to 1 minute to reduce the wait between the replicator's two attempts to send a package.
The following statistics process parameters are available:
| Parameter | Description and Values |
|---|---|
|
|
"Using Server Process Logs" for information about locating and reading log files. Valid values:
Default value: |
|
|
Specifies who receives problem notifications. The account name in this field receives reports of any problems the Statistics process finds. Valid values: Default value: |
The protocol server processes route messages to the Internet Messaging database. The SPS process parameters are common to both types of protocol server processes. In addition, each of these processes has specific parameters that you can configure to define how the processes work.
The following IMAP4SRV process parameters are available for IMAP4 protocol server processes only:
| Parameter | Description and Values |
|---|---|
|
|
E-mail address suffix to be added to addresses that have had the domain name stripped. This is used only when communicating with messages from Oracle InterOffice clients because they do not use standard addressing formats.See Also:: the domain parameter for more information Valid values: Any address suffix.
For example, if Default value: |
|
|
URL from your Web site where Netscape 4.0.x users can go to change their password. For other clients, you must provide a link to this URL in your Web site. See Also:: "" for more information. Valid values: Default value: |
|
|
Specifies whether the approximate message size is used rather than the exact size. Calculating the approximate size is more efficient, but some clients do not accept approximate sizes for messages. See the documentation for the clients that your users will be using to determine whether or not you can use approximate sizes. Valid values: Default Value: |
|
|
Valid values:
Default Value: |
|
|
Specifies whether the user's disk space usage will be compared against the user's quota. If the usage exceeds the quota, no new e-mail will be retrieved. eMail Server will send an alert to the client indicating that the quota is exceeded. The user's quota is specified in the user's directory entry. See Also:: "Creating an eMail Server User Account" for more information Valid values: Default Value: |
|
|
Default character set for text objects. Valid values: Refer to "Configuring the Gateway for Multibyte Support" for a complete list of available character sets. Default Value: |
|
|
This parameter specifies the default domain name to use if there is no the address_suffix parameter for more information Valid values: Default value: |
|
|
Specifies how often the user will receive new e-mail, in seconds. This parameter sets the new e-mail interval for the entire system and prevents the system from being overloaded by users checking for e-mail too often. Users cannot override this value. If the user's client software has a button that they click to get new e-mail, this actually checks for e-mail only after the specified interval has passed. Valid values: Default Value: |
|
|
Specifies the method used to encode non-ASCII characters in the message header according to the MIME standard. Valid values: See Also::"Configuring the Method for Encoding MIME Content" for more information about these encoding methods Default Value: |
|
|
"Using Server Process Logs" for information about locating and reading log files Valid values:
Default value: |
|
|
Specifies whether the gateway should store the body parts encoded, decoded, or both. Oracle InterOffice clients, including SDK-based clients, can only read messages in decoded format, but if you want to use S/MIME for authenticating digital signatures of clients, you must store messages encoded. Valid values: Default value: |
|
|
Defines the content transfer encoding method used to encode text body parts of outbound messages. Valid values: Standard transfer encoding methods are base64, quoted-printable, 7bit, 8bit, and binary. Non-standard encoding methods can also be used. "Configuring the Method for Encoding MIME Content" for more information about these values Default value: |
|
|
Defines a dummy top-level domain. Use this parameter if you want to support multiple top-level domains, such as
For example, you might create a domain called Valid Values: Default Value: |
The following IOLISTENER process parameters are available:
| Parameter | Description and Values |
|---|---|
|
|
Port number for the eMail Server Probe.See Also:: "Monitoring Protocol Server Processes" for more information on the Probe Default value: |
|
|
Specifies flags to set SSL and debug. Valid values:
If you want to set more than one type of flag, use the sum of the values for each type of flag that you want. For example, to enable SSL (64) and free database connections (128), add their values (64+128) to get a value of 192. Default value: |
|
|
"Using Server Process Logs" for information about locating and reading log files Valid values:
Default value: |
|
|
Maximum number of protocol server process instances that can be running. Valid values: Default value: |
The following POP3SRV process parameters are available for POP3 protocol server processes only:
| Parameter | Description and Values |
|---|---|
|
|
E-mail address suffix to be added to addresses that have had the domain name stripped. This is used only when communicating with messages from Oracle InterOffice clients because they do not use standard addressing formats.See Also:: the domain parameter for more information Valid values: Any address suffix.
For example, if Default value: |
|
|
Default character set for text objects. Valid values: Refer to "Configuring the Gateway for Multibyte Support" for a complete list of available character sets Default Value: |
|
|
Delete messages from the INBOX, if specified by the client. Valid values: Default value: |
|
|
This parameter specifies the default domain name to use if there is no For Oracle InterOffice clients, this domain name will also be stripped from addresses when displaying the message.
For example, if the address_suffix parameter for more information Valid values: Default value: |
|
|
Specifies the method used to encode non-ASCII characters in the message header according to the MIME standard. Valid values: See Also::"Configuring the Method for Encoding MIME Content" for more information about these encoding methods Default Value: |
|
|
"Using Server Process Logs" for information about locating and reading log files. Valid values:
Default value: |
|
retrieval |
Specifies whether to retrieve unread messages or all messages. Valid values: Default value: |
|
|
Defines the content transfer encoding method used to encode text body parts of outbound messages. Valid values: Standard transfer encoding methods are base64, quoted-printable, 7bit, 8bit, and binary. Non-standard encoding methods can also be used. "Configuring the Method for Encoding MIME Content" for more information about these values Default value: |
|
|
Defines a dummy top-level domain. Use this parameter if you want to support multiple top-level domains, such as
For example, you might create a domain called Valid Values: Default Value: |
You can use the scalable protocol server (SPS) process parameters to specify information that is common to all protocol server process parameters. The following SPS process parameters are available for both IMAP4SRV and POP3SRV processes:
| Parameter | Description and Values |
|---|---|
|
|
Name of the file that contains the SSL trusted certificate (do not type the .txt extension). This file is located in the $ORACLE_HOME/office/admin directory. Default value: |
|
|
Name of the configuration file that defines the number of database connections per instance (do not type the .cfg suffix). This file is located in the $ORACLE_HOME/office/config/node_sid directory. If all protocol server process instances have the same parameters, they can share the same configuration file. If they have different parameters, you should create different files. Default values: |
|
|
Specifies flags to set SSL and debug. Valid values:
If you want to set more than one type of flag, use the sum of the values for each type of flag that you want. For example, to set SSL (64) and free database connections (128), add their values (64+128) to get a value of 192. Default value: |
|
|
Maximum number of client connections to this protocol server process instance. Valid values:
On Solaris, the value for Chapter 9, "Managing Processes" for more information about the maximum_connections parameter Default value: |
|
|
Port number for incoming messages. Default values: |
|
|
SSL port number for incoming messages. Default values: |
|
 Copyright © 2001 Oracle Corporation. All Rights Reserved. |
|