Oracle eMail Server Administrator's Guide Release 5.2 A86653-01 |
| Library | Service | Index

# 11
Process Parameter Reference

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:

- Common Process Parameters

- Gateway Process Parameters

- LDAP Server Process Parameters

- Messaging Server Process Parameters

- Protocol Server Process Parameters

## Common Process Parameters

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.

### Common Process Parameters

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.

Parameter | Description and Values
--- | ---
`defaultStartUp` | Indicates whether to start this process when you issue a startup all command. Valid values: `Enabled` (start this process on the startup all command) `Disabled` (do not start this process on the startup all command)
`execArguments` | Pass command-line arguments to a process in this field.
`guardianID` | Instance number of the guardian process that controls this process.
`instance` | Instance number of the registered process. When numbering instances, remember that each node has a set of instances registered during installation. These are all registered instance 1 (for example, postman1). Each registered process of a particular type (for example, postman) must have an instance number that is unique on the node where it is registered. You can, however, use the same instance number for different types of processes (postman1 and replicator1), and you can use the same instance number for processes on different nodes. Valid values: `0` (represents the default set of parameters for a process) `1` to `99` (represent registered process instances)
`server` | Process type, such as postman or replicator.

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

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:

Parameter | Description and Values
--- | ---
`duration` | Number of hours an active or passive period lasts.
`sleepTime` | Number of minutes the process sleeps after completing one work cycle in an active period. Specify Sleeptime in a time slice only when `status` is `A` (active).
`startTime` | Time the process begins an active or passive (inactive) period. Valid values: `0` to `23` (integers: 0 represents midnight, 23 represents 11PM)
`state` | Indicates whether the period is an active or passive period. Valid values: `A` (active) `P` (passive)

#### Guidelines for Using Schedule Parameters

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.

## Gateway Process Parameters

#####

Parameter | Description and Values
--- | ---
`cfgparamfilename` | This parameter is reserved for future use.
`content_disposition` | Specifies how attachments are presented to the recipient. Adheres to RFC1806 syntax and semantics. Valid values: `inline` (presents attachments inline as part of the message body) `attachment` (present attachments as external attachments; if any other value is specified, the gateway assumes `attachment`) Default value: `attachment`
`default_charset` | 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: `iso-8859-1`
`default_encoding` | 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. See Also:: "Configuring the Method for Encoding MIME Content" for more information about these values. Default value: `base64`
`default_textencoding` | 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. See Also:: "Configuring the Method for Encoding MIME Content" for more information about these values. Default value: `quoted-printable`
`default_type` | 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. Valid values:See Also:: "Creating a MIME Attachment Map" for a list of attachment Type IDs. Default value: `1`
`do_uudecode` | Specifies whether the gateway should automatically decode the data encoded with UUENCODE. Valid values: `0` (do not automatically decode) `1` (automatically decode) Default value: `1`
`do_uuencode` | 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: `0` (do not encode binary data) `1` (encode binary data) Default value: `1`
`domSuffix` | String attached to incomplete eMail Server sender address (addresses that do not contain @ or !) and unqualified receipt addresses. Default value: Null
`log_level` | Log message level. See Also:: "Using Server Process Logs" for information about locating and reading log files. Valid values: `0` (no logging) `1` (error messages only) `2` (minimum information and warnings) `3` (medium information) `4` (maximum information) `5` (debugging information) Default value: `2`
`prefixgwy` | 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: `0` (does not remove qualified domain identifiers) `1` (removes qualified domain identifiers) Default value: `0`
`send_summary` | 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. Valid values:See Also:: "Creating a MIME Attachment Map" for a list of attachment Type IDs. Default value: `1`
store_body | Specifies whether the gateway should store the body parts encoded, decoded, or both. Valid values: `1` (encoded) `2` (decoded) `3` (both encoded and decoded) `4` (store S/MIME) `5` (store S/MIME) If this is set to `2` (decoded), then Oracle InterOffice clients, including SDK-based clients, will not be able to read messages. If this is set to 4 (store S/MIME), then messages are encoded, all others are decoded. If this is set to `5` (store S/MIME), then messages are both in encoded and decoded format, all others are decoded. Default value: `2`
`store_shell` | Specifies whether the gateway should store the message shell with the body part information. Valid values: `0` (does not store message shell) `1` (stores message shell) Default value: `1`
`stripgwytkns` | 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: `0` (does not remove qualified domain identifiers) `1` (removes qualified domain identifiers) Default value: `1`
`stripqualname` | Specifies whether to remove qualified domain identifiers from the Reply-to, Sender, and Recipient fields. If `domSuffix` is not null, the `domSuffix` is appended. If `domSuffix` is null, the qualified domain identifiers are NOT removed, even if this value is set to 1. Valid values: `0` (does not remove qualified domain identifiers) `1` (removes qualified domain identifiers) Default value: `1`

