To match sqwebmail-4.0.3.20040509, here are some corrections to authlib/README.authdebug.html.in to reference the new sqwebmaild configuration file, and fix a couple of other minor errors.
Regards, Brian.
--- courier-imap-3.0.3.20040509.orig/authlib/README.authdebug.html.in Wed Apr 21 02:10:05 2004 +++ courier-imap-3.0.3.20040509/authlib/README.authdebug.html.in Tue May 11 09:37:14 2004 @@ -16,8 +16,9 @@ <h2>1. Turn on debugging</h2> <p> -For courier-imap, you need to set one of the following values in [EMAIL PROTECTED]@/pop3d and/or @sysconfdir@/imapd: +Set one of the following values in the configuration file +<code>@sysconfdir@/pop3d</code>, <code>@sysconfdir@/imapd</code> or +<code>@sysconfdir@/sqwebmaild</code> as appropriate: </p> <pre> @@ -25,12 +26,20 @@ DEBUG_LOGIN=2 # turn on authentication debugging AND show passwords </pre> -<p>and then restart the daemons. For sqwebmail, you can either put this in [EMAIL PROTECTED]@/authdaemonrc, or you can start sqwebmail like this:</p> +<p>Then restart the relevant daemons using pop3d.rc, imapd.rc or +sqwebmaild.rc, for example:</p> +<pre> [EMAIL PROTECTED]@/sqwebmaild.rc stop [EMAIL PROTECTED]@/sqwebmaild.rc start +</pre> + +<p>These scripts also restart authdaemond and pass the DEBUG_LOGIN +environment variable from the configuration file. If for some reason you are +starting authdaemond manually, then it is up to you to set the environment +variable yourself:</p> <pre> # DEBUG_LOGIN=1 @libexecdir@/authlib/authdaemond start -# DEBUG_LOGIN=1 @libexecdir@/sqwebmail/sqwebmaild start </pre> <p> @@ -54,18 +63,6 @@ # killall -1 syslogd </pre> -<p> -If you don't want to mess around with your syslog configuration, you can -also get authdaemond to log to a file. Just change the last line of [EMAIL PROTECTED]@/authlib/authdaemond as follows: -</p> - -<pre> -exec $DIR/$AUTHDAEMOND -stderr=/var/tmp/authdaemond.log $1 -# was: -# exec $DIR/$AUTHDAEMOND -stderrlogger=${sbindir}/courierlogger -stderrloggername=$AUTHDAEMOND $1 -</pre> - <h2>2. Issue a manual login</h2> <p> @@ -111,6 +108,7 @@ a number of standalone <b>client modules</b> which are executed, one after the other, resulting in one of three conditions: </p> +<dl> <dt>ACCEPT</dt> <dd>The user was authenticated successfully</dd> <dt>REJECT</dt> @@ -120,6 +118,7 @@ <dd>The module suffered an internal failure, such as inability to contact an external database. The login is rejected, and no further modules are tried.</dd> +</dl> <p> In a typical courier installation, there is only one client module: @@ -134,12 +133,9 @@ </p> <pre> -[ pop3d/imapd client: @sysconfdir@/pop3d and @sysconfdir@/imapd ] +[ client config file: @sysconfdir@/pop3d, imapd or sqwebmaild ] AUTHMODULES="authdaemon" -[ sqwebmail client: @sysconfdir@/authmodulelist ] -authdaemon - [ authdaemond server: @sysconfdir@/authdaemonrc ] authmodulelist="authpam authuserdb" </pre> @@ -215,6 +211,7 @@ <p>Why "authdaemond.plain"? Well, in fact you can have up to four separate authdaemond modules built:</p> +<dl> <dt>authdaemond.plain</dt> <dd>Contains the non-database modules (e.g. authpam, authuserdb, authcram, authpwd)</dd> @@ -224,6 +221,7 @@ <dd>Same as authdaemond.plain but also contains authmysql</dd> <dt>authdaemond.pgsql</dt> <dd>Same as authdaemond.plain but also contains authpgsql</dd> +</dl> <p>They are separated this way to make it easier to package and distribute the software, although it does mean that you can't have a single @@ -242,7 +240,7 @@ <h2>4. Read the documentation</h2> <p> -Most of the configuration files like authldaprc, authmysql are well +Most of the configuration files like authldaprc, authmysqlrc are well documented with comments. </p> @@ -264,7 +262,7 @@ If you are using userdb authentication, you definitely need to read <a href="http://www.courier-mta.org/makeuserdb.html">man makeuserdb</a>, <a href="http://www.courier-mta.org/userdb.html">man userdb</a>, and -<a href="http://www.courier-mta.org/userdbpw.html">man userdb</a>. +<a href="http://www.courier-mta.org/userdbpw.html">man userdbpw</a>. </p> <h2>5. Use the mailing list</h2> @@ -294,8 +292,7 @@ against, e.g. vpopmail, openldap, mysql, pgsql</li> <li>The transcript of the 'telnet' session you used to test [courier-imap]</li> <li>The corresponding debug output which was generated for that session</li> -<li>The contents of the 'pop3d' and 'imapd' configuration files [courier-imap]</li> -<li>The contents of the 'authmodulelist' configuration file [sqwebmail]</li> +<li>The contents of the 'pop3d', 'imapd' or 'sqwebmaild' configuration files</li> <li>The contents of the any other relevant configuration files, e.g. authldaprc, authmysqlrc</li> <li>A copy of the database entry you are trying to authenticate against: @@ -347,6 +344,9 @@ <pre> # @libexecdir@/authdaemon<b>d</b> start </pre> +However, current versions of courier-imap/sqwebmail do not require you to +start authdaemond yourself; pop3d.rc, imapd.rc and sqwebmaild.rc handle this +for you. </p> <h3>I get logged "pop3d: @libexecdir@/authlib/authfoo: No such file or directory"</h3> @@ -355,9 +355,9 @@ <pre> AUTHMODULES="authdaemon" </pre> -in the pop3d/imapd configuration files. This is the client which talks to -authdaemond, and it's the only standalone module you will get. All the other -authentication modules are compiled into authdaemond. +in the pop3d/imapd/sqwebmaild configuration files. This is the client which +talks to authdaemond, and it's the only standalone module you will get. All +the other authentication modules are compiled into authdaemond. <br /> To change the authentication modules used, you need to edit authdaemonrc and set the 'authmodulelist' parameter. @@ -400,16 +400,16 @@ # ./configure --with-authmsql --with-mysql-libs=/usr/local/mysql/lib \ --with-mysql-includes=/usr/local/mysql/include </pre> +</p> <p> -On some systems (e.g. FreeBSD), the mysqlclient library dpends on the math +On some systems (e.g. FreeBSD), the mysqlclient library depends on the math and compression libraries. For these systems, try: </p> <pre> # LDFLAGS="-lm -lz" ./configure --with-authmysql ... same as before </pre> -</p> </body> </html>