Re: [Dovecot] problem with virtual plugin/index files?
Hello,
Timo: on Oct 29th I wrote
with latest 2.0.6 (601065674f74), the following virtual mailbox is not behaving correctly. I'm quite sure that the problem has not existed in some earlier 2.0.x (maybe only INBOX as mailbox then though):
~user/Maildir/virtual/.week/dovecot-virtual contains
INBOX INBOX.* -INBOX.Trash inthread refs younger 604800
This works as expected for the first time. But later on, also older messages/ threads are included until I delete the virtual/.week/dovecot.index*.
Just want to state that this problem still persists with latest version. Any idea?
Thanks and greetings, Lutz
-- Lutz Preßler <Lutz.Pressler@SerNet.DE> http://www.SerNet.DE/ SerNet Service Network GmbH, Bahnhofsallee 1b, D-37081 Göttingen Tel.: +49-551-370000-2, FAX: +49-551-370000-9 AG Göttingen, HRB 2816, GF: Dr. Johannes Loxen
On Thu, 2010-12-02 at 11:08 +0100, Lutz Preßler wrote:
I know there are problems related to this with INTHREAD, but they aren't very easy to solve and for now I've more important things to do.. If it seemed to work before, it was due to luck or due to some bug causing an unnecessary index rebuild. You could set :INDEX=MEMORY to work around this, but I don't know how much worse the performance would become. Or you could just manually delete the virtual indexes once a week.
Hello Timo,
virtual file with "inthread/younger" (other dynamic searches?) in it and indexes leading to too many (or too few?) search results.
On Do, 02 Dez 2010, Timo Sirainen wrote:
Thanks again for your work, Lutz
On 18.8.2012, at 0.12, Lutz Preßler wrote:
Just about the same amount of work I think. I haven't really looked at virtual plugin for a while, so I can't easily say how much work it would be. But my guess is that it wouldn't be easy.
On Thu, 23 Aug 2012, Timo Sirainen wrote:
Thanks. To force MEMORY indexes only (with location option in namespace or forcibly - with warnings - by having empty index files for one mailbox chattr +i'ed (extended attributes immutable flag on Linux filesystems)) disables full text search indexing also. What about regular deletion of main index files. Is this a problem with FTS? "doveadm fts rescan" necessary, too?
Btw, with 2.1 search results with or without fts indexes (solr,squat) differ in substring behaviour (http://wiki2.dovecot.org/Plugins/FTS/Squat). Namespaces with INDEX=MEMORY allow for a "slow search view". But then no attachment content is searched...
Lutz
participants (2)
-
Lutz Preßler
-
Timo Sirainen