Re: [Dovecot] Incorrect response when opening read-only mailboxes with per-user flags?
unsubscribe On Wed, Mar 27, 2013 at 1:16 PM, Guido Berhoerster < guido+dovecot@berhoerster.name> wrote: > * Timo Sirainen [2013-03-27 20:27]: > > On 27.3.2013, at 13.41, Guido Berhoerster < > guido+dovecot@berhoerster.name> wrote: > > > > > After some debugging on the protocol level I've finally found the > > > problem with per-user seen flags in read-only mailboxes. Dovecot > > > actually does allow storing the seen flag on messages but AFAICS > > > it does not communicate that correctly to clients, this is what > > > its response to selecting a read-only mailbox with "lrs" ACL in > > > effect for the logged in user looks like: > > > > > > 2 SELECT "Public/Test" > > .. > > > 2 OK [READ-ONLY] Select completed. > > > > > > Shouldn't PERMANENTFLAGS contain \Seen here if per-user seen > > > flags are enable and should it even be tagged READ-ONLY at all in > > > this case? At least clients such as Python imaplib, IMAPClient, > > > or Roundcube will open such mailboxes with EXAMINE and thus do > > > not allow the modification of flags. > > > > Are you still testing on v2.0? It could be a bug in it. > > Yes, this is 2.0.9 from RHEL6. > -- > Guido Berhoerster >
Re: [Dovecot] Incorrect response when opening read-only mailboxes with per-user flags?
On 27.3.2013, at 22.16, Guido Berhoerster wrote: > * Timo Sirainen [2013-03-27 20:27]: >> On 27.3.2013, at 13.41, Guido Berhoerster >> wrote: >> >>> After some debugging on the protocol level I've finally found the >>> problem with per-user seen flags in read-only mailboxes. Dovecot >>> actually does allow storing the seen flag on messages but AFAICS >>> it does not communicate that correctly to clients, this is what >>> its response to selecting a read-only mailbox with "lrs" ACL in >>> effect for the logged in user looks like: >>> >>> 2 SELECT "Public/Test" >> .. >>> 2 OK [READ-ONLY] Select completed. >>> >>> Shouldn't PERMANENTFLAGS contain \Seen here if per-user seen >>> flags are enable and should it even be tagged READ-ONLY at all in >>> this case? At least clients such as Python imaplib, IMAPClient, >>> or Roundcube will open such mailboxes with EXAMINE and thus do >>> not allow the modification of flags. >> >> Are you still testing on v2.0? It could be a bug in it. > > Yes, this is 2.0.9 from RHEL6. I remember fixing this bug. There's a very good chance that it would simply work with v2.1.
Re: [Dovecot] Incorrect response when opening read-only mailboxes with per-user flags?
* Timo Sirainen [2013-03-27 20:27]: > On 27.3.2013, at 13.41, Guido Berhoerster > wrote: > > > After some debugging on the protocol level I've finally found the > > problem with per-user seen flags in read-only mailboxes. Dovecot > > actually does allow storing the seen flag on messages but AFAICS > > it does not communicate that correctly to clients, this is what > > its response to selecting a read-only mailbox with "lrs" ACL in > > effect for the logged in user looks like: > > > > 2 SELECT "Public/Test" > .. > > 2 OK [READ-ONLY] Select completed. > > > > Shouldn't PERMANENTFLAGS contain \Seen here if per-user seen > > flags are enable and should it even be tagged READ-ONLY at all in > > this case? At least clients such as Python imaplib, IMAPClient, > > or Roundcube will open such mailboxes with EXAMINE and thus do > > not allow the modification of flags. > > Are you still testing on v2.0? It could be a bug in it. Yes, this is 2.0.9 from RHEL6. -- Guido Berhoerster
Re: [Dovecot] Incorrect response when opening read-only mailboxes with per-user flags?
On 27.3.2013, at 13.41, Guido Berhoerster wrote: > After some debugging on the protocol level I've finally found the > problem with per-user seen flags in read-only mailboxes. Dovecot > actually does allow storing the seen flag on messages but AFAICS > it does not communicate that correctly to clients, this is what > its response to selecting a read-only mailbox with "lrs" ACL in > effect for the logged in user looks like: > > 2 SELECT "Public/Test" .. > 2 OK [READ-ONLY] Select completed. > > Shouldn't PERMANENTFLAGS contain \Seen here if per-user seen > flags are enable and should it even be tagged READ-ONLY at all in > this case? At least clients such as Python imaplib, IMAPClient, > or Roundcube will open such mailboxes with EXAMINE and thus do > not allow the modification of flags. Are you still testing on v2.0? It could be a bug in it.