## LDAP Server Process Parameters

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.

### Forward Synchronization

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:

- person

- domain

- location

- organization

- equipment

- room

- role

- alias

- dl

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:

- When there are one INSERT and one DELETE rows of a particular object instance in the IOLM_SYNCLOG table, the server deletes all the rows related to it.

- When there are no INSERT, but multiple UPDATEs, and one DELETE, all the UPDATE rows are deleted.

- When there are one INSERT and multiple UPDATEs, and no DELETE, all the UPDATE rows are deleted.

- When there are only multiple UPDATEs, the server deletes all rows except one.

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.

### Forward Synchronization Parameters

The following forward synchronization parameters are available:

Parameter | Description and Values
--- | ---
`database_type` | Type of database. Do not change this value. Default value: `iofc`
`debug_level` | Sets the IOLDAP logging level. Valid values: `0` (no logging) `1` (trace function calls) `2` (debug packet handling) `4` (heavy trace debugging) `8` (connection management) `16` (print out packets sent and received) `32` (search filter processing) `64` (configuration file processing) `128` (access control list processing) `256` (stats log connections/operations/results) `512` (stats log entries sent) `1024` (print communication with the back end) `2048` (print entry parsing debugging) `65535` (enable all debugging) If you want to set more than one type of logging, then use the sum of the values for each type of logging that you want. For example, to see trace function calls (1) and debug packet handling (2), add their values (1+2) to get a value of 3. Default value: `0` (no logging)
`dit_root` | Specifies the relative location of the directory in the global directory namespace. Each LDAP process services a certain portion of the directory namespace, and each namespace has a parent namespace. In eMail Server, the namespace that the directory serves does not have a parent namespace, so this value is always null. Default value: Null
`ldap_admin_passwd` (Required) | Specifies the password for the administration account created when you install Oracle Internet Directory (or other LDAP directory).
`ldap_admin_login` (Required) | Specifies the name of the administration account created when you install Oracle Internet Directory (or other LDAP directory). Valid values: `cn=<``account``>` For example, if your account is called `orcladmin`, then this value would be: `cn=orcladmin`
`ldap_guest_login` | Specifies the name of the guest account created when you install Oracle Internet Directory (or other LDAP directory). Valid values: `cn=<``account``>` For example, if your account is called `guest`, then this value would be: `cn=guest`
`ldap_guest_passwd` | Specifies the password for the guest account created when you install Oracle Internet Directory (or other LDAP directory).
`ldap_repl_dn` | Specifies the name of the replication account created when you install Oracle Internet Directory (or other LDAP directory). Valid values: `cn=<``account``>` For example, if your account is called `repl`, then this value would be: `cn=repl`
`ldap_repl_passwd` | Specifies the password for the replication account created when you install Oracle Internet Directory (or other LDAP directory).
`ldap_supplier` (Required) | Specifies the TCP/IP host name of the machine where Oracle Internet Directory (or other LDAP directory) is running.
`ldap_supplier_port` (Required) | Specifies the port on which Oracle Internet Directory (or other LDAP directory) is running. Valid values: `0` to `99999` Default value: `389`
`max_concurrent_conn` | Sets a limit to the number of LDAP connections that can be made to an `IOODSSYNC` process at a time. Valid values: `0` to `64` Default value: `10`
`nls_language` | NLS language and character set. Default value: `AMERICAN_AMERICA.US7ASCII`
`referral` | Specifies the location of an LDAP server that may be able to find the entry that was queried if IOLDAP cannot locate the entry in an LDAP request. (Oracle Internet Directory does not currently support referrals. If you are using Oracle Internet Directory, then do not change the default value of this parameter.) For example, `ldap://ldap.itd.umich.edu`
`resulting_migrated_domain` | Domain structure after migration. Default value: Null For example, if your current domain is `us.oracle.com` and the new domain is `mydomain.com`, this parameter value would be: `dc=mydomain, dc=com`
`resulting_dl_migrated_domain` | DL Domain structure after migration. Default value: Null For example, if you want to put a 'dl' in a separate part of the DIT, the parameter value would be: `dc=dlcontainer, dc=mydomain, dc=com`
`suffix` (Required) | Specifies the domain of the eMail Server node. Verify that this parameter is set correctly for your site. If the parameter is not set correctly, then the directory searches will fail. Valid values: `dc=<``domain``>, dc=<``domain``> ...` For example, if your domain is `us.oracle.com`, then this value would be: `dc=us, dc=oracle, dc=com`

