[Dovecot] Weird glitches with public folders - Dovecot not using per-user INDEX?

[Kádár Tamás (KTamas)]

sorry. Using the latest version (2.0.5) on Debian Lenny. Here's the
full output of dovecot -n:

mail:~# dovecot -n
# 2.0.5: /usr/local/etc/dovecot/dovecot.conf
# OS: Linux 2.6.26-2-xen-amd64 x86_64 Debian 5.0.6
auth_mechanisms = plain login
disable_plaintext_auth = no
listen = *
mail_debug = yes
mail_location = maildir:~/Maildir
mail_plugins = acl
maildir_very_dirty_syncs = yes
namespace {
  inbox = yes
  location =
  prefix =
  separator = .
  type = private
}
namespace {
  location = maildir:/home/_shared/projects:INDEX=~/Maildir/_shared
  prefix = shared.
  separator = .
  subscriptions = no
  type = public
}
passdb {
  driver = pam
}
plugin {
  acl = vfile
  mail_log_events = delete undelete expunge copy mailbox_delete
mailbox_rename flag_change append
  mail_log_fields = uid box msgid from subject size vsize flags
  mail_log_group_events = yes
}
protocols = imap pop3
service imap {
  executable = imap
}
ssl_cert = </etc/ssl/certs/dovecot.pem
ssl_key = </etc/ssl/private/dovecot.pem
userdb {
  driver = passwd
}
verbose_proctitle = yes
protocol imap {
  mail_max_userip_connections = 10
  mail_plugins = acl imap_acl
}

Best regards,
Tamas
On Sat, Oct 2, 2010 at 8:45 PM, Charles Marcus
<CMarcus at media-brokers.com> wrote:
> At a bare minimum, it is always a good idea to at least say what version
> you're using...
>
> On 2010-10-02 10:29 AM, Kádár Tamás (KTamas) wrote:
>> Hi
>>
>> I have this public folder:
>>
>> namespace {
>>   location = maildir:/home/_shared/projects:INDEX=~/Maildir/_shared
>>   prefix = shared.
>>   separator = .
>>   subscriptions = no
>>   type = public
>> }
>>
>> Access is controlled by ACLs, everyone who has access is 'lrwstipek'
>> except for some people who also have 'xa' privileges.
>>
>> As you can see it is set to put its index to the user's Maildir so
>> they can have per-user \Seen flags. And that is the case -- most of
>> the time anyway. But for some folders, and I can't figure out why
>> those, they just don't work: if someone sets a message read it
>> immediately becomes read for everyone else, too, and vice versa if
>> someone marks a message unread, it becomes unread everywhere. Further
>> investigation shows that in these problematic folders, indeed all
>> users directly manipulate the flag of the email (i.e. X marks email Z
>> read, ",S" appears immediatelly in the filename).
>>
>> Anyone knows what I'm doing wrong? I can't seem to find anything
>> different with these problematic folders, ACLs look right etc.
>
> --
>
> Best regards,
>
> Charles
>