6 messages in net.sourceforge.lists.courier-usersRe: [courier-users] All imapd user ma...
FromSent OnAttachments
Dan ShearerMar 14, 2002 1:49 pm 
Dan ShearerMar 15, 2002 6:03 pm 
Adam KellyMar 16, 2002 3:22 am 
Dan ShearerMar 16, 2002 3:49 am 
Mark ConstableMar 16, 2002 4:07 am 
Dan ShearerMar 16, 2002 4:32 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [courier-users] All imapd user maildirs in single directoryActions...
From:Dan Shearer (da@tellurian.com.au)
Date:Mar 16, 2002 4:32:48 am
List:net.sourceforge.lists.courier-users

On Sat, 16 Mar 2002, Mark Constable wrote:

I'm only familiar with auth-mysql but with it there is a field for "homedir" and "maildir" seperately

I wasn't very informative about this before. I think a better answer is that all the auth modules have these things available to them and a little more, by virtue of the auth callback that is registered taking a struct authinfo*. Here is authinfo:

struct authinfo { const char *sysusername; const uid_t *sysuserid; gid_t sysgroupid; const char *homedir;

const char *address; const char *fullname; const char *maildir; const char *quota;

const char *passwd; : :

which is in addition to the variables MAILDIR, MAILDIRQUOTA and AUTHENTICATED. So far I think that the authoritative source is meant to be the authinfo structure, and that variables other than AUTHENTICATED are not supposed to be relied upon within the authentication chain. Presumably the tcpd connect-time variables can be expected to be reliable.

However I am guessing because I really don't know anything about the courier code.