### Reverse Synchronization Parameters

The following reverse synchronization parameters are available:

Parameter | Description and Values
--- | ---
`database_type` | Type of database. Do not change this value. Default value: `iofc`
`debug_level` | Sets the IOLDAP logging level. Valid values: `0` (no logging) `1` (trace function calls) `2` (debug packet handling) `4` (heavy trace debugging) `8` (connection management) `16` (print out packets sent and received) `32` (search filter processing) `64` (configuration file processing) `128` (access control list processing) `256` (stats log connections/operations/results) `512` (stats log entries sent) `1024` (print communication with the back end) `2048` (print entry parsing debugging) `65535` (enable all debugging) If you want to set more than one type of logging, then use the sum of the values for each type of logging that you want. For example, to see trace function calls (1) and debug packet handling (2), add their values (1+2) to get a value of 3. Default value: `0` (no logging)
`dit_root` | Specifies the relative location of the directory in the global directory namespace. Each LDAP process services a certain portion of the directory namespace, and each namespace has a parent namespace. In eMail Server, the namespace that the directory serves does not have a parent namespace, so this value is always null. Default value: Null
`ldap_admin_passwd` (Required) | Specifies the password for the administration account created when you install Oracle Internet Directory (or other LDAP directory).
`ldap_admin_login` (Required) | Specifies the name of the administration account created when you install Oracle Internet Directory (or other LDAP directory). Valid values: `cn=<``account``>` For example, if your account is called `orcladmin`, then this value would be: `cn=orcladmin`
`ldap_changelog_filter` (Required) | Specifies the change log object class filter. Valid values: (&(objectclass=changeLogEntry)(server=<server_name>)(changeNumber>=%d)) Changelog filter for Oracle Internet Directory only. (&(objectclass=changeLogEntry)(changeNumber>=%d)) Changelog filter for other LDAP directories. Default value: (&(objectclass=changeLogEntry)(server=<server_name>)(changeNumber>=%d))
`ldap_guest_login` | Specifies the name of the guest account created when you install Oracle Internet Directory (or other LDAP directory). Valid values: `cn=<``account``>` For example, if your account is called `guest`, then this value would be: `cn=guest`
`ldap_guest_passwd` | Specifies the password for the guest account created when you install Oracle Internet Directory (or other LDAP directory).
`ldap_repl_dn` | Specifies the name of the replication account created when you install Oracle Internet Directory (or other LDAP directory). Valid values: `cn=<``account``>` For example, if your account is called `repl`, then this value would be: `cn=repl`
`ldap_repl_passwd` | Specifies the password for the replication account created when you install Oracle Internet Directory (or other LDAP directory).
`ldap_supplier` (Required) | Specifies the TCP/IP host name of the machine where Oracle Internet Directory (or other LDAP directory) is running.
`ldap_supplier_port` (Required) | Specifies the port on which Oracle Internet Directory (or other LDAP directory) is running. Valid values: `0` to `99999` Default value: `389`
`max_concurrent_conn` | Sets a limit to the number of LDAP connections that can be made to an `IOODSSYNC` process at a time. Valid values: `0` to `64` Default value: `10`
`nls_language` | NLS language and character set. Default value: `AMERICAN_AMERICA.US7ASCII`
`referral` | Specifies the location of an LDAP server that may be able to find the entry that was queried if IOLDAP cannot locate the entry in an LDAP request. (Oracle Internet Directory does not currently support referrals. If you are using Oracle Internet Directory, then do not change the default value of this parameter.) For example, `ldap://ldap.itd.umich.edu`
`resulting_migrated_domain` | Domain structure after migration. Default value: Null For example, if your current domain is `us.oracle.com` and the new domain is `mydomain.com`, this parameter value would be: `dc=mydomain, dc=com`
`suffix` (Required) | Specifies the domain of the eMail Server node. Verify that this parameter is set correctly for your site. If the parameter is not set correctly, then the directory searches will fail. Valid values: `dc=<``domain``>, dc=<``domain``> ...` For example, if your domain is `us.oracle.com`, then this value would be: `dc=us, dc=oracle, dc=com`

