On Tue, Jan 15, 2008 at 04:13:56PM -0600, Roddie Hasan wrote:
> >You may find that it works if the uid is given as a name, rather than a
> >number. (This depends on what backend database you're using)
>
> From my courier-authlib debugs, this is what I saw being passed:
>
> Jan 12 16:35:08 krweb a
Sam,
> Furthermore -- and this goes beyond the IMAP server -- an account's home
> directory's, and maildir's, ownership should match what's given as the
> account primary uid, gid. If the account is a member of some other, auxiliary
> group, that's fine but the account's home directory and mail
Roddie Hasan writes:
It seems to only happen to users that are in more than one group. Courier
appears to be using the GID from /etc/passwd to do its thing and is
running in to problems where a user's Maildir is in a different group than
the login group (in my case, it's in the group that the
Brian,
Thanks for the reply.
> Looking in numlib/changeuidgid.c I see that libmail_changeuidgid() does
> *not* call initgroups(), but libmail_changeusername() does.
>
> You may find that it works if the uid is given as a name, rather than a
> number. (This depends on what backend database you're
On Tue, Jan 15, 2008 at 10:01:53AM -0600, Roddie Hasan wrote:
> I hit this over the weekend upgrading from 4.2.0 to 4.3.0 - Some users
> (myself included) were getting the following (or similar) message in
> various IMAP clients (or running imapd in a shell):
>
> * BYE [ALERT] Fatal error: Accou
I hit this over the weekend upgrading from 4.2.0 to 4.3.0 - Some users
(myself included) were getting the following (or similar) message in
various IMAP clients (or running imapd in a shell):
* BYE [ALERT] Fatal error: Account's mailbox directory is not owned by the
correct uid or gid: No such