search for: hdr_field_name

...29.000000000 -0500 +++ dovecot-2.1.7/src/plugins/fts-lucene/lucene-wrapper.cc 2012-07-24 14:03:14.000000000 -0400 @@ -1094,7 +1094,7 @@ return false; q = lucene_get_query(index, - t_lucene_utf8_to_tchar(index, arg->hdr_field_name, FALSE), + t_lucene_utf8_to_tchar(index, t_str_lcase(arg->hdr_field_name), FALSE), arg); break; default: Now: B SEARCH TO TEST * SEARCH 1 2 3 4 5 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 24 26 27...

...args = 0x0, seqset = {arr = {buffer = 0x88ee4a8, element_size = 8}, v = 0x88ee4a8, v_modifiable = 0x88ee4a8}, str = 0x0, time = 0, size = 0, flags = 0, search_flags = 0, thread_type = MAIL_THREAD_NONE, keywords = 0x0, modseq = 0x0, search_args = 0x0, search_result = 0x0}, context = 0x0, hdr_field_name = 0x0, not = 0, match_always = 0, result = -1} ret = <value optimized out> __PRETTY_FUNCTION__ = "index_search_result_update_flags" #6 0xf7da937d in virtual_sync_backend_boxes (ctx=0x93f6660) at virtual-sync.c:733 _data_stack_cur_id = 4 i = 0 ret = 155151376 #7 0xf7daa25...

...= {subargs = 0x0, seqset = {arr = {buffer = 0x97a9528, element_size = 8}, v = 0x97a9528, v_modifiable = 0x97a9528}, str = 0x0, time = 0, size = 0, flags = 0, search_flags = 0, thread_type = MAIL_THREAD_NONE, keywords = 0x0, modseq = 0x0, search_args = 0x0, search_result = 0x0}, context = 0x0, hdr_field_name = 0x0, not = 0, match_always = 0, result = -1} ret = <value optimized out> __PRETTY_FUNCTION__ = "index_search_result_update_flags" #6 0xf7ca238d in virtual_sync_backend_boxes (ctx=0x97dd378) at virtual-sync.c:733 _data_stack_cur_id = 4 i = 0...

..., body") is not appearing in the 'struct' data. WHere to find it ? lookup() gets struct mail_search_arg *args, which contains the entire IMAP SEARCH query. This could be used for more or less complex query builders. In case of a single header search, you should have args->args->hdr_field_name contain the header name and args->args->value.str contain the content you're searching for. > Q4 : Refresh : this is very unclear. How come there would not be the "latest" view on index. What is the real meaning of this function ? In case of Xapian it might not matter if it...

...e = 0, size = 0, flags = 0,? ? ? ? ? ? ? ? ?? ? ? ? ? ? search_flags = (unknown: 0), date_type = 0, thread_type = MAIL_THREAD_NONE, modseq = 0x0,? ?? ? ? ? ? ? search_result = 0x0, mime_part = 0x0}, initialized = {search_args = 0x0, keywords = 0x0,? ??? ? ? ? ? ? mailbox_glob = 0x0}, context = 0x0, hdr_field_name = 0x0, match_not = 0,? ? ? ? ? ? ? ? ? ??? ? ? ? ? match_always = 0, nonmatch_always = 0, fuzzy = 0, no_fts = 0, result = -1}? ? ? ? ? ? ? ? ? ??? ? ? ? message_count = 160? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?? ? ? ? ret = <optimized out>? ? ? ? ? ? ? ?...

...s not appearing in the 'struct' data. WHere to find it ? > lookup() gets struct mail_search_arg *args, which contains the entire IMAP SEARCH query. This could be used for more or less complex query builders. > > In case of a single header search, you should have args->args->hdr_field_name contain the header name and args->args->value.str contain the content you're searching for. > > Q4 : Refresh : this is very unclear. How come there would not be the "latest" view on index. What is the real meaning of this function ? > In case of Xapian it might not ma...

Hi! I'm using Dovecot 1.1.15 on OpenBSD 4.4. How can I debug this? # /usr/local/sbin/dovecot --exec-mail ext /usr/local/libexec/dovecot/expire- tool Segmentation fault (core dumped) # gdb /usr/local/sbin/dovecot (gdb) run --exec-mail ext /usr/local/libexec/dovecot/expire-tool Starting program: /usr/local/sbin/dovecot --exec-mail ext /usr/local/libexec/dovecot/expire-tool Program received

...= 0xcebd640, element_size = 8}, v = 0xcebd640, v_modifiable = 0xcebd640}, str = 0x0, time = 0, size = 0, flags = 0, search_flags = 0, date_type = 0, thread_type = MAIL_THREAD_NONE, keywords = 0x0, modseq = 0x0, search_args = 0x0, search_result = 0x0, mailbox_glob = 0x0}, context = 0x0, hdr_field_name = 0x0, not = 0, match_always = 0, nonmatch_always = 0, result = -1} ret = <value optimized out> __FUNCTION__ = "index_search_result_update_flags" #6 0x00002ba91276ac92 in virtual_sync_backend_box (ctx=0xdebcdb0, bbox=0xdcb8e38) at virtual-sync.c:725 sync_flags = <value opt...