## Messaging Server Process Parameters

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.

### Collector Process Parameters

Note: The collector process was previously known as the Garbage collector process.

The following collector process parameters are available:

Parameter | Description and Values
--- | ---
`billinfo_kept` | Specifies the number of days message billing data is kept. Valid Values: `0` to `365` (365 days equals one year) Default value: `45`
`directory` | Specifies whether the process removes unneeded internal replicator items. Valid values: `0` (does not remove unneeded internal replicator items) `1` (removes unneeded internal replicator items) Default value: `1`
`event_kept` | Number of days to retain calendar events. Valid Values: `0` to `1825` (1825 days equals five years) Default value: `180`
`log_kept` | Number of days to retain internal log messages. Valid Values: `0` to `365` (365 days equals one year) Default value: `10`
`log_level` | Log message level. See Also:: "Using Server Process Logs" for information about locating and reading log files. Valid values: `0` (no logging) `1` (error messages only) `2` (minimum information and warnings) `3` (medium information) `4` (maximum information) `5` (debugging information) Default value: `2`
`mail_collect` | Specifies whether this process collects unreferenced messages. Valid values: `0` (does not collect unreferenced messages) `1` (collects unreferenced messages) Default value: `1`
`mail_expiry` | Specifies whether this process removes expired messages. Valid values: `0` (does not remove expired messages) `1` (removes expired messages) Default value: `1`
`mail_pruning` | Specifies whether this process identifies unreferenced messages. Valid values: `0` (does not identify unreferenced messages) `1` (identifies unreferenced messages) Default value: `1`
`ops_mode` | 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: 0 (disables OPS) 1 (enables OPS) Default value: 0
`qstats_kept` | 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: `0` to `365` (365 days equals one year) Default value: `45`
`recipient` | 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: `0` (no original recipient information will be deleted) `1` (all original recipient information in all messages will be deleted) Default value: `0`
`registration` | 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: `0` (does not clean up registration records) `1` (cleans up registration records) Default value: `1`
`replog_kept` | 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: `0` to `1825` (1825 days equals five years) Default value: `5`
`scheduler` | Specifies whether this process cleans up events. Valid values: `0` (does not clean up events) `1` (cleans up events) Default value: `1`
`search_cache` | Enabling this parameter means that the collector process will clean up all Oracle ConText search cache data. Valid values: `0` (does not clean up Oracle ConText search cache) `1` (cleans up Oracle ConText search cache) Default value: `1`
`shadow_processes` | Specifies whether this process cleans up inactive database shadow processes. Valid values: `0` (does not clean up inactive database shadow processes) `1` (cleans up inactive database shadow processes) Default Value: `0`
`V1_mail` | 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: `0` (does not collect V1 garbage messages or run on the V1-V2 gateway node. `1` (collects V1 garbage messages and runs on the V1-V2 gateway node. Default value: `0`

### Guardian Process Parameters

The guardian process, ofcguard, does not have parameters to set.

### Monitor Process Parameters

The following monitor process parameters are available:

Parameter | Description and Values
--- | ---
`log_level` | Log message level. See Also:: "Using Server Process Logs" for information about locating and reading log files. Valid values: `0` (no logging) `1` (error messages only) `2` (minimum information and warnings) `3` (medium information) `4` (maximum information) `5` (debugging information) Default value: `2`
`no_prob_msg_subj` | Subject line for a "No problem" report. Default value: `eMail Server System Status`
`no_prob_recips` | Specifies who receives no-problem notifications. The account name in this field receives reports when the monitor does not find any problems. Valid values: Any addressable account name in your directory. Be sure to include the qualified domain. Default value: `ORAPOST.<``domain``>`
`prob_msg_subj` | Subject line for a problem report. Default value: `eMail Server System Alert`
`prob_recips` | Specifies who receives problem notifications. The account name in this field receives reports of any problems the monitor finds. Valid values: Any addressable account name in your directory. Be sure to include the qualified domain. Default value: `ORAPOST.<``domain``>`

### Postman Process Parameters

The following postman process parameters are available:

Parameter | Description and Values
--- | ---
`auto_reply_history` | 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 `auto_reply_history` determines how often any user receives Amy's Auto Reply message, solving the problem of one person receiving several Auto Reply messages from Amy within the time you specify. Valid values: `0` to `365` (365 days equals one year) Default value: `7`
`delivery_stats` | 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: `0` (disables delivery statistics collection) `1` (enables delivery statistics collection) Default value: `0`
`local_delivery` | Specifies whether this process handles messages destined for local users. Valid values: `0` (disables local delivery) `1` (enables local delivery) Default value: `1`
`log_level` | Log message level. See Also:: "Using Server Process Logs" for information about locating and reading log files. Valid values: `0` (no logging) `1` (error messages only) `2` (minimum information and warnings) `3` (medium information) `4` (maximum information) `5` (debugging information) Default value: `2`
`oma_notify_type` | This parameter is reserved for future use.
`ops_id` | This parameter is reserved for future use.
`ops_mode` | 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: `0` (disables OPS) `1` (enables OPS) Default value: `0`
`postmaster` | 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: Any addressable account name in your directory. Be sure to include the qualified domain. Default value: `ORAPOST.<``domain``>`
`recv_billing` | 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: `0` (disables billing information collection on received messages) `1` (enables billing information collection on received messages) Default value: `0`
`remote_delivery` | Specifies whether this process handles messages destined for remote users. Valid values: `0` (disables remote delivery) `1` (enables remote delivery) Default value: `1`
`return_delay` | 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: `0` to `365` (365 days equals one year) Default value: `3`
`rte_tab_refresh` | 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: `0` to `8192` Default value: `60`
`sead_msg_kept` | Number of days a message is held in this node's Dead Message queue before the collector removes it. Valid values: `1` to `365` (365 days equals one year) Default value: `5`
`send_billing` | 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: `0` (disables billing information collection on sent messages) `1` (enables billing information collection on sent messages) Default value: `0`
`V1_gateway` | Specifies whether this process acts as a V1-V2 gateway. Valid values: `0` (disables V1-V2 gateway tasks) `1` (enables V1-V2 gateway tasks) Default value: `0`
`V1_package_size` | Maximum number of messages sent at one time through the V1-V2 gateway from Oracle Mail to eMail Server. Valid values: `0` to `8192` Default value: `50`
`workspace` | 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: `25000` to `1000000` Default value: `65536`

#### Guidelines

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:

- postman1 to handle only local delivery (Local_Delivery=1, Remote_Delivery=0)

- postman2 to handle remote delivery (Remote_Delivery=1, Local_Delivery=0)

### Replicator Process Parameters

The following replicator process parameters are available:

Parameter | Description and Values
--- | ---
`log_level` | Log message level. See Also:: "Using Server Process Logs" for information about locating and reading log files. Valid values: `0` (no logging) `1` (error messages only) `2` (minimum information and warnings) `3` (medium information) `4` (maximum information) `5` (debugging information) Default value: `2`
`log_scan_interval` | Number of minutes between creating packages. Valid values: `1` to `2000` Default value: `10`
`max_log_scan_size` | Maximum number of data records in replog before creating a package. Valid values: `1` to `2000` Default value: `100`
`max_package_size` | Maximum number of data records per package created by this replicator. Valid values: `10` to `2000` Default value: `400`
`max_retry_attempt` | Maximum number of attempts to deliver a given package. Valid values: `1` to `10` Default value: `2`
`retry_interval` | Number of minutes between package delivery attempts. Valid values: `1` to `2000` Default value: `30`

#### Guidelines

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:

- Set `log_scan_interval` to a short time, about five minutes, to make sure that directory changes are propagated quickly.

- Set `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:

- Set `log_scan_interval` to 15 or 20 minutes to let information build up in the replog.

- Set `max_log_scan_size` to at least half the size of the maximum packet to create large packages of directory information.

- Set `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:

- You know that the network connection to the node is up.

- Waiting for package acknowledgments is slower than correcting problems as you transfer the information.

The recommended parameter changes during node installation are:

- Set `max_package_size` to 1000 objects to speed up the transfer.

- Set `max_retry_attempt` to 2 to let you handle problems after two attempts to send the same package.

- Set `retry_interval` to 1 minute to reduce the wait between the replicator's two attempts to send a package.

### Statistics Process Parameters

The following statistics process parameters are available:

Parameter | Description and Values
--- | ---
`log_level` | Log message level. See Also:: "Using Server Process Logs" for information about locating and reading log files. Valid values: `0` (no logging) `1` (error messages only) `2` (minimum information and warnings) `3` (medium information) `4` (maximum information) `5` (debugging information) Default value: `2`
`prob_recips` | Specifies who receives problem notifications. The account name in this field receives reports of any problems the Statistics process finds. Valid values: Any addressable account name in your directory. Be sure to include the qualified domain. Default value: `ORAPOST.<``domain``>`

## Protocol Server Process Parameters

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.

### IMAP4SRV Process Parameters (IMAP4-Specific)

The following IMAP4SRV process parameters are available for IMAP4 protocol server processes only:

Parameter | Description and Values
--- | ---
`address_suffix` | 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 `address_suffix=@acme.com`, then the address jdoe would have the suffix added to look like `jdoe@acme.com`. Default value: Null
`admin_url` | 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: Any valid URL. For example: `http://anywhere.com/newpass.html` Default value: Null
`apprx_size` | 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: `Y` (uses approximate sizes) `N` (does not use approximate sizes) Default Value: `Y`
`cache_size` | Cache size. Valid values: `small` (caches only the last accessed message in the user's current folder) `medium` (caches all unseen messages in the user's current folder) `large` (caches all the messages in the user's current folder) Default Value: `small`
`check_quota` | 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: `Y` (checks against the user's quota) `N` (does not check against the user's quota) Default Value: `N`
`default_charset` | 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: `iso-8859-1`
`domain` | This parameter specifies the default domain name to use if there is no `qualified_domain` specified with the address. This parameter must be the same as the domain the IMAP user belongs to.See Also:: the address_suffix parameter for more information Valid values: Any domain name that is currently defined in your system, such as `acme.com`. Default value: Null
`gnmail_intvl` | 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: `60` (minimum; there is no maximum) Default Value: `120`
`hdr_encoding` | Specifies the method used to encode non-ASCII characters in the message header according to the MIME standard. Valid values: `Q` (quoted-printable) `B` (base64) See Also:: "Configuring the Method for Encoding MIME Content" for more information about these encoding methods Default Value: `Q`
`log_level` | Log message level. See Also:: "Using Server Process Logs" for information about locating and reading log files Valid values: `0` (no logging) `1` (error messages only) `2` (minimum information and warnings) `3` (medium information) `4` (maximum information) `5` (debugging information) Default value: `2`
`store_body` | 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: `1` (encoded) `2` (decoded) `3` (both encoded and decoded) Default value: `2`
`text_encoding` | 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. See Also:: "Configuring the Method for Encoding MIME Content" for more information about these values Default value: `quoted-printable`
`virtual_domain` | Defines a dummy top-level domain. Use this parameter if you want to support multiple top-level domains, such as `.com` and `.edu`. The virtual domain is automatically appended to the user's domain for incoming messages, and it is stripped from outgoing messages. For example, you might create a domain called `.world` and then specify that domain for the `virtual_domain` parameter. Then, you can create subdomains `.world` such as `.edu.world` and `.com.world`. Valid Values: Any domain name that is currently defined in your system, such as `.world`. Default Value: Null

### IOLISTENER Process Parameters

The following IOLISTENER process parameters are available:

Parameter | Description and Values
--- | ---
`diagport` | Port number for the eMail Server Probe.See Also:: "Monitoring Protocol Server Processes" for more information on the Probe Default value: `5010`
`flags` | Specifies flags to set SSL and debug. Valid values: `0` (no flags) `32` (disables thread handle traps) `64` (enables SSL) `128` (frees database connections locked by client threads) 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: `0` (no flags)
`log_level` | Log message level. See Also:: "Using Server Process Logs" for information about locating and reading log files Valid values: `0` (no logging) `1` (error messages only) `2` (minimum information and warnings) `3` (medium information) `4` (maximum information) `5` (debugging information) Default value: `2`
`maxsvr` | Maximum number of protocol server process instances that can be running. Valid values: `1` to `1000` Default value: `1000`

### POP3SRV Process Parameters (POP3-Specific)

The following `POP3SRV` process parameters are available for POP3 protocol server processes only:

Parameter | Description and Values
--- | ---
`address_suffix` | 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 `address_suffix=@acme.com`, then the address jdoe would have the suffix added to look like `jdoe@acme.com`. Default value: Null
`default_charset` | 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: `iso-8859-1`
`delete_allowed` | Delete messages from the INBOX, if specified by the client. Valid values: `yes` (deletes messages) `no` (does not delete messages) Default value: `no`
`domain` | This parameter specifies the default domain name to use if there is no `qualified_domain` specified with the address. For Oracle InterOffice clients, this domain name will also be stripped from addresses when displaying the message. For example, if `domain=acme.com`, then the address `jdoe.acme.com` would be stripped of the domain to look like `jdoe`. Then, the `address_suffix` parameter is added to the address to look like `jdoe@acme.com`. See Also:: the address_suffix parameter for more information Valid values: Any domain name that is currently defined in your system, such as `acme.com`. Default value: Null
`hdr_encoding` | Specifies the method used to encode non-ASCII characters in the message header according to the MIME standard. Valid values: `Q` (quoted-printable) `B` (base64) See Also:: "Configuring the Method for Encoding MIME Content" for more information about these encoding methods Default Value: `Q`
`log_level` | Log message level. See Also:: "Using Server Process Logs" for information about locating and reading log files. Valid values: `0` (no logging) `1` (error messages only) `2` (minimum information and warnings) `3` (medium information) `4` (maximum information) `5` (debugging information) Default value: `2`
retrieval | Specifies whether to retrieve unread messages or all messages. Valid values: `Unread` (retrieve only unread messages) `All` (retrieve all messages) Default value: `All`
`text_encoding` | 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. See Also:: "Configuring the Method for Encoding MIME Content" for more information about these values Default value: `quoted-printable`
`virtual_domain` | Defines a dummy top-level domain. Use this parameter if you want to support multiple top-level domains, such as `.com` and `.edu`. The virtual domain is automatically appended to the user's domain for incoming messages, and it is stripped from outgoing messages. For example, you might create a domain called `.world` and then specify that domain for the `virtual_domain` parameter. Then, you can create subdomains to `.world` such as `.edu.world` and `.com.world`. Valid Values: Any domain name that is currently defined in your system, such as `.world`. Default Value: Null

### SPS Process Parameters (Common to both IMAP4 and POP3)

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
--- | ---
`certificate` | 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: `sslcerts`
`confnm` | 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: `iosps27` (IMAP4 clients) `iosps23` (POP3 clients)
`flags` | Specifies flags to set SSL and debug. Valid values: `0` (no flags) `32` (disables thread handle traps) `64` (enables SSL) `128` (frees database connections locked by client threads) 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: `0` (no flags)
`maxclt` | Maximum number of client connections to this protocol server process instance. Valid values: `1` to `900` On Solaris, the value for `maxclt` plus the value for `maximum_connections` in the iosps*.cfg file should be less than 1000. See Also:: Chapter 9, "Managing Processes" for more information about the maximum_connections parameter Default value: `900`
`port` | Port number for incoming messages. Default values: `143` (IMAP4 clients) `110` (POP3 clients) These default values are the standard ports used for the specified protocol servers, but you can change them, if necessary.
`sslport` | SSL port number for incoming messages. Default values: `993` (IMAP4 clients) `995` (POP3 clients) These default values are the standard SSL ports used for the specified protocol servers, but you can change them, if necessary.

| Copyright © 2001 Oracle Corporation. All Rights Reserved. |
| Library | Service | Index