On Dec 16, 2005, at 1:20 pm, Chris Wakelin wrote:
Looks like you're using version 1.0-stable (judging by the passdb/authdb option format). I'd recommend upgrading to 1.0alpha5 (which, actually, is probably more stable!). One of the features added to 1.0 alphas is a "-session" option to PAM authentication... which ought to trigger your mkhomedir module.
That's great, thanks!
I meant to say in my original posting what version of Dovecot I'm using
- of course I just installed the version marked "stable" on my distro (Gentoo) but 1.0alpha5 is also available in Portage, so upgrading wasn't a problem.
However I now have another issue:
dovecot: Dec 16 19:05:00 Info: imap-login: Login: user=<ned>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured dovecot: Dec 16 19:05:00 Error: imap(ned): mkdir(/home/DOMAIN/ned/.maildir/cur) failed: Permission denied dovecot: Dec 16 19:05:00 Info: imap-login: Login: user=<ned>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured dovecot: Dec 16 19:05:00 Error: imap(ned): mkdir(/home/DOMAIN/ned/.maildir/cur) failed: Permission denied dovecot: Dec 16 19:05:00 Error: imap(ned): mkdir(/home/DOMAIN/ned/.maildir/.INBOX.Sent) failed: Permission denied dovecot: Dec 16 19:05:00 Info: imap-login: Login: user=<ned>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured dovecot: Dec 16 19:05:00 Error: imap(ned): mkdir(/home/DOMAIN/ned/.maildir/cur) failed: Permission denied dovecot: Dec 16 19:05:00 Error: imap(ned): mkdir(/home/DOMAIN/ned/.maildir/cur) failed: Permission denied
I can remedy this easily by changing permissions on /home & /home/DOMAIN to 777, but obviously that's undesirable. Any suggestions, please?
I would have assumed that something clever went on in the background, ensuring that Dovecot &/or pam_mkhomedir had permission to make the new home directory. Otherwise, how does SSH manage it?
Stroller.