/usr/share/doc/mailutils-doc/mailutils.html/Debugging-Categories.html is in mailutils-doc 1:2.99.99-1ubuntu2.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 | <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<!-- Published by the Free Software Foundation,
51 Franklin Street, Fifth Floor
Boston, MA 02110-1301, USA
Copyright (C) 1999-2004, 2008-2012, 2014-2015 Free Software
Foundation, Inc.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.2 or
any later version published by the Free Software Foundation; with no
Invariant Sections, no Front-Cover, and no Back-Cover texts.
A copy of the license is included in the section entitled "GNU Free
Documentation License". -->
<!-- Created by GNU Texinfo 6.1, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Mailutils Manual: Debugging Categories</title>
<meta name="description" content="GNU Mailutils Manual: Debugging Categories">
<meta name="keywords" content="GNU Mailutils Manual: Debugging Categories">
<meta name="resource-type" content="document">
<meta name="distribution" content="global">
<meta name="Generator" content="makeinfo">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<link href="index.html#Top" rel="start" title="Top">
<link href="Function-Index.html#Function-Index" rel="index" title="Function Index">
<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
<link href="debugging.html#debugging" rel="up" title="debugging">
<link href="frm-and-from.html#frm-and-from" rel="next" title="frm and from">
<link href="Level-BNF.html#Level-BNF" rel="prev" title="Level BNF">
<style type="text/css">
<!--
a.summary-letter {text-decoration: none}
blockquote.indentedblock {margin-right: 0em}
blockquote.smallindentedblock {margin-right: 0em; font-size: smaller}
blockquote.smallquotation {font-size: smaller}
div.display {margin-left: 3.2em}
div.example {margin-left: 3.2em}
div.lisp {margin-left: 3.2em}
div.smalldisplay {margin-left: 3.2em}
div.smallexample {margin-left: 3.2em}
div.smalllisp {margin-left: 3.2em}
kbd {font-style: oblique}
pre.display {font-family: inherit}
pre.format {font-family: inherit}
pre.menu-comment {font-family: serif}
pre.menu-preformatted {font-family: serif}
pre.smalldisplay {font-family: inherit; font-size: smaller}
pre.smallexample {font-size: smaller}
pre.smallformat {font-family: inherit; font-size: smaller}
pre.smalllisp {font-size: smaller}
span.nolinebreak {white-space: nowrap}
span.roman {font-family: initial; font-weight: normal}
span.sansserif {font-family: sans-serif; font-weight: normal}
ul.no-bullet {list-style: none}
-->
</style>
</head>
<body lang="en">
<a name="Debugging-Categories"></a>
<div class="header">
<p>
Previous: <a href="Level-BNF.html#Level-BNF" accesskey="p" rel="prev">Level BNF</a>, Up: <a href="debugging.html#debugging" accesskey="u" rel="up">debugging</a> [<a href="index.html#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="Function-Index.html#Function-Index" title="Index" rel="index">Index</a>]</p>
</div>
<hr>
<a name="Debugging-Categories-1"></a>
<h4 class="subsection">2.3.3 Debugging Categories</h4>
<dl compact="compact">
<dt>acl</dt>
<dd><p>This category enables debugging of Access Control Lists. Available
levels are:
</p>
<dl compact="compact">
<dt>error</dt>
<dd><p>As usual, displays errors, not directly reported otherwise.
</p></dd>
<dt>trace0</dt>
<dd><p>Basic tracing of ACL processing.
</p></dd>
<dt>trace9</dt>
<dd><p>Traces the process of matching the ACL conditions.
</p></dd>
</dl>
</dd>
<dt>config</dt>
<dd><p>This category affects configuration parser and/or lexical
analyzer. The following levels are supported:
</p>
<dl compact="compact">
<dt>trace0</dt>
<dd><p>Minimal information about configuration statements.
</p></dd>
<dt>trace2</dt>
<dd><p>Trace lexical structure of the configuration files.
</p></dd>
<dt>trace7</dt>
<dd><p>Trace execution of the configuration parser.
</p></dd>
</dl>
<p>Due to its specific nature, this category cannot be enabled from the
configuration file. A special hook is provided to facilitate
debugging the configuration parser, namely, a pragmatic comment in
form:
</p>
<div class="example">
<pre class="example">#debug=<var>debug-level-list</var>
</pre></div>
<p>causes <var>debug-level-list</var> to be parsed as described above. Thus, to
force debugging of the configuration parser, one would add the following
line at the very beginning of the configuration file:
</p>
<div class="example">
<pre class="example">#debug=config.trace7
</pre></div>
</dd>
<dt>mailbox</dt>
<dd><p>Operations over mailboxes. This module supports the following levels:
‘<samp>error</samp>’, ‘<samp>trace0</samp>’, ‘<samp>trace1</samp>’, and ‘<samp>prot</samp>’. The
latter is used by remote mailbox support libraries.
</p>
</dd>
<dt>auth</dt>
<dd><p>Enables debugging information about authentication and authorization.
This category supports the following levels: ‘<samp>error</samp>’,
‘<samp>trace0</samp>’, ‘<samp>trace1</samp>’, and ‘<samp>trace2</samp>’.
</p>
<p>In level ‘<samp>trace0</samp>’, user data are reported along with the
<em>data source</em> they were obtained from. The output may look like this:
</p>
<div class="example">
<pre class="example">pop3d: source=system, name=gray, passwd=x, uid=120, gid=100,
gecos=Sergey Poznyakoff, dir=/home/gray, shell=/bin/bash,
mailbox=/var/mail/gray, quota=0, change_uid=1
</pre></div>
<p>In the ‘<samp>trace1</samp>’ level, additional flow traces are displayed.
</p>
<p>In the level ‘<samp>trace2</samp>’, a detailed flow trace is displayed, which
looks like the following:
</p>
<div class="example">
<pre class="example">pop3d: Trying generic...
pop3d: generic yields 38=Function not implemented
pop3d: Trying system...
pop3d: system yields 0=Success
pop3d: Trying generic...
pop3d: generic yields 4135=Authentication failed
pop3d: Trying system...
pop3d: system yields 0=Success
</pre></div>
</dd>
<dt>mailer</dt>
<dd><p>Debugs mailer operations. The following levels are supported:
</p>
<dl compact="compact">
<dt>error</dt>
<dd><p>Displays mild error conditions.
</p></dd>
<dt>trace0</dt>
<dd><p>Traces mailer operations in general: displays what part of the message
is being sent, etc.
</p></dd>
<dt>trace6</dt>
<dd><p>When used together with ‘<samp>prot</samp>’, displays security-sensitive
information (such as passwords, user keys, etc). in plaintext. By
default, such information is replaced with asteriscs to reduce the
possibility of security compromise.
</p></dd>
<dt>trace7</dt>
<dd><p>When used together with ‘<samp>prot</samp>’, displays the <em>payload</em>
information as it is being sent. The <em>payload</em> is the actual
message contents, i.e. the part of SMTP transaction that goes after
the ‘<samp>DATA</samp>’ command and which ends with a terminating dot line.
Setting this level can generate huge amounts of information.
</p></dd>
<dt>prot</dt>
<dd><p>For SMTP mailer: outputs transcripts of SMTP sessions.
</p></dd>
</dl>
<p><em>Note:</em> Unless in a very secure environment, it is advised to
avoid using level settings such as mailer.prot or mailer (without
explicit level part), because the resulting output tends to be
extremely copious and reveals sender private and security-sensitive
data. If you wish to trace SMTP session flow, use ‘<samp>mailer.=prot</samp>’
or at least ‘<samp>mailer.prot,!trace6</samp>’.
</p>
</dd>
<dt>serve</dt>
<dd><p>This category provides debugging information for Mailutils IP
server objects. It supports the ‘<samp>error</samp>’ and ‘<samp>trace0</samp>’ levels.
</p>
</dd>
<dt>folder</dt>
<dd><p>This category controls debugging information shown for operations
related to Mailutils folders.
</p>
</dd>
<dt>remote</dt>
<dd><p>The remote category is used by <code>imap4d</code> and <code>pop3d</code>
servers to request showing additional information in the session
transcripts. This category takes effect only when the <code>transcript</code>
configuration variable is set. Valid levels are:
</p>
<dl compact="compact">
<dt>trace6</dt>
<dd><p>Show security-sensitive information (user passwords, etc.)
</p></dd>
<dt>trace7</dt>
<dd><p>Show payload information
</p></dd>
</dl>
</dd>
</dl>
<hr>
<div class="header">
<p>
Previous: <a href="Level-BNF.html#Level-BNF" accesskey="p" rel="prev">Level BNF</a>, Up: <a href="debugging.html#debugging" accesskey="u" rel="up">debugging</a> [<a href="index.html#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="Function-Index.html#Function-Index" title="Index" rel="index">Index</a>]</p>
</div>
</body>
</html>
|