Previous: , Up: pmult configuration   [Contents][Index]

13.1.4 Debugging Pmult

If needed, pmult can be instructed to provide additional debugging information. The amount of this information is configured by three configuration statements. First of all, the standard debug block statement controls debugging of the underlying GNU Mailutils libraries (see Mailutils Configuration File in GNU Mailutils Manual). Secondly, the debug statement controls debugging output of the pmult utility itself. The pmilter-debug statement controls debugging output of the underlying MeTA1 libraries, and, finally, the log-level statement, described in the previous subsection, defines debugging level for the Milter library (libgacopyz).

Pmult Conf: debug spec

Set debugging level for the pmult code. See Mailutils Configuration File in GNU Mailutils Manual, for a description of spec syntax. Multiplexor-specific debugging is enabled by the ‘pmult’ category. The following levels are used:


Prints the following information:

  • opening and closing incoming connections;
  • entering particular Pmilter stage handlers;
  • received requests with unknown command code;
  • header modification requests that does not match any headers.

Information about milter to Pmilter request translation.


Detailed dump of message body chunks received during Pmilter ‘DATA’ stage.


Logs bad recipient addresses.

This information is printed using the output channel defined in the logging statement (see Mailutils Configuration File in GNU Mailutils Manual).

Pmult Conf: pmilter-debug level

Set debug verbosity level for the Pmilter library. Argument is a positive integer between zero (no debugging, the default), and 100 (maximum debugging).

Pmilter debugging information is printed on the standard error. Use pies stderr statement to capture this stream and redirect it to the syslog or file (see Output Redirectors in Pies Manual).

Previous: , Up: pmult configuration   [Contents][Index]