search for: listindex

...Used to update folder's size in dovecot.index. So the worst that can happen is that the vsize becomes wrong. If you're using quota=count, it could become wrong. But this gets fixed automatically anyway later on. * autoexpunge.lock : Only used if you have autoexpunge settings. > - Would LISTINDEX indexes be regenerated properly for mdbox if lost/corrupted? Properly, meaning without losing flags, message numbering or some other vital data. If yes, then I assume they can be stored on local storage per server, and not on NFS. If LISTINDEX can be regenerated, will LISTINDEX be updated if it'...

Hello, I'm using dovecot on my personal / private email server. I have set up virtual mailboxes in my inbox namespace like this: namespace inbox { inbox = yes prefix = "Virtual/" separator = / location = "virtual:~/.emails_virtual:LAYOUT=fs:INDEX=dovecot.virtual.index:LISTINDEX=dovecot.virtual.list.index" list = yes subscriptions = yes mailbox { auto = subscribe } } I had quite some trouble with it at first with UIDs changing all the time, but after adding INDEX and LISTINDEX it started to work just fine. I've created dovecot_virtual files like this...

...her files that don't need to exist permanently. The path could point to tmpfs for example. This is especially useful to avoid creating lock files to NFS or other remote filesystems. For example: mail_location=sdbox:~/sdbox:VOLATILEDIR=/tmp/volatile/%2.256Nu/%u + mail_location's LISTINDEX=<path> can now contain a full path. This allows storing mailbox list index to a different storage than the rest of the indexes, for example to tmpfs. + mail_location can now include NO-NOSELECT parameter. This automatically deletes any \NoSelect mailboxes that have no children. T...

...her files that don't need to exist permanently. The path could point to tmpfs for example. This is especially useful to avoid creating lock files to NFS or other remote filesystems. For example: mail_location=sdbox:~/sdbox:VOLATILEDIR=/tmp/volatile/%2.256Nu/%u + mail_location's LISTINDEX=<path> can now contain a full path. This allows storing mailbox list index to a different storage than the rest of the indexes, for example to tmpfs. + mail_location can now include NO-NOSELECT parameter. This automatically deletes any \NoSelect mailboxes that have no children. T...

...pfs for example. This is especially useful to avoid creating lock > files to NFS or other remote filesystems. For example: > mail_location=sdbox:~/sdbox:VOLATILEDIR=/tmp/volatile/%2.256Nu/%u Is "/tmp/volatile" auto-created, or must be pre-created? > + mail_location's LISTINDEX=<path> can now contain a full path. > This allows storing mailbox list index to a different storage > than the rest of the indexes, for example to tmpfs. Is this in any way related to VOLATILEDIR? Can they be set to the same value without problems? > + mail_location can now...

It seems MemorySSA.cpp is the only real code where we found the problem happening. Is it possible to change the source of MemorySSA.cpp to hide the problem and buy some time for now? Now we use an empty generic_def_path_iterator with Optional<ListIndex> N being initialized by None as the end of range. Can we initialize the Optional var with a special value instead of None? iterator_range<def_path_iterator> def_path(ListIndex From) { return make_range(def_path_iterator(this, From), def_path_iterator()); } On Mon, Jul 17, 2017 a...

...w dumb questions: - I assume VOLATILEDIR can't be used with configurations where multiple servers access the same mdbox because lockfiles need to be shared as well? Or does this option touch only some (lock)files that do not need to be shared between servers accessing same mailbox? - Would LISTINDEX indexes be regenerated properly for mdbox if lost/corrupted? Properly, meaning without losing flags, message numbering or some other vital data. If yes, then I assume they can be stored on local storage per server, and not on NFS. If LISTINDEX can be regenerated, will LISTINDEX be updated if it...

...er <leithner at itronic.at> wrote: > Any idea why this doesn't setup work anymore in 2.2.32? > > thx > > Harald > > I just ran into the same thing myself. For me, when I added this to the "location" in the expunged namespace, it started working again: ...:LISTINDEX=expunged.list.index I can't tell you why exactly (presumably has something to do with "mailbox_list_index = yes"). Perhaps the devs might know?

