Sun Java System Messaging Server 6.3 Administration Guide

25.4.1 Understanding Service Log Characteristics

This section describes the following log characteristics for the message store and administration services: logging levels, categories of logged events, filename conventions for logs, and log-file directories. Logging Levels

The level, or priority, of logging defines how detailed, or verbose, the logging activity is to be. A higher priority level means less detail; it means that only events of high priority (high severity) are logged. A lower level means greater detail; it means that more events are recorded in the log file.

You can set the logging level separately for each service—POP, IMAP, HTTP, Admin, and Default by setting the logfile.service.loglevel configuration parameter (see 25.4.3 Defining and Setting Service Logging Options). You can also use logging levels to filter searches for log events. Table 25–6 describes the available levels. These logging levels are a subset of those defined by the UNIX syslog facility.

Table 25–6 Logging Levels for Store and Administration Services




The minimum logging detail. An event is written to the log whenever a severe problem or critical condition occurs—such as when the server cannot access a mailbox or a library needed for it to run. 


An event is written to the log whenever an error condition occurs—such as when a connection attempt to a client or another server fails. 


An event is written to the log whenever a warning condition occurs—such as when the server cannot understand a communication sent to it by a client. 


An event is written to the log whenever a notice (a normal but significant condition) occurs—such as when a user login fails or when a session closes. This is the default log level. 


An event is written to the log with every significant action that takes place—such as when a user successfully logs on or off or creates or renames a mailbox. 


The most verbose logging. Useful only for debugging purposes. Events are written to the log at individual steps within each process or task, to pinpoint problems. 

When you select a particular logging level, events corresponding to that level and to all higher (less verbose) levels are logged. The default level of logging is Notice.

Note –

The more verbose the logging you specify, the more disk space your log files will occupy; for guidelines, see 25.4.3 Defining and Setting Service Logging Options Categories of Logged Events

Within each supported service or protocol, Messaging Server further categorizes logged events by the facility, or functional area, in which they occur. Every logged event contains the name of the facility that generated it. These categories aid in filtering events during searches. Table 25–7 lists the categories that Messaging Server recognizes for logging purposes.

Table 25–7 Categories in Which Log Events Occur




Undifferentiated actions related to this protocol or service 


Actions related to Messaging Server accessing the LDAP directory database 


Actions related to network connections (socket errors fall into this category) 


Actions related to user accounts (user logins fall into this category) 


Protocol-level actions related to protocol-specific commands (errors returned by POP, IMAP, or HTTP functions fall into this category) 


Actions related to the gathering of server statistics 


Low-level actions related to accessing the message store (read/write errors fall into this category) 

For examples of using categories as filters in log searches, see 25.4.4 Searching and Viewing Service Logs Service Log File Directories

Every logged service is assigned a single directory, in which its log files are stored. All IMAP log files are stored together, as are all POP log files, and log files of any other service. You define the location of each directory, and you also define how many log files of what maximum size are permitted to exist in the directory.

Make sure that your storage capacity is sufficient for all your log files. Log data can be voluminous, especially at lower (more verbose) logging levels.

It is important also to define your logging level, log rotation, log expiration, and server-backup policies appropriately so that all of your log-file directories are backed up and none of them become overloaded; otherwise, you may lose information. See 25.4.3 Defining and Setting Service Logging Options.