[Dovecot] question regarding rw-access on mailbox on creation/login (dovecot 1.2.17)
skdovecot at smail.inf.fh-brs.de
Wed Mar 6 12:35:56 EET 2013
-----BEGIN PGP SIGNED MESSAGE-----
On Wed, 6 Mar 2013, Götz Reinicke - IT Koordinator wrote:
> currently I have one new user with a problem. When she logs in to
> dovecot with pop3 from her apple mail, dovecot tells problems with the
> +w permission.
> Error: open(/var/mail/******) failed: Permission denied
> (euid=3462(******) egid=548(dozenten) missing +w perm: /var/mail)
> /var/mail is rw by root.mail
Does /var/mail/****** already exist? Do you have a mbox there and Dovecot
needs to create a lock file there? If so, try flock.
# Which locking methods to use for locking mbox. There are four available:
# dotlock: Create <mailbox>.lock file. This is the oldest and most
# solution. If you want to use /var/mail/ like directory, the
# will need write access to that directory.
# dotlock_try: Same as dotlock, but if it fails because of permissions or
# because there isn't enough disk space, just skip it.
# fcntl : Use this if possible. Works with NFS too if lockd is used.
# flock : May not exist in all systems. Doesn't work with NFS.
# lockf : May not exist in all systems. Doesn't work with NFS.
# You can use multiple locking methods; if you do the order they're
# in is important to avoid deadlocks if other MTAs/MUAs are using multiple
# locking methods as well. Some operating systems don't allow using some
# them simultaneously.
#mbox_read_locks = fcntl
#mbox_write_locks = dotlock fcntl
dotlock will fail in your system.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
-----END PGP SIGNATURE-----
More information about the dovecot