Hi all,
I'm new on the list and I've got a problem that archive, Google, and brain
searches have failed to rectify:
My server has existing "/etc/passwd" accounts with existing e-mail traffic.
I've just added vpopmail to simplify future account administration since the
server's usage is increasing. I would like to continue to support system
accounts in addition to vpopmail accounts, at least for awhile.
I've attempted to use vchkpw to authenticate both system (/etc/passwd) accounts
and virtual (vpopmail) accounts, as vchkpw's documentation suggests it will
do. Unfortunately, my system accounts can not authenticate via vchkpw as
called by both IMAP and SMTP-AUTH services. Virtual accounts authenticate
correctly to both mechanisms.
I'm running Qmail-1.03 (Patches: badrcptto, Krzysztof Dabrowski's
smtp-auth); Vpopmail 5.2.2; Courier-IMAP 2.2.0 (using authvchkpw module);
all on a RedHat 8.0 system.
The obligatory 'run' script snippet:
exec /usr/local/bin/softlimit -m 4000000 \
tcpserver -v -H -R -l "$LOCAL" -x /etc/tcp.smtp.cdb \
-u $VPMUID -g $VPMGID 0 smtp \
/var/qmail/bin/qmail-smtpd $LOCAL /home/vpopmail/bin/vchkpw \
/bin/true
(VPMUID and VPMGID are set to the vpopmail uid and vchkpw gid. LOCAL is the
FQDN of the server).
I've found that authentication via [EMAIL PROTECTED] passes/fails correctly
to both IMAP and SMTP. Authentication via a 'systemusername' or
'systemusername@' results in vpopmail logging a "user not found" message.
If I add the 'authpam' module into courier-imap's configuration, both system
and virtual accounts will authenticate. SMTP-AUTH still fails, of course.
I found info on google about making sure vchkpw is running with sufficient
permissions to access /etc/shadow and believe I have that correctly
implemented.
So, my question in a nutshell is: Does vchkpw really handle both system and
virtual accounts, and if so, what might I be doing wrong to keep it from
working as advertised?
If you've even gotten this far, thanks for your time!
Cheers,
Paul Robinson
gotclue.net
