search for: o_stream_destroy

...ot/libdovecot.so.0(+0xce5b1) [0x7f44248755b1] -> /usr/lib64/dovecot/libdovecot.so.0(+0x3d941) [0x7f44247e4941] -> /usr/lib64/dovecot/lib20_zlib_plugin.so(+0x5cdf) [0x7f44233c4cdf] -> /usr/lib64/dovecot/libdovecot.so.0(+0xf4b46) [0x7f442489bb46] -> /usr/lib64/dovecot/libdovecot.so.0(o_stream_destroy+0x13) [0x7f442489be83] -> /usr/lib64/dovecot/libdovecot-storage.so.0(maildir_save_finish+0x173) [0x7f4424b93973] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_save_cancel+0x36) [0x7f4424b68696] -> dovecot/imap [user at example.com X.X.X.X APPEND](+0xede9) [0x55a9d7e86de9] -&g...

...0) { - ctx->failed = TRUE; - mail_storage_set_critical(STORAGE(ctx->mbox->storage), - "utime(%s) failed: %m", path); - } - } - output_errno = ctx->output->stream_errno; o_stream_destroy(&ctx->output); > Ok, this is looking less like a feature request and more like a bug > report. > > The function maildir_save_finish() in > lib-storage/index/maildir/maildir-save.c is being passed the correct > time information, and is setting the mtime properly with a cal...

...t; /usr/lib/dovecot/libdovecot.so.0(+0x9afc1) [0x7faa1923afc1] -> /usr/lib/dovecot/libdovecot.so.0(+0x994af) [0x7faa192394af] -> /usr/lib/dovecot/libdovecot.so.0(+0xa5eda) [0x7faa19245eda] -> /usr/lib/dovecot/libdovecot.so.0(+0xa4566) [0x7faa19244566] -> /usr/lib/dovecot/libdovecot.so.0(o_stream_destroy+0xe) [0x7faa192446ee] -> /usr/lib/dovecot/libdovecot-sieve.so.0(+0x7e44b) [0x7faa17d3a44b] -> /usr/lib/dovecot/libdovecot-sieve.so.0(+0x7ea14) [0x7faa17d3aa14] -> /usr/lib/dovecot/libdovecot.so.0(+0xa6d88) [0x7faa19246d88] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x4c) [0x7fa...

...1: -> libdovecot:buffer_get_space_unsafe(0x42a68, 0x4, 0x4, 0x1cd70) /1 at 1: <- libdovecot:buffer_append_space_unsafe() = 0x42a8c /1 at 1: -> libdovecot:o_stream_uncork(0xa1968, 0xffbfedb0, 0x0, 0x1) /1 at 1: <- libdovecot:o_stream_uncork() = 0xa1918 /1 at 1: -> libdovecot:o_stream_destroy(0xffbfed3c, 0x0, 0x0, 0x1) /1 at 1: -> libdovecot:o_stream_unref(0xffbfed3c, 0x0, 0x0, 0x1) doveconf: Panic: output stream is missing error handling /1: write(2, " d o v e c o n f : P a".., 58) = 58 /1: getcontext(0xFFBFE988) /1: open("/proc/self/as", O_...

Hello, I have a new director ring I am setting up on centos 7 with dovecot 2.3.1. I haven't been able to replecate this in testing, but as soon as I start pushing production traffic to the new ring I see dozens of these in the logs: Apr 18 00:34:00 d.director.imapd.sonic.net kernel: imap-login[163107]: segfault at 10 ip 00007ff625698dd5sp 00007ffe4b77bb28 error 4 in

http://dovecot.org/releases/2.2/rc/dovecot-2.2.17.rc1.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.17.rc1.tar.gz.sig Quite a lot of changes, so here's a release candidate first. If no problems are reported I'll make v2.2.17 release early next week. Please test especially non-Linux systems as there are some larger configure/Makefile changes done since v2.2.16. * Dovecot no

http://dovecot.org/releases/2.2/rc/dovecot-2.2.17.rc1.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.17.rc1.tar.gz.sig Quite a lot of changes, so here's a release candidate first. If no problems are reported I'll make v2.2.17 release early next week. Please test especially non-Linux systems as there are some larger configure/Makefile changes done since v2.2.16. * Dovecot no

...&key, &value)) { + /* key is the mailbox, value is the access key */ + o_stream_send_str(os, (const char *) value); + o_stream_send(os, ":", 1); + o_stream_send_str(os, (const char *) key); + o_stream_send(os, "\n", 1); + } + hash_table_iterate_deinit(&iter); + o_stream_destroy(&os); + + return TRUE; +} + +// read/modify/write the access keys +static bool urlauth_keys_update(struct mail_storage *storage, + enum urlauth_keys_action action, + const char *mailbox, + buffer_t *out_key) +{ + const char *path; + int flags, fd; + pool_t pool; + struct hash_table *ke...