search for: mailbox_free

...> /usr/local/lib/dovecot/lib20_virtual_plugin.so(+0x9f94) [0x7f1232059f94] -> /usr/local/lib/dovecot/lib20_virtual_plugin.so(+0x9fe9) [0x7f1232059fe9] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(mailbox_close+0x1a) [0x7f12333825da] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(mailbox_free+0x13) [0x7f1233382663] -> dovecot/imap() [0x41870f] -> dovecot/imap() [0x423ce4] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_handle_timeouts+0xda) [0x7f12330d28aa] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x9c) [0x7f12330d3cbc] -> /usr/local/lib/do...

...20, at 17.07, Timo Sirainen <timo at sirainen.com> wrote: > >> This is what the log says in the moment of crashing: >> dovecot: lmtp(53852): Panic: Module context mail_crypt_user_module missing >> *** backtrace *** (see: https://pastebin.com/YCiFtxmy) > > It shows mailbox_free() in the backtrace, so it's probably crashing in mail_crypt_mailbox_close()'s MAIL_CRYPT_CONTEXT(box). But looking at the code, I can't see how that could be possible. Maybe there is some kind of memory corruption or something. Looks like there's a bug when some users have mail_cr...

Hello everybody, hope you?re all well! We have a really strange bug with our dovecot setup. After weeks and month of debugging we?re finally reached the point when we ask you for help. Our basic setup is quite simple: a single dovecot 2.3.10 (0da0eff44) install on Debian 10 with LDAP as user/passdb and sieve, imap_sieve and mail_crypt as mail_plugins. For the mail_crypt we have a special rule

...o.0(+0xe0d18) [0x7f4e042b7d18] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xc6f91) [0x7f4e0429df91] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xc7023) [0x7f4e0429e023] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xbe6c4) [0x7f4e042956c4] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_free+0x19) [0x7f4e042176b9] -> /usr/lib/dovecot/modules/lib20_virtual_plugin.so(+0x9dac) [0x7f4e028cddac] -> /usr/lib/dovecot/modules/lib20_virtual_plugin.so(+0x9e59) [0x7f4e028cde59] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_close+0x1a) [0x7f4e0421762a] -> /usr/lib/dovecot/modules...

...th v2.3.5.1 on Debian 9 and had the issue right from the beginning. >> This is what the log says in the moment of crashing: >> dovecot: lmtp(53852): Panic: Module context mail_crypt_user_module missing >> *** backtrace *** (see: https://pastebin.com/YCiFtxmy) > > It shows mailbox_free() in the backtrace, so it's probably crashing in mail_crypt_mailbox_close()'s MAIL_CRYPT_CONTEXT(box). But looking at the code, I can't see how that could be possible. Maybe there is some kind of memory corruption or something. > >> dovecot: lmtp(53852): Fatal: master: service...

Hi, It looks like I've found something strange. It looks like dovecot updates fts-lucene index every time I'm opening virtual folder that contains FTS query: indexer-worker(dion): Warning: fts-lucene: Settings have changed, rebuilding index for mailbox dovecot-virtual is pretty simple: archive/INBOX BODY "test" first of all, I'm trying to perform FTS in archive/INBOX

...e042b7d18] -> > /usr/lib/dovecot/libdovecot-storage.so.0(+0xc6f91) [0x7f4e0429df91] -> > /usr/lib/dovecot/libdovecot-storage.so.0(+0xc7023) [0x7f4e0429e023] -> > /usr/lib/dovecot/libdovecot-storage.so.0(+0xbe6c4) [0x7f4e042956c4] -> > /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_free+0x19) > [0x7f4e042176b9] -> > /usr/lib/dovecot/modules/lib20_virtual_plugin.so(+0x9dac) > [0x7f4e028cddac] -> > /usr/lib/dovecot/modules/lib20_virtual_plugin.so(+0x9e59) > [0x7f4e028cde59] -> > /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_close+0x1a) > [0x7f4e04217...

Hi, This appears to be some sort of dovecot bug. When I use the -r option to recursively delete a mailbox and sub-folders, it removes the sub-folders but not the inbox. It gives me the error below: doveadm mailbox delete -u denise at lifelinetechnique.com.au -r -s inbox doveadm(denise at lifelinetechnique.com.au): Error: Can't delete mailbox inbox: INBOX can't be deleted. Our user

...> /usr/local/lib/dovecot/lib20_virtual_plugin.so(+0x93d5) [0x7fa3111ba3d5] -> /usr/local/lib/dovecot/lib20_virtual_plugin.so(+0x9429) [0x7fa3111ba429] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(mailbox_close+0x1a) [0x7fa312b0a8ea] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(mailbox_free+0x13) [0x7fa312b0c453] -> dovecot/imap(cmd_logout+0x40) [0x4113c0] -> dovecot/imap(command_exec+0x75) [0x4194f5] -> dovecot/imap() [0x417bb0] -> dovecot/imap() [0x417c46] -> dovecot/imap(client_handle_input+0x11d) [0x417f3d] -> dovecot/imap(client_input+0x6f) [0x4182bf] -> /usr...

...-> /usr/lib/dovecot/libdovecot-storage.so.0(mdbox_s torage_rebuild+0x24) [0x7f99cf5f4414] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0x53565) [0x7f99cf5f4565] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_close+0x1a) [0x7f99cf5c8caa] -> /usr/lib/dovec ot/libdovecot-storage.so.0(mailbox_free+0x13) [0x7f99cf5c8cf3] -> dovecot/imap(client_destroy+0x109) [0x7f99cfaa69e9] -> dovecot/imap(client_input+0xaa) [0x7f99cfaa6dba] -> /usr/lib/dovecot/libdovecot.so.0(i o_loop_call_io+0x48) [0x7f99cf366c98] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0xa7) [0x7f99cf367d27] -&...

