Decpite having pwdb installed, pam is installed with default -pwdb, wich causes +pam with courer-imap not to work. I guess this is more a pam issue, but you shouldn't be able to install courier-imap with pam-support if your pam isn't working :) Reproducible: Always Steps to Reproduce: 1. angelica root # emerge -pv pwdb pam These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild R ] sys-libs/pwdb-0.62 -debug (-selinux) 0 kB [ebuild R ] sys-libs/pam-0.77-r1 +berkdb -debug -pwdb* (-selinux) 0 kB The * is just because I forced-install pam with pwdb (an then everything with courier and other apps started to work) 2. emerge courier-imap 3. Actual Results: Worked like a charm, but noone could log in through pam. Portage 2.0.51-r3 (default-x86-2004.2, gcc-3.3.4, glibc-2.3.4.20040808-r1, 2.4.27-grsec-2.0.1 i686) ================================================================= System uname: 2.4.27-grsec-2.0.1 i686 AMD Duron(tm) processor Gentoo Base System version 1.4.16 Autoconf: sys-devel/autoconf-2.59-r5 Automake: sys-devel/automake-1.8.5-r1 Binutils: sys-devel/binutils-2.14.90.0.8-r1 Headers: sys-kernel/linux-headers-2.4.21-r1 Libtools: sys-devel/libtool-1.5.2-r5 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O3 -march=i686 -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" COMPILER="" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/bind /var/qmail/alias /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O3 -march=i686 -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache distlocks sandbox" GENTOO_MIRRORS="http://ftp.du.se/pub/os/gentoo http://gentoo.oregonstate.edu http://www.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="apache2 apm arts avi berkdb bitmap-fonts chroot crypt curl encode f77 foomaticdb fortran gd gdbm gif gmp gpm gtk2 imap imlib ipv6 java jpeg libg++ libwww mad mailbox maildir mbox mcal mikmod motif mpeg mysql ncurses nls oggvorbis opengl oss pam pdflib perl png python quicktime readline ruby sasl sdl session slang snmp spamassassin spell ssl svga tcpd tiff truetype x86 xml2 xmms xv zlib"
which one doesn't work? pop3 or imap. Please attach your /etc/pam.d/pop3 and /etc/pam.d/imap to this bug. Also post the output of ` qpkg -f /etc/pam.d/pop3` and `qpkg -f /etc/pam.d/imap`
It's pop3 that require pwdb in pam. .~ > qpkg -f /etc/pam.d/pop3 net-mail/courier-imap * .~ > qpkg -f /etc/pam.d/imap net-mail/courier-imap * /etc/pam.d/pop3 #%PAM-1.0 auth required /lib/security/pam_pwdb.so shadow account required /lib/security/pam_pwdb.so password required /lib/security/pam_cracklib.so password required /lib/security/pam_pwdb.so nullok use_authtok md5 shadow session required /lib/security/pam_pwdb.so imap uses pam_stack.so
I think that /etc/pam.d/pop3 is from the old courier-imap. my courier-imap-3.0.8 has #%PAM-1.0 # # $Id: system-auth.authpam,v 1.1 2001/02/02 05:42:57 mrsam Exp $ # # Copyright 1998-2001 Double Precision, Inc. See COPYING for # distribution information. # # This is a sample authpam configuration file that uses pam_stack # (circa linux-pam 0.72). auth required pam_nologin.so auth required pam_stack.so service=system-auth account required pam_stack.so service=system-auth session required pam_stack.so service=system-auth It could be that when you upgraded, you didn't update your /etc/pam.d/pop3 you can check with `equery k courier-imap`
The k or check option isn't available in the "stable" gentoolkit, only in ~x86. But you might be right. Because I did do an upgrade from courier-imap 3.0.7, and I never tested pop3 with 3.0.7. Strange though, tested to do a new emerge of courier-imap, but it didn't prompt me if I wanted to change my "old" looking pop3-file with a newer one.
try `emerge --noconfmem courier-imap`
Sorry, haven't had time to look at this once more, as I fixed it manually. I guess this could be closed if not anybody else is having the same problem or can duplicate it.
I just upgraded to 4.0.1, and ran into the following problem: I can no longer log into my account. Not sure if this is a realted issue. What info do you need from me to examine the problem?
@ comment #7 file a new bug assign to netmail@g.o with emerge info, emerge courier-imap -vp, error messasges, mail log error messages, describe your imap setup. did you do etc-update and carefully merge configuration, init script?
@Comment #7 (Balarama Bosch) I've had the same problem and have entered a bug for it: bug 80879. Please add your comments!
moving this to a more reasonable location.
Discussion about #7 has been RESOLVED->WORKSFORME and there is nothing to do here. It wasn't really a bug so this is a RESOLVED->INVALID. Cheers, Ferdy
