On Tue, 21 Jan 2003, Kamau Allan wrote:
> Thank you Matthew Crocker and Taymour A. El Erian. The error did indeed go
> away. After increasing the pop3's softlimit value.
> However I am still unable to login using pop3
>
> My login conversation is as follows,
>
> [aaron@development aaron]$ telnet localhost 110
> Trying 127.0.0.1...
> Connected to development (127.0.0.1).
> Escape character is '^]'.
> +OK <[EMAIL PROTECTED]>
> user [EMAIL PROTECTED]
> +OK
> pass aaron
> -ERR authorization failed
> Connection closed by foreign host.
Turn on debugging for the pop3 service and see what additional information
you can get.
in your run script add
DEBUGLEVEL=31
and modify the env command in the script to be:
exec /usr/bin/env - DEBUGLEVEL=$DEBUGLEVEL /usr/sbin/softlimit -m ....
then restart the service (svc -du /service/qmail-pop3)
from the docs (/var/qmail/doc/QLDAPINSTALL)
10. Debugging: as said befor you can compile qmail-lspawn and the auth
modules
with a flexible debugging facility (option DEBUG).
The debug output gets logged through splogger or your favorite logging
tool
connected to stderr for tcpserver-pop/imap chain.
To turn on debugging you need only to define the LOGLEVEL environment
variable (e.g. with env, env LOGLEVEL=3 qmail-start ...)
There are these LOGLEVEL:
LOGLEVEL=1 -> Errors
LOGLEVEL=2 -> Warnings
LOGLEVEL=4 -> Info
LOGLEVEL=8 -> Info^2
LOGLEVEL=16 -> Debug
LOGLEVEL=32 -> Debug^2
LOGLEVEL=64 -> LDAP Debug
LOGLEVEL=128 -> LDAP Debug^2
LOGLEVEL=256 -> PASSWD, this level is normaly off because it shows
critical data (unencrypted and crypted passwords). To
turn it on edit checkpassword.c and increase the level
for init_debug().
WARNING: on production machines don't use levels higher 3 or you will
get
incredible huge logfiles.
NOTE: too high debuglevels are reduced to the maximum allowed debug
level
if the level parameter in init_debug() is smaler.
The LOGLEVEL is compare with a bit mask, so that
LOGLEVEL=3 will report warnings and errors but LOGLEVEL=2 will
only report warnings.
With the new log support the environment variable is LOGLEVEL
but
the old DEBUGLEVEL is still supported.
The new log support will no longer add the log output to bounce
messages.
If you machine isn't in production yet try a value of '255' it will pretty
much show you everything that is going on.
-Matt
--
----------------------------------------------------------------------
Matthew S. Crocker
Vice President / Internet Division Email: [EMAIL PROTECTED]
Crocker Communications Phone: (413) 746-2760
PO BOX 710 Fax: (413) 746-3704
Greenfield, MA 01302-0710 http://www.crocker.com
----------------------------------------------------------------------
