search for: last_indexed_uid

...box using the "telnet localhost imap ... 3 SEARCH text "test" method as described on the dovecot wiki. Everything seemed to work. But when I used balsa to search a mailbox other than my inbox, I got no results. "doveadm dump" on the searched mailbox showed that "last_indexed_uid" to be the last uid of my inbox. Stopping dovecot, deleting out the dovecot-index* files, starting dovecot, and re-running "doveadm dump" showed a non-existant last_indexed_uid -- that is, last_indexed_uid did not show up in the dump output. Using the telnet method above to attempt...

...rote: > > >> Especially what is in the "fts" header vs. "next uid" header? Does the UID in "fts" header keep changing every time you save a new mail? I suppose it will. > > Diff between 2 emails: > next uid = 30104 | next uid = 30105 > last_indexed_uid = 30103 | last_indexed_uid = 30104 So Dovecot thinks it has indexed everything. >> You could also monitor (e.g. tcpdump/wireshark) the network traffic between Dovecot <-> Solr what happens when a new mail arrives. I suspect Dovecot sends it to Solr, which for whatever reason jus...

On 21 May 2018, at 14.11, kadafax at gmail.com wrote: > > Le 21/05/2018 ? 12:38, Aki Tuomi a ?crit : >> can you try turning on pluign { fts_enforced = yes } and repeat your test? > > Same (wrong) result: > 1. Send an email with "too6Ouka" in the body > > 2. Search against "too6Ouka": > # doveadm search -u username mailbox INBOX body too6Ouka

...t; header vs. "next uid" header? Does >>>> the UID in "fts" header keep changing every time you save a new >>>> mail? I suppose it will. >>> >>> Diff between 2 emails: >>> next uid = 30104 ???| ???next uid = 30105 >>> last_indexed_uid = 30103 ???| ???last_indexed_uid = 30104 >> >> So Dovecot thinks it has indexed everything. >> >>>> You could also monitor (e.g. tcpdump/wireshark) the network traffic >>>> between Dovecot <-> Solr what happens when a new mail arrives. I >>&gt...

...size . = 4 record_align = 4 -- Extension 4 -- name ........ = vsize hdr_size .... = 0 reset_id .... = 0 record_offset = 12 record_size . = 4 record_align = 4 -- Extension 5 -- name ........ = fts hdr_size .... = 12 reset_id .... = 0 record_offset = 0 record_size . = 0 record_align = 0 header - last_indexed_uid ..... = 30103 - settings_checksum .... = 0 -- Keywords -- 0 = unknown-1 1 = unknown-2 2 = unknown-5 3 = unknown-8 4 = unknown-6 5 = unknown-3 6 = unknown-7 7 = unknown-0 8 = NonJunk 9 = $Forwarded 10 = $label1 11 = $label2 12 = Junk 13 = $label3 14 = $label...

...is in the "fts" header vs. "next uid" header? Does >>> the UID in "fts" header keep changing every time you save a new mail? >>> I suppose it will. >> >> Diff between 2 emails: >> next uid = 30104 ???| ???next uid = 30105 >> last_indexed_uid = 30103 ???| ???last_indexed_uid = 30104 > > So Dovecot thinks it has indexed everything. > >>> You could also monitor (e.g. tcpdump/wireshark) the network traffic >>> between Dovecot <-> Solr what happens when a new mail arrives. I >>> suspect Dovecot...

...= (unknown: 4294957808)} #1 0x00007ffff489aade in rescan_clear_unseen_mailboxes (index=index at entry=0x555555822e20, rescan_ctx=rescan_ctx at entry=0x0) at lucene-wrapper.cc:863 iter = 0x55555588d530 info = <optimized out> vname = <optimized out> hdr = {last_indexed_uid = 0, settings_checksum = 3784394109, unused = 0} ns = 0x55555580f6c0 #2 0x00007ffff489b700 in lucene_settings_check (index=0x555555822e20) at lucene-wrapper.cc:429 set_checksum = <optimized out> ret = <optimized out> #3 lucene_index_build_init (index=0x55555582...