...) >> [0x7fb0fc0d99a8] -> >> /usr/local/lib/dovecot/libdovecot-storage.so.0(+0xd92d1) >> [0x7fb0fc0bf2d1] -> >> /usr/local/lib/dovecot/libdovecot-storage.so.0(+0xd9363) >> [0x7fb0fc0bf363] -> >> /usr/local/lib/dovecot/libdovecot-storage.so.0(index_storage_mailbox_free+0x9) >> [0x7fb0fc0b0f39] -> >> /usr/local/lib/dovecot/libdovecot-storage.so.0(+0xd05a4) >> [0x7fb0fc0b65a4] -> >> /usr/local/lib/dovecot/libdovecot-storage.so.0(mailbox_free+0x19) >> [0x7fb0fc030c99] -> >> /usr/local/lib/dovecot/lib20_virtual_plugin.so(+...

...correct way of recursively deleting a mailbox as there is nothing in the man page about the -r option. It's on purpose: if (mailbox_is_any_inbox(box)) { /* IMAP protocol allows this, but I think it's safer to not allow it. */ mailbox_free(&box); client_send_tagline(cmd, "NO INBOX can't be deleted."); return TRUE; } Why do you want to delete the INBOX of the user? - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEVAwUBWZVFPXz1H7kL/d9rAQIs2wf/X2l5XvH...

...ins. Was this happening with old Dovecot versions, or did it start after v2.3.10 upgrade? > This is what the log says in the moment of crashing: > dovecot: lmtp(53852): Panic: Module context mail_crypt_user_module missing > *** backtrace *** (see: https://pastebin.com/YCiFtxmy) It shows mailbox_free() in the backtrace, so it's probably crashing in mail_crypt_mailbox_close()'s MAIL_CRYPT_CONTEXT(box). But looking at the code, I can't see how that could be possible. Maybe there is some kind of memory corruption or something. > dovecot: lmtp(53852): Fatal: master: service(lmtp): c...

...e, NULL)); } if (mailbox_mark_index_deleted(box, TRUE) < 0){ struct mail_storage *storage = mailbox_get_storage(box); i_error("Can't delete INDEX %s: %s", name,mail_storage_get_last_error(storage, NULL)); } mailbox_free(&box); } } I got this errors. Nov 26 17:39:29 brc dovecot: imap(alex at exemplo.com.br): Panic: file index-status.c: line 144 (index_storage_get_status): assertion failed: (box->opened) Nov 26 17:39:29 brc dovecot: imap(alex at exemplo.com.br): Error: Raw backtrace: /opt/addons/lib/dov...

