search for: imap_arg_list

....org")) After a quick look at the source, this seems to be due to src/lib-imap/imap-bodystructure.c:imap_write_list, which always separates list items with spaces. In the case of an envelope, only the top-level list should be space-separated. Indeed, not adding a space between items of type IMAP_ARG_LIST in the recursive call makes the test pass again. Cheers, -- Guilhem. -------------- next part -------------- A non-text attachment was scrubbed... Name: test-imap-bodystructure.diff Type: text/x-diff Size: 3361 bytes Desc: not available URL: <http://dovecot.org/pipermail/dovecot/attachments/20...

...IMAP_PARSE_FLAG_LITERAL_SIZE, &args); + if (ret == -1) { + if (!ctx->failed) + client_send_command_error(cmd, NULL); + ctx->failed = TRUE; + return catenate_finish(ctx, TRUE); + } + if (ret < 0) + return FALSE; + + // continuing the CATENATE list + i_assert(args->type == IMAP_ARG_LIST); + if (args[1].type != IMAP_ARG_EOL) { + i_assert(ctx->args == NULL); + ctx->args = &args[1]; // MULTIAPPEND + } + args = IMAP_ARG_LIST_ARGS(args); + + if (args->type == IMAP_ARG_EOL) { + /* end of CATENATE list. finish the message and return + to regular MULTIAPPEND processi...

...3, v_modifiable = 0x2e746f63}}, literal8 = 0} (gdb) p args[63] $65 = {type = 140396088, parent = 0x0, str_len = 140396088, _data = {str = 0x0, literal_size = 279172874240, list = {arr = {buffer = 0x0, element_size = 65}, v = 0x0, v_modifiable = 0x0}}, literal8 = 0} (gdb) p args[64] $66 = {type = IMAP_ARG_LIST, parent = 0x0, str_len = 0, _data = {str = 0x0, literal_size = 0, list = {arr = {buffer = 0x0, element_size = 0}, v = 0x0, v_modifiable = 0x0}}, literal8 = 0} (gdb) p args[65] $67 = {type = IMAP_ARG_NIL, parent = 0x0, str_len = 0, _data = {str = 0x0, literal_size = 0, list = {arr = {buffer = 0x0...

On 06.12.2016 09:32, Toni Mattila wrote: > Hi, > > On 05-Dec-16 20:28, Toni Mattila wrote: >> Panicing stopped when all index files where deleted. > > It happens again in same user account, so rebuilding indexes didn't > fix it. > > Here's bt full instead of just bt: > #0 0x001d4402 in __kernel_vsyscall () > No symbol table info available. > #1