...l code where we found the >> problem happening. > > > This is doubtful, ¸FWIW :) > >> >> Is it possible to change the source of >> MemorySSA.cpp to hide the problem and buy some time for now? Now we >> use an empty generic_def_path_iterator with Optional<ListIndex> N >> being initialized by None as the end of range. Can we initialize the >> Optional var with a special value instead of None? >> >> iterator_range<def_path_iterator> def_path(ListIndex From) { >> return make_range(def_path_iterator(this, From), def_pa...

...her files that don't need to exist permanently. The path could point to tmpfs for example. This is especially useful to avoid creating lock files to NFS or other remote filesystems. For example: mail_location=sdbox:~/sdbox:VOLATILEDIR=/tmp/volatile/%2.256Nu/%u + mail_location's LISTINDEX=<path> can now contain a full path. This allows storing mailbox list index to a different storage than the rest of the indexes, for example to tmpfs. + mail_location can now include NO-NOSELECT parameter. This automatically deletes any \NoSelect mailboxes that have no children. T...

...her files that don't need to exist permanently. The path could point to tmpfs for example. This is especially useful to avoid creating lock files to NFS or other remote filesystems. For example: mail_location=sdbox:~/sdbox:VOLATILEDIR=/tmp/volatile/%2.256Nu/%u + mail_location's LISTINDEX=<path> can now contain a full path. This allows storing mailbox list index to a different storage than the rest of the indexes, for example to tmpfs. + mail_location can now include NO-NOSELECT parameter. This automatically deletes any \NoSelect mailboxes that have no children. T...

...in 2.2.32? >>> >>> thx >>> >>> Harald >>> >>> >>> >> I just ran into the same thing myself. For me, when I added this to the >> "location" in the expunged namespace, it started working again: >> >> ...:LISTINDEX=expunged.list.index >> >> I can't tell you why exactly (presumably has something to do with >> "mailbox_list_index = yes"). Perhaps the devs might know? >> > > Thx, this seams to fixed the problem. > Dovecot guys, any idea why this was the case? I ju...

...= create special_use = \Sent } mailbox Archive { auto = create special_use = \Archive } } namespace lazyexpunge { prefix = .EXPUNGED/ hidden = yes list = children subscriptions = no separator = / location = mdbox:~/mdbox:INDEX=~/mdbox:MAILBOXDIR=expunged:LISTINDEX=expunged.list.index } ==================== Can see its working since can see files in the mdbox storage along with indexs etc ... but there seems little to no documentation on how to delete from the expunged namespace and atm trying to even search doesnt seem to work .. doveadm -Dvvv search -u m...

...namespace inbox { </div> <div> inbox = yes </div> <div> prefix = "Virtual/" </div> <div> separator = / </div> <div> location = "virtual:~/.emails_virtual:LAYOUT=fs:INDEX=dovecot.virtual.index:LISTINDEX=dovecot.virtual.list.index" </div> <div> list = yes </div> <div> subscriptions = yes </div> <div> mailbox { </div> <div> auto = subscribe </div> <div> } </div> <div>...

...> mailbox Archive { > auto = create > special_use = \Archive > } > > } > > namespace lazyexpunge { > prefix = .EXPUNGED/ > hidden = yes > list = children > subscriptions = no > separator = / > location = > mdbox:~/mdbox:INDEX=~/mdbox:MAILBOXDIR=expunged:LISTINDEX=expunged.list.index > } > > ==================== > > Can see its working since can see files in the mdbox storage along with > indexs etc ... but there seems little to no documentation on how to > delete from the expunged namespace and atm trying to even search doesnt > seem...

...) > >>> > >>>> > >>>> Is it possible to change the source of > >>>> MemorySSA.cpp to hide the problem and buy some time for now? > Now we > >>>> use an empty generic_def_path_iterator with Optional<ListIndex> N > >>>> being initialized by None as the end of range. Can we > initialize the > >>>> Optional var with a special value instead of None? > >>>> > >>>> iterator_range<def_path_iterator> def_path(ListIndex...

...special_use = \Archive >> } >> >> } >> >> namespace lazyexpunge { >> prefix = .EXPUNGED/ >> hidden = yes >> list = children >> subscriptions = no >> separator = / >> location = >> mdbox:~/mdbox:INDEX=~/mdbox:MAILBOXDIR=expunged:LISTINDEX=expunged.list.index >> } >> >> ==================== >> >> Can see its working since can see files in the mdbox storage along with >> indexs etc ... but there seems little to no documentation on how to >> delete from the expunged namespace and atm trying to...

...userdb namespace { inbox = yes list = yes prefix = separator = / } namespace expunged { hidden = yes inbox = no list = no prefix = EXPUNGED/ separator = / location = mdbox:/var/mail/.8d1/mail/4/03/xtra30:INDEX=/var/mail/.8d1/index/4/03/xtra30/index:MAILBOXDIR=expunged:LISTINDEX=expunged.list.index:SUBSCRIPTIONS=expunged.subscriptions ### also from userdb } plugin { lazy_expunge = EXPUNGED/ } ----8<----- (full doveconf available on request) State of the account before delete: mailbox "Test" exists, 20 messages in it: x LIST * * * LIST (\HasNoChildren \UnM...

...t; >>> >>> This is doubtful, ¸FWIW :) >>> >>>> >>>> Is it possible to change the source of >>>> MemorySSA.cpp to hide the problem and buy some time for now? Now we >>>> use an empty generic_def_path_iterator with Optional<ListIndex> N >>>> being initialized by None as the end of range. Can we initialize the >>>> Optional var with a special value instead of None? >>>> >>>> iterator_range<def_path_iterator> def_path(ListIndex From) { >>>> return make_ran...

...ric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext vacation-seconds mdbox_preallocate_space = yes namespace { hidden = yes list = no location = mdbox:/storage1/fast/%{userdb:path}:MAILBOXDIR=expunged:LISTINDEX=expunged.list.index:FULLDIRNAME=iTrNiCs-DBOx-mAiLs:INDEX=/storage1/indexes/vmail/%{userdb:path}:ALT=/storage1/slow/%{userdb:path}:VOLATILEDIR=/tmp/%{userdb:path} prefix = "#EXPUNGED/" subscriptions = no type = private } namespace { list = children location = mdbox:%%h/mdbox pr...