courier logs whatever the auth-module puts into $AUTHENTICATED:
fprintf(stderr, "INFO: LOGOUT, user=%s, ip=[%s],"
" headers=%lu, body=%lu\n",
getenv("AUTHENTICATED"), getenv("TCPREMOTEIP"),
Use one of the auth-module which comes with courier, or fix
vmailmgr (which also has a couple of other problems reported).
Do you know about other problems? What kind of?
The problem is:
We're using qmail with vmailmgrd (for virtual hosts) with pop & smtp. So we
decided to use courier-imap as an additional module because it's faster than
pop and we like the possbility to keep messages in folders or to mark them
as seen/deleted...
But we don't want to have a conf for vmailmgr (qmail) and another for imap.
We're just talking about a solution with qmail & SQL where every user (vdoms
too) is listed in the SQL-table. There are solution for qmail to handle this
(auth via SQL).
The Benefit is that users who want to connect via imap could be
authenticated through the auth-SQL too.
So we have only ONE database for the whole mail-system.
Is anybody using this? (or similiar?)
milli
15 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Re: courier-imap ...