[Dovecot] dovecot-shared
I'm confused about dovecot-shared.
If the file exists, \SEEN flags are NOT shared?
So if dovecot-shared exists, flags are actually private. The doc seems clear on this (albeit not worded very well). I only question it because intuitively you would think the opposite. If backwards compatibility is the reason for this reverse behavior, the file should have been named dovecot-private-flags. In fact that's a great name to stick a list of flags (one-per-line) that are private.
-frnak
On 28.12.2009, at 2.08, Frank Cusack wrote:
I'm confused about dovecot-shared.
If the file exists, \SEEN flags are NOT shared?
Right.
So if dovecot-shared exists, flags are actually private. The doc seems clear on this (albeit not worded very well). I only question it because intuitively you would think the opposite. If backwards compatibility is the reason for this reverse behavior, the file should have been named dovecot-private-flags.
I was thinking it more like "if this file exists, it's a shared mailbox, so there are many users reading it, so each user should have their own private (seen) flags".
In fact that's a great name to stick a list of flags (one-per-line) that are private.
Yeah, that's been in todo for a while. I'd probably make dovecot-shared file have options:
private = \Seen Spam NotSpam shared = \Answered default = private # or shared
Of course if default is private there's not much point in specifying the private flags and vice versa for shared..
On December 29, 2009 1:59:53 AM -0500 Timo Sirainen tss@iki.fi wrote:
Yeah, that's been in todo for a while. I'd probably make dovecot-shared file have options:
I was just thinking today it would be nice to have per-USER private or shared. So e.g. all users by default might share \Seen \Answered but some admin users have private \Seen, and don't have to worry about resetting the \Seen flag when investigating for problems.
This can be done already in a limited fashion with the 's' ACL (remove it for said admin users in the case above), but perhaps annoying if your mail client presents an error dialog when it fails to set the \Seen flag.
-frank
On Tue, 2009-12-29 at 03:03 -0500, Frank Cusack wrote:
On December 29, 2009 1:59:53 AM -0500 Timo Sirainen tss@iki.fi wrote:
Yeah, that's been in todo for a while. I'd probably make dovecot-shared file have options:
I was just thinking today it would be nice to have per-USER private or shared. So e.g. all users by default might share \Seen \Answered but some admin users have private \Seen, and don't have to worry about resetting the \Seen flag when investigating for problems.
Are you still talking about shared mailboxes, or also users' private mailboxes?
This can be done already in a limited fashion with the 's' ACL (remove it for said admin users in the case above), but perhaps annoying if your mail client presents an error dialog when it fails to set the \Seen flag.
I'm too lazy to verify now, but I think Dovecot sends an OK reply even if it doesn't have permissions to update flags, exactly because a NO reply would cause clients to show annoying popups.
On December 29, 2009 4:49:56 PM -0500 Timo Sirainen tss@iki.fi wrote:
On Tue, 2009-12-29 at 03:03 -0500, Frank Cusack wrote:
On December 29, 2009 1:59:53 AM -0500 Timo Sirainen tss@iki.fi wrote:
Yeah, that's been in todo for a while. I'd probably make dovecot-shared file have options:
I was just thinking today it would be nice to have per-USER private or shared. So e.g. all users by default might share \Seen \Answered but some admin users have private \Seen, and don't have to worry about resetting the \Seen flag when investigating for problems.
Are you still talking about shared mailboxes, or also users' private mailboxes?
shared (public) mailboxes.
This can be done already in a limited fashion with the 's' ACL (remove it for said admin users in the case above), but perhaps annoying if your mail client presents an error dialog when it fails to set the \Seen flag.
I'm too lazy to verify now, but I think Dovecot sends an OK reply even if it doesn't have permissions to update flags, exactly because a NO reply would cause clients to show annoying popups.
it probably does, seeing how my mail client doesn't complain.
-frank
On December 29, 2009 3:03:56 AM -0500 Frank Cusack fcusack@fcusack.com wrote:
I was just thinking today it would be nice to have per-USER private or shared. So e.g. all users by default might share \Seen \Answered but some admin users have private \Seen, and don't have to worry about resetting the \Seen flag when investigating for problems.
Perhaps not such a good idea, as I just realized there is then a conflict on deciding which flags are set. Do the shared flags take precedence, so that when you enter a mailbox you see the effects of previous action? Of course that doesn't make sense b/c then there's no point of private flags but if used for admin purposes as I suggest, you never see the mailbox as other users see it (wrt the private flags).
Which brings me to another question. How is the filename manipulated when there are private flags? I wrote a cron job for a previous case I mentioned where flags are shared, to "expunge" messages from a shared mailbox which is on a different filesystem than the users' and the lazy_expunge plugin is in effect. It looks for :2,*T* in the filename. I suppose it wouldn't make sense to make the T flag private but I'm curious.
-frank
participants (2)
-
Frank Cusack
-
Timo Sirainen