That's strange. Dovecot anyway used access() system call to verify that the directory isn't writable. Some possibilities:
1. Did you enable SELinux / AppArmor or something similar that prevents
Dovecot from accessing home directories?
2. Some filesystem ACL was set to the home directory that prevents
writes? I don't really know anything about ACLs..
3. Are there multiple annaleins? Check with ls -ldn /home/annalein that
it's 1000.
I guess the last possibility is that Dovecot's check is just buggy. You
could get a strace output to see what Dovecot is really doing and send
it to me. You can do this by changing in dovecot.conf:
protocol pop3 {
..
mail_location = /usr/bin/strace -o /tmp/dovecot.log /usr/lib/dovecot/pop3
}
On Wed, 2009-05-20 at 11:19 +0200, Anna Obertacke wrote:
> Hi,
>
> that is not the problem
>
> drwxr-x--x 20 annalein annalein 12288 2009-05-18 19:05
> annalein
>
> /home/annalein is writable by annalein.
>
>
> Am 19.05.2009 um 21:46 schrieb Timo Sirainen:
>
> > On Tue, 2009-05-19 at 11:07 +0200, Anna Obertacke wrote:
> >> May 19 10:00:38 ubuntu dovecot: POP3(annalein):
> >> mkdir(/home/annalein/Maildir/cur) failed: Permission denied
> >> (euid=1000(annalein) egid=1000(annalein) missing +w perm: /home/
> >> annalein)
> >
> > It says /home/annalein isn't writable by annalein user. I'd
> > guess /home/annalein is no longer owned by annalein?
> >
>
signature.asc
Description: This is a digitally signed message part