Hi There! I can not find anything about this message: dovecot[23202]: lmtp(jakob): Debug: Mailbox <lmtp DATA>: Opened mail UID=1 because: header Message-ID (Cache file is unusable) dovecot[23202]: lmtp(jakob): Debug: Mailbox <lmtp DATA>: Opened mail UID=1 because: virtual size (Cache file is unusable) And the next is: dovecot[23202]: lmtp(jakob): rphlK01SG1qiWgAAk1Mx3g: sieve:

...NULL) { @@ -64,7 +63,7 @@ box = mailbox_alloc(ns->list, "INBOX", 0); ctx = quota_transaction_begin(box); - ret = quota_test_alloc(ctx, I_MAX(1, mail_size), &too_large); + ret = quota_test_alloc(ctx, I_MAX(1, mail_size), too_large); quota_transaction_rollback(&ctx); mailbox_free(&box); @@ -82,6 +81,7 @@ struct mail_storage_service_user *service_user; struct mail_user *user; const char *value = NULL, *error; + bool too_large; int ret; if (client->recipient == NULL) { @@ -98,14 +98,21 @@ if (ret == 0) { value = nouser_reply; } else if (ret > 0) {...

...o.0(+0xf39a8) > [0x7fb0fc0d99a8] -> > /usr/local/lib/dovecot/libdovecot-storage.so.0(+0xd92d1) > [0x7fb0fc0bf2d1] -> > /usr/local/lib/dovecot/libdovecot-storage.so.0(+0xd9363) > [0x7fb0fc0bf363] -> > /usr/local/lib/dovecot/libdovecot-storage.so.0(index_storage_mailbox_free+0x9) > [0x7fb0fc0b0f39] -> > /usr/local/lib/dovecot/libdovecot-storage.so.0(+0xd05a4) > [0x7fb0fc0b65a4] -> > /usr/local/lib/dovecot/libdovecot-storage.so.0(mailbox_free+0x19) > [0x7fb0fc030c99] -> > /usr/local/lib/dovecot/lib20_virtual_plugin.so(+0xabdc) &g...

...ox=0x10a34128) at ../../../src/lib/array.h:198 198 *count_r = array->buffer->used / array->element_size; #0 0x00002afabdfbd6a2 in virtual_config_free (mbox=0x10a34128) at ../../../src/lib/array.h:198 count = <value optimized out> #1 0x00002afabdfbf659 in virtual_mailbox_free (box=0x0) at virtual-storage.c:327 No locals. #2 0x00002afabddb4db4 in fts_mailbox_free (box=0x10a34128) at fts-storage.c:73 fbox = (struct fts_mailbox *) 0x10a36f20 #3 0x00002afabcb05db9 in mailbox_free (_box=<value optimized out>) at mail-storage.c:638 box = (struct mailbo...

This is a different bug, and I suspect it might be caused by virtual plugin. We'll look into it. Aki On 04.01.2018 23:41, Jakob Sch?rz wrote: > Hi! > > This is very strange... > This error affects only one mailaccount, and it happend not yesterday. > The file > > /var/lib/dovecot/db/indexes/Maildir/jakob/INBOX/dovecot.index > > which hat "Panic: Leaked view

...0585d0) at virtual-storage.c:253 #3 0xb7d9ed7b in virtual_mailbox_close (box=0x800585d0) at virtual-storage.c:307 #4 0xb7f403ff in mail_thread_mailbox_close (box=0x800585d0) at index-thread.c:628 #5 0xb7f0d3fe in mailbox_close (box=0x800585d0) at mail-storage.c:1182 #6 0xb7f0d472 in mailbox_free (_box=0xbffff878) at mail-storage.c:1197 #7 0x8001e0ae in imap_status_get (cmd=0x80053948, ns=0x80052220, mailbox=0x8003a250 "virtual/openstack", items=0xbffff8f8, result_r=0xbffff900) at imap-status.c:96 #8 0x80011f64 in cmd_status (cmd=0x80053948) at cmd-status.c:40 #9 0x80...