You guessed it, more Courier-IMAP with VPOPMAIL questions, sorry. :-(
System: RedHat 7.2 and RedHat 7.3
I've been working on this for two weeks and have read all the emails and
all the mail archives and all the instructions, and all the google.com
references I could find and nothing seems to be doing what I want.
I'm trying to get Courier-IMAP 1.5.3.20020813 working with VPOPMAIL 5.3.8.
I need to get system /etc/passwd (user/password) authentication for normal
system (shell) accounts, IP-ALIAS (user/password) authentication for virtual
accounts, which should fall back to ([EMAIL PROTECTED]/password)
authentication for virtual accounts as a last resort.
I can get system accounts working, no problem with Courier-IMAP. I can
get VPOPMAIL-userdb-Courier-IMAP working, but that doesn't do the
IP-ALIAS functions, i.e., it doesn't authenticate (user/password) when I
telnet virtual1.domain.com 110 and try to log in with user user1 with
pass user1Password.
Actually it appears that the Courier-IMAP authvchkpw program doesn't work
or at least is not working like I expected.
I've gone through so many configuration iterations my head is spinning.
I've tried several different ones every day for the last two weeks.
VPOPMAIL seems to be doing what it should...I'm just having terrible times
getting the COURIER-IMAP AUTHVCHKPW to work or do what I want.
I'm building from (modified) *.src.rpm files so I don't think that the
problem is a previous installation. I'm very careful to wipe out the
previous iteration of install before trying a new iteration.
Questions:
1. Am I missing something simple?
2. Is there a way to log more information from the Courier-IMAP authentication
methods?
3. Is there a way to use VPOPMAIL vchkpw authentication instead of
Courier-IMAP authchkpw authentication to work in Courier-IMAP and do
all three authentication methods?
4. What happens if there are multiple authentication programs installed?
Does it just go down the list trying until one works?
5. SSL compiles but stopped being enabled on startup when I upgraded from
Courier-IMAP 1.3.8 to 1.5.3. What configuration process determines
whether or not the SSL stuff is configured to start up when
/etc/init.d/courier-imap start is run?
I've been using Courier-IMAP with great success for over a year with
simple system accounts.
Here is my current VPOPMAIL configuration:
./configure \
--enable-ip-alias-domain=y \
--enable-qmail-ext=y \
--enable-roaming-users=y \
--enable-tcprules-prog=/bin/tcprules \
--enable-passwd=y
Here is my current Courier-IMAP configuration:
./configure \
--enable-workarounds-for-imap-client-bugs \
--with-ssl \
--with-pam \
--with-authvchkpw \
--without-authdaemon \
--without-authcustom \
--without-authcram \
--without-userdb \
--without-authshadow \
--without-authpwd
Much thanks in advance to anyone who would take the time to help me
out.
--
David Wayne Summers Linux: Because reboots are for upgrades!
[EMAIL PROTECTED] PGP Key: http://summersoft.fay.ar.us/~david/pgp.txt
PGP Key fingerprint = C0 E0 4F 50 DD A9 B6 2B 60 A1 31 7E D2 28 6D A8