Thank you Aki, for your quick response.
*dovecot-shared* file flag should actually enable the *INDEXPVT *setting
in the NameSpace for each mailbox it has been created in, as it did for
INDEX setting.
Below folows the output of the `dovecot -n` command:
> On 29/03/2021 02:28 Panayiotis Fafakos wrote:
>
>
> Dear Timo,
>
> we have successfully used dovecot-shared file flag in
> MaildirPublicNameSpaces with private index files, to have per-user-seen flags
> for some but not all mailboxesunder public folders.
> This was actually done on old
yes, this is getting to a mess
Details can be seen here :
https://github.com/grosjo/fts-xapian/issues/72
It shows that sometimes mailbox_list_get_root_forced return the generic
INDEX value, sometimes the namespace value
thank you for your help
On 2021-03-28 12:03, Aki Tuomi wrote:
Hi!
m
Dear Timo,
we have successfully used *dovecot-shared* file flag in *Maildir
**Public *NameSpaces with private index files, to have per-user-seen
flags for some but not all *mailboxes *under public folders.
This was actually done on older dovecot versions (i.e *dovecot
v2.2.33.2*) , using a *lo
Any update on this? Dovecot 2.3.14 makes doveadm altmove -r functional?
De: dovecot en nombre de María Arrea
Enviado: Monday, March 22, 2021 3:15:13 PM
Cc: dovecot@dovecot.org
Asunto: Re: Question about doveadm altmove
zlib plugin, as far as I know, only suppo
Hi
Anyone on that ?
Thank you so much
On 2021-03-22 18:16, Joan Moreau wrote:
Hi
The function mailbox_list_get_root_forced returns sometimes the first
or the second value of the INDEX param for the same mailbox.
How to make sure this returns only the correct one of the corresponding
mail
Hi!
mail_location = maildir:/var/vmail/%d/%n:LAYOUT=fs:INDEX=/var/mailindex
This is going to put everyone's indexes under /var/mailindex, without
separating them properly. Might cause fun issues.
Can you give an concrete example of what your issue is?
Aki
> On 28/03/2021 13:35 Joan Moreau wr
