PAM problem with Courier

[Stefan Hornburg <racke@linuxia.de>]

Hello, Debian developers !

As some of you have noticed, I'm resp. my company works on a complete
Courier package which eventually replaces the imap-only package.
I'm trying to get authentification with MySQL to get work with PAM
instead of the courier-authmysql module. I installed the
libpam-mysql module from woody.

Any access with a existing local user comes through to the PAM 
modules, other accesses are failing before PAM is tried.

Hints are welcome, relevant config file see below.

Ciao
        Racke

/etc/pam.d/pop3
#%PAM-1.0
#
# $Id: pop3d.authpam,v 1.1 2000/10/06 02:19:19 mrsam Exp $
#
# Copyright 1998 - 1999 Double Precision, Inc.  See COPYING for
# distribution information.
#
# To use the authpam authentication module with courierpop3d, you must
# configure your PAM library to authenticate the "pop3" service.
# See your system documentation for information on how to configure your
# PAM services. In most cases, all you need to do is to install this file
# as /etc/pam.d/pop3, but check your system documentation to make sure.

auth	   required	/lib/security/pam_warn.so
auth       requisite	/lib/security/pam_mysql.so host=localhost database=snailrace user=racke password=nevairbe table=users usercol=id passwordcol=crypt crypt=y

/etc/courier/pop3d
##VERSION: $Id: pop3d.dist.in,v 1.1 2000/12/10 18:02:12 mrsam Exp $
#
# pop3d created from pop3d.dist by sysconftool
#
# Do not alter lines that begin with ##, they are used when upgrading
# this configuration.
#
#  Copyright 1998 - 2000 Double Precision, Inc.  See COPYING for
#  distribution information.
#
#  Courier POP3 daemon configuration
#
##NAME: install_prefix:0
#
#  This is read by /usr/sbin/pop3d
#
#  The following settings shouldn't be changed.

prefix=/usr
exec_prefix=/usr
sbindir="/usr/sbin"

##NAME: PIDFILE:0
#

PIDFILE=/var/run/courier/pop3d.pid

##NAME: MAXDAEMONS:0
#
#  Maximum number of POP3 servers started
#

MAXDAEMONS=40

##NAME: MAXPERIP:4
#
#  Maximum number of connections to accept from the same IP address

MAXPERIP=4

##NAME: AUTHMODULES:0
#
#########################################################################
##
## Authentication modules which attempt to validate userid/password
## combinations.  See authpam(8) for more information.  The default set
## is installed at configuration time.  You may have to edit the following
## to remove unnecessary authentication modules.  In particular, if
## authpam is included in the list below, you will have to remove authpwd
## and authshadow, since their functionality is included in the authpam
## module.
##
#########################################################################

AUTHMODULES="authpam"

##NAME: POP3AUTH:0
#
# To advertise the SASL capability, per RFC 2449, uncomment the POP3AUTH
# variable:
#
# POP3AUTH="LOGIN"


##NAME: POP3AUTH_TLS:0
#
# To also advertise SASL PLAIN if SSL is enabled, uncomment the
# POP3AUTH_TLS environment variable:
#
# POP3AUTH_TLS="LOGIN PLAIN"


##NAME: PORT:0
#
# Port to listen on for connections.  Default is port 110

PORT=110

##NAME: ADDRESS:0
#
# IP address to listen on.  0 means all IP addresses.

ADDRESS=0

##NAME: TCPDOPTS:0
#
# Other couriertcpd(1) options.  The following defaults should be fine.
#

TCPDOPTS="-nodnslookup -noidentlookup"

##NAME: POP3DSTART:0
#
# POP3DSTART is not referenced anywhere in the standard Courier programs
# or scripts.  Rather, this is a convenient flag to be read by your system
# startup script in /etc/rc.d, like this:
#
#  prefix=/usr
#  exec_prefix=/usr
#  . ${sysconfdir}/pop3d
#  case x$POP3DSTART in
#  x[yY]*)
#        /usr/sbin/pop3d start
#        ;;
#  esac
#
# The default setting is going to be NO, until Courier is shipped by default
# with enough platforms so that people get annoyed with having to flip it to
# YES every time.

POP3DSTART=YES