search for: notify_context

...== -1) { and line 106: IN_CLOSE | IN_MODIFY); + i_warning("inotify_add_watch returned %d", watchdescriptor); if (watchdescriptor < 0) { and line 145: } + inotify_rm_watch("removing wd %d from inotify fd %d", io->notify_context, ctx->inotify_fd); if (inotify_rm_watch(ctx->inotify_fd, io->notify_context) < 0) Or something similar. If that doesn't help and output looks consistent (we're not removing a watch descriptor from a wrong fd etc.), can you try removing the fd_close_on_exec call please...

...inotify. If it is set to dnotify or inotify, failure to compile a test program results in an error. Also, it adds | file change notification method ..... : <method> to the output at the end of configure. The only thing I don't like about this patch is the fact that I had to add a field notify_context to struct io, but I didn't see a different way to handle this. Also, the patch doesn't support the condition parameter, it simply always asks for all the relevant changes. I don't really see that it is useful for in the context of file system notifications anyway. I modeled this after...

As promised, here it is finally. v1.0 is getting nearer and I want people to start looking at Dovecot's sources. Getting some more help with development would be nice, but I'd also like to hear if there are any hidden bugs in the code. So, one week from now I'll start offering 1000 EUR for the first person to point out a remotely exploitable security hole in Dovecot. See

...replication_mail_transaction_commit (txn=0x801c811b0, changes=0x7fffffffd3d0) at replication-plugin.c:258 ctx = (struct replication_mail_txn_context *) 0x801c811b0 ruser = (struct replication_user *) 0x0 priority = REPLICATION_PRIORITY_NONE #1 0x0000000801490749 in notify_contexts_mail_transaction_commit (t=0x801c24600, changes=0x7fffffffd3d0) at notify-plugin.c:132 ctx = (struct notify_context *) 0x801c8d020 mail_txn = (struct notify_mail_txn *) 0x801c282b0 #2 0x0000000801491a53 in notify_transaction_commit (t=0x801c24600, changes_r=0x7fffffff...

Hi, We have a Ubuntu 14.04 server with dovecot 2.2.9 If I try to run /usr/bin/doveadm search -u email at exmaple.com mailbox Junk savedbefore 30d It will dump a core file. We have a similar config on an other server and there is no problem there. Any ideas how to prevent the core dump? root at triws2:~# gdb --args doveadm search -u email at example.com mailbox Junk savedbefore 30d Reading

...x = 0xa9848, view = 0xb8720, cache = 0xaf638, mail_vfuncs = 0x960f0, is_recent = 0x32810 <mbox_mail_is_recent>, md5hdr_ext_idx = 1, notify_to = 0x0, notify_files = 0x0, notify_ios = 0x0, notify_last_check = 0, notify_last_sent = 0, min_notify_interval = 0, notify_callback = 0, notify_context = 0x0, next_lock_notify = 1129305608, last_notify_type = MAILBOX_LOCK_NOTIFY_NONE, commit_log_file_seq = 0, commit_log_file_offset = 0, keyword_names = 0xa98c4, cache_fields = 0xaf798, recent_flags = 0x0, recent_flags_start_seq = 0, recent_flags_count = 0, synced_recent_count = 0,...

...set = 0x0, open_error = MAIL_ERROR_NONE, input = 0x0, index_prefix = 0x0, flags = MAILBOX_FLAG_IGNORE_ACLS, transaction_count = 0, enabled_features = (unknown: 0), partial_cache = {uid = 0, physical_start = 0, physical_pos = 0, virtual_pos = 0}, tmp_sync_view = 0x0, notify_callback = 0x0, notify_context = 0x0, generation_sequence = 0, search_results = {arr = {buffer = 0x5555557e1f20, element_size = 8}, v = 0x5555557e1f20, v_modifiable = 0x5555557e1f20}, module_contexts = {arr = {buffer = 0x5555557e1fd8, element_size = 8}, v = 0x5555557e1fd8, v_modifiable = 0x5555557e1fd8}, opened = 0...

To some users happens this assertion failure while deleting a message. dovecot: Mar 10 08:40:44 Panic: IMAP(user): file index-sync.c: line 39 (index_mailbox_set_recent_uid): assertion failed: (seq_range_exists (&ibox->recent_flags, uid)) dovecot: Mar 10 08:40:44 Error: IMAP(user): Raw backtrace: [see bleow] dovecot: Mar 10 08:40:44 Error: child 17683 (imap) killed with signal 6 And the

...mail-log-plugin.c:174 value = 0x8 <Address 0x8 out of bounds> #11 0x00007f5c786087be in mail_log_append_mail_message (ctx=0x661ec8, mail=0x67b618, event=MAIL_LOG_EVENT_SAVE, desc=0x61f4b0 "copy from INBOX") at mail-log-plugin.c:219 _data_stack_cur_id = 4 #12 0x00007f5c7880ba57 in notify_contexts_mail_copy (src=0x6636f8, dst=0x67b618) at notify-plugin.c:69 ctx = (struct notify_context *) 0x642310 mail_txn = (struct notify_mail_txn *) 0x0 #13 0x00007f5c7880c1e3 in notify_copy (ctx=0x667ed0, mail=0x6636f8) at notify-storage.c:113 ret = <value optimized out> #14 0x00007f5c79e4e29a in...