Mailfromd |
|
General-Purpose Mail Filter |
Sergey Poznyakoff |
Mailfromd Manual (split by node): | ? |
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: (mailutils)Debug Statement section `Debug Statement' 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
).
Set debugging level for the pmult
code. See Mailutils Configuration File: (mailutils)Debug Statement section `Debug Statement' in GNU Mailutils Manual, for a description of spec syntax. The following
debugging levels are used:
Prints the following information:
Information about milter to Pmilter request translation.
Detailed dump of message body chunks received during Pmilter ‘DATA’ stage.
Bad recipient addresses.
This information is printed using the output channel defined in the
logging
statement (see Mailutils Configuration File: (mailutils)Logging Statement section `Logging Statement' in GNU Mailutils Manual).
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 (pies)Output Redirectors section `Output Redirectors' in Pies Manual).
Mailfromd Manual (split by node): | ? |
Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved.