Roland Schneider wrote:
Dear Schneider,
The maillog will have some entry - courier probably gets bad
values for $HOME, $UID or $DEFAULT (Maildir).
Then use the utility 'authtest' which comes with courier.
--- From authtest ---
[root@spacelab authlib]# ./authtest -s authvckpw dav...@domain.no test
Authenticated: module authvckpw
Home directory: /var/qmail/vpopmail/domains/domain.no/davidk
UID/GID: 89/89
AUTHADD=dav...@domain.no
AUTHFULLNAME=davidk
--- Catalog structure /var/qmail/vpopmail/domains/domain.no/ ---
[root@spacelab domain.no] # find
.
./.vpasswd.lock
./davidk
./davidk/Maildir
./davidk/Maildir/cur
./davidk/Maildir/new
./davidk/Maildir/tmp
./.qmail-default
./postmaster
./postmaster/Maildir
./postmaster/Maidir/new
./postmaster/Maildir/tmp
(all the files are owned by vpopmail.vchkpw and are chmoded 700)
Also, all the courier-imap prosesses are runned under root(UID 0)
--- Logs ---
The warning and errorlog doesn't say much, but when I tail the info log
it says this:
May 9 18:14:43 spacelab pop3d: Connection, ip=[::ffff:127.0.0.1] (when I
start the session)
May 9 18:14:55 spacelab pop3d: /usr/lib/courier/imap/bin/pop3d:
Permission denied (after I have written in my username and password)
The permission on pop3d is 755 and is owned by root.root.
I have worked on this problem the whole day so I hope the reason behind
this problem is obvious to some of the folks on this list.
But you dont need vpopmail at all for authentication via mySQL,
this functionality is already built into courier and makes life
much easier.
The main reason why I use vpopmail is to be able to have virtual
domains. All the domains are laying in the vpopmail home directory. As
you probably understand I am not that familiar with courier and have not
studied the topic you are touching now.
Can courier replace vpopmail completely and if so, where is the benefit?
1 message in net.sourceforge.lists.courier-usersRe: [courier-users] Problems with log...
