Configutil Reference

Cnewman — Sat, 05 May 2012 01:12:45 GMT

New page: This information lists the configuration parameters that you set for Messaging Server by using the <code>configutil</code> command. For a full description and syntax of the <code>configuti...

New page

This information lists the configuration parameters that you set for Messaging Server by using the <code>configutil</code> command. For a full description and syntax of the <code>configutil</code> command, see [https://wikis.oracle.com/display/CommSuite/configutil configutil].

<dl><dt>[[description Option|alarm.diskavail.msgalarmdescription]]<dd>

Description for the diskavail alarm.
Syntax: stringDefault: <code>percentage mail partition diskspace available</code>
<dt>[[statinterval Option|alarm.diskavail.msgalarmstatinterval]]<dd>

Interval in seconds between disk availability checks. Set to 0 to
disable checks of disk usage.
Syntax: int32Default: <code>3600</code>
<dt>[[threshold Option|alarm.diskavail.msgalarmthreshold]]<dd>

Percentage of disk space availability below which an alarm is sent.
Syntax: int32Default: <code>10</code>
<dt>[[thresholddirection Option|alarm.diskavail.msgalarmthresholddirection]]<dd>

Specifies whether the alarm is issued when disk space availability is
below threshold (-1) or above it (1).
Syntax: int32Default: <code>-1</code>
<dt>[[warninginterval Option|alarm.diskavail.msgalarmwarninginterval]]<dd>

Interval in hours between subsequent repetition of disk availability alarms.
Syntax: int32
<dt>[[noticehost Option|alarm.msgalarmnoticehost]]<dd>

Machine to which to send warning messages. If you are using LMTP, set
this to the machine name of the SMTP host. If this is not set, it
will default to the value of <code>service.http.smtphost</code> (as of
7.2-7.02 release) or the loopback address.
Syntax: host
<dt>[[noticeport Option|alarm.msgalarmnoticeport]]<dd>

The SMTP port to which to connect when sending alarm messages.
Syntax: uint16Default: <code>25</code>
<dt>[[noticercpt Option|alarm.msgalarmnoticercpt]]<dd>

Recipient of alarm notice.
Syntax: non-empty-stringDefault: <code>postmaster</code>
<dt>[[noticesender Option|alarm.msgalarmnoticesender]]<dd>

Address of sender of alarm.
Syntax: non-empty-stringDefault: <code>postmaster</code>
<dt>[[noticetemplate Option|alarm.msgalarmnoticetemplate]]<dd>

Message template. <code>%s</code> in the template is replaced with the
following in order: sender, recipient, alarm description, alarm
instance, alarm current value and alarm summary text. DELETED: Too
prone to format errors, support dropped in 6.3 release.
Syntax: non-empty-stringDefault: <code>From: %s\r\nTo: %s\r\nSubject: ALARM: %s of "%s" is %u\r\n\r\n%s\r\n</code>
<dt>[[description Option|alarm.serverresponse.msgalarmdescription]]<dd>

Description for the serverresponse alarm.
Syntax: stringDefault: <code>server response time in seconds</code>
<dt>[[statinterval Option|alarm.serverresponse.msgalarmstatinterval]]<dd>

Checking interval (seconds). Set to 0 to disable checking of server response.
Syntax: int32Default: <code>600</code>
<dt>[[threshold Option|alarm.serverresponse.msgalarmthreshold]]<dd>

If server response time in seconds exceeds this value, alarm issued.
Syntax: int32Default: <code>10</code>
<dt>[[thresholddirection Option|alarm.serverresponse.msgalarmthresholddirection]]<dd>

Specifies whether alarm is issued when server response time is greater
than (1) or less than (-1) the threshold.
Syntax: int32Default: <code>1</code>
<dt>[[warninginterval Option|alarm.serverresponse.msgalarmwarninginterval]]<dd>

Interval in hours between subsequent repetition of server response alarm.
Syntax: int32
<dt>[[sslnicknames Option|encryption.rsa.nssslpersonalityssl]]<dd>

Nicknames of the certificates in the SSL certificate database to offer
as the server certificate. Only one nickname of each certificate type
is permitted (e.g., one RSA certificate, one DSS certificate) so
normally only one will be specified.
Syntax: name-list
<dt>[[accounturl Option|gen.accounturl]]<dd>

Location of the server administration resource for end users (obsolete).
Syntax: url
<dt>[[filterurl Option|gen.filterurl]]<dd>

URL for incoming mail (server side) filter (obsolete).
Syntax: url
<dt>[[folderurl Option|gen.folderurl]]<dd>

URL for personal folder management (obsolete).
Syntax: url
<dt>[[installedlanguages Option|gen.installedlanguages]]<dd>

Alphabets only, comma separated list (e.g. "en, fr"). This is
identical to RFC-2068 "Accept-Language" definition, but no q-value.
Syntax: non-empty-stringDefault: <code>en,de,fr,es,ja,ko,zh-CN,zh-TW</code>
<dt>[[listurl Option|gen.listurl]]<dd>

URL for mailing list management (obsolete).
Syntax: url
<dt>[[welcomemsg Option|gen.newuserforms]]<dd>

Welcome message for new users. The maximum size is 1 MB. Syntax: "$"
line separators, with headers.
Syntax: non-empty-string
<dt>[[welcomemsg Option|gen.newuserforms;lang-*]]<dd>

Localized welcome message for new users. The maximum size is 1
MB. Syntax: "$" line separators, with headers.
Syntax: non-empty-string
<dt>[[sitelanguage Option|gen.sitelanguage]]<dd>

Default language tag.
Syntax: non-empty-stringDefault: <code>en</code>
<dt>[[enable Option|local.autorestart]]<dd>

Enable automatic restart of failed or frozen (unresponsive) servers
including IMAP, POP, HTTP, job controller, dispatcher, and MMP
servers.
Syntax: boolDefault: <code>1</code>
<dt>[[timeout Option|local.autorestart.timeout]]<dd>

Failure retry time-out. If a server fails more than once during this
designated period of time, then the system will stop trying to restart
this server. If this happens in an HA system, Messaging Server is
shutdown and a failover to the other system occurs. The value (set in
seconds) should be set to a period value longer than the msprobe
interval. (See crontab setting for the msprobe's schedule).
Syntax: uint32Default: <code>600</code>
<dt>[[dbtxnsync Option|local.dbtxnsync]]<dd>

Set the database transaction synchronization level. A value of 0 or 1
selects none while a value of 2 requests that all writes be
synchronously flushed to the log on every transaction commit.
Syntax: int32Default: <code>0</code>
<dt>[[debug Option|local.domainmap.debuglevel]]<dd>

Level of debugging messages for domain map.
Syntax: int32Default: <code>0</code>
<dt>[[enablelastaccess Option|local.enablelastaccess]]<dd>

Enables last access time tracking. Access time data is used by
<code>imsconnutil</code> and <code>mboxutil -o -t</code>.
Syntax: boolDefault: <code>0</code>
<dt>[[enable Option|local.ens.enable]]<dd>

Enable ENS server on <code>start-msg</code> startup.
Syntax: boolDefault: <code>0</code>
<dt>[[port Option|local.ens.port]]<dd>

TCP port the ENS server will listen on. If this is set,
<code>local.store.notifyplugin.*.enshost</code> and
<code>local.store.notifyplugin.*.ensport</code> must
also be configured to match.
Syntax: uint16Default: <code>7997</code>
<dt>[[loglevel Option|local.ensloglevel]]<dd>

Level of ENS client library logging to the process nslog
file. Messages are also filtered per the loglevel of the
process. Allowed values are as in
<code>logfile.*.loglevel</code>. But the value "debug" generates
lots of data and is not recommended.
Syntax: enumstrcaseDefault: <code>information</code>
<dt>[[hostname Option|local.hostname]]<dd>

Fully qualified DNS hostname of this mail server.
Syntax: host
<dt>[[altservice Option|local.http.altservice]]<dd>

The mshttpd daemon (webmail proxy) normally checks the
'mailAllowedServiceAccess' and related LDAP attributes to see if the 'http'
service is enabled for that user. If this is set to 1, it will instead
use 'mshttpd' as the service name for such checks. This is useful if
different access control settings are needed for the mshttpd daemon
than for a front-end http server such as the one used by Convergence.
Syntax: boolDefault: <code>0</code>
<dt>[[enableuserlist Option|local.http.enableuserlist]]<dd>

Enables <code>imsconnutil</code> connected user listing for HTTP service.
Syntax: boolDefault: <code>0</code>
<dt>[[forcetelemetry Option|local.http.forcetelemetry]]<dd>

Force telemetry for all users. Warning: this generates a lot of data
and should not be used on a production system.
Syntax: boolDefault: <code>0</code>
<dt>[[replayformat Option|local.http.replayformat]]<dd>

Format for authentication replay from mshttpd to IMAP backend. Supports %o for
original userid, %s for user@domain, %U for userid only, %V for virtual domain,
%A[attr] for value of specified user's attribute.
''Introduced in release: 7 patch 13''Syntax: string
<dt>[[sslnicknames Option|local.http.sslnicknames]]<dd>

List of SSL/TLS server certificate nicknames (only one per certificate
type) for HTTP to offer clients if SSL/TLS enabled. Overrides
<code>encryption.rsa.nssslpersonalityssl</code>.
Syntax: name-list
<dt>[[adminbypassquota Option|local.imap.adminbypassquota]]<dd>

Allow admin users to bypass quota enforcement when they append
messages to mailboxes with the IMAP APPEND command.
Syntax: boolDefault: <code>0</code>
<dt>[[enableuserlist Option|local.imap.enableuserlist]]<dd>

Enables <code>imsconnutil</code> connected user listing for IMAP service.
Syntax: boolDefault: <code>0</code>
<dt>[[fixinternaldate Option|local.imap.fixinternaldate]]<dd>

Whether to fix the IMAP internaldate for appended messages when the
client fails to pass a valid date argument.
Syntax: boolDefault: <code>1</code>
<dt>[[forcetelemetry Option|local.imap.forcetelemetry]]<dd>

Force telemetry for all users. Warning: this generates a lot of data and should
not be used on a production system.
Syntax: boolDefault: <code>0</code>
<dt>[[immediateflagupdate Option|local.imap.immediateflagupdate]]<dd>

When set to yes, seen and deleted flags for users other than the mailbox owner are
updated in the database on disk immediately, instead of being buffered and
updated once in a while. This is needed for IMAP IDLE to work correctly with shared
folders.
Syntax: boolDefault: <code>1</code>
<dt>[[logprotocolerrors Option|local.imap.logprotocolerrors]]<dd>

If greater than zero, protocol errors are logged as debug messages for IMAP.
Syntax: uint32Default: <code>0</code>
<dt>[[maxnoops Option|local.imap.maxnoops]]<dd>

Maximum number of NOOP commands accepted before connection is forcibly
closed.
Syntax: uint32Default: <code>0</code>
<dt>[[maxprotocolerrors Option|local.imap.maxprotocolerrors]]<dd>

Maximum number of protocol errors allowed before connection is forcibly closed.
Syntax: uint32Default: <code>9999</code>
<dt>[[polldelay Option|local.imap.polldelay]]<dd>

Solaris-only. Wait time before calling poll() in milliseconds.
Workaround for poll performance bug on Solaris (6438988,
6379476). Setting this to -1 activates a different workaround as of
mirasol (this might be backported to patch 24). The alternate code
tries to keep the size of the poll array relatively constant and
instead uses -1 in the poll array for inactive descriptors. The poll
array will be larger, but change size less frequently so at this point
in time the impact on performance of the -1 setting is unknown
although expected to be better than a value of 0.

The default has changed from 1 to -1 in the mirasol release.Syntax: int32
<dt>[[sslnicknames Option|local.imap.sslnicknames]]<dd>

List of SSL/TLS server certificate nicknames (only one per certificate
type) for IMAP to offer clients if SSL/TLS enabled. Overrides
<code>encryption.rsa.nssslpersonalityssl</code>.
Syntax: name-list
<dt>[[catchallenabled Option|local.imta.catchallenabled]]<dd>

Controls whether or not catch all addresses (mail or
mailAlternateAddress in the form <code>@domain</code>) are
enabled. DELETED: No longer relevant with <code>dirsync</code>
obsoleted (as of Messaging Server 6.0).
Syntax: boolDefault: <code>1</code>
<dt>[[enable Option|local.imta.enable]]<dd>

Enable <code>imta</code> server on <code>start-msg</code> startup.
Syntax: boolDefault: <code>0</code>
<dt>[[ldap_host_alias_list Option|local.imta.hostnamealiases]]<dd>

Defines the list of hosts used to determine the local host name in
direct LDAP lookups. The length limit is 1024. This parameter can be
overridden with the <code>ldap_host_alias_list</code> MTA option.
Syntax: host-list
<dt>[[imta_tailor Option|local.imta.imta_tailor]]<dd>

Location of the <code>imta_tailor</code> file for this MTA
instance. DELETED: determined at run-time.
Syntax: filepath
<dt>[[ldsearchtimeout Option|local.imta.ldsearchtimeout]]<dd>

Specifies the LDAP search timeout when searching for users and
groups. DELETED: Use the <code>LDAP_TIMEOUT</code> MTA option instead.
Syntax: int32Default: <code>-1</code>
<dt>[[lookupandsync Option|local.imta.lookupandsync]]<dd>

Defines which type of entries should be synched when using the direct
LDAP lookup module. Specify 1 for users (default), 2 for groups, or 3
for users and groups. DELETED: No longer relevant with
<code>dirsync</code> obsoleted (as of Messaging Server 6.0).
Syntax: uint32Default: <code>1</code>
<dt>[[lookupfallbackaddress Option|local.imta.lookupfallbackaddress]]<dd>

When using the direct LDAP lookup module, this parameter allows the
last alias lookup to be skipped. Instead the recipient address is
rewritten to a fixed address. This parameter is used in conjunction
with a SEND_ACCESS mapping rule to return an error code. DELETED: No
longer relevant with <code>dirsync</code> obsoleted (as of Messaging
Server 6.0).
Syntax: non-empty-string
<dt>[[lookupmaxnbfailed Option|local.imta.lookupmaxnbfailed]]<dd>

When using the direct LDAP lookup module, this parameter defines when
the routing process stops performing unsuccessful LDAP searches (in
processes). DELETED: No longer relevant with <code>dirsync</code>
obsoleted (as of Messaging Server 6.0).
Syntax: int32Default: <code>-1</code>
<dt>[[lookupreturnwhenfound Option|local.imta.lookupreturnwhenfound]]<dd>

DELETED: No longer relevant with <code>dirsync</code> obsoleted (as of
Messaging Server 6.0).
Syntax: boolDefault: <code>0</code>
<dt>[[ldap_mail_aliases Option|local.imta.mailaliases]]<dd>

List of comma-delineated LDAP attributes that override the default
attributes. These attributes should be email addresses that can be
routed.
Syntax: non-empty-string
<dt>[[nsmsglogenable Option|local.imta.nsmsglog.enable]]<dd>

DELETED: Use the <code>LOG_MESSAGES_SYSLOG</code> MTA option instead.
Syntax: boolDefault: <code>0</code>
<dt>[[reverseenabled Option|local.imta.reverseenabled]]<dd>

Triggers the generation of the reverse database. How the reverse
database is actually used is controlled by the
<code>USE_REVERSE_DATABASE</code> option. DELETED: No longer relevant
with <code>dirsync</code> obsoleted (as of Messaging Server 6.0).
Syntax: boolDefault: <code>1</code>
<dt>[[ldap_schematag Option|local.imta.schematag]]<dd>

Defines the types of LDAP entries that are supported by the MTA
(comma-separated list).
Syntax: non-empty-string
<dt>[[scope Option|local.imta.scope]]<dd>

Informs <code>dirsync</code> which entries it should
synchronize. DELETED: No longer relevant with <code>dirsync</code>
obsoleted (as of Messaging Server 6.0).
Syntax: non-empty-string
<dt>[[sims_migrate Option|local.imta.sims_migrate]]<dd>

DELETED: No longer relevant with <code>dirsync</code> obsoleted (as of
Messaging Server 6.0).
Syntax: boolDefault: <code>0</code>
<dt>[[sslnicknames Option|local.imta.sslnicknames]]<dd>

List of SSL/TLS server certificate nicknames (only one per certificate
type) for MTA to offer clients if TLS enabled. Overrides
<code>encryption.rsa.nssslpersonalityssl</code>.
Syntax: name-list
<dt>[[ssrenabled Option|local.imta.ssrenabled]]<dd>

Triggers the generation of the server side rule database. How the SSR
database is actually used is controlled by the ssr channel
keyword. DELETED: No longer relevant with <code>dirsync</code>
obsoleted (as of Messaging Server 6.0).
Syntax: boolDefault: <code>1</code>
<dt>[[statssamplesize Option|local.imta.statssamplesize]]<dd>

If set, this parameter tells <code>dirsync</code> to print out on the
standard output. DELETED: No longer relevant with <code>dirsync</code>
obsoleted (as of Messaging Server 6.0).
Syntax: int32Default: <code>0</code>
<dt>[[ugfilter Option|local.imta.ugfilter]]<dd>

Sets the LDAP search filter that <code>dirsync</code> uses when
searching for users and groups. DELETED: No longer relevant with
<code>dirsync</code> obsoleted (as of Messaging Server 6.0).
Syntax: non-empty-stringDefault: <code>objectClass=inetLocalMailRecipient</code>
<dt>[[vanityenabled Option|local.imta.vanityenabled]]<dd>

Controls whether or not vanity domains are enabled. DELETED: Use the
<code>DOMAIN_MATCH_URL</code> MTA option instead.
Syntax: boolDefault: <code>1</code>
<dt>[[ipv6in Option|local.ipv6.in]]<dd>

When set to a value of 1, this option instructs Messaging Server to
accept inbound IPv6 connections for all services provided that the
host has at least one network interface configured for IPv6. Services
specifically configured to listen on only IPv4 interfaces cannot also
accept inbound IPv6 connections. When set to a value of 0, inbound
IPv6 connections are not allowed.


Inbound IPv4 connections will always be permitted.
Syntax: bool
<dt>[[ipv6out Option|local.ipv6.out]]<dd>

When set to a value of 1, this option instructs Messaging Server to
attempt outbound IPv6 connections for all services provided that the
host has at least one network interface configured for IPv6. Services
specifically configured to bind their source IP address only to IPv4
interfaces cannot attempt IPv6 outbound connections. For example, an
SMTP client bound to a specific IPv4 interface cannot then establish
an outbound IPv6 connection. When set to a value of 0, outbound IPv6
connections are not allowed.


When set to a value of 1, outbound services will attempt DNS lookups
of both A and AAAA records. Connection attempts will then be made in
the order dictated by the [[#ipv6sortorder|<code>ipv6sortorder</code>]] option. Note the
DNS lookups will always request A records. This option only controls
whether or not AAAA records are also requested.
Syntax: bool
<dt>[[ipv6sortorder Option|local.ipv6.sortorder]]<dd>

Controls the order in which IPv4 (A) and IPv6 (AAAA) DNS address
records are used when attempting connections to other named systems.
<table> <tr><td><code>default</code></td><td>Process A
and AAAA records in the order returned by the operating
system.</td></tr> <tr><td><code>a</code></td><td>Process only A
records; ignore AAAA records.</td></tr>
<tr><td><code>aaaa</code></td><td>Process only AAAA records; ignore A
records.</td></tr> <tr><td><code>a-aaaa</code></td><td>Process A
records, then AAAA records.</td></tr>
<tr><td><code>aaaa-a</code></td><td>Process AAAA records, then A
records</td></tr> </table>Syntax: enumstr
<dt>[[ldapauthpoolsize Option|local.ldapauthpoolsize]]<dd>

Default LDAP pool size for authentication.
Syntax: int32Default: <code>10</code>
<dt>[[ldapcheckcert Option|local.ldapcheckcert]]<dd>

Verify the LDAP server certificate.
Syntax: boolDefault: <code>1</code>
<dt>[[ldapconnecttimeout Option|local.ldapconnecttimeout]]<dd>

Time in seconds to wait for a new LDAP connection to complete.
Syntax: int32Default: <code>60</code>
<dt>[[ldapmodifytimeout Option|local.ldapmodifytimeout]]<dd>

Time in seconds to wait for LDAP modify operations to complete.
Syntax: int32Default: <code>60</code>
<dt>[[ldappoolrefreshinterval Option|local.ldappoolrefreshinterval]] (minutes)<dd>

Length of time in minutes before LDAP connections are automatically
closed then re-established to the LDAP server. Also, length of elapsed
time in minutes until the failover directory server reverts back to
the primary directory server. If set to -1, use the code default which
is 35 minutes.
Syntax: int32Default: <code>-1</code>
<dt>[[ldapsearchtimeout Option|local.ldapsearchtimeout]]<dd>

Timeout, in seconds, for all LDAP searches using ldappool which do not
already have a timeout. Connections which time out while searching are
also now removed from the pool, making failover possible if an LDAP
load balancer is used.
Syntax: int32Default: <code>60</code>
<dt>[[ldaptrace Option|local.ldaptrace]]<dd>

Enable LDAP trace (debug) logging. Deprecated in favor of
local.debugkeys 'ldap' key.
Syntax: boolDefault: <code>0</code>
<dt>[[lockdir Option|local.lockdir]]<dd>

Full pathname of server lock directory. Defaults to
/tmp/.ENCODED_SERVERROOT/lock/, where ENCODED_SERVERROOT is composed
of mail server user plus the $SERVERROOT with / replaced by _.
e.g. /tmp/.mailsrv_opt_sun_comms_messaging64/lock/
If the directory does not exist, it will be created.


IMPORTANT: Stop and restart all message store
processes immediately after changing this value. New processes will
use the new value and be unable to communicate with a stored using the
old value.
Syntax: absdirpath
<dt>[[enable Option|local.metermaid.enable]]<dd>

Enable the Metermaid service on <code>start-msg</code> startup.
Syntax: boolDefault: <code>0</code>
<dt>[[connection_stats_interval Option|local.mfagent.connection_stats_interval]]<dd>

Set how often, in seconds, to refresh the connection
statistics. DELETED: Removed in 7u3.
Syntax: int32Default: <code>5</code>
<dt>[[debug Option|local.mfagent.debug]]<dd>

Set a bit mask for various types of debugging. DELETED: Removed in 7u3.
Syntax: int32Default: <code>0</code>
<dt>[[enable Option|local.mfagent.enable]]<dd>

Enable JES Monitoring Framework agent on <code>start-msg</code>
startup. DELETED: Removed in 7u3.
Syntax: boolDefault: <code>0</code>
<dt>[[host_stats_interval Option|local.mfagent.host_stats_interval]]<dd>

Set how often, in seconds, to refresh the hosts statistics. DELETED:
Removed in 7u3.
Syntax: int32Default: <code>6</code>
<dt>[[listenaddr Option|local.mfagent.listenaddr]]<dd>

Sets the bind address for the mfagent. DELETED: Removed in 7u3.
Syntax: interface-addressDefault: <code>INADDR_ANY</code>
<dt>[[max_report_hosts Option|local.mfagent.max_report_hosts]]<dd>

Sets the maximum number of hosts to be reported on for channel queues.
Do not set higher than 12. DELETED: Removed in 7u3.
Syntax: int32Default: <code>10</code>
<dt>[[monitor_level Option|local.mfagent.monitor_level]]<dd>

Sets the level of transaction monitoring. The range is 0 (least) to 7
(most). DELETED: Removed in 7u3.
Syntax: int32Default: <code>0</code>
<dt>[[oldest_message_update Option|local.mfagent.oldest_message_update]]<dd>

Sets the frequency of updating the oldest message info. The oldest
message info is updated every nth time the connection stats are
updated, n being this parameter. DELETED: Removed in 7u3.
Syntax: int32Default: <code>16</code>
<dt>[[port Option|local.mfagent.port]]<dd>

Sets the port on which the mfagent listens. DELETED: Removed in 7u3.
Syntax: uint16Default: <code>16</code>
<dt>[[secret Option|local.mfagent.secret]]<dd>

The shared secret used to authenticate connections to the mfagent. DELETED:
Removed in 7u3.
Syntax: password
<dt>[[timeout Option|local.mfagent.timeout]]<dd>

Timeout for how long components will try to connect to the mfagent.
DELETED: Removed in 7u3.
Syntax: uint32Default: <code>30</code>
<dt>[[enable Option|local.mmp.enable]]<dd>

Enable the MMP service on <code>start-msg</code> startup.
Syntax: boolDefault: <code>0</code>
<dt>[[activate Option|local.msgtrace.active]]<dd>

Enable message tracing. Permitted values are <code>yes</code>
and <code>msgtrace</code>.
Syntax: printable-ascii-string
<dt>[[obsoleteimap Option|local.obsoleteimap]]<dd>

Allow old IMAP2bis and IMAP4 commands.
Syntax: boolDefault: <code>1</code>
<dt>[[forcetelemetry Option|local.pop.forcetelemetry]]<dd>

Force telemetry for all users. Warning: this generates a lot of data
and should not be used on a production system.
Syntax: boolDefault: <code>0</code>
<dt>[[lockmailbox Option|local.pop.lockmailbox]]<dd>

When set to 1 (on), this parameter limits the number of pop sessions
allowed to access a mailbox at a time to one. When set to 0 (off), pop
users can access mailboxes in multiple sessions concurrently.
Syntax: boolDefault: <code>0</code>
<dt>[[logprotocolerrors Option|local.pop.logprotocolerrors]]<dd>

If greater than zero, protocol errors are logged as debug messages for POP.
Syntax: uint32Default: <code>0</code>
<dt>[[maxprotocolerrors Option|local.pop.maxprotocolerrors]]<dd>

Maximum number of protocol errors allowed before connection is forcibly closed.
Syntax: uint32Default: <code>9999</code>
<dt>[[sslnicknames Option|local.pop.sslnicknames]]<dd>

List of SSL/TLS server certificate nicknames (only one per certificate
type) for POP to offer clients if SSL/TLS enabled. Overrides
<code>encryption.rsa.nssslpersonalityssl</code>.
Syntax: name-list
<dt>[[poplogmboxstat Option|local.poplogmboxstat]]<dd>

POP log will show mailbox statistics on login and logout if the value
is set to 1.
Syntax: boolDefault: <code>0</code>
<dt>[[preferpoll Option|local.preferpoll]]<dd>

On Solaris 10 and later, the IMAP and MMP servers can use Solaris
Event Completion Ports instead of the poll system call. Setting this
to 0 will enable use of Solaris Event Completion Ports which may
perform faster, but may create operational problems as this feature
has not yet had adequate testing. The default value of 1 will prefer
use of the standard poll API over Solaris Event Completion Ports. See
also <code>local.imap.polldelay</code> and Solaris bug 6438988,
6379476. At some point in the future when testing is sufficient, the
default may change to 0.
Syntax: bool
<dt>[[timeout Option|local.probe.cert.timeout]]<dd>

Timeout before restart.
Syntax: uint32Default: <code>0</code>
<dt>[[warningthreshold Option|local.probe.cert.warningthreshold]]<dd>

Number of seconds of Certificate service non-response before a warning
message is logged to the <code>default</code> log file.
Syntax: int32
<dt>[[timeout Option|local.probe.http.timeout]]<dd>

Timeout before restart.
Syntax: uint32Default: <code>0</code>
<dt>[[warningthreshold Option|local.probe.http.warningthreshold]]<dd>

Number of seconds of HTTP service non-response before a warning
message is logged to the <code>default</code> log file.
Syntax: int32
<dt>[[timeout Option|local.probe.imap.timeout]]<dd>

Timeout before restart.
Syntax: uint32Default: <code>0</code>
<dt>[[warningthreshold Option|local.probe.imap.warningthreshold]]<dd>

Number of seconds of IMAP service non-response before a warning
message is logged to the <code>default</code> log file.
Syntax: int32
<dt>[[timeout Option|local.probe.job_controller.timeout]]<dd>

Timeout before restart.
Syntax: uint32Default: <code>0</code>
<dt>[[warningthreshold Option|local.probe.job_controller.warningthreshold]]<dd>

Number of seconds of Job Controller non-response before a warning
message is logged to the <code>default</code> log file.
Syntax: int32
<dt>[[timeout Option|local.probe.lmtp.timeout]]<dd>

Timeout before restart.
Syntax: uint32Default: <code>0</code>
<dt>[[warningthreshold Option|local.probe.lmtp.warningthreshold]]<dd>

Number of seconds of LMTP service non-response before a warning
message is logged to the <code>default</code> log file.
Syntax: int32
<dt>[[timeout Option|local.probe.pop.timeout]]<dd>

Timeout before restart.
Syntax: uint32Default: <code>0</code>
<dt>[[warningthreshold Option|local.probe.pop.warningthreshold]]<dd>

Number of seconds of POP service non-response before a warning message
is logged to the <code>default</code> log file.
Syntax: int32
<dt>[[timeout Option|local.probe.smtp.timeout]]<dd>

Timeout before restart.
Syntax: uint32Default: <code>0</code>
<dt>[[warningthreshold Option|local.probe.smtp.warningthreshold]]<dd>

Number of seconds of SMTP service non-response before a warning
message is logged to the <code>default</code> log file.
Syntax: int32
<dt>[[timeout Option|local.probe.submit.timeout]]<dd>

Timeout before restart.
Syntax: uint32Default: <code>0</code>
<dt>[[warningthreshold Option|local.probe.submit.warningthreshold]]<dd>

Number of seconds of SMTP Submit service non-response before a warning
message is logged to the <code>default</code> log file.
Syntax: int32
<dt>[[warningthreshold Option|local.probe.warningthreshold]]<dd>

Specifies the value, in number of seconds, of a warning threshold for
all mail services. When the response time of a service is longer than
the specified number of seconds, <code>msprobe</code> sends a warning
message to the <code>default</code> log file.
Syntax: int32
<dt>[[projectid Option|local.projectid]]<dd>

The <code>projectid</code> option specifies the numeric identifier
Messaging Server uses when obtaining shared memory segments. This
identifier is used in ftok() calls to generate a shared memory segment
key. By default, a value of 7 is used. Only the lowest eight bits of
the value are significant.
''Introduced in release: 7 Update 3''Syntax: uint32Default: <code>7</code>
<dt>[[enable Option|local.purge.enable]]<dd>

Enable <code>purge</code> server on <code>start-msg</code>
startup. Defaults to local.store.enable setting.
Syntax: bool
<dt>[[queuedir Option|local.queuedir]]<dd>

Full pathname of spool directory or local queue directory to be
monitored by <code>msprobe</code>.
Syntax: absdirpath
<dt>[[rbac Option|local.rbac]]<dd>

Enable use of Role-Based Access Controls on Solaris (don't require
root access).
Syntax: boolDefault: <code>0</code>
<dt>[[rfc822headerallow8bit Option|local.rfc822header.allow8bit]]<dd>

Allow 8-bit characters in message headers in Messenger Express. If
this parameter is set to "no"; or if the 8-bit character is invalid,
then the character will be displayed as "?".
Syntax: boolDefault: <code>0</code>
<dt>[[enable Option|local.sched.enable]]<dd>

Enable the Scheduler service on <code>start-msg</code> startup.
Syntax: boolDefault: <code>0</code>
<dt>[[crontab Option|local.schedule.*]]<dd>

Set a task run schedule, enabled with
<code>local.schedule.*.enable</code>. Uses UNIX <code>crontab</code>
format: minute hour day-of-month month-of-year day-of-week command
arguments.
Syntax: non-empty-string
<dt>[[enable Option|local.schedule.*.enable]]<dd>

Whether a task should be scheduled.
Syntax: boolDefault: <code>0</code>
<dt>[[enable Option|local.schedule.expire.enable]]<dd>

Whether the expire task should be scheduled.
Defaults to local.store.enable setting.
Syntax: bool
<dt>[[enable Option|local.schedule.msprobe.enable]]<dd>

Whether the msprobe task should be scheduled.
Syntax: boolDefault: <code>1</code>
<dt>[[enable Option|local.schedule.purge.enable]]<dd>

Whether the purge task should be scheduled.
Defaults to local.imta.enable setting.
Syntax: bool
<dt>[[crontab Option|local.schedule.return_job]]<dd>

Interval for running <code>return_job</code>, enabled with
<code>local.schedule.return_job.enable</code>. Uses UNIX
<code>crontab</code> format: minute hour day-of-month month-of-year
day-of-week command arguments.
Syntax: non-empty-string
<dt>[[enable Option|local.schedule.return_job.enable]]<dd>

Whether the return_job task should be scheduled.
Defaults to local.imta.enable setting.
Syntax: bool
<dt>[[enable Option|local.schedule.snapshot.enable]]<dd>

Whether the snapshot / verify task should be
scheduled. Defaults to local.store.enable setting.
Syntax: bool
<dt>[[enable Option|local.schedule.snapshotverify.enable]]<dd>

Whether the process log verify task for rolling
backups should be scheduled. Defaults to local.store.enable setting.
Syntax: bool
<dt>[[servergid Option|local.servergid]]<dd>

DELETED: Server group id in UNIX. Now uses primary group of serveruid
instead.
Syntax: non-empty-string
<dt>[[serveruid Option|local.serveruid]]<dd>

User id of server in UNIX. This is deprecated in favor of
the <code>user</code> option in <code>restrcted.cnf</code> which is
used preferentially.
Syntax: non-empty-string
<dt>[[allowcollect Option|local.service.http.allowcollect]]<dd>

Set this to 0 to prevent the server from performing remote POP mailbox collection.
Syntax: boolDefault: <code>1</code>
<dt>[[allowldapaddresssearch Option|local.service.http.allowldapaddresssearch]]<dd>

Whether legacy webmail client users can search the directory
(Messenger Express & Communications Express).
Syntax: boolDefault: <code>0</code>
<dt>[[charsetvalidation Option|local.service.http.charsetvalidation]]<dd>

Set this to "0" to disable charset validation on data sent to webmail
client (not recommended). Setting this to "0" is a workaround to view
messages in webmail that are not labelled with the correct charset
(the charset would be set then in the browser), but this will also
likely generate Javascript errors and so cannot be recommended.
Syntax: boolDefault: <code>1</code>
<dt>[[cookiename Option|local.service.http.cookiename]]<dd>

The cookie name to use to pass the HTTP session ID rather than
including it as part of the URL. It defaults to
<code>webmailsid</code> if <code>local.webmail.sso.uwcenabled</code>
is enabled, and is unset if <code>local.webmail.sso.uwcenabled</code>
is not enabled.
Syntax: non-empty-string
<dt>[[filterhiddenmailinglists Option|local.service.http.filterhiddenmailinglists]]<dd>

Excludes the <code>mgmanhidden</code> attribute from the search filter
when set to 0.
Syntax: boolDefault: <code>1</code>
<dt>[[generatereceivedheader Option|local.service.http.generatereceivedheader]]<dd>

If set to "0", webmail will not generate a Received header, which
normally contains the IP address of the sender.
Syntax: boolDefault: <code>1</code>
<dt>[[gzipattach Option|local.service.http.gzip.attach]]<dd>

Enables (when set to 1) or disables attachment download gzip by
default for Internet Explorer clients.
Syntax: boolDefault: <code>0</code>
<dt>[[gzipdynamic Option|local.service.http.gzip.dynamic]]<dd>

Enables or disables compression of dynamic content (for example:
request to <code>*.msc</code> files) delivered to Messenger Express or
Communications Express mail clients. This can be disabled if Messenger
Express or Communications Express users are getting corrupted content
and cannot open their mail pages.
Syntax: boolDefault: <code>1</code>
<dt>[[gzipstatic Option|local.service.http.gzip.static]]<dd>

Enables or disables compression of static content (for example: HTML
files) delivered to Messenger Express or Communications Express mail
clients. This can be disabled if Messenger Express or Communications
Express users are getting corrupted content and cannot open their mail
pages.
Syntax: boolDefault: <code>1</code>
<dt>[[htmlprocessor Option|local.service.http.htmlprocessor]]<dd>

Whether to enable the new html mail processor and sanitizer in mshttpd
(bug 12220148 [Sun 6637129]), etc).
''Introduced in release: 7 Update 4''Syntax: boolDefault: <code>1</code>
<dt>[[ims5compat Option|local.service.http.ims5compat]]<dd>

Set this to 1 on the MEMs and the backend servers to use 5.2 Messaging
Express with a 6.x MEM.
Syntax: boolDefault: <code>0</code>
<dt>[[ldapaddresssearchattrs Option|local.service.http.ldapaddresssearchattrs]]<dd>

A comma-delineated list of LDAP attributes returned to webmail users
in a directory search.
Syntax: non-empty-string
<dt>[[maxcollectmsglen Option|local.service.http.maxcollectmsglen]]<dd>

Maximum message size the server collects from a remote POP mailbox. If
any message in the mailbox to be collect exceeds this size, the
collection will halt when that message is encountered.
Syntax: uint32Default: <code>104857600</code>
<dt>[[maxldaplimit Option|local.service.http.maxldaplimit]]<dd>

Sets the maximum LDAP lookup limit.
Syntax: uint32Default: <code>500</code>
<dt>[[nofilecache Option|local.service.http.nofilecache]]<dd>

Disable html files caching, used for debugging.
Syntax: boolDefault: <code>0</code>
<dt>[[popbindaddr Option|local.service.http.popbindaddr]]<dd>

IP address to which to bind outgoing POP connections when collecting
external mail. If unset, defaults to the value of
<code>service.listenaddr</code>.
Syntax: non-empty-string
<dt>[[httpproxyadmin Option|local.service.http.proxy.admin]]<dd>

Back-end store admin login name.
Syntax: non-empty-stringDefault: <code>admin</code>
<dt>[[httpadmin Option|local.service.http.proxy.admin.*]]<dd>

Store admin login name for a specific host if different from
<code>local.service.http.proxy.admin</code>. Not configured by
default.
Syntax: non-empty-string
<dt>[[httpproxyadminpass Option|local.service.http.proxy.adminpass]]<dd>

Back-end store admin password. Consider
using <code>proxyadminpass</code> instead.
Syntax: password
<dt>[[httpadminpass Option|local.service.http.proxy.adminpass.*]]<dd>

Store admin password for a specific host if different from
<code>local.service.http.proxy.adminpass</code>. Not configured by
default.
Syntax: password
<dt>[[proxyport Option|local.service.http.proxy.port]]<dd>

Configures the port number of the back-end Messenger Express (HTTP)
server with the Messaging Multiplexor.
Syntax: uint16Default: <code>80</code>
<dt>[[httpport Option|local.service.http.proxy.port.*]]<dd>

Port number for a specific back-end Messenger Express (HTTP) server if
different from <code>local.service.http.proxy.port</code>. Not
configured by default.
Syntax: uint16
<dt>[[rfc2231compliant Option|local.service.http.rfc2231compliant]]<dd>

Enables webmail's RFC-2231 encoder so that the attachment filename
will be encoded in the method defined by RFC-2231.
Syntax: boolDefault: <code>0</code>
<dt>[[showunreadcounts Option|local.service.http.showunreadcounts]]<dd>

Shows unread count in parentheses after the folder name. This
parameter is only applicable for the Messenger Express and
Communications Express web clients. For the Convergence web client
this setting is always enabled.
Syntax: boolDefault: <code>0</code>
<dt>[[smtpauthpassword Option|local.service.http.smtpauthpassword]]<dd>

Password that will be used when <code>mshttpd</code> submits mail
to the MTA. See [[#smtpauthuser|smtpauthuser]].
Syntax: passwordDefault: <code><admin.password></code>
<dt>[[smtpauthuser Option|local.service.http.smtpauthuser]]<dd>

When <code>mshttpd</code> submits mail to the MTA, SMTP authentication
will be used if both <code>smtpauthuser</code>
and <code>smtpauthpassword</code> are set. These two options specify
the administrative user name and password that are used to submit mail
on behalf of end users.
Syntax: non-empty-stringDefault: <code>admin</code>
<dt>[[usesentdate Option|local.service.http.usesentdate]]<dd>

If this is set to "1", webmail will use a message's Date: header for
the date the message was received. If set to "0", webmail will use the
date the message arrived in the user's mailbox, which is considered
more accurate.
Syntax: boolDefault: <code>0</code>
<dt>[[xmailer Option|local.service.http.xmailer]]<dd>

Override X-Mailer header with this string.
Syntax: non-empty-string
<dt>[[active Option|local.service.pab.active]]<dd>

1 if PAB host is active, 0 otherwise.
Syntax: int32
<dt>[[alwaysusedefaulthost Option|local.service.pab.alwaysusedefaulthost]]<dd>

Enables one PAB server to be used (overriding hostname in PAB URIs).
Syntax: boolDefault: <code>0</code>
<dt>[[attributelist Option|local.service.pab.attributelist]]<dd>

Add new attributes to a personal address book entry. With this
parameter, you can create an attribute that does not already exist.
Syntax: non-empty-stringDefault: <code>pabattrs</code>
<dt>[[defaulthostindex Option|local.service.pab.defaulthost]]<dd>

Index of default host.
Syntax: int32Default: <code>0</code>
<dt>[[enable Option|local.service.pab.enabled]]<dd>

Enable or disable Personal Address Book (PAB) feature.
Syntax: boolDefault: <code>0</code>
<dt>[[ldapbasedn Option|local.service.pab.ldapbasedn]]<dd>

Base DN for PAB searches. If not set, it defaults to the value of
<code>local.ugldapbasedn</code>.
Syntax: non-empty-string
<dt>[[ldapbinddn Option|local.service.pab.ldapbinddn]]<dd>

Bind DN for PAB searches. If not set, it defaults to the value of
<code>local.ugldapbinddn</code>.
Syntax: non-empty-string
<dt>[[ldaphost Option|local.service.pab.ldaphost]]<dd>

Hostname of the PAB Directory Server. If not set, it
defaults to the value of <code>local.ugldaphost</code>.
Syntax: non-empty-string
<dt>[[ldappasswd Option|local.service.pab.ldappasswd]]<dd>

Password for user specified by
<code>local.service.pab.ldapbinddn</code>. If not set, it defaults to
the value of <code>local.ugldapbindcred</code>.
Syntax: password
<dt>[[ldapport Option|local.service.pab.ldapport]]<dd>

Port number of the PAB Directory Server. If not set, it defaults to
the value of <code>local.ugldapport</code>.
Syntax: uint16
<dt>[[ldapusessl Option|local.service.pab.ldapusessl]]<dd>

Use SSL to connect to the PAB Directory Server.
Syntax: boolDefault: <code>0</code>
<dt>[[maxnumberofentries Option|local.service.pab.maxnumberofentries]]<dd>

Maximum number of entries a single PAB can store.
Syntax: uint32Default: <code>500</code>
<dt>[[migrate415 Option|local.service.pab.migrate415]]<dd>

Enables PAB migration when set to 1.
Syntax: boolDefault: <code>0</code>
<dt>[[numberofhosts Option|local.service.pab.numberofhosts]]<dd>

Number of PAB servers (up to a maximum of 16).
Syntax: uint32Default: <code>1</code>
<dt>[[proxyadmin Option|local.service.proxy.admin]]<dd>

Default store admin login name.
Syntax: non-empty-stringDefault: <code>admin</code>
<dt>[[imapadmin Option|local.service.proxy.admin.*]]<dd>

Store admin login name for a specific host if different from
<code>local.service.proxy.admin</code>. Not configured by default.
Syntax: non-empty-string
<dt>[[proxyadminpass Option|local.service.proxy.adminpass]]<dd>

Default store admin password.
Syntax: passwordDefault: <code><admin.password></code>
<dt>[[imapadminpass Option|local.service.proxy.adminpass.*]]<dd>

Store admin password for a specific host if different from
<code>local.service.proxy.adminpass</code>. Not configured by default.
Syntax: password
<dt>[[proxyimapport Option|local.service.proxy.imapport]]<dd>

Default IMAP port number for backend store servers.
Syntax: uint16Default: <code>143</code>
<dt>[[imapport Option|local.service.proxy.imapport.*]]<dd>

IMAP port number for a specific backend store server.
Syntax: uint16Default: <code>143</code>
<dt>[[proxyimapssl Option|local.service.proxy.imapssl]]<dd>

Enable SSL access to backend store servers. Defaults to 1 if backend
store IMAP port is 993, and 0 otherwise.
Syntax: bool
<dt>[[proxyserverlist Option|local.service.proxy.serverlist]]<dd>

Message store server list to list shared folders from. Takes a
space-separated string. Not configured by default.
Syntax: non-empty-string
<dt>[[proxytrustmailhost Option|local.service.proxy.trustmailhost]]<dd>

Whether to proxy commands such as urlfetch to the user's LDAP
mailhost, if that server is not listed in proxyserverlist.
''Introduced in release: 7 Update 4''Syntax: boolDefault: <code>0</code>
<dt>[[enable Option|local.smsgateway.enable]]<dd>

Enable the SMS service on <code>start-msg</code> startup.
Syntax: boolDefault: <code>0</code>
<dt>[[foreground Option|local.smsgateway.foreground]]<dd>

Run the SMS Gateway Server in the foreground with debugging enabled.
Syntax: int32Default: <code>0</code>
<dt>[[cachettl Option|local.snmp.cachettl]]<dd>

Cache entry time to live in seconds.
Syntax: int32Default: <code>30</code>
<dt>[[contextname Option|local.snmp.contextname]]<dd>

SNMPv3 context name to register this instance's MIBs under; the
default value is the value of <code>service.defaultdomain</code>.
Syntax: non-empty-string
<dt>[[directoryscan Option|local.snmp.directoryscan]]<dd>

Traverse on-disk channel queues for .HELD files and to update
information on oldest queued message files.
Syntax: boolDefault: <code>1</code>
<dt>[[enable Option|local.snmp.enable]]<dd>

Enable the SNMP subagent on <code>start-msg</code> startup.
Syntax: boolDefault: <code>0</code>
<dt>[[enablecontextname Option|local.snmp.enablecontextname]]<dd>

Register this instance's MIBs under an SNMPv3 context name.
Syntax: boolDefault: <code>0</code>
<dt>[[listenaddr Option|local.snmp.listenaddr]]<dd>

The IPv4 address to listen on when running as a SNMP master agent.
The allowed values for this option include an IPv4 address in dotted decimal
form (e.g., 127.0.0.1), or a short form or fully-qualified DNS host name which
will be resolved to an IPv4 address by obtaining the DNS A record for the
name. To explicitly specify the default value of binding to all available
interfaces, the string "INADDR_ANY" may be used. To bind to the loopback
device, 127.0.0.1, the string "localhost" may be specified.
Syntax: interface-addressDefault: <code>INADDR_ANY</code>
<dt>[[port Option|local.snmp.port]]<dd>

UDP port to listen on when running as a SNMP master agent.
Syntax: uint16Default: <code>161</code>
<dt>[[registerindices Option|local.snmp.registerindices]]<dd>

Register as visible MIB variables the applIndex, assocIndex, and
mtaGroupIndex MIB indices By default, these MIB variables are implicit
and not explicitly shown as distinct MIB variables when walking the
MIBs.
Syntax: boolDefault: <code>0</code>
<dt>[[servertimeout Option|local.snmp.servertimeout]]<dd>

Maximum number of seconds to wait for each step in probing a server
(connect to, read from, write to, etc.).
Syntax: int32Default: <code>5</code>
<dt>[[standalone Option|local.snmp.standalone]]<dd>

Run as a standalone SNMP agent when set to 1 or "true".
Syntax: boolDefault: <code>0</code>
<dt>[[ssladjustciphersuites Option|local.ssladjustciphersuites]]<dd>

Adjust which SSL cipher suites are enabled or disabled. SSL cipher
suites control the level of protection required between SSL client and
server. Different cipher suites have different properties and use
different cryptographic algorithms. At any time a specific
crytographic algorithm might be weakened or compromised by new
research in cryptography. The ability to change the default cipher
suites allows the software to adapt as security technology changes.
In addition as CPUs get faster, the key size necessary to provide
several years of comfortable protection increases, even if the
algorithm is considered state-of-the-art.


The default set of SSL cipher suites used may change over time as more
secure ones are introduced and weaker ones are deprecated. It is
expected most deployments will be happy with the default set of cipher
suites and it is generally not a good idea to adjust the available
cipher suites without reason. However, here are some scenarios where
it may be helpful to adjust cipher suites: 1. a site with specific
security policies may wish to provide a fixed list of cipher suites to
use that is set by site policy rather than simply using
state-of-the-art suites provided by the NSS library. Such a site
would typically configure this setting to '-ALL,...' where '...'
contains the cipher suite names. 2. A site which is experimenting
with higher performance or more secure cipher suites that require
installation of special server certificate types, for example the
elliptic curve cipher suites. Such a site would enable these
additional suites once installation was complete using a setting such
as '+TLS_ECDH_RSA_WITH_AES_128_CBC_SHA' to enable an ECDH_RSA cipher
suite from RFC 4492. 3. If a site is forced to continue supporting a
particularly old client that only supports weak cipher suites, they
can be explicitly enabled (for example 'WEAK+DES' enables the
single-DES cipher suites. 4. In the event the cryptographic research
community discovers a vulnerability in one or more of the ciphers
enabled by default, this provides a mechanism to immediately disable
those ciphers. For example, to disable all ciphers using the 'RC4'
algorithm, simply set '-RC4'.


As of 2008-Jan-29, the available cipher suites in the NSS library are
as follows: TLS_DHE_RSA_WITH_AES_256_CBC_SHA,
TLS_DHE_DSS_WITH_AES_256_CBC_SHA, TLS_RSA_WITH_AES_256_CBC_SHA,
TLS_DHE_DSS_WITH_RC4_128_SHA, TLS_DHE_RSA_WITH_AES_128_CBC_SHA,
TLS_DHE_DSS_WITH_AES_128_CBC_SHA, SSL_RSA_WITH_RC4_128_MD5,
SSL_RSA_WITH_RC4_128_SHA, TLS_RSA_WITH_AES_128_CBC_SHA,
SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA,
SSL_RSA_FIPS_WITH_3DES_EDE_CBC_SHA, SSL_RSA_WITH_3DES_EDE_CBC_SHA,
SSL_DHE_RSA_WITH_DES_CBC_SHA, SSL_DHE_DSS_WITH_DES_CBC_SHA,
SSL_RSA_FIPS_WITH_DES_CBC_SHA, SSL_RSA_WITH_DES_CBC_SHA,
TLS_RSA_EXPORT1024_WITH_RC4_56_SHA,
TLS_RSA_EXPORT1024_WITH_DES_CBC_SHA, SSL_RSA_EXPORT_WITH_RC4_40_MD5,
SSL_RSA_EXPORT_WITH_RC2_CBC_40_MD5, SSL_RSA_WITH_NULL_SHA,
SSL_RSA_WITH_NULL_MD5, TLS_ECDH_ECDSA_WITH_NULL_SHA,
TLS_ECDH_ECDSA_WITH_RC4_128_SHA, TLS_ECDH_ECDSA_WITH_3DES_EDE_CBC_SHA,
TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA,
TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA, TLS_ECDHE_ECDSA_WITH_NULL_SHA,
TLS_ECDHE_ECDSA_WITH_RC4_128_SHA,
TLS_ECDHE_ECDSA_WITH_3DES_EDE_CBC_SHA,
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA,
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA, TLS_ECDH_RSA_WITH_NULL_SHA,
TLS_ECDH_RSA_WITH_RC4_128_SHA, TLS_ECDH_RSA_WITH_3DES_EDE_CBC_SHA,
TLS_ECDH_RSA_WITH_AES_128_CBC_SHA, TLS_ECDH_RSA_WITH_AES_256_CBC_SHA,
TLS_ECDHE_RSA_WITH_NULL_SHA, TLS_ECDHE_RSA_WITH_RC4_128_SHA,
TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA,
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA,
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA. This list exlcudes the SSL2
cipher suites as Messaging Server has not supported SSL2 since the 6.0
release. While the standard names for cipher suites (as published in
TLS RFCs) are preferred, there is limited support for legacy names
used in previous releases and for some OpenSSL names.
Syntax: non-empty-string
<dt>[[ssldblegacy Option|local.ssldblegacy]]<dd>

When set, this requires SSL/TLS server certificates, CAs and CRLs to
be stored in the legacy cert8.db and key3.db formats supported by our
SSL/TLS library. When this is not set, both the legacy cert8.db/key3.db
and the modern cert9.db/key4.db formats are supported. The legacy
format requires servers to be shut down when updating the database for
any reason. The modern format allows updates to be performed while the
servers are running.
''Introduced in release: 7 patch 17''Syntax: boolDefault: <code>0</code>
<dt>[[ssldbpath Option|local.ssldbpath]]<dd>

Specifies the location of certificates and key files.
Syntax: absdirpath
<dt>[[ssldbprefix Option|local.ssldbprefix]]<dd>

Specifies the prefixes of the certificate and key files.
Syntax: non-empty-string
<dt>[[sslv3enable Option|local.sslv3enable]]<dd>

Determines whether legacy support for the SSLv3 protocol (as opposed
to the modern TLS protocol) is enabled. This is presently enabled by
default but may be disabled by default in the future. Security sensitive
sites should disable this support as SSLv3 is lacking some security
improvements available in TLS 1.0 and later. However, SSLv3 support may
be necessary to interoperate with older mail clients or mail clients
that are less concerned with modern security.
''Introduced in release: 7 Update 4''Syntax: boolDefault: <code>1</code>
<dt>[[verifyurl Option|local.sso.*.verifyurl]]<dd>

This is a trusted circle SSO (legacy) parameter. It sets the verify
URL values for peer SSO applications. "*" is the application ID of a
peer SSO application whose SSO cookies are to be honored. The
standard form of the value of the verify URL is
<code>http://[peer_hostname]:[port]/VerifySSO?</code>.
Syntax: non-empty-string
<dt>[[backupexclude Option|local.store.backup.exclude]]<dd>

Specifies mailboxes to be excluded from a backup operation. You can
specify a single mailbox or a list of mailboxes separated by the "%"
character.
Syntax: non-empty-string
<dt>[[backupdir Option|local.store.backupdir]]<dd>

Directory for backup image of message store data.
Syntax: absdirpath
<dt>[[cachesynclevel Option|local.store.cachesynclevel]]<dd>

Synchronization level for store cache file. 0: no sync, 1: data sync only, 2:
data sync and metadata sync (that is, all file attributes, including
access time and modification time).
Syntax: uint32Default: <code>1</code>
<dt>[[checkdiskusage Option|local.store.checkdiskusage]]<dd>

Stops messages from being delivered to a message store partition when
the partition fills more than a specified percentage of available disk
space. If disk usage goes higher than the specified threshold, the
store daemon locks the partition, logs a message to the default log
files, and sends an email notification to the postmaster. When disk
usage falls below the threshold, the partition is unlocked, and
messages are again delivered to the store.
Syntax: boolDefault: <code>1</code>
<dt>[[checkmailhost Option|local.store.checkmailhost]]<dd>

Enable checking that the user <code>mailhost</code> attribute matches
this server.
Syntax: boolDefault: <code>1</code>
<dt>[[dbnumcaches Option|local.store.dbnumcaches]]<dd>

The number of mboxlist db caches. If it is 0 or 1, the cache will be
allocated contiguously in memory. If it is greater than 1, the cache
will be broken up into ncache equally sized, separate pieces of
memory.
Syntax: uint32Default: <code>1</code>
<dt>[[dbsync Option|local.store.dbsync]]<dd>

If this is set to "yes", cached database information will be flushed
to disk before the database file is closed.
Syntax: boolDefault: <code>0</code>
<dt>[[autodetect Option|local.store.deadlock.autodetect]]<dd>

Sets whether all or just one thread resolves deadlock.
Syntax: boolDefault: <code>0</code>
<dt>[[checkinterval Option|local.store.deadlock.checkinterval]]<dd>

Specifies the sleep length (in microseconds) before
<code>lock_detect</code> is set again.
Syntax: uint32Default: <code>1000</code>
<dt>[[deadlockaggressive Option|local.store.deadlockaggressive]]<dd>

A non zero integer N indicates aggressive deadlock resolution,
combined by delaying transaction retries by N seconds.
Syntax: uint32Default: <code>10</code>
<dt>[[diskusagethreshold Option|local.store.diskusagethreshold]]<dd>

Specifies the disk-usage threshold for the partition-monitoring
feature. (For details about this feature, see
<code>local.store.checkdiskusage</code>). The value of
<code>local.store.diskusagethreshold</code> is a percentage from 1 to
99.
Syntax: uint32Default: <code>99</code>
<dt>[[enable Option|local.store.enable]]<dd>

Enable the Message Store when starting services.
Syntax: boolDefault: <code>0</code>
<dt>[[ensureownerrights Option|local.store.ensureownerrights]]<dd>

By default, the store grants list and administer rights to a folder's
owner. If this parameter is set to "0", however, then these owner
rights can be removed in order to create hidden folders.
Syntax: boolDefault: <code>1</code>
<dt>[[cleanonly Option|local.store.expire.cleanonly]]<dd>

Perform <code>purge</code> only, do not perform
<code>imexpire</code>. DELETED: (removed as of Messaging Server 7.0
Syntax: boolDefault: <code>0</code>
<dt>[[exploglevel Option|local.store.expire.loglevel]]<dd>

Specify an expire log level: 0: no log. 1: log summary for the entire expire
session. 2: log one message per mailbox expired. 3: log one message
per message expired.
Syntax: uint32Default: <code>0</code>
<dt>[[workday Option|local.store.expire.workday]]<dd>

Perform expire/cleanup on this day of the week. Values: 0-6 (0=
Sunday). DELETED: Use <code>local.schedule.expire</code> instead.
Syntax: uint32
<dt>[[expungesynclevel Option|local.store.expungesynclevel]]<dd>

Sync level for store expunge file. 0: no sync, 1: data sync only, 2:
data sync and metadata sync (that is, all file attributes, including
access time and modification time).
Syntax: uint32Default: <code>1</code>
<dt>[[finalcheckpoint Option|local.store.finalcheckpoint]]<dd>

Perform a final checkpoint of the transaction log before closing the
mailbox list database.
Syntax: boolDefault: <code>0</code>
<dt>[[indexsynclevel Option|local.store.indexsynclevel]]<dd>

Synchronization level for store index file. 0: no sync, 1: data sync
only, 2: data sync and metadata sync (that is, all file attributes,
including access time and modification time).
Syntax: uint32Default: <code>1</code>
<dt>[[listimplicit Option|local.store.listimplicit]]<dd>

When set to "1", implicitly shared folders will appear in lists
performed by store admins.
Syntax: boolDefault: <code>0</code>
<dt>[[logexpungedetails Option|local.store.logexpungedetails]]<dd>

If set to "yes", expunge details will be logged.
Syntax: non-empty-string
<dt>[[maxfolders Option|local.store.maxfolders]]<dd>

Specifies a maximum number of folders. Set to 0 for infinite.
Syntax: int32Default: <code>0</code>
<dt>[[maxlog Option|local.store.maxlog]]<dd>

Specifies the maximum number of allowable accumulated database
transaction log files before the server is deemed unhealthy, after
which <code>msprobe</code> will trigger a restart of
<code>stored</code>.
Syntax: uint32Default: <code>50</code>
<dt>[[maxmessages Option|local.store.maxmessages]]<dd>

Specifies a maximum number of messages per folder.
Syntax: uint32Default: <code>16000000</code>
<dt>[[messagesynclevel Option|local.store.messagesynclevel]]<dd>

Synchronization level for store message file. 0: no sync, 1: data sync only, 2:
data sync and metadata sync (that is, all file attributes, including
access time and modification time).
Syntax: uint32Default: <code>1</code>
<dt>[[messagetypeplugin Option|local.store.messagetypeplugin]]<dd>

Full pathname and command line arguments (preceded by a "$" character)
for message typing plugin. DELETED: Appears code to actually load
plug-ins was not present in 6.3 or later; haven't checked earlier
releases.
Syntax: non-empty-string
<dt>[[plugins Option|local.store.notifyplugin]]<dd>

Enable notifications via ENS and/or JMQ by specifying a library name
of "libibiff" or "libjmqnotify" respectively. Each library name should
then be followed by an instance name preceded by a "$" character.
Each library/instance pair should be separated from the next by a "$"
character. Several instances of plugins may be specified with different
instance names. The name given in the instance field for each specified
plugin is the name used to look up the configuration for that plugin.
The instance name "ms-internal" is reserved.


This option is not used for Unified Configuration.
Syntax: non-empty-stringDefault: <code>libibiff$ms-internal$</code>
<dt>[[annotatemsg Option|local.store.notifyplugin.*.annotatemsg.enable]]<dd>

Specifies whether AnnotateMsg events will generate a notification.
Syntax: boolDefault: <code>0</code>
<dt>[[changeflag Option|local.store.notifyplugin.*.changeflag.enable]]<dd>

Specifies whether ChangeFlag events will generate a notification.
Syntax: boolDefault: <code>0</code>
<dt>[[copymsg Option|local.store.notifyplugin.*.copymsg.enable]]<dd>

Specifies whether IMAP COPY operations will generate Copy events or UpdateMsg
events.
''Introduced in release: 7 Update 1''Syntax: boolDefault: <code>0</code>
<dt>[[debug Option|local.store.notifyplugin.*.debuglevel]]<dd>

Level of debugging messages for notification plugins.
Syntax: int32Default: <code>0</code>
<dt>[[deletemsg Option|local.store.notifyplugin.*.deletemsg.enable]]<dd>

Specifies whether DeleteMsg events will generate a notification.
Syntax: bool
<dt>[[destinationtype Option|local.store.notifyplugin.*.destinationtype]]<dd>
JMQ destination type, queue or topic.Syntax: non-empty-stringDefault: <code>topic</code>
<dt>[[enable Option|local.store.notifyplugin.*.enable]]<dd>

Specifies whether to generate notifications for this destination. The
most typical use of this is to disable the default destination for a
plugin, so notifications are only sent to destinations specified in
the ldapdestination attribute in users directory entries.
''Introduced in release: 7 Update 2''Syntax: boolDefault: <code>0</code>
<dt>[[enseventkey Option|local.store.notifyplugin.*.enseventkey]]<dd>

Event key to use for ENS notifications. %M is replaced at runtime with the mailbox name for mailbox-related events.
Syntax: non-empty-string
<dt>[[enshost Option|local.store.notifyplugin.*.enshost]]<dd>

The IP address or hostname of the ENS server. If unset, defaults to the
value of <code>service.listenaddr</code> or the loopback address.
Syntax: non-empty-string
<dt>[[ensport Option|local.store.notifyplugin.*.ensport]]<dd>

The TCP port number of the ENS server.
Syntax: uint16
<dt>[[expungemsg Option|local.store.notifyplugin.*.expungemsg.enable]]<dd>

Specifies whether ExpungeMsg events will generate a notification.
Syntax: boolDefault: <code>0</code>
<dt>[[jmqhost Option|local.store.notifyplugin.*.jmqhost]]<dd>

The hostname of the JMQ broker.
Syntax: non-empty-string
<dt>[[jmqport Option|local.store.notifyplugin.*.jmqport]]<dd>

The port number of the JMQ broker.
Syntax: uint16
<dt>[[jmqpwd Option|local.store.notifyplugin.*.jmqpwd]]<dd>

The JMQ user password.
Syntax: password
<dt>[[jmqqueue Option|local.store.notifyplugin.*.jmqqueue]]<dd>

The topic or queue to which JMQ will publish events (overrides
<code>local.store.notifyplugin.*.jmqtopic</code> if set).
Syntax: non-empty-string
<dt>[[jmqtopic Option|local.store.notifyplugin.*.jmqtopic]]<dd>

The topic or queue to which JMQ will publish events.
Syntax: non-empty-string
<dt>[[jmquser Option|local.store.notifyplugin.*.jmquser]]<dd>

The JMQ username.
Syntax: non-empty-string
<dt>[[ldapdestination Option|local.store.notifyplugin.*.ldapdestination]]<dd>

Specifies what ldap destination is to be used to look up a JMQ
notification destination. If this is not specified, or the user lacks
this attribute, or the value of this attribute is zero length, the
library id is used as the destination.
''Introduced in release: 7 Update 2''Syntax: non-empty-string
<dt>[[loguser Option|local.store.notifyplugin.*.loguser.enable]]<dd>

Specifies whether LogUser events will generate a notification.
Syntax: bool
<dt>[[maxbodysize Option|local.store.notifyplugin.*.maxbodysize]]<dd>

Specifies the maximum size (in bytes) of the body that will be
transmitted with the notification.
Syntax: uint32
<dt>[[maxheadersize Option|local.store.notifyplugin.*.maxheadersize]]<dd>

Specifies the maximum size (in bytes) of the header that will be
transmitted with the notification.
Syntax: uint32
<dt>[[msgflags Option|local.store.notifyplugin.*.msgflags.enable]]<dd>

Enables the msgflag notification mechanism.
Syntax: bool
<dt>[[msgtypes Option|local.store.notifyplugin.*.msgtypes.enable]]<dd>

Determines whether to include message type counts in PurgeMsg,
DeleteMsg, Copy, NewMsg, and UpdateMsg messages.
Syntax: boolDefault: <code>0</code>
<dt>[[newmsg Option|local.store.notifyplugin.*.newmsg.enable]]<dd>

Specifies whether NewMsg events will generate a notification.
Syntax: bool
<dt>[[noninbox Option|local.store.notifyplugin.*.noneinbox.enable]]<dd>

Determines whether all folders generate notifications or if only the
INBOX generates notifications: 0: only INBOX, 1: all folders.
Syntax: bool
<dt>[[persistent Option|local.store.notifyplugin.*.persistent]]<dd>

Specifies whether persistent JMQ messages are to be used.
Syntax: boolDefault: <code>0</code>
<dt>[[priority Option|local.store.notifyplugin.*.priority]]<dd>

The priority to be used for JMQ notification messages.
Syntax: int32Default: <code>4</code>
<dt>[[purgemsg Option|local.store.notifyplugin.*.purgemsg.enable]]<dd>

Specifies whether PurgeMsg events will generate a notification.
Syntax: bool
<dt>[[readmsg Option|local.store.notifyplugin.*.readmsg.enable]]<dd>

Specifies whether ReadMsg events will generate a notification.
Syntax: bool
<dt>[[ttl Option|local.store.notifyplugin.*.ttl]]<dd>

The time-to-live for JMQ messages. 0 means no timeout.
Syntax: uint32Default: <code>0</code>
<dt>[[updatemsg Option|local.store.notifyplugin.*.updatemsg.enable]]<dd>

Specifies whether UpdateMsg events will generate a notification.
Syntax: bool
<dt>[[debug Option|local.store.notifyplugin.debuglevel]]<dd>

Level of debugging messages for ibiff plugin. DELETED: Use
<code>local.store.notifyplugin.*.debuglevel</code>
instead.
Syntax: int32Default: <code>0</code>
<dt>[[deletemsg Option|local.store.notifyplugin.deletemsg.enable]]<dd>

Specifies whether DeleteMsg events will generate a notification to
ENS. DELETED: Use
<code>local.store.notifyplugin.*.deletemsg.enable</code> instead.
Syntax: bool
<dt>[[enseventkey Option|local.store.notifyplugin.enseventkey]]<dd>

Event key to use for ENS notifications. DELETED: USE
<code>local.store.notifyplugin.*.enseventkey</code> instead.
Syntax: non-empty-string
<dt>[[enshost Option|local.store.notifyplugin.enshost]]<dd>

The IP address or hostname of the ENS server. DELETED: Use
<code>local.store.notifyplugin.*.enshost</code> instead.
Syntax: non-empty-string
<dt>[[ensport Option|local.store.notifyplugin.ensport]]<dd>

The TCP port number of the ENS server. DELETED: Use
<code>local.store.notifyplugin.*.ensport</code> instead.
Syntax: uint16
<dt>[[expungeheaders Option|local.store.notifyplugin.expungeheaders]]<dd>

If set to 1, then message headers will be included in DeleteMsg
notifications. <code>local.store.notifyplugin.*.maxheadersize</code>
must also be non-zero. DELETED: Never used.
Syntax: boolDefault: <code>0</code>
<dt>[[jdebuglevel Option|local.store.notifyplugin.jdebuglevel]]<dd>

Level of debugging messages for JMQ notification plugin. DELETED: Use
<code>local.store.notifyplugin.*.debuglevel</code> instead.
Syntax: int32Default: <code>0</code>
<dt>[[jmaxbodysize Option|local.store.notifyplugin.jmaxbodysize]]<dd>

Specifies the maximum size (in bytes) of the body that will be
transmitted with the notification to JMQ. DELETED: Use
<code>local.store.notifyplugin.*.maxbodysize</code> instead.
Syntax: uint32Default: <code>0</code>
<dt>[[jmaxheadersize Option|local.store.notifyplugin.jmaxheadersize]]<dd>

Specifies the maximum size (in bytes) of the header that will be
transmitted with the notification to JMQ. DELETED: Use
<code>local.store.notifyplugin.*.maxheadersize</code> instead.
Syntax: uint32Default: <code>0</code>
<dt>[[jmqhost Option|local.store.notifyplugin.jmqhost]]<dd>

The hostname of the JMQ broker. DELETED: Use
<code>local.store.notifyplugin.*.jmqhost</code> instead.
Syntax: non-empty-string
<dt>[[jmqport Option|local.store.notifyplugin.jmqport]]<dd>

The port number of the JMQ broker. DELETED: Use
<code>local.store.notifyplugin.*.jmqport</code> instead.
Syntax: uint16
<dt>[[jmqpwd Option|local.store.notifyplugin.jmqpwd]]<dd>

The JMQ user password. DELETED: Use
<code>local.store.notifyplugin.*.jmqpwd</code> instead.
Syntax: password
<dt>[[jmqtopic Option|local.store.notifyplugin.jmqtopic]]<dd>

The topic to which JMQ will publish events. DELETED: Use
<code>local.store.notifyplugin.*.jmqtopic</code> instead.
Syntax: non-empty-string
<dt>[[jmquser Option|local.store.notifyplugin.jmquser]]<dd>

The JMQ username. DELETED: Use
<code>local.store.notifyplugin.*.jmquser</code> instead.
Syntax: non-empty-string
<dt>[[loguser Option|local.store.notifyplugin.loguser.enable]]<dd>

Specifies whether LogUser events will generate a notification to
ENS. DELETED: Use
<code>local.store.notifyplugin.*.loguser.enable</code> instead.
Syntax: bool
<dt>[[maxbodysize Option|local.store.notifyplugin.maxbodysize]]<dd>

Specifies the maximum size (in bytes) of the body that will be
transmitted with the notification to ENS. DELETED: Use
<code>local.store.notifyplugin.*.maxbodysize</code> instead.
Syntax: uint32
<dt>[[maxheadersize Option|local.store.notifyplugin.maxheadersize]]<dd>

Specifies the maximum size (in bytes) of the header that will be
transmitted with the notification to ENS. DELETED: Use
<code>local.store.notifyplugin.*.maxheadersize</code> instead.
Syntax: uint32
<dt>[[msgflags Option|local.store.notifyplugin.msgflags]]<dd>

Enables the msgflag notification mechanism. DELETED: Use
<code>local.store.notifyplugin.*.msgflags.enable</code> instead.
Syntax: bool
<dt>[[newmsg Option|local.store.notifyplugin.newmsg.enable]]<dd>

Specifies whether NewMsg events will generate a notification. DELETED:
Use <code>local.store.notifyplugin.*.newmsg.enable</code> instead.
Syntax: bool
<dt>[[noninbox Option|local.store.notifyplugin.noneinbox.enable]]<dd>

Determines whether all folders generate notifications or if only the
INBOX generates notifications to ENS: 0: only INBOX, 1: all
folders. DELETED: Use
<code>local.store.notifyplugin.*.noneinbox.enable</code> instead.
Syntax: bool
<dt>[[purgemsg Option|local.store.notifyplugin.purgemsg.enable]]<dd>

Specifies whether PurgeMsg events will generate a notification to
ENS. DELETED: Use
<code>local.store.notifyplugin.*.purgemsg.enable</code> instead.
Syntax: bool
<dt>[[readmsg Option|local.store.notifyplugin.readmsg.enable]]<dd>

Specifies whether ReadMsg events will generate a notification to
ENS. DELETED: Use
<code>local.store.notifyplugin.*.readmsg.enable</code> instead.
Syntax: bool
<dt>[[updatemsg Option|local.store.notifyplugin.updatemsg.enable]]<dd>

Specifies whether UpdateMsg events will generate a notification to
ENS. DELETED: Use
<code>local.store.notifyplugin.*.readmsg.enable</code> instead.
Syntax: bool
<dt>[[overquotastatus Option|local.store.overquotastatus]]<dd>

Enable quota enforcement before messages are enqueued in the MTA. This
prevents the MTA queues from filling up. When set, and a user is not
yet over quota, but an incoming message pushes the user over quota,
then the message is delivered, but the <code>mailuserstatus</code>
LDAP attribute is set to <code>overquota</code> so no more messages
will be accepted by the MTA.
Syntax: boolDefault: <code>0</code>
<dt>[[perusersynclevel Option|local.store.perusersynclevel]]<dd>

Synchronization level for store peruser file. 0: no sync, 1: data sync only, 2:
data sync and metadata sync (that is, all file attributes, including
access time and modification time).
Syntax: uint32Default: <code>1</code>
<dt>[[pin Option|local.store.pin]]<dd>

Mailboxes to protect from deletion or modification except by the
Message Store Administrator. The format is as follows:
"mailbox1<code>%</code>mailbox2<code>%</code>mailbox
3", where mailbox1, mailbox2 and mailbox
3 are the mailboxes to be protected (note that spaces can be used
in mailbox names), and <code>%</code> is the separator between each
mailbox.
Syntax: non-empty-string
<dt>[[quotaoverdraft Option|local.store.quotaoverdraft]]<dd>

Used to provide compatibility with systems that migrated from the
Netscape Messaging Server. When set to "on", allow delivery of one
message that puts disk usage over quota. After the user is over quota,
messages are deferred or bounced, the quota warning message is sent,
and the quota grace period timer starts. Treated as "on" if
<code>local.store.overquotastatus</code> is set.
Syntax: boolDefault: <code>0</code>
<dt>[[enable Option|local.store.relinker.enabled]]<dd>

Enables real-time re-linking of messages in the append code, and
<code>stored</code> purge. The <code>relinker</code> command-line tool
may be run even if this option is off, however since
<code>stored</code> will not purge the repository, <code>relinker
-d</code> must be used for this task. Turning this option on affects
message delivery performance in exchange for the disk space savings.
Syntax: boolDefault: <code>0</code>
<dt>[[maxage Option|local.store.relinker.maxage]]<dd>

Maximum age in hours for messages to be kept in the repository, or
considered by the <code>relinker</code> command-line. -1 means no age
limit, that is, only purge orphaned messages from the repository. For
<code>relinker</code> it means process existing messages regardless of
age. Shorter values keep the repository smaller thus allow
<code>relinker</code> or <code>stored</code> purge to run faster and
reclaim disk space faster, while longer values allow duplicate message
re-linking over a longer period of time, for example, when users copy
the same message to the store several days apart, or when running a
migration over several days or weeks.
Syntax: int32Default: <code>24</code>
<dt>[[minsize Option|local.store.relinker.minsize]]<dd>

Minimum size in kilobytes for messages to be considered by run-time or
command-line <code>relinker</code>. Setting a non-zero value gives up
the <code>relinker</code> benefits for smaller messages in exchange
for a smaller repository.
Syntax: uint32Default: <code>0</code>
<dt>[[purgecycle Option|local.store.relinker.purgecycle]]<dd>

Approximate duration in hours of an entire <code>stored</code> purge
cycle. The actual duration depends on the time it takes to scan each
directory in the repository. Smaller values will use more I/O and
larger values will not reclaim disk space as fast. 0 means run purge
continuously without any pause between directories. -1 means don't run
purge in <code>stored</code> (then purge must be performed using the
<code>relinker -d</code> command).
Syntax: uint32Default: <code>24</code>
<dt>[[rollingdbbackup Option|local.store.rollingdbbackup]]<dd>

Controls whether rolling store database backups are made. (yes/no).
''Introduced in release: 7.0''Syntax: non-empty-stringDefault: <code>1</code>
<dt>[[seenckpinterval Option|local.store.seenckpinterval]]<dd>

Set peruser db archive interval (in number of hours). Set to "0" to
disable peruser archiving.
Syntax: uint32Default: <code>6</code>
<dt>[[seenckpstart Option|local.store.seenckpstart]]<dd>

Set initial hour of the peruser db archive after stored starts
running. Allowed values are 0 (midnight) - 23 (11PM). If this variable
is not set, the initial archive starts an hour after stored starts
running.
Syntax: uint32Default: <code>0</code>
<dt>[[sharedfolders Option|local.store.sharedfolders]]<dd>

Enables shared folder listing and namespaces. SELECT and LSUB are not
affected by this option. Users can SELECT their shared folders and use
LSUB to list subscribed shared folders when this option is disabled.
Syntax: boolDefault: <code>1</code>
<dt>[[snapshotdirs Option|local.store.snapshotdirs]]<dd>

Number of separate snapshots to store on disk. Minimum is 2. Recommend
enough to be sure you have a good database back by the time you figure
out the current one is beyond repair.
Syntax: uint16Default: <code>3</code>
<dt>[[snapshotinterval Option|local.store.snapshotinterval]]<dd>

Interval of time between snapshots in minutes. It is recommended that you
perform this procedure at least once a day. DELETED: Removed in Messaging
Server 7.0
Syntax: non-empty-stringDefault: <code>1440</code>
<dt>[[snapshotpath Option|local.store.snapshotpath]]<dd>

Specifies the path in which to copy the <code>mboxlist</code>
directory. Permissions must be set for the message store
owner. Snapshots will be placed in subdirectories.
Syntax: dirpathDefault: <code>dbdata/snapshots</code>
<dt>[[subscribesynclevel Option|local.store.subscribesynclevel]]<dd>

Synchronization level for store subscribe file. 0: no sync, 1: data
sync only, 2: data sync and metadata sync (that is, all file
attributes, including access time and modification time).
Syntax: uint32Default: <code>1</code>
<dt>[[synclevel Option|local.store.synclevel]]<dd>

Default sync level for store files. -1: no default, 0: no sync, 1:
data sync only, 2: data sync and metadata sync (that is, all file
attributes, including access time and modification time).
Syntax: int32Default: <code>-1</code>
<dt>[[supportedlanguages Option|local.supportedlanguages]]<dd>

Languages supported by server code.
Syntax: non-empty-stringDefault: <code>[en,de,fr,es,af,ca,da,nl,fi,gl,ga,is,it,no,pt,sv,eu,sq,cs,hu,pl,ro,hr,sk,sl,et,lv,lt,ru,bg,be,sr,mk,uk,el,tr,ar,he,yi,th,ja,ko,zh-CN,zh-TW]</code>
<dt>[[threadholddelay Option|local.threadholddelay]]<dd>

Set a thread hold delay time (in milliseconds) for IMAP and POP
connections. This is the amount of time that asynchronous read and
write operations will try to keep a worker thread around.
Syntax: uint32Default: <code>75</code>
<dt>[[tmpdir Option|local.tmpdir]]<dd>

Temporary file directory; defaults to $SERVERROOT/data/tmp/.
Syntax: absdirpath
<dt>[[ugldapbasedn Option|local.ugldapbasedn]]<dd>

Root of the user/group configuration tree in the Directory Server.
Syntax: non-empty-string
<dt>[[ugldapbindcred Option|local.ugldapbindcred]]<dd>

Password for the user/group administrator.
Syntax: password
<dt>[[ugldapbinddn Option|local.ugldapbinddn]]<dd>

DN of the user/group administrator.
Syntax: non-empty-string
<dt>[[ugldaphost Option|local.ugldaphost]]<dd>

LDAP server list for user/group lookup. Takes a space-separated
string. If empty or not set, the loopback interface is used.
Syntax: string
<dt>[[ugldappoolsize Option|local.ugldappoolsize]]<dd>

Default LDAP pool size. DELETED: Feature not implemented.
Syntax: int32Default: <code>1</code>
<dt>[[ugldapport Option|local.ugldapport]]<dd>

LDAP port for user/group lookup. As of the mirasol release, if this
is set to 636 then SSL will be used regardless of ugldapusessl setting.
Syntax: uint16Default: <code>389</code>
<dt>[[ugldapusessl Option|local.ugldapusessl]]<dd>

Use SSL to connect to user/group LDAP server.
Syntax: boolDefault: <code>0</code>
<dt>[[enable Option|local.watcher.enable]]<dd>

Enable the Watcher service on <code>start-msg</code>
startup. The watcher service is a daemon that monitors Messaging
Server and restarts services that fail. Refer to
<code>local.autorestart</code> and the Administration Guide for
details.
Syntax: boolDefault: <code>0</code>
<dt>[[port Option|local.watcher.port]]<dd>

<code>watcher</code> listen port.
Syntax: uint16Default: <code>49994</code>
<dt>[[cert_enable Option|local.webmail.cert.enable]]<dd>

Verify certificates against a CRL. When this is set, ensure that the
<code>crlenable</code> parameter in the <code>smime.conf</code> is set
to 1.
Syntax: boolDefault: <code>0</code>
<dt>[[cert_port Option|local.webmail.cert.port]]<dd>

Specifies a port number on the machine where the Messaging Server runs
to use for CRL communication. This port is used locally for that
machine only. The value must be greater than 1024.
Syntax: uint16Default: <code>55443</code>
<dt>[[da_host Option|local.webmail.da.host]]<dd>

The iPlanet Delegated Administrator 1.x hostname. Initially set to
value of <code>local.hostname</code>. This parameter is available for
backwards compatibility only, and should no longer be used.
Syntax: non-empty-string
<dt>[[da_port Option|local.webmail.da.port]]<dd>

The iPlanet Delegated Administrator 1.x port. This parameter is
available for backwards compatibility only, and should no longer be
used.
Syntax: uint16Default: <code>8080</code>
<dt>[[port Option|local.webmail.sieve.port]]<dd>

The port of the web container where the Mail Filter has been deployed.
Syntax: uint16
<dt>[[sslport Option|local.webmail.sieve.sslport]]<dd>

The SSL port of the web container where the Mail Filter has been deployed.
Syntax: uint16
<dt>[[crldfromto Option|local.webmail.smime.crldfromto]]<dd>

If not set to 0, this value will override the value of
<code>local.webmail.cert.port</code>.DELETED: Useless option.
Syntax: int32Default: <code>0</code>
<dt>[[enable Option|local.webmail.smime.enable]]<dd>

Controls whether the S/MIME features are available to Web Client Mail
users who have permission to use them.
Syntax: boolDefault: <code>0</code>
<dt>[[amauthcertificatealias Option|local.webmail.sso.amauthcertificatealias]]<dd>

The nickname of the client certificate in the certificate file
database. DELETED: Unused.
Syntax: non-empty-string
<dt>[[amcertdbpassword Option|local.webmail.sso.amcertdbpassword]]<dd>

Password for the certificate key database file. DELETED: Unused.
Syntax: password
<dt>[[amcookiename Option|local.webmail.sso.amcookiename]]<dd>

Access Manager cookie name. By default Access Manager saves its
session handle in a cookie called <code>iPlanetDirectoryPro</code>. If
Access Manager is configured to use another cookie name, then that
name needs to be configured in Messaging Server as
<code>local.webmail.sso.amcookiename</code> so that Messaging Server
knows what to look for when doing single-sign on. Default value must
not be changed if Access Manager has default configuration. DELETED:
Unused.
Syntax: non-empty-stringDefault: <code>iPlanetDirectoryPro</code>
<dt>[[amloginhack Option|local.webmail.sso.amloginhack]]<dd>

Enable testing with a DS other than Access Manager. DELETED: Unused.
Syntax: boolDefault: <code>0</code>
<dt>[[amloglevel Option|local.webmail.sso.amloglevel]]<dd>

AMSDK logging level. The SSO library used by Messaging Server has its
own logging mechanism separate from Messaging Server. Its messages are
logged in a file called <code>http_sso</code> under
<code>msg-svr-base/log</code>. By default only messages with info (3)
or higher are logged, but it is possible to increase the logging level
by setting the logging level to a value from 1 to 5 (1: errors, 2:
warnings, 3: info, 4: debug, 5: maxdebug). Be aware that the library
doesn't have the same notion of message importances as Messaging
Server and that setting the level to debug (4) can result in a lot of
meaningless data. Also the <code>http_sso</code> log file is not
managed by common Messaging Server logging code and is never cleaned
up or rolled over. It is the responsibility of the system
administrator to clean it up when setting the log level higher than
the default. DELETED: Unused.
Syntax: int32Default: <code>3</code>
<dt>[[ammsgserverurl Option|local.webmail.sso.ammsgserverurl]]<dd>

The URL to which <code>/am_listener</code> should be appended to
construct the Access Manager notification URL. DELETED: Unused.
Syntax: url
<dt>[[amnamingurl Option|local.webmail.sso.amnamingurl]]<dd>

The URL where Access Manager runs the naming service. Mandatory
variable for single sign-on through Access Manager. Typically this URL
is <code>http://[server]:[port]/amserver/namingservice</code>. DELETED:
Unused.
Syntax: url
<dt>[[amtrustservercerts Option|local.webmail.sso.amtrustservercerts]]<dd>

Whether to trust SSL certificates not in the client certificate file
database. DELETED: Unused.
Syntax: boolDefault: <code>0</code>
<dt>[[cookiedomain Option|local.webmail.sso.cookiedomain]]<dd>

This is a trusted circle SSO (legacy) parameter. The string value of
this parameter is used to set the cookie domain value of all SSO
cookies set by the Messenger Express HTTP server. This domain must
match the DNS domain used by the Messenger Express browser to access
the server. It is not the hosted domain name. This value must start
with a period.
Syntax: non-empty-string
<dt>[[sso_enable Option|local.webmail.sso.enable]]<dd>

Enable (legacy) trusted circle single sign on functions, including
accepting and verifying SSO cookies presented by the client when the
login page is fetched. It returns an SSO cookie to the client for a
successful login and responds to requests from other SSO partners to
verify its own cookies. Set this to zero to disable trusted circle
SSO.
Syntax: boolDefault: <code>0</code>
<dt>[[sso_id Option|local.webmail.sso.id]]<dd>

This is a trusted circle SSO (legacy) parameter. The string value of
this parameter is used as the application ID value when formatting SSO
cookies set by the Messenger Express HTTP server. The default value is
null. This is an arbitrary string. Its value must match what you
specify for the Delegated Administrator in its
<code>resource.properties</code> file. The corresponding entry in
<code>resource.properties</code> would be:
<code>Verificationurl-XXX-YYY =
http://webmailhost:webmailport/VerifySSO?</code> Where
<code>XXX</code> is the <code>local.webmail.sso.prefix</code> value
set above, and <code>YYY</code> is the value of
<code>local.webmail.sso.id</code> set here.
Syntax: non-empty-string
<dt>[[sso_prefix Option|local.webmail.sso.prefix]]<dd>

This is a trusted circle SSO (legacy) parameter. It specifies the
prefix value when formatting SSO cookies set by the webmail
server. Only SSO cookies with this prefix value are recognized by the
server; all other SSO cookies are ignored.
Syntax: non-empty-string
<dt>[[singlesignoff Option|local.webmail.sso.singlesignoff]]<dd>

This parameter is used by trusted circle SSO (legacy). When this
parameter is set, the server will remove all single sign-on cookies
for the user matching the value of
<code>local.webmail.sso.prefix</code>. If set to 0 in this context,
the server removes only its single sign-on user cookie.
Syntax: boolDefault: <code>1</code>
<dt>[[uwccontexturi Option|local.webmail.sso.uwccontexturi]]<dd>

Specifies the path in which Communications Express is
deployed. Specify this parameter only when Communications Express is
not deployed under <code>/</code>. For example, if Communications
Express is deployed in <code>/uwc</code>,
<code>local.webmail.sso.uwccontexturi=uwc</code>.
Syntax: non-empty-string
<dt>[[uwcenabled Option|local.webmail.sso.uwcenabled]]<dd>

Enables (when set to 1) or disables (when set to 0) Communications
Express access to Messenger Express. When enabled, the session ID
will be passed in a cookie with the name of the value of
<code>local.service.http.cookiename</code> (if set) or
<code>webmailsid</code> if <code>local.service.http.cookiename</code>
is not set. Both <code>local.webmail.sso.uwcenabled</code> and
<code>local.service.http.cookiename</code> must match on the front and
back ends.
Syntax: int32Default: <code>0</code>
<dt>[[uwchome Option|local.webmail.sso.uwchome]]<dd>

Specifies the URL required to access the home link.
Syntax: non-empty-string
<dt>[[uwclogouturl Option|local.webmail.sso.uwclogouturl]]<dd>

Specifies the URL Messenger Express uses to invalidate the Communications
Express session.
Syntax: url
<dt>[[uwcport Option|local.webmail.sso.uwcport]]<dd>

Specifies the Communications Express port.
Syntax: uint16Default: <code>80</code>
<dt>[[uwcsslport Option|local.webmail.sso.uwcsslport]]<dd>

Specifies the Communications Express SSL port.
Syntax: uint16Default: <code>443</code>
<dt>[[buffersize Option|logfile.*.buffersize]]<dd>

Size of log buffers in bytes. DELETED: Never used.
Syntax: uint32Default: <code>0</code>
<dt>[[expirytime Option|logfile.*.expirytime]]<dd>

Maximum time in seconds a log file is kept.
Syntax: uint32Default: <code>604800</code>
<dt>[[filemode Option|logfile.*.filemode]]<dd>

File mode used to create log files in octal. This will be masked with
octal 0666 and the process umask to set actual log file permissions.
If you want a process with a different userid but in the same group
as the Messaging Server user to have read access to log files, use
0640.
''Introduced in release: 7 Update 4''Syntax: uoctalDefault: <code>0600</code>
<dt>[[flushinterval Option|logfile.*.flushinterval]]<dd>

Time interval in seconds between logfile buffer flushes.
Syntax: uint32Default: <code>60</code>
<dt>[[logdir Option|logfile.*.logdir]]<dd>

Directory path for log files. If this is not specified, log files
will be placed in the <code>msg-install-path/data/log</code>
directory.


For the MTA, this option is only used by Message Store insertion tasks
Directory path to the imta log file used for Message Store insertion
(ims_master, LMTP). It is not used by other parts of the
MTA which always log to the default location. The default location is
<code>msg-install-path/data/log</code>. Changing that path to a
soft-link is supported.
Syntax: dirpath
<dt>[[loglevel Option|logfile.*.loglevel]]<dd>

Logging level: nolog, emergency, alert, critical, error, warning,
notice, information, or debug. This is ignored by the dispatcher and
job_controller unless the [[#use_nslog|use_nslog]] option is
set for them, and ignored by the MMP
if [[#use_nslog|use_nslog]] is set to 0.
Syntax: enumstrcaseDefault: <code>notice</code>
<dt>[[logtype Option|logfile.*.logtype]]<dd>

Never used. DELETED: Use <code>syslogfacility</code> instead.
Syntax: non-empty-stringDefault: <code>NscpLog</code>
<dt>[[maxlogfiles Option|logfile.*.maxlogfiles]]<dd>

Maximum number of log files to retain.
Syntax: uint32Default: <code>10</code>
<dt>[[maxlogfilesize Option|logfile.*.maxlogfilesize]]<dd>

Maximum size in bytes of each log file. In the Mirasol release, the default
value was increased to keep more historical data. In previous versions, the
default value was 2097152 (2MB).
Syntax: uint32Default: <code>20971520</code>
<dt>[[maxlogsize Option|logfile.*.maxlogsize]]<dd>

Maximum total size in bytes of all log files. In the Mirasol release, the default
value was increased to keep more historical data. In previous versions, the
default value was 20971520 (20MB).
Syntax: uint64Default: <code>209715200</code>
<dt>[[minfreediskspace Option|logfile.*.minfreediskspace]]<dd>

DELETED: Unimplemented feature. Minimum amount of free disk space in
bytes that must be available for logging.
Syntax: uint32Default: <code>5242880</code>
<dt>[[rollovertime Option|logfile.*.rollovertime]]<dd>

The length of time in seconds to keep a log file active. That is, the
maximum period of time to record data to a single log file.
Syntax: uint32Default: <code>86400</code>
<dt>[[syslogfacility Option|logfile.*.syslogfacility]]<dd>

Specifies whether or not logging is directed to the syslog
service. The values can be none, user, mail, daemon, or local0 to
local7. If the value is set, messages are logged to the syslog
facility corresponding to the set value and all other log file
service options are ignored. The special value of none disables use
of the syslog service.
Syntax: non-empty-stringDefault: <code>none</code>
<dt>[[loglevel Option|logfile.imta.loglevel]]<dd>

Specify an MTA log level used for the imta log file (primarily used by
ims_master). One of nolog, emergency, alert, critical, error, warning,
notice, information, or debug.
Syntax: enumstrcaseDefault: <code>notice</code>
<dt>[[backlog Option|metermaid.config.backlog]]<dd>

The number of connections to permit to be established in the TCP listen queue.
Syntax: uint32Default: <code>5</code>
<dt>[[listenaddr Option|metermaid.config.listenaddr]]<dd>

The IPv4 address on which MeterMaid should listen. If unset, defaults to the
value of <code>service.listenaddr</code>.


The allowed values for this option include an IPv4 address in dotted decimal
form (e.g., 127.0.0.1), or a short form or fully-qualified DNS host name which
will be resolved to an IPv4 address by obtaining the DNS A record for the
name. To explicitly specify the default value of binding to all available
interfaces, the string "INADDR_ANY" may be used. To bind to the loopback
device, 127.0.0.1, the string "localhost" may be specified.
Syntax: interface-addressDefault: <code>INADDR_ANY</code>
<dt>[[maxthreads Option|metermaid.config.maxthreads]]<dd>

Maximum number of work threads.
Syntax: uint32Default: <code>10</code>
<dt>[[port Option|metermaid.config.port]]<dd>

TCP port number on which MeterMaid listens for connections.
Syntax: uint16Default: <code>63837</code>
<dt>[[secret Option|metermaid.config.secret]]<dd>

Secret used to authenticate MeterMaid clients with the server.
Syntax: password
<dt>[[server_host Option|metermaid.config.serverhost]]<dd>

Host or IP address of the MeterMaid server to use.
Syntax: host
<dt>[[connectfrequency Option|metermaid.mtaclient.connectfrequency]]<dd>

Attempt a connection every connectfrequency seconds.
Syntax: uint32
<dt>[[connecttimeout Option|metermaid.mtaclient.connectwait]]<dd>

How long a thread should wait for a connection to be established to
Metermaid (seconds).
Syntax: uint32Default: <code>5</code>
<dt>[[debug Option|metermaid.mtaclient.debug]]<dd>

Enables debug output from the MTA client into SMTP log files.
Syntax: int32Default: <code>0</code>
<dt>[[max_conns Option|metermaid.mtaclient.maxconns]]<dd>

How many concurrent connections can be established to MeterMaid from a
single process.
Syntax: uint32Default: <code>3</code>
<dt>[[timeout Option|metermaid.mtaclient.readwait]]<dd>

How long in seconds to wait for communication with MeterMaid.
Syntax: uint32Default: <code>10</code>
<dt>[[block_time Option|metermaid.table.*.block_time]]<dd>

The initial period for greylisting during which requests will be
blocked.
''Introduced in release: 7 Update 4''Syntax: non-empty-stringDefault: <code>pt5m</code>
<dt>[[data_type Option|metermaid.table.*.data_type]]<dd>

Type of data to be stored in this table; one of <code>ipv4</code> or
<code>string</code>.
Syntax: non-empty-stringDefault: <code>string</code>
<dt>[[inactivity_time Option|metermaid.table.*.inactivity_time]]<dd>

The period for greylisting during which a resubmitted entry will
remain 'known' to MeterMaid.
''Introduced in release: 7 Update 4''Syntax: non-empty-stringDefault: <code>p7d</code>
<dt>[[max_entries Option|metermaid.table.*.max_entries]]<dd>

Maximum number of entries to maintain in this table.
Syntax: uint32Default: <code>1000</code>
<dt>[[table_options Option|metermaid.table.*.options]]<dd>

Space-separated list of options for this table; can include
<code>penalize</code> or <code>nocase</code> (for string data).
Syntax: printable-ascii-string-list
<dt>[[quota Option|metermaid.table.*.quota]]<dd>

Number of connections to permit per quota_time.
Syntax: uint32Default: <code>100</code>
<dt>[[quota_time Option|metermaid.table.*.quota_time]]<dd>

Number of seconds to allow quota.
Syntax: non-empty-stringDefault: <code>1m</code>
<dt>[[resubmit_time Option|metermaid.table.*.resubmit_time]]<dd>

The period for greylisting during which a request must be received
again in order to be permitted in the future.
''Introduced in release: 7 Update 4''Syntax: non-empty-stringDefault: <code>pt4h</code>
<dt>[[storage Option|metermaid.table.*.storage]]<dd>

Method of data storage for this table; one of <code>hash</code> or
<code>splay</code>.
Syntax: non-empty-stringDefault: <code>hash</code>
<dt>[[table_type Option|metermaid.table.*.type]]<dd>

The type of table; choose between <code>throttle</code> or
<code>simple</code>.
Syntax: non-empty-stringDefault: <code>throttle</code>
<dt>[[value_type Option|metermaid.table.*.value_type]]<dd>

When using a 'simple' table, this specifies the kind of data used for
the values in this table. Currently one may choose between
<code>integer</code> or <code>string</code>.
''Introduced in release: 7 Update 1''Syntax: non-empty-stringDefault: <code>integer</code>
<dt>[[nsclassname Option|nsclassname]]<dd>

Reference to Java class for Messaging Server panels for Administration
Server. DELETED: No longer relevant with Administration Server
obsolete (as of Messaging Server 6.3).
Syntax: non-empty-string
<dt>[[command Option|pipeprograms.*.path]]<dd>

Program delivery path specification.
Syntax: filepath
<dt>[[params Option|pipeprograms.*.pipeparams]]<dd>

Program delivery arguments.
Syntax: non-empty-string
<dt>[[perms Option|pipeprograms.*.pipeperm]]<dd>

Program delivery execution option.
Syntax: non-empty-string
<dt>[[connectfrequency Option|pmxbl.connectfrequency]]<dd>

Attempt a connection to the PureMessage IP Blocker service every
connectfrequency seconds.
Syntax: uint32
<dt>[[connecttimeout Option|pmxbl.connectwait]]<dd>

How long a probe attempt for the PureMessage IP Blocker service should
wait for a connection to the server be established.
Syntax: uint32
<dt>[[max_conns Option|pmxbl.maxconns]]<dd>

How many concurrent connections can be established to the PureMessage
IP Blocker service from a single process.
Syntax: uint32Default: <code>3</code>
<dt>[[port Option|pmxbl.port]]<dd>

TCP port number on which the PureMessage IP Blocker service is
running.
Syntax: uint16Default: <code>4466</code>
<dt>[[timeout Option|pmxbl.readwait]]<dd>

How long in seconds to wait for communication with the PureMessage IP
Blocker service.
Syntax: uint32Default: <code>10</code>
<dt>[[server_host Option|pmxbl.serverhost]]<dd>

Host where the PureMessage IP Blocker service is running.
Syntax: hostDefault: <code>localhost</code>
<dt>[[policystoremodule Option|policy.store.module]]<dd>

Policy store module name.
Syntax: non-empty-stringDefault: <code>policy_store_ldap</code>
<dt>[[presencestoremodule Option|presence.store.module]]<dd>

Presence store module name.
Syntax: non-empty-stringDefault: <code>presence_store_simple</code>
<dt>[[pubsubstoremodule Option|pubsub.store.module]]<dd>

Pubsub store module name.
Syntax: non-empty-stringDefault: <code>pubsub_store_simple</code>
<dt>[[authenticationldapattributes Option|sasl.default.authenticationldapattributes]]<dd>

A space-separated list of additional LDAP user attributes to look up
and pass to the third-party authentication server. To enable support
for a third-party authentication server, set the authenticationserver
option. For developer instructions and SDK see the directory
msg_svr_base/examples/tpauth.
''Introduced in release: 7 Update 4 patch 22.01''Syntax: name-list
<dt>[[auto_transition Option|sasl.default.auto_transition]]<dd>

When set and a user provides a plain text password, the password
storage format will be transitioned to the default password storage
method for the directory server. This can be used to migrate from
plaintext passwords to APOP or CRAM-MD5.
Syntax: boolDefault: <code>0</code>
<dt>[[auxprop_plugin Option|sasl.default.auxprop_plugin]]<dd>

Do not use. Never supported. Removed in 7 update 4. DELETED: Use
<code>sasl.default.authenticationserver</code> instead.
Syntax: non-empty-string
<dt>[[canon_user_plugin Option|sasl.default.canon_user_plugin]]<dd>

Do not use. Never supported. Removed in 7 update 4. DELETED: Use
<code>sasl.default.authenticationserver</code> instead.
Syntax: non-empty-string
<dt>[[usedomainmap Option|sasl.default.ldap.domainmap]]<dd>

Look up domains prior to locating users when performing authentication. If
disabled, then search the entire user/group subtree when authenticating a user.
Syntax: boolDefault: <code>1</code>
<dt>[[has_plain_passwords Option|sasl.default.ldap.has_plain_passwords]]<dd>

Boolean to indicate directory stores plaintext passwords which enables
APOP and CRAM-MD5.
Syntax: boolDefault: <code>0</code>
<dt>[[searchfilter Option|sasl.default.ldap.searchfilter]]<dd>

This is the default search filter used to look up users for basic
authentication and identity purposes when one is not specified in
the <code>inetDomainSearchFilter</code> for the domain. The syntax is
the same as <code>inetDomainSearchFilter</code> (see schema guide).
Syntax: non-empty-stringDefault: <code>(&(uid=%U)(objectclass=inetmailuser))</code>
<dt>[[searchfordomain Option|sasl.default.ldap.searchfordomain]]<dd>

By default, the authentication system looks up the domain in LDAP
following the rules for domain lookup then looks up the user. However,
if this option is set to "0" rather than the default value of "1", then
the domain lookup does not happen and a search for the user (using the
<code>sasl.default.ldap.searchfilter</code>) occurs directly under the
LDAP tree specified by <code>local.ugldapbasedn</code>. This is
provided for compatibility with legacy single-domain schemas, but use
is not recommended for new deployments as even a small company may go
through a merger or name change which requires support for multiple
domains.
Syntax: boolDefault: <code>1</code>
<dt>[[log_level Option|sasl.default.log_level]]<dd>

Do not use. Removed in 7 update 4. DELETED: Use <code>debugkeys</code>
instead.
Syntax: int32Default: <code>1</code>
<dt>[[mech_list Option|sasl.default.mech_list]]<dd>

A space-separated list of SASL mechanisms to enable. If non-empty,
this overrides the <code>sasl.default.ldap.has_plain_passwords</code>
option as well as the <code>service.imap.allowanonymouslogin</code>
option. This option applies to all protocols (IMAP, POP,
SMTP). Removed in 7 update 4. DELETED:
Use <code>sasl.default.ldap.has_plain_passwords</code>
or <code>sasl.default.authenticationserver</code> instead.
Syntax: non-empty-string
<dt>[[plugin_list Option|sasl.default.plugin_list]]<dd>

Do not use. Never supported. Removed in 7 update 4. DELETED: Use
<code>sasl.default.authenticationserver</code> instead.
Syntax: non-empty-string
<dt>[[pwcheck_method Option|sasl.default.pwcheck_method]]<dd>

Other values will break server. Removed in 7 update 4. DELETED: Use
<code>sasl.default.authenticationserver</code> instead.
Syntax: non-empty-stringDefault: <code>auxprop</code>
<dt>[[requireauthenticationserver Option|sasl.default.requireauthenticationserver]]<dd>

When an authentication server is configured using the
authenticationserver option, and requireauthenticationserver is 1 (the
default) that server must be running and responding to requests or
authentication will not succeed. If requireauthenticationserver is set
to 0, then built-in authentication mechanisms will be permitted even
if the authentication server ceases to respond to requests.
Syntax: bool
<dt>[[server_load_mech_list Option|sasl.default.server_load_mech_list]]<dd>

Deprecated, never documented. List of SASL mechanisms to load at process
startup. DELETED: Use <code>sasl.default.authenticationserver</code> instead.
Syntax: non-empty-string
<dt>[[transition_criteria Option|sasl.default.transition_criteria]]<dd>

No longer supported or used. See sasl.default.auto_transition. DELETED: Use
<code>sasl.default.auto_transition</code> instead.
Syntax: non-empty-string
<dt>[[authcachesize Option|service.authcachesize]]<dd>

The maximum number of concurrent users/entries in the cache.


The Messaging Server can cache the results of LDAP user lookups and
successful authentication (e.g., when logging into IMAP, POP or
SMTP). The <code>authcachesize</code> option defines the number of
authentication user cache entries. A higher setting for
<code>authcachesize</code> improves performance while using more memory. A lower
setting reduces performance and reduces the amount of memory used.
The MMP legacy configuration presently uses the LdapCacheSize option
for this purpose.
Syntax: uint32Default: <code>10000</code>
<dt>[[authcachettl Option|service.authcachettl]]<dd>

The length of time in seconds an authentication cache entry will
remain valid. Set to 0 to disable authentication caching.
Syntax: uint32Default: <code>900</code>
<dt>[[dcroot Option|service.dcroot]]<dd>

Root of DC tree in Directory Server.
Syntax: non-empty-string
<dt>[[defaultdomain Option|service.defaultdomain]]<dd>

Messaging Server default domain. This is used to determine whether a
domain is the default domain or a hosted domain.
Syntax: domain
<dt>[[dnsresolveclient Option|service.dnsresolveclient]]<dd>

Sets whether or not to reverse name lookup client host.
Syntax: boolDefault: <code>0</code>
<dt>[[domainallowed Option|service.ens.domainallowed]]<dd>

Access filters specifying which domains and/or IP addresses are
allowed ENS access.
''Introduced in release: 7 Update 4''Syntax: non-empty-string
<dt>[[domainnotallowed Option|service.ens.domainnotallowed]]<dd>

Access filters specifying which domains and/or IP addresses are not
allowed ENS access.
''Introduced in release: 7 Update 4''Syntax: non-empty-string
<dt>[[experimentalldapmemcache Option|service.experimentalldapmemcache]]<dd>

Enable/disable experimental LDAP SDK memcache feature (not recommended).
DELETED: New authentication support makes this obsolete.
Syntax: boolDefault: <code>0</code>
<dt>[[notspam Option|service.feedback.notspam]]<dd>

Email address where to send reports of not-spam mail.
Syntax: non-empty-string
<dt>[[spam Option|service.feedback.spam]]<dd>

Email address where to send reports of spam mail.
Syntax: non-empty-string
<dt>[[allowanonymouslogin Option|service.http.allowanonymouslogin]]<dd>

This enables the SASL ANONYMOUS mechanism for mshttpd.
Syntax: boolDefault: <code>0</code>
<dt>[[connlimits Option|service.http.connlimits]]<dd>

Maximum number of connections per IP address for the selected
server. The syntax is: "realm1,realm2,..." where a realm has the form
of address ranges and maximum number of connections expressed as any of
the following four forms:
<table>
<tr>
<th colspan="2">a.b.c.d|e.f.g.h:m</th>
<th>IPv4 address, netmask, connection max</th>
</tr>
<tr>
<td> </td>
<td>a.b.c.d</td><td>IPv4 address</td>
</tr>
<tr>
<td> </td>
<td>e.f.g.h</td><td>network mask</td>
</tr>
<tr>
<td> </td>
<td>m</td><td>maximum connection count</td>
</tr>
<tr>
<th colspan="2">a.b.c.d/p:m</th>
<th>IPv4 address, routing prefix, connection max</th>
</tr>
<tr>
<td> </td>
<td>a.b.c.d</td><td>IPv4 address</td>
</tr>
<tr>
<td> </td>
<td>p</td><td>routing prefix</td>
</tr>
<tr>
<td> </td>
<td>m</td><td>maximum connection count</td>
</tr>
<tr>
<th colspan="2">a.b.c.d|e.f.g.h:m</th>
<th>IPv4 address, netmask, connection max</th>
</tr>
<tr>
<td> </td>
<td>a.b.c.d</td><td>IPv4 address</td>
</tr>
<tr>
<td> </td>
<td>e.f.g.h</td><td>network mask</td>
</tr>
<tr>
<td> </td>
<td>m</td><td>maximum connection count</td>
</tr>
<tr>
<th colspan="2">[a/p]:m</th>
<th>IPv6 address, routing prefix, connection max</th>
</tr>
<tr>
<td> </td>
<td>a</td><td>IPv6 address; compressed "::" format allowed</td>
</tr>
<tr>
<td> </td>
<td>p</td><td>routing prefix</td>
</tr>
<tr>
<td> </td>
<td>m</td><td>maximum connection count</td>
</tr>
<tr>
<th colspan="2">a.b.c.d|e.f.g.h:m</th>
<th>IPv4 address, netmask, connection max</th>
</tr>
<tr>
<td> </td>
<td>a.b.c.d</td><td>IPv4 address</td>
</tr>
<tr>
<td> </td>
<td>e.f.g.h</td><td>network mask</td>
</tr>
<tr>
<td> </td>
<td>m</td><td>maximum connection count</td>
</tr>
<tr>
<th colspan="2">:m</th>
<th>Match any address</th>
</tr>
<tr>
<td> </td>
<td>m</td><td>maximum connection count</td>
</tr>
</table>

There should be at least one realm of the form ":m" to cover the default case
by matching any IPv4 or IPv6 address. To match only IPv4 addresses, use
"0.0.0.0/0:m" or "0.0.0.0|0.0.0.0:m". And to match only IPv6 addresses, use
"[::0/0]:m".
Syntax: non-empty-string
<dt>[[domainallowed Option|service.http.domainallowed]]<dd>

Access filters specifying which domains and/or IP addresses are
allowed HTTP access.
Syntax: non-empty-string
<dt>[[domainnotallowed Option|service.http.domainnotallowed]]<dd>

Access filters specifying which domains and/or IP addresses are not
allowed HTTP access.
Syntax: non-empty-string
<dt>[[enable Option|service.http.enable]]<dd>

Enable the HTTP service on <code>start-msg</code> startup (note:
HTTP over SSL service is enabled/disabled separately using
<code>service.http.enablesslport</code>).
Syntax: boolDefault: <code>0</code>
<dt>[[enablesslport Option|service.http.enablesslport]]<dd>

Sets whether or not the HTTP over SSL service is started. If both
<code>service.http.enable</code> and
<code>service.http.enablesslport</code> are turned off, then
<code>stored</code> does not try to monitor http.
Syntax: boolDefault: <code>0</code>
<dt>[[extrauserldapattrs Option|service.http.extrauserldapattrs]]<dd>

Extra LDAP attributes returned to client (for customization). Syntax:
attrname[:w][,attrname]... (:w if read-write attribute).
Syntax: non-empty-string
<dt>[[fullfromheader Option|service.http.fullfromheader]]<dd>

If set, use the cn and mail attributes from the user's LDAP entry to
build the "From:" header for outgoing messages. If not set, expect the
MTA to rewrite the "From:" header.
Syntax: boolDefault: <code>1</code>
<dt>[[af Option|service.http.httpcharset.af]]<dd>

Default http character set for Afrikaans.
Syntax: non-empty-stringDefault: <code>utf-8</code>
<dt>[[ar Option|service.http.httpcharset.ar]]<dd>

Default http character set for Arabic.
Syntax: non-empty-stringDefault: <code>utf-8</code>
<dt>[[be Option|service.http.httpcharset.be]]<dd>

Default http character set for Byelorussian.
Syntax: non-empty-stringDefault: <code>utf-8</code>
<dt>[[bg Option|service.http.httpcharset.bg]]<dd>

Default http character set for Bulgarian.
Syntax: non-empty-stringDefault: <code>utf-8</code>
<dt>[[ca Option|service.http.httpcharset.ca]]<dd>

Default http character set for Catalan.
Syntax: non-empty-stringDefault: <code>utf-8</code>
<dt>[[cs Option|service.http.httpcharset.cs]]<dd>

Default http character set for Czech.
Syntax: non-empty-stringDefault: <code>utf-8</code>
<dt>[[da Option|service.http.httpcharset.da]]<dd>

Default http character set for Danish.
Syntax: non-empty-stringDefault: <code>utf-8</code>
<dt>[[de Option|service.http.httpcharset.de]]<dd>

Default http character set for German.
Syntax: non-empty-stringDefault: <code>utf-8</code>
<dt>[[el Option|service.http.httpcharset.el]]<dd>

Default http character set for Greek.
Syntax: non-empty-stringDefault: <code>utf-8</code>
<dt>[[es Option|service.http.httpcharset.es]]<dd>

Default http character set for Spanish.
Syntax: non-empty-stringDefault: <code>utf-8</code>
<dt>[[et Option|service.http.httpcharset.et]]<dd>

Default http character set for Estonian.
Syntax: non-empty-stringDefault: <code>utf-8</code>
<dt>[[eu Option|service.http.httpcharset.eu]]<dd>

Default http character set for Basque.
Syntax: non-empty-stringDefault: <code>utf-8</code>
<dt>[[fi Option|service.http.httpcharset.fi]]<dd>

Default http character set for Finnish.
Syntax: non-empty-stringDefault: <code>utf-8</code>
<dt>[[fr Option|service.http.httpcharset.fr]]<dd>

Default http character set for French.
Syntax: non-empty-stringDefault: <code>utf-8</code>
<dt>[[ga Option|service.http.httpcharset.ga]]<dd>

Default http character set for Irish.
Syntax: non-empty-stringDefault: <code>utf-8</code>
<dt>[[gl Option|service.http.httpcharset.gl]]<dd>

Default http character set for Galician.
Syntax: non-empty-stringDefault: <code>utf-8</code>
<dt>[[he Option|service.http.httpcharset.he]]<dd>

Default http character set for Hebrew.
Syntax: non-empty-stringDefault: <code>utf-8</code>
<dt>[[hr Option|service.http.httpcharset.hr]]<dd>

Default http character set for Croatian.
Syntax: non-empty-stringDefault: <code>utf-8</code>
<dt>[[hu Option|service.http.httpcharset.hu]]<dd>

Default http character set for Hungarian.
Syntax: non-empty-stringDefault: <code>utf-8</code>
<dt>[[is Option|service.http.httpcharset.is]]<dd>

Default http character set for Icelandic.
Syntax: non-empty-stringDefault: <code>utf-8</code>
<dt>[[it Option|service.http.httpcharset.it]]<dd>

Default http character set for Italian.
Syntax: non-empty-stringDefault: <code>utf-8</code>
<dt>[[ja Option|service.http.httpcharset.ja]]<dd>

Default http character set for Japanese.
Syntax: non-empty-stringDefault: <code>utf-8</code>
<dt>[[ko Option|service.http.httpcharset.ko]]<dd>

Default http character set for Korean.
Syntax: non-empty-stringDefault: <code>utf-8</code>
<dt>[[lt Option|service.http.httpcharset.lt]]<dd>

Default http character set for Lithuanian.
Syntax: non-empty-stringDefault: <code>utf-8</code>
<dt>[[lv Option|service.http.httpcharset.lv]]<dd>

Default http character set for Latvian.
Syntax: non-empty-stringDefault: <code>utf-8</code>
<dt>[[mk Option|service.http.httpcharset.mk]]<dd>

Default http character set for Macedonian.
Syntax: non-empty-stringDefault: <code>utf-8</code>
<dt>[[nl Option|service.http.httpcharset.nl]]<dd>

Default http character set for Dutch.
Syntax: non-empty-stringDefault: <code>utf-8</code>
<dt>[[no Option|service.http.httpcharset.no]]<dd>

Default http character set for Norwegian.
Syntax: non-empty-stringDefault: <code>utf-8</code>
<dt>[[pl Option|service.http.httpcharset.pl]]<dd>

Default http character set for Polish.
Syntax: non-empty-stringDefault: <code>utf-8</code>
<dt>[[pt Option|service.http.httpcharset.pt]]<dd>

Default http character set for Portuguese.
Syntax: non-empty-stringDefault: <code>utf-8</code>
<dt>[[ro Option|service.http.httpcharset.ro]]<dd>

Default http character set for Romanian.
Syntax: non-empty-stringDefault: <code>utf-8</code>
<dt>[[ru Option|service.http.httpcharset.ru]]<dd>

Default http character set for Russian.
Syntax: non-empty-stringDefault: <code>utf-8</code>
<dt>[[sk Option|service.http.httpcharset.sk]]<dd>

Default http character set for Slovak.
Syntax: non-empty-stringDefault: <code>utf-8</code>
<dt>[[sl Option|service.http.httpcharset.sl]]<dd>

Default http character set for Slovenian.
Syntax: non-empty-stringDefault: <code>utf-8</code>
<dt>[[sq Option|service.http.httpcharset.sq]]<dd>

Default http character set for Albanian.
Syntax: non-empty-stringDefault: <code>utf-8</code>
<dt>[[sr Option|service.http.httpcharset.sr]]<dd>

Default http character set for Serbian.
Syntax: non-empty-stringDefault: <code>utf-8</code>
<dt>[[sv Option|service.http.httpcharset.sv]]<dd>

Default http character set for Swedish.
Syntax: non-empty-stringDefault: <code>utf-8</code>
<dt>[[th Option|service.http.httpcharset.th]]<dd>

Default http character set for Thai.
Syntax: non-empty-stringDefault: <code>utf-8</code>
<dt>[[tr Option|service.http.httpcharset.tr]]<dd>

Default http character set for Turkish.
Syntax: non-empty-stringDefault: <code>utf-8</code>
<dt>[[uk Option|service.http.httpcharset.uk]]<dd>

Default http character set for Ukrainian.
Syntax: non-empty-stringDefault: <code>utf-8</code>
<dt>[[yi Option|service.http.httpcharset.yi]]<dd>

Default http character set for Yiddish.
Syntax: non-empty-stringDefault: <code>utf-8</code>
<dt>[[zh-cn Option|service.http.httpcharset.zh-cn]]<dd>

Default http character set for Simplified Chinese.
Syntax: non-empty-stringDefault: <code>utf-8</code>
<dt>[[zh-tw Option|service.http.httpcharset.zh-tw]]<dd>

Default http character set for Traditional Chinese.
Syntax: non-empty-stringDefault: <code>utf-8</code>
<dt>[[idletimeout Option|service.http.idletimeout]]<dd>

Timeout, in minutes, for the low-level HTTP connection (which is
different from the webmail session). Lower values will use fewer
socket handles and higher values cause less overhead when the client
needs to recreate the connection.
Syntax: uint32Default: <code>3</code>
<dt>[[ipsecurity Option|service.http.ipsecurity]]<dd>

Sets whether or not to restrict session access to login IP
addresses. If set to yes, when the user logs in, the server remembers
which IP address the user used to log in. Then it only allows that IP
address to use the session cookie it issues to the user.
Syntax: boolDefault: <code>1</code>
<dt>[[ldappoolsize Option|service.http.ldappoolsize]]<dd>

Default LDAP pool size. DELETED: Feature never implemented.
Syntax: int32Default: <code>1</code>
<dt>[[af Option|service.http.mailcharset.af]]<dd>

Default mail character set for Afrikaans.
Syntax: non-empty-stringDefault: <code>iso-8859-1</code>
<dt>[[ar Option|service.http.mailcharset.ar]]<dd>

Default mail character set for Arabic.
Syntax: non-empty-stringDefault: <code>iso-8859-6</code>
<dt>[[be Option|service.http.mailcharset.be]]<dd>

Default mail character set for Byelorussian.
Syntax: non-empty-stringDefault: <code>iso-8859-5</code>
<dt>[[bg Option|service.http.mailcharset.bg]]<dd>

Default mail character set for Bulgarian.
Syntax: non-empty-stringDefault: <code>iso-8859-5</code>
<dt>[[ca Option|service.http.mailcharset.ca]]<dd>

Default mail character set for Catalan.
Syntax: non-empty-stringDefault: <code>iso-8859-1</code>
<dt>[[cs Option|service.http.mailcharset.cs]]<dd>

Default mail character set for Czech.
Syntax: non-empty-stringDefault: <code>iso-8859-2</code>
<dt>[[da Option|service.http.mailcharset.da]]<dd>

Default mail character set for Danish.
Syntax: non-empty-stringDefault: <code>iso-8859-1</code>
<dt>[[de Option|service.http.mailcharset.de]]<dd>

Default mail character set for German.
Syntax: non-empty-stringDefault: <code>iso-8859-1</code>
<dt>[[el Option|service.http.mailcharset.el]]<dd>

Default mail character set for Greek.
Syntax: non-empty-stringDefault: <code>iso-8859-7</code>
<dt>[[es Option|service.http.mailcharset.es]]<dd>

Default mail character set for Spanish.
Syntax: non-empty-stringDefault: <code>iso-8859-1</code>
<dt>[[et Option|service.http.mailcharset.et]]<dd>

Default mail character set for Estonian.
Syntax: non-empty-stringDefault: <code>iso-8859-4</code>
<dt>[[eu Option|service.http.mailcharset.eu]]<dd>

Default mail character set for Basque.
Syntax: non-empty-stringDefault: <code>iso-8859-1</code>
<dt>[[fi Option|service.http.mailcharset.fi]]<dd>

Default mail character set for Finnish.
Syntax: non-empty-stringDefault: <code>iso-8859-1</code>
<dt>[[fr Option|service.http.mailcharset.fr]]<dd>

Default mail character set for French.
Syntax: non-empty-stringDefault: <code>iso-8859-1</code>
<dt>[[ga Option|service.http.mailcharset.ga]]<dd>

Default mail character set for Irish.
Syntax: non-empty-stringDefault: <code>iso-8859-1</code>
<dt>[[gl Option|service.http.mailcharset.gl]]<dd>

Default mail character set for Galician.
Syntax: non-empty-stringDefault: <code>iso-8859-1</code>
<dt>[[he Option|service.http.mailcharset.he]]<dd>

Default mail character set for Hebrew.
Syntax: non-empty-stringDefault: <code>iso-8859-8</code>
<dt>[[hr Option|service.http.mailcharset.hr]]<dd>

Default mail character set for Croatian.
Syntax: non-empty-stringDefault: <code>iso-8859-2</code>
<dt>[[hu Option|service.http.mailcharset.hu]]<dd>

Default mail character set for Hungarian.
Syntax: non-empty-stringDefault: <code>iso-8859-2</code>
<dt>[[is Option|service.http.mailcharset.is]]<dd>

Default mail character set for Icelandic.
Syntax: non-empty-stringDefault: <code>iso-8859-1</code>
<dt>[[it Option|service.http.mailcharset.it]]<dd>

Default mail character set for Italian.
Syntax: non-empty-stringDefault: <code>iso-8859-1</code>
<dt>[[ja Option|service.http.mailcharset.ja]]<dd>

Default mail character set for Japanese.
Syntax: non-empty-stringDefault: <code>iso-2022-jp</code>
<dt>[[ko Option|service.http.mailcharset.ko]]<dd>

Default mail character set for Korean.
Syntax: non-empty-stringDefault: <code>euc-kr</code>
<dt>[[lt Option|service.http.mailcharset.lt]]<dd>

Default mail character set for Lithuanian.
Syntax: non-empty-stringDefault: <code>iso-8859-4</code>
<dt>[[lv Option|service.http.mailcharset.lv]]<dd>

Default mail character set for Latvian.
Syntax: non-empty-stringDefault: <code>iso-8859-4</code>
<dt>[[mk Option|service.http.mailcharset.mk]]<dd>

Default mail character set for Macedonian.
Syntax: non-empty-stringDefault: <code>iso-8859-5</code>
<dt>[[nl Option|service.http.mailcharset.nl]]<dd>

Default mail character set for Dutch.
Syntax: non-empty-stringDefault: <code>iso-8859-1</code>
<dt>[[no Option|service.http.mailcharset.no]]<dd>

Default mail character set for Norwegian.
Syntax: non-empty-stringDefault: <code>iso-8859-1</code>
<dt>[[pl Option|service.http.mailcharset.pl]]<dd>

Default mail character set for Polish.
Syntax: non-empty-stringDefault: <code>iso-8859-2</code>
<dt>[[pt Option|service.http.mailcharset.pt]]<dd>

Default mail character set for Portuguese.
Syntax: non-empty-stringDefault: <code>iso-8859-1</code>
<dt>[[ro Option|service.http.mailcharset.ro]]<dd>

Default mail character set for Romanian.
Syntax: non-empty-stringDefault: <code>iso-8859-2</code>
<dt>[[ru Option|service.http.mailcharset.ru]]<dd>

Default mail character set for Russian.
Syntax: non-empty-stringDefault: <code>iso-8859-5</code>
<dt>[[sk Option|service.http.mailcharset.sk]]<dd>

Default mail character set for Slovak.
Syntax: non-empty-stringDefault: <code>iso-8859-2</code>
<dt>[[sl Option|service.http.mailcharset.sl]]<dd>

Default mail character set for Slovenian.
Syntax: non-empty-stringDefault: <code>iso-8859-2</code>
<dt>[[sq Option|service.http.mailcharset.sq]]<dd>

Default mail character set for Albanian.
Syntax: non-empty-stringDefault: <code>iso-8859-1</code>
<dt>[[sr Option|service.http.mailcharset.sr]]<dd>

Default mail character set for Serbian.
Syntax: non-empty-stringDefault: <code>iso-8859-5</code>
<dt>[[sv Option|service.http.mailcharset.sv]]<dd>

Default mail character set for Swedish.
Syntax: non-empty-stringDefault: <code>iso-8859-1</code>
<dt>[[th Option|service.http.mailcharset.th]]<dd>

Default mail character set for Thai.
Syntax: non-empty-stringDefault: <code>tis-620</code>
<dt>[[tr Option|service.http.mailcharset.tr]]<dd>

Default mail character set for Turkish.
Syntax: non-empty-stringDefault: <code>iso-8859-9</code>
<dt>[[uk Option|service.http.mailcharset.uk]]<dd>

Default mail character set for Ukrainian.
Syntax: non-empty-stringDefault: <code>iso-8859-5</code>
<dt>[[yi Option|service.http.mailcharset.yi]]<dd>

Default mail character set for Yiddish.
Syntax: non-empty-stringDefault: <code>iso-8859-8</code>
<dt>[[zh-cn Option|service.http.mailcharset.zh-cn]]<dd>

Default mail character set for Simplified Chinese.
Syntax: non-empty-stringDefault: <code>gb2312</code>
<dt>[[zh-tw Option|service.http.mailcharset.zh-tw]]<dd>

Default mail character set for Traditional Chinese.
Syntax: non-empty-stringDefault: <code>big5</code>
<dt>[[maxmessagesize Option|service.http.maxmessagesize]]<dd>

Maximum message size client is allowed to send. (Limit imposed by the
SMTP server also applies).
Syntax: uint32Default: <code>5242880</code>
<dt>[[maxpostsize Option|service.http.maxpostsize]]<dd>

Maximum HTTP post content length. If not specified, uses
max(5*1024*1024, <code>service.http.maxmessagesize</code>).
Syntax: uint32
<dt>[[maxsessions Option|service.http.maxsessions]]<dd>

Maximum number of sessions per server process.
Syntax: uint32Default: <code>6000</code>
<dt>[[maxthreads Option|service.http.maxthreads]]<dd>

Maximum number of threads per server process.
Syntax: uint32Default: <code>250</code>
<dt>[[numprocesses Option|service.http.numprocesses]]<dd>

Number of HTTP server processes. Note that the watcher must be
enabled for stop-msg to correctly shut down all processes if this is
set to a value larger than one.
Syntax: uint32Default: <code>1</code>
<dt>[[plaintextmincipher Option|service.http.plaintextmincipher]]<dd>

If this is > 0, then disable use of plaintext passwords unless a
security layer (SSL or TLS) is activated. This forces users to enable
SSL or TLS on their client to login which prevents exposure of their
passwords on the network.
Syntax: int32Default: <code>0</code>
<dt>[[port Option|service.http.port]]<dd>

Messenger Express HTTP port.
Syntax: uint16Default: <code>8990</code>
<dt>[[resourcetimeout Option|service.http.resourcetimeout]]<dd>

Time, in seconds, after which <code>mshttpd</code> flushes cached
session data from memory. Lower values will use less memory and higher
values incur less overhead from resynchronizing from the session
database. For correct session expiration this timeout is never higher
than half the session timeout (<code>mshttpd</code> enforces this).
Syntax: uint32Default: <code>900</code>
<dt>[[sessiontimeout Option|service.http.sessiontimeout]]<dd>

Webmail client session timeout in seconds.
Syntax: uint32Default: <code>7200</code>
<dt>[[smtphost Option|service.http.smtphost]]<dd>

A space-separated list of SMTP relay server hostnames. If not
specified, it will default to the value of
<code>local.hostname</code>. If none of the servers respond, a last
resort attempt will be made to connect to the users mailhost.
Syntax: host-list
<dt>[[smtpport Option|service.http.smtpport]]<dd>

SMTP relay port.
Syntax: uint16Default: <code>25</code>
<dt>[[smtptls Option|service.http.smtptls]]<dd>

Whether to use TLS for SMTP connections.
Syntax: boolDefault: <code>0</code>
<dt>[[sourceurl Option|service.http.sourceurl]]<dd>

URL of webmail server.
Syntax: url
<dt>[[spooldir Option|service.http.spooldir]]<dd>

Attachment spool directory for client outgoing mail; if unspecified, uses the
directory specified in the <code>local.tmpdir</code> option.
Syntax: absdirpath
<dt>[[sslcachesize Option|service.http.sslcachesize]]<dd>

Number of SSL sessions to be cached.
Syntax: uint32Default: <code>0</code>
<dt>[[sslport Option|service.http.sslport]]<dd>

HTTP over SSL port number.
Syntax: uint16Default: <code>8991</code>
<dt>[[sslsourceurl Option|service.http.sslsourceurl]]<dd>

URL of webmail server when SSL is enabled.
Syntax: url
<dt>[[sslusessl Option|service.http.sslusessl]]<dd>

Sets whether or not to enable SSL.
Syntax: boolDefault: <code>0</code>
<dt>[[allowanonymouslogin Option|service.imap.allowanonymouslogin]]<dd>

This enables the SASL ANONYMOUS mechanism for use by IMAP.
Syntax: boolDefault: <code>0</code>
<dt>[[banner Option|service.imap.banner]]<dd>

IMAP protocol welcome banner. One line string, with virtual
parameters: %h=hostname, %p=protocol(ESMTP,POP or IMAP), %P=Product
Name, %v and %V=Version (short or long).
Syntax: non-empty-stringDefault: <code>%h %p service (%P %V)</code>
<dt>[[capability_acl Option|service.imap.capability.acl]]<dd>

Advertise the ACL IMAP extension.
Syntax: boolDefault: <code>1</code>
<dt>[[capability_annotate Option|service.imap.capability.annotate]]<dd>

Advertise the ANNOTATE-EXPERIMENT-1 IMAP extension.
Syntax: boolDefault: <code>1</code>
<dt>[[capability_binary Option|service.imap.capability.binary]]<dd>

Advertise the BINARY IMAP extension.
Syntax: boolDefault: <code>1</code>
<dt>[[capability_catenate Option|service.imap.capability.catenate]]<dd>

Advertise the CATENATE IMAP extension.
Syntax: boolDefault: <code>1</code>
<dt>[[capability_children Option|service.imap.capability.children]]<dd>

Advertise the CHILDREN IMAP extension.
Syntax: boolDefault: <code>1</code>
<dt>[[capability_condstore Option|service.imap.capability.condstore]]<dd>

Advertise the CONDSTORE IMAP extension.
Syntax: boolDefault: <code>1</code>
<dt>[[capability_context_search Option|service.imap.capability.context_search]]<dd>

Advertise the CONTEXT=SEARCH IMAP extension.
Syntax: boolDefault: <code>1</code>
<dt>[[capability_context_sort Option|service.imap.capability.context_sort]]<dd>

Advertise the CONTEXT=SORT IMAP extension.
Syntax: boolDefault: <code>1</code>
<dt>[[capability_enable Option|service.imap.capability.enable]]<dd>

Advertise the ENABLE IMAP extension.
Syntax: boolDefault: <code>1</code>
<dt>[[capability_esearch Option|service.imap.capability.esearch]]<dd>

Advertise the ESEARCH IMAP extension.
Syntax: boolDefault: <code>1</code>
<dt>[[capability_esort Option|service.imap.capability.esort]]<dd>

Advertise the ESORT IMAP extension.
Syntax: boolDefault: <code>1</code>
<dt>[[capability_id Option|service.imap.capability.id]]<dd>

Advertise the IMAP ID extension.
Syntax: boolDefault: <code>1</code>
<dt>[[capability_idle Option|service.imap.capability.idle]]<dd>

Advertise and enable the IDLE IMAP extension.
Syntax: boolDefault: <code>1</code>
<dt>[[capability_imap4 Option|service.imap.capability.imap4]]<dd>

Advertise the IMAP4 capability. The default is yes if
<code>local.obsoleteimap</code> is set.
Syntax: boolDefault: <code>0</code>
<dt>[[capability_imap4rev1 Option|service.imap.capability.imap4rev1]]<dd>

Advertise the IMAP4rev1 capability.
Syntax: boolDefault: <code>1</code>
<dt>[[capability_language Option|service.imap.capability.language]]<dd>

Advertise the LANGUAGE IMAP extension.
Syntax: boolDefault: <code>1</code>
<dt>[[capability_literal Option|service.imap.capability.literal_plus]]<dd>

Advertise the LITERAL+ IMAP extension.
Syntax: boolDefault: <code>1</code>
<dt>[[capability_metadata Option|service.imap.capability.metadata]]<dd>

Advertise the METADATA IMAP extension.
Syntax: boolDefault: <code>1</code>
<dt>[[capability_namespace Option|service.imap.capability.namespace]]<dd>

Advertise the NAMESPACE IMAP extension.
Syntax: boolDefault: <code>1</code>
<dt>[[capability_notify Option|service.imap.capability.notify]]<dd>

Advertise the NOTIFY IMAP extension.
Syntax: boolDefault: <code>0</code>
<dt>[[capability_qresync Option|service.imap.capability.qresync]]<dd>

Advertise the QRESYNC IMAP extension.
Syntax: boolDefault: <code>1</code>
<dt>[[capability_quota Option|service.imap.capability.quota]]<dd>

Advertise the QUOTA IMAP extension.
Syntax: boolDefault: <code>1</code>
<dt>[[capability_sasl_ir Option|service.imap.capability.sasl_ir]]<dd>

Advertise the SASL-IR IMAP extension.
Syntax: boolDefault: <code>1</code>
<dt>[[capability_searchres Option|service.imap.capability.searchres]]<dd>

Advertise the SEARCHRES IMAP extension.
Syntax: boolDefault: <code>1</code>
<dt>[[capability_sort Option|service.imap.capability.sort]]<dd>

Advertise the SORT IMAP extension.
Syntax: boolDefault: <code>1</code>
<dt>[[capability_starttls Option|service.imap.capability.starttls]]<dd>

Advertise the STARTTLS IMAP extension.
Syntax: boolDefault: <code>1</code>
<dt>[[capability_thread_references Option|service.imap.capability.thread_references]]<dd>

Advertise the THREAD=REFERENCES IMAP extension.
Syntax: boolDefault: <code>1</code>
<dt>[[capability_thread_subject Option|service.imap.capability.thread_subject]]<dd>

Advertise the THREAD=ORDEREDSUBJECT IMAP extension.
Syntax: boolDefault: <code>1</code>
<dt>[[capability_uidplus Option|service.imap.capability.uidplus]]<dd>

Advertise the UIDPLUS IMAP extension.
Syntax: boolDefault: <code>1</code>
<dt>[[capability_unselect Option|service.imap.capability.unselect]]<dd>

Advertise the UNSELECT IMAP extension.
Syntax: boolDefault: <code>1</code>
<dt>[[capability_urlauth Option|service.imap.capability.urlauth]]<dd>

Advertise the URLAUTH IMAP extension.
Syntax: boolDefault: <code>1</code>
<dt>[[capability_within Option|service.imap.capability.within]]<dd>

Advertise the WITHIN IMAP extension.
Syntax: boolDefault: <code>1</code>
<dt>[[capability_x_netscape Option|service.imap.capability.x_netscape]]<dd>

Advertise the X-NETSCAPE IMAP extension.
Syntax: boolDefault: <code>0</code>
<dt>[[capability_x_sun_imap Option|service.imap.capability.x_sun_imap]]<dd>

Advertise the X-SUN-IMAP IMAP extension.
Syntax: boolDefault: <code>1</code>
<dt>[[capability_x_sun_sort Option|service.imap.capability.x_sun_sort]]<dd>

Advertise the X-SUN-SORT IMAP extension.
Syntax: boolDefault: <code>1</code>
<dt>[[capability_x_unauthenticate Option|service.imap.capability.x_unauthenticate]]<dd>

Advertise the X-UNAUTHENTICATE IMAP extension.
Syntax: boolDefault: <code>1</code>
<dt>[[capability_xrefresh Option|service.imap.capability.xrefresh]]<dd>

Advertise the XREFRESH IMAP extension.
Syntax: boolDefault: <code>1</code>
<dt>[[capability_xsender Option|service.imap.capability.xsender]]<dd>

Advertise the XSENDER IMAP extension.
Syntax: boolDefault: <code>1</code>
<dt>[[capability_xserverinfo Option|service.imap.capability.xserverinfo]]<dd>

Advertise the XSERVERINFO IMAP extension.
Syntax: boolDefault: <code>0</code>
<dt>[[capability_xum1 Option|service.imap.capability.xum1]]<dd>

Advertise the XUM1 IMAP extension.
Syntax: boolDefault: <code>1</code>
<dt>[[connlimits Option|service.imap.connlimits]]<dd>

Maximum number of connections per IP address for the selected
server. The syntax is: "realm1,realm2,..." where a realm has the form
of address ranges and maximum number of connections expressed as any of
the following four forms:
<table>
<tr>
<th colspan="2">a.b.c.d|e.f.g.h:m</th>
<th>IPv4 address, netmask, connection max</th>
</tr>
<tr>
<td> </td>
<td>a.b.c.d</td><td>IPv4 address</td>
</tr>
<tr>
<td> </td>
<td>e.f.g.h</td><td>network mask</td>
</tr>
<tr>
<td> </td>
<td>m</td><td>maximum connection count</td>
</tr>
<tr>
<th colspan="2">a.b.c.d/p:m</th>
<th>IPv4 address, routing prefix, connection max</th>
</tr>
<tr>
<td> </td>
<td>a.b.c.d</td><td>IPv4 address</td>
</tr>
<tr>
<td> </td>
<td>p</td><td>routing prefix</td>
</tr>
<tr>
<td> </td>
<td>m</td><td>maximum connection count</td>
</tr>
<tr>
<th colspan="2">a.b.c.d|e.f.g.h:m</th>
<th>IPv4 address, netmask, connection max</th>
</tr>
<tr>
<td> </td>
<td>a.b.c.d</td><td>IPv4 address</td>
</tr>
<tr>
<td> </td>
<td>e.f.g.h</td><td>network mask</td>
</tr>
<tr>
<td> </td>
<td>m</td><td>maximum connection count</td>
</tr>
<tr>
<th colspan="2">[a/p]:m</th>
<th>IPv6 address, routing prefix, connection max</th>
</tr>
<tr>
<td> </td>
<td>a</td><td>IPv6 address; compressed "::" format allowed</td>
</tr>
<tr>
<td> </td>
<td>p</td><td>routing prefix</td>
</tr>
<tr>
<td> </td>
<td>m</td><td>maximum connection count</td>
</tr>
<tr>
<th colspan="2">a.b.c.d|e.f.g.h:m</th>
<th>IPv4 address, netmask, connection max</th>
</tr>
<tr>
<td> </td>
<td>a.b.c.d</td><td>IPv4 address</td>
</tr>
<tr>
<td> </td>
<td>e.f.g.h</td><td>network mask</td>
</tr>
<tr>
<td> </td>
<td>m</td><td>maximum connection count</td>
</tr>
<tr>
<th colspan="2">:m</th>
<th>Match any address</th>
</tr>
<tr>
<td> </td>
<td>m</td><td>maximum connection count</td>
</tr>
</table>

There should be at least one realm of the form ":m" to cover the default case
by matching any IPv4 or IPv6 address. To match only IPv4 addresses, use
"0.0.0.0/0:m" or "0.0.0.0|0.0.0.0:m". And to match only IPv6 addresses, use
"[::0/0]:m".
Syntax: non-empty-string
<dt>[[domainallowed Option|service.imap.domainallowed]]<dd>

Access filters specifying which domains and/or IP addresses are
allowed IMAP access.
Syntax: non-empty-string
<dt>[[domainnotallowed Option|service.imap.domainnotallowed]]<dd>

Access filters specifying which domains and/or IP addresses are not
allowed IMAP access.
Syntax: non-empty-string
<dt>[[enable Option|service.imap.enable]]<dd>

Enable the IMAP service on <code>start-msg</code> startup (note:
IMAP over SSL service is enabled/disabled separately using
<code>service.imap.enablesslport</code>).
Syntax: boolDefault: <code>0</code>
<dt>[[enablesslport Option|service.imap.enablesslport]]<dd>

Sets whether or not IMAP over SSL service is started.
Syntax: boolDefault: <code>0</code>
<dt>[[ensidle Option|service.imap.ensidle]]<dd>

If set, use ENS for imkill without idle, if unset, use JMQ. DELETED:
Removed in 7 update 4.
Syntax: boolDefault: <code>0</code>
<dt>[[enable Option|service.imap.idle]]<dd>

Sets values for <code>local.store.notifyplugin</code> and
<code>local.store.notifyplugin.*.*.enable</code> for IMAP IDLE to
work. DELETED: Removed in 7 update 4. Use
<code>service.imap.capability.idle</code> instead.
Syntax: boolDefault: <code>1</code>
<dt>[[jmqlibrary Option|service.imap.idle.jmq.library]]<dd>

The pathname to the JMQ library. Defaults to
/opt/sun/mq/lib/libmqcrt.so on Linux, /opt/SUNWimq/lib/64/libmqcrt.so
on 64-bit Solaris and /opt/SUNWimq/lib/libmqcrt.so on 32-bit
Solaris. DELETED: Removed in 7 update 4.
Syntax: non-empty-string
<dt>[[jmqhost Option|service.imap.idle.jmqhost]]<dd>

The name or address of the host where the JMQ broker is to be found.
DELETED: No longer used.
Syntax: non-empty-string
<dt>[[jmqpwd Option|service.imap.idle.jmqpassword]]<dd>

The JMQ password used to subscribe to messaging events. DELETED: No
longer used.
Syntax: password
<dt>[[jmqport Option|service.imap.idle.jmqport]]<dd>

The port number the JMQ broker is listening on. DELETED: No longer used.
Syntax: uint16
<dt>[[jmqtopic Option|service.imap.idle.jmqtopic]]<dd>

The JMQ topic to which mail events are published. DELETED: No longer used.
Syntax: non-empty-stringDefault: <code>JES-MS-IDLE</code>
<dt>[[jmquser Option|service.imap.idle.jmquserid]]<dd>

The JMQ userid used to subscribe to messaging events. DELETED: No longer used.
Syntax: non-empty-string
<dt>[[idletimeout Option|service.imap.idletimeout]]<dd>

Maximum idle time for connections (in minutes).
Syntax: uint32Default: <code>30</code>
<dt>[[enable Option|service.imap.indexer.enable]]<dd>

If enabled, send IMAP search queries to the Indexing Server.
Syntax: boolDefault: <code>0</code>
<dt>[[server_host Option|service.imap.indexer.hostname]]<dd>

Fully qualified host name or IP address of the Indexing Server.
Syntax: host
<dt>[[port Option|service.imap.indexer.port]]<dd>

TCP port on which the Indexing Service listens for incoming TCP connections.
Syntax: uint16Default: <code>8070</code>
<dt>[[prefix_search Option|service.imap.indexer.prefix_search]]<dd>

The <code>prefix_search</code> option specifies which, if any, search
parameters sent to the indexer should be preceeded by a "*", so that a
search for <code>subject mine</code> would match "determine" as well
as "mine". The value given should be one or more of <code>subject
text body from to cc bcc</code> separated by one or more spaces. Use
with caution as this imposes a significant load on the indexer.
''Introduced in release: 7 Update 4''Syntax: printable-ascii-string-list
<dt>[[substring_search Option|service.imap.indexer.substring_search]]<dd>

The <code>substring_search</code> option specifies which, if any,
search parameters sent to the indexer should be preceeded and followed
by a "*", so that a search for <code>subject ear</code> would match
"searches" as well as "ear". The value given should be one or more of
<code>subject text body from to cc bcc</code> separated by one or more
spaces. Use with caution as this imposes a significant load on the
indexer.
''Introduced in release: 7 Update 4''Syntax: printable-ascii-string-list
<dt>[[suffix_search Option|service.imap.indexer.suffix_search]]<dd>

The <code>suffix_search</code> option specifies which, if any, search
parameters sent to the indexer should be followed by a "*", so that a
search for <code>subject search</code> would match 'searches' as well
as "search". The value given should be one or more of <code>subject
text body from to cc bcc</code> separated by one or more spaces.
''Introduced in release: 7 Update 4''Syntax: printable-ascii-string-list
<dt>[[jmqtopic Option|service.imap.kill.jmqtopic]]<dd>

The JMQ topic to which kill user events are published. DELETED: No longer used.
Syntax: non-empty-stringDefault: <code>JES-MS-IDLE</code>
<dt>[[maxsessions Option|service.imap.maxsessions]]<dd>

Maximum number of sessions per server process.
Syntax: uint32Default: <code>4000</code>
<dt>[[maxthreads Option|service.imap.maxthreads]]<dd>

Maximum number of threads per server process.
Syntax: uint32Default: <code>250</code>
<dt>[[numprocesses Option|service.imap.numprocesses]]<dd>

Number of IMAP server processes. Note that the watcher must be
enabled for stop-msg to correctly shut down all processes if this is
set to a value larger than one.
Syntax: uint32Default: <code>1</code>
<dt>[[plaintextmincipher Option|service.imap.plaintextmincipher]]<dd>

If this is > 0, then disable use of plaintext passwords unless a
security layer (SSL or TLS) is activated. This forces users to enable
SSL or TLS on their client to login which prevents exposure of their
passwords on the network.
Syntax: int32Default: <code>0</code>
<dt>[[port Option|service.imap.port]]<dd>

IMAP server port number.
Syntax: uint16Default: <code>143</code>
<dt>[[sslcachesize Option|service.imap.sslcachesize]]<dd>

Number of SSL sessions to be cached.
Syntax: uint32Default: <code>0</code>
<dt>[[sslport Option|service.imap.sslport]]<dd>

IMAP over SSL port number.
Syntax: uint16Default: <code>993</code>
<dt>[[sslusessl Option|service.imap.sslusessl]]<dd>

Sets whether or not to enable SSL.
Syntax: boolDefault: <code>0</code>
<dt>[[submituser Option|service.imap.submituser]]<dd>

Store userid used by the MTA when resolving submit IMAP URLs in BURL commands.
Syntax: non-empty-string
<dt>[[withinresolution Option|service.imap.withinresolution]] (minutes)<dd>

Interval (in minutes) between recalculations of Contexts involving the
search options YOUNGER or OLDER. The value 0 means 30 seconds.
Syntax: int32Default: <code>30</code>
<dt>[[ldappoolsize Option|service.imta.ldappoolsize]]<dd>

Default LDAP pool size. DELETED: Feature never implemented.
Syntax: int32Default: <code>0</code>
<dt>[[ldapmemcachesize Option|service.ldapmemcachesize]]<dd>

Experimental LDAP SDK memcache size in bytes. DELETED: New authentication
support makes this obsolete.
Syntax: uint32Default: <code>131072</code>
<dt>[[ldapmemcachettl Option|service.ldapmemcachettl]]<dd>

Experimental LDAP SDK memcache entry time to live in seconds.
DELETED: New authentication support makes this obsolete.
Syntax: uint32Default: <code>30</code>
<dt>[[listenaddr Option|service.listenaddr]]<dd>

The IPv4 address to listen on.
The allowed values for the <code>listenaddr</code> option include an IPv4 address in dotted decimal
form (e.g., 127.0.0.1), or a short form or fully-qualified DNS host name which
will be resolved to an IPv4 address by obtaining the DNS A record for the
name. To explicitly specify the default value of binding to all available
interfaces, the string "INADDR_ANY" may be used. To bind to the loopback
device, 127.0.0.1, the string "localhost" may be specified.
Syntax: interface-addressDefault: <code>INADDR_ANY</code>
<dt>[[loginseparator Option|service.loginseparator]]<dd>

Character(s) to be used as login separator (between userid and domain).
Syntax: non-empty-stringDefault: <code>@</code>
<dt>[[allowanonymouslogin Option|service.pop.allowanonymouslogin]]<dd>

Sets whether or not anonymous login is allowed by POP.
Syntax: boolDefault: <code>0</code>
<dt>[[banner Option|service.pop.banner]]<dd>

POP protocol welcome banner. One line string, with virtual parameters:
%h=hostname, %p=protocol(ESMTP,POP or IMAP), %P=Product Name, %v and
%V=Version (short or long).
Syntax: non-empty-stringDefault: <code>%h %p service (%P %V)</code>
<dt>[[connlimits Option|service.pop.connlimits]]<dd>

Maximum number of connections per IP address for the selected
server. The syntax is: "realm1,realm2,..." where a realm has the form
of address ranges and maximum number of connections expressed as any of
the following four forms:
<table>
<tr>
<th colspan="2">a.b.c.d|e.f.g.h:m</th>
<th>IPv4 address, netmask, connection max</th>
</tr>
<tr>
<td> </td>
<td>a.b.c.d</td><td>IPv4 address</td>
</tr>
<tr>
<td> </td>
<td>e.f.g.h</td><td>network mask</td>
</tr>
<tr>
<td> </td>
<td>m</td><td>maximum connection count</td>
</tr>
<tr>
<th colspan="2">a.b.c.d/p:m</th>
<th>IPv4 address, routing prefix, connection max</th>
</tr>
<tr>
<td> </td>
<td>a.b.c.d</td><td>IPv4 address</td>
</tr>
<tr>
<td> </td>
<td>p</td><td>routing prefix</td>
</tr>
<tr>
<td> </td>
<td>m</td><td>maximum connection count</td>
</tr>
<tr>
<th colspan="2">a.b.c.d|e.f.g.h:m</th>
<th>IPv4 address, netmask, connection max</th>
</tr>
<tr>
<td> </td>
<td>a.b.c.d</td><td>IPv4 address</td>
</tr>
<tr>
<td> </td>
<td>e.f.g.h</td><td>network mask</td>
</tr>
<tr>
<td> </td>
<td>m</td><td>maximum connection count</td>
</tr>
<tr>
<th colspan="2">[a/p]:m</th>
<th>IPv6 address, routing prefix, connection max</th>
</tr>
<tr>
<td> </td>
<td>a</td><td>IPv6 address; compressed "::" format allowed</td>
</tr>
<tr>
<td> </td>
<td>p</td><td>routing prefix</td>
</tr>
<tr>
<td> </td>
<td>m</td><td>maximum connection count</td>
</tr>
<tr>
<th colspan="2">a.b.c.d|e.f.g.h:m</th>
<th>IPv4 address, netmask, connection max</th>
</tr>
<tr>
<td> </td>
<td>a.b.c.d</td><td>IPv4 address</td>
</tr>
<tr>
<td> </td>
<td>e.f.g.h</td><td>network mask</td>
</tr>
<tr>
<td> </td>
<td>m</td><td>maximum connection count</td>
</tr>
<tr>
<th colspan="2">:m</th>
<th>Match any address</th>
</tr>
<tr>
<td> </td>
<td>m</td><td>maximum connection count</td>
</tr>
</table>

There should be at least one realm of the form ":m" to cover the default case
by matching any IPv4 or IPv6 address. To match only IPv4 addresses, use
"0.0.0.0/0:m" or "0.0.0.0|0.0.0.0:m". And to match only IPv6 addresses, use
"[::0/0]:m".
Syntax: non-empty-string
<dt>[[domainallowed Option|service.pop.domainallowed]]<dd>

Access filters specifying which domains and/or IP addresses are
allowed POP access.
Syntax: non-empty-string
<dt>[[domainnotallowed Option|service.pop.domainnotallowed]]<dd>

Access filters specifying which domains and/or IP addresses are not
allowed POP access.
Syntax: non-empty-string
<dt>[[enable Option|service.pop.enable]]<dd>

Enable the POP service on <code>start-msg</code> startup (note:
POP over SSL service is enabled/disabled separately using
<code>service.pop.enablesslport</code>).
Syntax: boolDefault: <code>0</code>
<dt>[[enablesslport Option|service.pop.enablesslport]]<dd>

Sets whether or not POP over SSL service is started.
Syntax: boolDefault: <code>0</code>
<dt>[[idletimeout Option|service.pop.idletimeout]]<dd>

Maximum idle time for connections (in minutes).
Syntax: uint32Default: <code>10</code>
<dt>[[maxsessions Option|service.pop.maxsessions]]<dd>

Maximum number of sessions per server process.
Syntax: uint32Default: <code>600</code>
<dt>[[maxthreads Option|service.pop.maxthreads]]<dd>

Maximum number of threads per server process.
Syntax: uint32Default: <code>250</code>
<dt>[[numprocesses Option|service.pop.numprocesses]]<dd>

Number of POP server processes. Note that the watcher must be
enabled for stop-msg to correctly shut down all processes if this is
set to a value larger than one.
Syntax: uint32Default: <code>1</code>
<dt>[[plaintextmincipher Option|service.pop.plaintextmincipher]]<dd>

If this is > 0, then disable use of plaintext passwords unless a
security layer (SSL or TLS) is activated. This forces users to enable
SSL or TLS on their client to login which prevents exposure of their
passwords on the network.
Syntax: int32Default: <code>0</code>
<dt>[[port Option|service.pop.port]]<dd>

POP server port number.
Syntax: uint16Default: <code>110</code>
<dt>[[sslcachesize Option|service.pop.sslcachesize]]<dd>

Number of SSL sessions to be cached.
Syntax: uint32Default: <code>0</code>
<dt>[[sslport Option|service.pop.sslport]]<dd>

POP over SSL port.
Syntax: uint16Default: <code>995</code>
<dt>[[sslusessl Option|service.pop.sslusessl]]<dd>

Sets whether or not to enable SSL.
Syntax: boolDefault: <code>0</code>
<dt>[[timeout Option|service.readtimeout]]<dd>

Time in seconds that msprobe waits after sending a request that goes
unfulfilled before restarting a service.
Syntax: uint32Default: <code>30</code>
<dt>[[plaintextmincipher Option|service.smtp.plaintextmincipher]]<dd>

If this is > 0, then disable use of plaintext passwords unless a
security layer (SSL or TLS) is activated. This forces users to enable
SSL or TLS on their client to login which prevents exposure of their
passwords on the network.
''Introduced in release: 7 Update 4''Syntax: int32Default: <code>0</code>
<dt>[[sessionstoremodule Option|session.store.module]]<dd>

Session store module name.
Syntax: non-empty-stringDefault: <code>session_store_simple</code>
<dt>[[admins Option|store.admins]]<dd>

Space separated list of user ids with message store administrator
privileges.
Syntax: non-empty-stringDefault: <code>admin</code>
<dt>[[compliance Option|store.archive.compliance]]<dd>

Enable compliance archive.
Syntax: boolDefault: <code>0</code>
<dt>[[intext Option|store.archive.intext]]<dd>

Controls whether or not address reversal processing is done while
archiving to determine whether addresses are internal or external.
''Introduced in release: 7U4 patch 26''Syntax: boolDefault: <code>0</code>
<dt>[[operational Option|store.archive.operational]]<dd>

Enable operational archive.
Syntax: boolDefault: <code>0</code>
<dt>[[path Option|store.archive.path]]<dd>

Archive injection directory.
Syntax: path
<dt>[[posteddatemode Option|store.archive.posteddatemode]]<dd>

Controls how the Axs:One PostedDate field is populated. A setting of 0 uses
the header Date: field. A positive value N that's less than 100 uses
the date information from the Nth header Received: field counting
from the top of the header. A negative value N greater than -100 uses
the date information from the (-N)th header Date: field counting from the
bottom of the header. A value of 100, the default, uses the IMAP message
internal date.
''Introduced in release: 7U4 patch 26''Syntax: int32Default: <code>100</code>
<dt>[[reportdir Option|store.archive.reportdir]]<dd>

Archive confirm report directory.
Syntax: absdirpath
<dt>[[retrieveport Option|store.archive.retrieveport]]<dd>

Archive retrieve server port.
Syntax: uint16Default: <code>80</code>
<dt>[[retrieveserver Option|store.archive.retrieveserver]]<dd>

Archive retrieve server.
Syntax: non-empty-string
<dt>[[retrievetimeout Option|store.archive.retrievetimeout]]<dd>

Archive retrieve timeout in seconds.
Syntax: uint32Default: <code>30</code>
<dt>[[tmpdir Option|store.archive.tmpdir]]<dd>

Temporary directory for archived message retrieval. If not set,
<code>local.tmpdir</code> is used.
Syntax: absdirpath
<dt>[[autorepair Option|store.autorepair]]<dd>

Repair damaged mailboxes automatically.
Syntax: boolDefault: <code>1</code>
<dt>[[autorepairdebug Option|store.autorepairdebug]]<dd>
Backup mailbox index files to <code>local.tmpdir</code>/storedebug directory
before repair. Maximum number of backup mailboxes is 10. Remove the files and
directories under storedebug manually when they are not needed.''Introduced in release: 7u4 patch 26''Syntax: boolDefault: <code>0</code>
<dt>[[debug Option|store.checkpoint.debug]]<dd>

<code>stored</code> checkpoint debug.
Syntax: int32Default: <code>0</code>
<dt>[[stresslimit Option|store.checkpoint.stresslimit]]<dd>

Max <code>stored</code> checkpoint duration in seconds. Throttling
starts when checkpoint duration exceeds this limit.
Syntax: uint32Default: <code>60</code>
<dt>[[cleanupage Option|store.cleanupage]]<dd>

Age (in hours) of expired or expunged message before purge will
permanently remove it. The minimum allowed value is 1; the maximum is
504 (3 weeks).
Syntax: uint32Default: <code>1</code>
<dt>[[cleanupsize Option|store.cleanupsize]]<dd>

Minimum number of expunged messages before purge will permanently remove them.
Syntax: uint32Default: <code>100</code>
<dt>[[dbcachesize Option|store.dbcachesize]]<dd>

Mailbox list database cache size. Setting the optimal cache size can
make a big difference in overall Message Store performance. Cache
efficiency can be determined by running <code>msg-svr-base/lib/db_stat
-m -h store.dbtmpdir/mboxlist</code>, where
<code>store.dbtmpdir</code> is the value of the
<code>store.dbtmpdir</code> option.
Syntax: uint32Default: <code>16777216</code>
<dt>[[debug Option|store.dbreplicate.debug]]<dd>

Enable mboxlist database replication debugging.
Syntax: int32Default: <code>0</code>
<dt>[[dbtmpdir Option|store.dbtmpdir]]<dd>

Mailbox list database temporary directory. Defaults to
/tmp/.ENCODED_SERVERROOT/store/, where ENCODED_SERVERROOT is composed
of mail server user plus the $SERVERROOT with / replaced by _.
e.g. /tmp/.mailsrv_opt_sun_comms_messaging64/store/
This is a directory which
is very heavily accessed. If the disks that house the mboxlist
database temporary directory are not fast enough at very large sites,
performance problems might occur. As part of their performance and
tuning steps, sites should take a note of this and define a value for
this parameter which either points to a memory mapped file system, or
which points to a location on a fast file system.
Syntax: absdirpath
<dt>[[defaultacl Option|store.defaultacl]]<dd>

Default ACL. DELETED: Removed in Messaging Server 6.3.
Syntax: non-empty-stringDefault: <code>anyone lrs</code>
<dt>[[defaultmailboxquota Option|store.defaultmailboxquota]]<dd>

Default mailbox quota (in bytes).
Syntax: non-empty-stringDefault: <code>-1</code>
<dt>[[defaultmessagequota Option|store.defaultmessagequota]]<dd>

Default message quota (in number of messages).
Syntax: non-empty-stringDefault: <code>-1</code>
<dt>[[defaultpartition Option|store.defaultpartition]]<dd>

Default partition. Only applicable on INBOX. Subfolders will be
created in the partition of the parent folder.
Syntax: non-empty-stringDefault: <code>primary</code>
<dt>[[diskflushinterval Option|store.diskflushinterval]]<dd>

DELETED: Use <code>local.store.*synclevel</code> instead.
Syntax: uint32Default: <code>15</code>
<dt>[[encryptnew Option|store.encryptnew]]<dd>
Encrypt new messages.
''Introduced in release: 7u4 patch 24''Syntax: boolDefault: <code>0</code>
<dt>[[expiresieve Option|store.expire.sieve]]<dd>

Enable sieve script in expire rules.
Syntax: boolDefault: <code>0</code>
<dt>[[deleted Option|store.expirerule.*.deleted]]<dd>

Syntax: "and"|"or". When set to "or", expire messages if the 'Deleted'
system flag is set or other criteria in the expire rule are met.
When set to "and", expire messages if the 'Deleted' system flag is set
and other criteria in the expire rule are met.
Syntax: enumstr
<dt>[[exclusive Option|store.expirerule.*.exclusive]]<dd>

When this parameter is set to "1", it is the only rule applied even
if other rules match the given criteria.
Syntax: boolDefault: <code>0</code>
<dt>[[folderpattern Option|store.expirerule.*.folderpattern]]<dd>

Folders for which the rule apply. Syntax: POSIX regular expression.
For examples, refer to <code>imexpire</code> Folder Patterns Using
Regular Expressions in the Admin Guide.
Syntax: non-empty-string
<dt>[[foldersizebytes Option|store.expirerule.*.foldersizebytes]]<dd>

Maximum number of bytes in folder.
Syntax: uint32Default: <code>0</code>
<dt>[[messagecount Option|store.expirerule.*.messagecount]]<dd>

Upper limit on number of messages to be kept in the specified folders.
Syntax: uint32Default: <code>0</code>
<dt>[[messagedays Option|store.expirerule.*.messagedays]]<dd>

Upper limit on how long a message is kept in the specified folders (in
days).
Syntax: uint32Default: <code>0</code>
<dt>[[messagesize Option|store.expirerule.*.messagesize]]<dd>

Size of an over-sized message.
Syntax: uint32Default: <code>0</code>
<dt>[[messagesizedays Option|store.expirerule.*.messagesizedays]]<dd>

Days an over-sized message should remain in a folder.
Syntax: uint32Default: <code>0</code>
<dt>[[seen Option|store.expirerule.*.seen]]<dd>

Syntax: "and"|"or". When set to "or", expire messages if the 'Seen'
system flag is set or other criteria in the expire rule are met.
When set to "and", expire messages if the 'Seen' system flag is set
and other criteria in the expire rule are met.
Syntax: enumstrcase
<dt>[[expirestart Option|store.expirestart]]<dd>

<code>imexpire</code> start time. Format: 0-23 (represents
hour). DELETED: Use <code>local.schedule.expire</code> instead.
Syntax: int32Default: <code>23</code>
<dt>[[enable Option|store.folderquota.enable]]<dd>

Enable quota by folder.
Syntax: boolDefault: <code>0</code>
<dt>[[indexeradmins Option|store.indexeradmins]]<dd>

Space separated list of user ids with message store indexer
administrator privileges. The last access timestamp will not be
updated when authenticating with a user id in this list.
Syntax: non-empty-string
<dt>[[keylabel Option|store.keylabel]]<dd>
The label of the message store key in the keystore.
''Introduced in release: 7u4 patch 24''Syntax: non-empty-stringDefault: <code>msgstore</code>
<dt>[[keypass Option|store.keypass]]<dd>
Keystore password.
''Introduced in release: 7u4 patch 24''Syntax: password
<dt>[[mailboxexpungesize Option|store.mailboxexpungesize]]<dd>

Size (in bytes) of expired or expunged message before purge will
permanently remove it. Minimum value is 1048576. DELETED: Use
<code>store.cleanupsize</code> instead.
''Introduced in release: 7.0''Syntax: uint32Default: <code>5242880</code>
<dt>[[mailboxpurgedelay Option|store.mailboxpurgedelay]]<dd>

When a mailbox is deleted by the end user, expunge all the
messages and purge the data after store.cleanupage has expired.
Expunged messages can be restored with 'mboxutil -R'.
Expunged messages are moved to the new location when a mailbox
is renamed.
''Introduced in release: 7u4 patch 26''Syntax: boolDefault: <code>0</code>
<dt>[[maxcachefilesize Option|store.maxcachefilesize]]<dd>

Maximum cache file size (in bytes). A new cache file is created when
the current cache file size has exceeded this limit. Minimum value is
1048576.
''Introduced in release: 7.0''Syntax: uint32Default: <code>536870912</code>
<dt>[[contenttype Option|store.messagetype.*]]<dd>

Defines a message type.
Syntax: non-empty-string
<dt>[[flagname Option|store.messagetype.*.flagname]]<dd>

Flag name of a message type.
Syntax: non-empty-string
<dt>[[quotaroot Option|store.messagetype.*.quotaroot]]<dd>

Quota root of a message type.
Syntax: non-empty-string
<dt>[[enable Option|store.messagetype.enable]]<dd>

Enable the message type feature.
Syntax: boolDefault: <code>0</code>
<dt>[[header Option|store.messagetype.header]]<dd>

Defines an alternative message type header field.
Syntax: non-empty-string
<dt>[[dbcachesize Option|store.msghash.dbcachesize]]<dd>

Message hash database cache size.
Syntax: uint32Default: <code>8388608</code>
<dt>[[enable Option|store.msghash.enable]]<dd>

Enable message hash database.
Syntax: boolDefault: <code>0</code>
<dt>[[nummsgs Option|store.msghash.nummsgs]]<dd>

Message hash database size.
Syntax: uint32Default: <code>0</code>
<dt>[[cachepath Option|store.partition.*.cachepath]]<dd>

Path name of a store partition containing the mailbox cache files. If
this is not a full path, this is relative to the store/partition
subdirectory of the data directory. If not specified, the value for
<code>store.partition.*.path</code> configutil parameter is used.
Syntax: dirpath
<dt>[[messagepath Option|store.partition.*.messagepath]]<dd>

Path name of a store partition containing the message files. If this
is not a full path, this is relative to the store/partition
subdirectory of the data directory. If not specified, the value for
<code>store.partition.*.path</code> configutil parameter is used.
Syntax: dirpath
<dt>[[path Option|store.partition.*.path]]<dd>

Path name of a store partition. If this is not a full path, this is
relative to the store/partition subdirectory of the data directory.
Syntax: path
<dt>[[path Option|store.partition.primary.path]]<dd>

Path name of the primary partition, (if not a full path, this is
relative to the store/partition subdirectory of the data directory).
Syntax: pathDefault: <code>primary</code>
<dt>[[restrictanyone Option|store.privatesharedfolders.restrictanyone]]<dd>

Disallow regular users sharing private folders to anyone.
Syntax: boolDefault: <code>0</code>
<dt>[[restrictdomain Option|store.privatesharedfolders.restrictdomain]]<dd>

Disallow regular users sharing private folders to users in another domain.
Syntax: boolDefault: <code>0</code>
<dt>[[shareflags Option|store.privatesharedfolders.shareflags]]<dd>

Private shared folders share \Seen and \Deleted flags across users.
Syntax: boolDefault: <code>0</code>
<dt>[[user Option|store.publicsharedfolders.user]]<dd>

Public shared folder owner's userid.
Syntax: printable-ascii-string
<dt>[[count Option|store.purge.count]]<dd>

Minimum number of expunged cache records before purge will permanently
remove them. The minimum allowed value is 1; maximum is 1000000.
Syntax: uint32Default: <code>500</code>
<dt>[[maxthreads Option|store.purge.maxthreads]]<dd>

Maximum number of threads.
Syntax: uint32Default: <code>0</code>
<dt>[[percentage Option|store.purge.percentage]]<dd>

Percentage of expunged cache records before purge will permanently remove it.
Syntax: uint32Default: <code>5</code>
<dt>[[quotaenforcement Option|store.quotaenforcement]]<dd>

Enable quota enforcement. When off, the quota database is still updated, but
messages are always delivered.
Syntax: boolDefault: <code>1</code>
<dt>[[quotaexceededmsg Option|store.quotaexceededmsg]]<dd>

Message to be sent to user when quota exceeds
<code>store.quotawarn</code>. The message must contain a header
(with at least a subject line), followed by $$, then the message
body. The $ represents a new line. There is support for the following
variables: [ID] - userid, [DISKUSAGE] - disk usage, [NUMMSG] - number
of messages, [PERCENT] - <code>store.quotawarn</code>
percentage, [QUOTA] - mailquota attribute, [MSGQUOTA] - mailmsgquota
attribute.
Syntax: non-empty-string
<dt>[[quotaexceededmsg Option|store.quotaexceededmsg;lang-*]]<dd>

Localized message to be sent to user when quota exceeds
<code>store.quotawarn</code>. The message must contain a header
(with at least a subject line), followed by $$, then the message
body. The $ represents a new line. There is support for the following
variables: [ID] - userid, [DISKUSAGE] - disk usage, [NUMMSG] - number
of messages, [PERCENT] - <code>store.quotawarn</code>
percentage, [QUOTA] - mailquota attribute, [MSGQUOTA] - mailmsgquota
attribute.
Syntax: non-empty-string
<dt>[[quotaexceededmsginterval Option|store.quotaexceededmsginterval]] (days)<dd>

Interval (in days) to wait before sending another quota exceeded
message.
Syntax: int32Default: <code>7</code>
<dt>[[quotagraceperiod Option|store.quotagraceperiod]]<dd>

Time (in hours) a mailbox must be over quota before messages to the
mailbox will bounce back to the sender.
Syntax: uint32Default: <code>120</code>
<dt>[[quotanotification Option|store.quotanotification]]<dd>

Enables quota notification for the message store.
Syntax: boolDefault: <code>0</code>
<dt>[[quotawarn Option|store.quotawarn]]<dd>

Percentage of quota that must be exceeded before clients are sent an
over quota warning.
Syntax: int32Default: <code>90</code>
<dt>[[serviceadmingroupdn Option|store.serviceadmingroupdn]]<dd>

DN of service administrator group.
Syntax: non-empty-string
<dt>[[enable Option|store.typequota.enable]]<dd>

Enable quota by type.
Syntax: boolDefault: <code>0</code>
<dt>[[umask Option|store.umask]]<dd>

File mode creation mask for message store processes (in octal). By
default, store file access by other users or users in the same group
is forbidden by file permissions. Setting umask to '027' will allow
users in the same primary group as local.serveruid to read
subsequently created message store files.
Syntax: uoctalDefault: <code>077</code>
</dl>
[[Category: Legacy]]
[[Category: Reference]]

MsgServerDocWiki - Recent changes [en]

Configutil Reference

MMP Reference

Configutil Reference