Ap_debug, cache_debug, dequeue_debug, filter_debug, log_debug, mm_debug, os_debug, return_debug MTA Options

From MsgServerDocWiki

(Link to this page as [[Ap debug, cache debug, dequeue debug, filter debug, log debug, mm debug, os debug, return debug MTA Options]])
Jump to: navigation, search


One or more of the options discussed on this page are restricted. Restricted options are not intended for general use and if set may cause severe operational problems. If you believe you need to set a restricted option you should first check with Sun support.


MTA debugging control (ap_debug, cache_debug, dequeue_debug, filter_debug, log_debug, mm_debug, os_debug, return_debug)

Several options are provided to control debug output for various MTA components and subsystemms:

ap_debug (integer)

RESTRICTED. this option enables internal MTA debugging; it is intended for use by Sun and is not intended to be used by end sites. Specifically, it enables debugging of the AP routines (low level address parsing routines). Higher settings of ap_debug cause more verbose output. The precise debug output can be expected to vary between and during releases. When enqueuing messages, in order for ap_debug values greater than 0 to take effect, both the master_debug and slave_debug channel options must be set on the source channel except for the L channel where just master_debug or slave_debug is sufficient.

cache_debug (0 or 1)

The cache_debug option controls debugging regarding the direct LDAP caching of lookup results (domains, aliases, address reversals). The default is 0, meaning that such debug output is disabled. Setting this option to 1 enables the debug output; the information is output just before the MTA component exits. (So for instance, imsimta test -rewrite will output information regarding what it cached at the end of its other, normal output---since imsimta test -rewrite most often is used to test just one or a couple of addresses, there is not often much it had to cache. An SMTP server process will output to its log file information regarding what it cached just before it shuts down at the end of its lifetime -- since SMTP server processes typically last for some time, there may be quite a bit of caching that occurred.)

dequeue_debug (0 or 1)

This option specifies whether or not debugging output from the MTA's dequeue facility QU is produced; (note that master channel programs, since they are generally dequeue oriented, usually use QU routines). If enabled with a value of 1, this output will be produced on all channels that use the QU routines. The default value of 0 disables this output.

filter_debug (0 or 1)

New in Messaging Server 6.2. Control whether the stack state information part of Sieve filter debugging is put in debug logs.

log_debug (0 or 1)

RESTRICTED: This option may be used to enable internal debugging of MTA logging activity; it is intended for use by Sun, and is not intended to be used by end sites.

mm_debug (integer)

This option enables internal enqueue debugging; it is intended for use by Sun, and is not intended to be used by end sites. In particular, it is not intended for, and is not supported for use for, logging purposes. Specifically, it enables debugging of the MM routines (enqueue routines handling address rewriting, mappings conversions, etc.). Note that generally at least one of master_debug or slave_debug must be set on a channel in order for mm_debug settings to take effect; the OpenVMS L channel is an exception and requires setting both master_debug and slave_debug. (In PMDF V5.1 and earlier, all channels required setting both master_debug and slave_debug for MM_DEBUG to take effect.) Higher settings of mm_debug cause more verbose output. For instance, currently a value of 1 or more includes some message file access debugging and some alias file/database access debugging and some overview of header processing and debugging of access mapping table checks and debugging of address/subaddress variant lookups, and some commenting about spam/virus filter package verdicts; a value of 2 or more includes debugging of conversion probes and debugging of filters and some debugging of URL lookups (LDAP and file) and debugging of auto-registration and debugging of mailing list keyword processing and debugging of constructing address/subaddress variants and debugging of domainMap/domain-match-cache usage, and further information regarding spam/virus filter package access and errors; a value of 3 or more includes debugging of mapping table use and further debugging of the actual attribute lookups for LDAP URL lookups and domain lookups (including domain caching info) and (as of JES MS 6.2) debugging regarding the reason when a message for multiple recipients is "split up" into different copies; a value of 4 or more includes some file reading debug especially on OpenVMS; a value of 5 causes very verbose output, including actual contents of the incoming message body, and details regarding spam/virus filter package opt in or opt out; in particular, a value of 8 or more includes some debugging of creating message files and writing out lines of message files and reading in message lines. The precise debug output can be expected to vary between and during releases.

os_debug (0 or 1)

RESTRICTED. this option enables internal MTA debugging; it is intended for use by Sun and is not intended to be used by end sites. Specifically, it enables debugging of the OS routines (low level operating system interface routines).

return_debug (0 or 1)

The return_debug option enables or disables debugging output in the nightly message bouncer batch job. A value of 0 disables this output (the default) while a value of 1 enables it. Debugging output, if enabled, in iMS 5.2 will appear in the Job Controller's log file, usually a job_controller.log-* file, and in JES MS 6.1p1 and later will appear in the IMTA_LOG:return-uniquestring.log log file.

Retrieved from "http://msg.wikidoc.info/index.php/Ap_debug%2C_cache_debug%2C_dequeue_debug%2C_filter_debug%2C_log_debug%2C_mm_debug%2C_os_debug%2C_return_debug_MTA_Options"
Personal tools