Debug

This tab allows you to manage debug settings.

Warning: Use very carefully! Turning these options on can produce (and probably will) huge amount of logs.

Figure. Logging management: Debug tab.

Field

Description

System performance (Log actions exceeding time in seconds)

Insert time in seconds, if you want to have logged system actions lasting longer than the value specified here.

Mail flow, queue and processing logs

Check the box if you want to have logged most actions performed with email messages (antispam, antivirus, etc.)

This feature logs actions taken after an email is received via SMTP and can indicate bottle necks, such as heavy content filters (that scan body of messages without a message size limitation).

For very experienced administrators.

Note: The kind of logs where content filters / rules are mentioned differ: When a CF / rule alters mail delivery, it is written in SMTP logs (e.g.: rejection). When it alters spam/nospam behavior, it is in AntiSpam logs (e.g.: rejection, change spam score, etc.).
For other cases, you would need to enable mail flow logs to know whether a CF / rule had a hit. SMTP log example:
127.0.0.1 [1A40] 14:16:04 Message for <mike@icewarp.com> not delivered. Reasons:[ContentFilter=Viagra,Bypass=Q], Action:REJECT

API logs

Check the box if you want to have logged every API use. This includes not only any server setting change, but also for example any setting changes performed by users in their WebClients etc.

DNS logs

Check the box if you want to have logged DNS service and communication with your DNS server.

SQL logs

Select how you want to have logged database actions:

  • None: none of database actions are logged.

  • Log all SQL: really all is logged! Even showing folders in a WebClient.

  • Log only failed SQL: only failed database enquiries are logged.

  • Log connection maintenance: provides internal information about working with a database such as connecting/disconnecting, parameter binding, results fetching etc. This level includes ALL SQL queries logging.

AD sync logs

Select how you want to have logged Active Directory synchronization:

  • None: no logs at all.

  • Summary: after each domain synchronization, only one log row is written.

    e. g.: [1E84] 13:56:01 Synchronizing domain tests.icewarp.com finished, Users( 0 created,20 updated,0 deleted, 7 skipped, 27 listed), Groups( 0 created,1 updated,0 deleted, 40 skipped, 41 listed)

  • Debug: all important operations + failed user synchronizations are logged.

    Example of a failed synchronization log:

    SYSTEM [1DB8] 13:51:47 Skipping item 1, because of missing email

  • Extended: all data obtained from a remote AD server are logged. Logs are really vast: use advisedly. (The AD output can be truncated. Maximum size of one log record is limited by the c_system_log_maxlogsize API variable. AD result is logged as one record.)

    These logs are available for GroupWare, SMTP and IMAP.

Kerberos logs

Select how you want to have logged Kerberos authentication.

Only the Debug and Extended levels produce outputs.

For more details, refer to the Domains and Accounts: Domain: Directory Service chapter: Kerberos/GSSAPI/SSO section.

Directory Cache logs

Select how you want to have logged directory cache:

  • None: no logs at all

  • Summary: start and stop of wave mode is logged.

  • Debug: the summary level plus reading from memory, disk, database, getting information about a directory and SQL errors are logged.

  • Extended: all previous plus SQL queries and internal parts locking are logged.

For more details on directory cache, refer to Directory Cache.

WCS logs

Select how you want to have logged WCS (Web Coverage Service):

  • None and Summary: no logs at all.

  • Debug and Extended: any WCS communication is logged.