#### 3.2.5 The `logging` Statement ¶

#### Syntax ¶

    logging {
      # Send diagnostics to syslog.
      syslog boolean;

      # Print message severity levels.
      print-severity boolean;

      # Output only messages with a severity equal to or
      # greater than this one.
      severity string;

      # Set syslog facility.
      facility name;

      # Log session ID
      session-id boolean;

      # Tag syslog messages with this string.
      tag text;
    }

#### Description ¶

The `logging` block statement configures where the diagnostic output goes and how verbose it is.

Configuration: syslog bool ¶

  If ‘`syslog`’ is set to ‘`yes`’, the diagnostics will go to syslog. Otherwise, it goes to the standard error.

The default syslog facility is determined at compile time, it can be inspected using the following command (see mailutils info):

    $ mailutils info log_facility

Configuration: facility name ¶

  Use syslog facility name. Valid argument values are: ‘`user`’, ‘`daemon`’, ‘`auth`’, ‘`authpriv`’, ‘`mail`’, ‘`cron`’, ‘`local0`’ through ‘`local7`’ (all names case-insensitive), or a facility number.

Configuration: tag text ¶

  Tag syslog messages with text. By default, program name is used as syslog tag.

Configuration: print-severity bool ¶

  Print Mailutils severity name before each message.

Configuration: severity name ¶

  Output only messages with a severity equal to or greater than this one. Valid arguments are: ‘`debug`’, ‘`info`’, ‘`notice`’, ‘`warning`’, ‘`error`’, ‘`crit`’, ‘`alert`’, ‘`emerg`’,

Configuration: session-id bool ¶

  Print session ID with each diagnostic message. This is useful for programs that handle multiple user sessions simultaneously, such as `pop3d` and `imap4d`.