...0x557be7f69208}, str = 0x0, time = 0, size = 0, flags = 0, search_flags = (unknown: 0), date_type = 0, thread_type = MAIL_THREAD_NONE, modseq = 0x0, search_result = 0x0, mime_part = 0x0}, initialized = {search_args = 0x0, keywords = 0x0, mailbox_glob = 0x0}, context = 0x0, hdr_field_name = 0x0, match_not = 0, match_always = 0, nonmatch_always = 0, fuzzy = 0, no_fts = 0, result = -1} message_count = 2008 ret = <optimized out> __FUNCTION__ = "index_search_result_update_appends" #6 0x00007f8d4096dc37 in search_result_update (resu...

...IMAP SEARCH query. This could be used for more or less complex query </div> <div> builders. </div> <div> <br> </div> <div> In case of a single header search, you should have </div> <div> args->args->hdr_field_name contain the header name and </div> <div> args->args->value.str contain the content you're searching for. </div> <div> <br> </div> <div> Q4 : Refresh : this is very unclear. How come there would not be the </div&...

...appearing in the 'struct' data. WHere to find it ? > > lookup() gets struct mail_search_arg *args, which contains the entire IMAP SEARCH query. This could be used for more or less complex query builders. > > In case of a single header search, you should have args->args->hdr_field_name contain the header name and args->args->value.str contain the content you're searching for. > >> Q4 : Refresh : this is very unclear. How come there would not be the "latest" view on index. What is the real meaning of this function ? > > In case of Xapian it mig...

...t, body") is not appearing in the 'struct' data. WHere to find it ? lookup() gets struct mail_search_arg *args, which contains the entire IMAP SEARCH query. This could be used for more or less complex query builders. In case of a single header search, you should have args->args->hdr_field_name contain the header name and args->args->value.str contain the content you're searching for. Q4 : Refresh : this is very unclear. How come there would not be the "latest" view on index. What is the real meaning of this function ? In case of Xapian it might not matter if it autom...

...a. WHere to find it ? >> lookup() gets struct mail_search_arg *args, which contains the entire >> IMAP SEARCH query. This could be used for more or less complex query >> builders. >> >> In case of a single header search, you should have >> args->args->hdr_field_name contain the header name and >> args->args->value.str contain the content you're searching for. >> >> Q4 : Refresh : this is very unclear. How come there would not be the >> "latest" view on index. What is the real meaning of this function ? >>...

...ct mail_search_context *) 0x8171b58 t = (struct mailbox_transaction_context *) 0x8192eb0 mail = (struct mail *) 0x8199028 search_arg = {next = 0x0, type = SEARCH_FLAGS, value = {subargs = 0x0, seqset = 0x0, str = 0x0, time = 0, size = 0, flags = MAIL_DELETED, keywords = 0x0}, context = 0x0, hdr_field_name = 0x0, not = 0, match_always = 0, result = -1} failed = <value optimized out> #6 0x0805b505 in cmd_expunge (cmd=0x8165028) at cmd-expunge.c:62 client = (struct client *) 0x8162f50 #7 0x0805f8ed in client_command_input (cmd=0x8165028) at client.c:580 client = (struct client *) 0x8162f50...

...b87d0 t = (struct mailbox_transaction_context *) 0x2ac06e9aed10 mail = (struct mail *) 0x2ac06e9b89e8 search_arg = {next = 0x0, type = SEARCH_FLAGS, value = {subargs = 0x0, seqset = 0x0, str = 0x0, time = 0, size = 0, flags = MAIL_DELETED, keywords = 0x0}, context = 0x0, hdr_field_name = 0x0, not = 0, match_always = 0, result = -1} failed = <value optimized out> #2 0x00000000004171da in cmd_expunge (cmd=0x2ac06e982378) at cmd-expunge.c:62 client = (struct client *) 0x2ac06e982000 #3 0x000000000041b53c in client_command_input (cmd=0x2ac06e982378) at client....

...30fc in search_body (arg=0x1f5e80, context=0xffbff5b0) at index-search.c:448 448 ret = message_body_search(arg->value.str, (gdb) print *arg $10 = {next = 0x0, type = SEARCH_BODY, value = {subargs = 0x0, seqset = 0x0, str = 0x1f5ea8 "meeting"}, context = 0x0, hdr_field_name = 0x0, not = 0, match_always = 0, result = -1} (gdb) print *context Attempt to dereference a generic pointer. (gdb) print (struct search_body_context *) contec xt $11 = (struct search_body_context *) 0xffbff5b0 (gdb) print (struct search_body_context * ) context $12 = {index_ctx = 0xffbff5b0, in...

and finally , for fts_backend_xxxx_lookup_multi, why is that backend dependent ? Would- nt the below function below be the same for any backend ? Waiting fro your feedback on all those questions Thank you JM ----------------- static int fts_backend_xapian_lookup_multi(struct fts_backend *_backend, struct mailbox *const boxes[], struct mail_search_arg *args, enum fts_lookup_flags flags,

...gt; 'struct' data. WHere to find it ? > lookup() gets struct mail_search_arg *args, which contains the entire > IMAP SEARCH query. This could be used for more or less complex query > builders. > > In case of a single header search, you should have > args->args->hdr_field_name contain the header name and > args->args->value.str contain the content you're searching for. > > Q4 : Refresh : this is very unclear. How come there would not be the > "latest" view on index. What is the real meaning of this function ? > In case of Xapian it...