search for: deleted_count

...eeing log lines where the deleted count is blank (using default pop3_logout_format), so "del=%d/%m" is displaying in the logs as: "del=/1186" for example. In src/pop3/pop3-client.c:552: tab[4].value = client->delete_success ? dec2str(client->deleted_count) : 0; Shouldn't this be: tab[4].value = client->delete_success ? dec2str(client->deleted_count) : "0"; (very minor bug) -- Dave

I''ve "inherited" the administration of a puppet-dashboard (version 1.1.0, installed on RHEL 5.6 from puppetlabs RPM), and have hit a problem I''m hoping for some help with. In short, one table, "resource_statuses" appears to be growing at a rate far higher then the other tables: mysql> select count(*) from nodes; +----------+ | count(*) | +----------+ |

Upon thinking, the variable names may not be descriptive enough as `host` is a bit ambiguous and `deleted_count` may refer to a different command than expunge in imap and may be valid to track at some point so I have changed `host` to `client_ip` and `deleted_count` in imap to `expunged_count`, below is the modified diff for version 1.2.11. diff -crB dovecot-1.2.11.orig/src/imap/client.c dovecot-1.2.11/src...

...x801c19e80, > notify_handler_context = 0x0, max_fd_count = 0, time_moved_callback = > 0x800d53bb0 <mail_storage_service_time_moved>, > next_max_time = 1477240784, ioloop_wait_usecs = 29863, io_pending_count = > 1, running = 1, iolooping = 1} > (gdb) p *ctx > $4 = {kq = 22, deleted_count = 0, events = {arr = {buffer = 0x801c5acc0, > element_size = 32}, v = 0x801c5acc0, v_modifiable = 0x801c5acc0}} > (gdb) p *events > $5 = {ident = 23, filter = -1, flags = 0, fflags = 0, data = 8, udata = > 0x801c4f980} > (gdb) > > > > On Sun, Oct 23, 2016 at 11:27 AM,...

grrr. /home/mrm $ gdb /usr/local/bin/doveadm GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for

...> notify_handler_context = 0x0, max_fd_count = 0, > time_moved_callback = 0x800d53bb0 <mail_storage_service_time_moved>, > next_max_time = 1477257580, ioloop_wait_usecs = 27148, io_pending_count = > 1, > running = 1, iolooping = 1} > (gdb) p* ctx > $5 = {kq = 21, deleted_count = 0, events = {arr = {buffer = 0x801cd9740, > element_size = 32}, v = 0x801cd9740, v_modifiable = 0x801cd9740}} > (gdb) p *events > $6 = {ident = 22, filter = -1, flags = 0, fflags = 0, data = 8, > udata = 0x801c4f980} > (gdb) > > thebighonker.lerctr.org ~ $ ps auxw|gr...

...6,10 +56,22 @@ return client; } -void client_destroy(struct client *client) +static const char *client_stats(struct client *client) +{ + return t_strdup_printf("retr=%dB/%d#, del=%d exp=%d", + client->retr_bytes, + client->retr_messages, + client->deleted_count, + client->expunged_count); +} + +void client_destroy(struct client *client, const char *reason) { int ret; + if (reason != NULL) + i_info("%s %s", reason, client_stats(client)); + if (client->command_pending) { /* try to deinitialize the command */ i_stream...

Hi All I am experiencing a mail download problem with dovecot's pop3 protocol. We use outlook XP 2002 mail clients and I have setup a mail system with pop accounts on a Fedora 2 installation using dovecot. Some of the clients download email fine but others do not download email and also do not give any error messages. I have enabled the "verbose" options in the

...00}, handler_context = 0x801d17560, notify_handler_context = 0x0, max_fd_count = 0, time_moved_callback = 0x800d53bb0 <mail_storage_service_time_moved>, next_max_time = 1477257580, ioloop_wait_usecs = 27148, io_pending_count = 1, running = 1, iolooping = 1} (gdb) p* ctx $5 = {kq = 21, deleted_count = 0, events = {arr = {buffer = 0x801cd9740, element_size = 32}, v = 0x801cd9740, v_modifiable = 0x801cd9740}} (gdb) p *events $6 = {ident = 22, filter = -1, flags = 0, fflags = 0, data = 8, udata = 0x801c4f980} (gdb) thebighonker.lerctr.org ~ $ ps auxw|grep doveadm mrm 46965 0.0 0....

...01c5ac80}, handler_context = 0x801c19e80, notify_handler_context = 0x0, max_fd_count = 0, time_moved_callback = 0x800d53bb0 <mail_storage_service_time_moved>, next_max_time = 1477240784, ioloop_wait_usecs = 29863, io_pending_count = 1, running = 1, iolooping = 1} (gdb) p *ctx $4 = {kq = 22, deleted_count = 0, events = {arr = {buffer = 0x801c5acc0, element_size = 32}, v = 0x801c5acc0, v_modifiable = 0x801c5acc0}} (gdb) p *events $5 = {ident = 23, filter = -1, flags = 0, fflags = 0, data = 8, udata = 0x801c4f980} (gdb) On Sun, Oct 23, 2016 at 11:27 AM, Larry Rosenman <larryrtx at gmail.com>...

...ontext = 0x0, max_fd_count = 0, >> time_moved_callback = 0x800d53bb0 <mail_storage_service_time_moved>, >> next_max_time = 1477257580, ioloop_wait_usecs = 27148, io_pending_count = >> 1, >> running = 1, iolooping = 1} >> (gdb) p* ctx >> $5 = {kq = 21, deleted_count = 0, events = {arr = {buffer = 0x801cd9740, >> element_size = 32}, v = 0x801cd9740, v_modifiable = 0x801cd9740}} >> (gdb) p *events >> $6 = {ident = 22, filter = -1, flags = 0, fflags = 0, data = 8, >> udata = 0x801c4f980} >> (gdb) >> >> thebighonke...

...nt = 0, >>> time_moved_callback = 0x800d53bb0 <mail_storage_service_time_moved>, >>> next_max_time = 1477257580, ioloop_wait_usecs = 27148, io_pending_count = >>> 1, >>> running = 1, iolooping = 1} >>> (gdb) p* ctx >>> $5 = {kq = 21, deleted_count = 0, events = {arr = {buffer = 0x801cd9740, >>> element_size = 32}, v = 0x801cd9740, v_modifiable = 0x801cd9740}} >>> (gdb) p *events >>> $6 = {ident = 22, filter = -1, flags = 0, fflags = 0, data = 8, >>> udata = 0x801c4f980} >>> (gdb) >>&...

I am looking through the logging options and wondering if there are a couple of things that we can do 1. Logouts don't seem to show the IP address of the logout, we typically see multiple sessions at a time and wondering if there is a way to tie the logouts to an IP 2. POP logouts show the number of messages retrieved/deleted but I don't see a way to do this with IMAP, is there a logout

...ved_callback = 0x800d53bb0 <mail_storage_service_time_moved>, > >>> next_max_time = 1477257580, ioloop_wait_usecs = 27148, > io_pending_count = > >>> 1, > >>> running = 1, iolooping = 1} > >>> (gdb) p* ctx > >>> $5 = {kq = 21, deleted_count = 0, events = {arr = {buffer = > 0x801cd9740, > >>> element_size = 32}, v = 0x801cd9740, v_modifiable = 0x801cd9740}} > >>> (gdb) p *events > >>> $6 = {ident = 22, filter = -1, flags = 0, fflags = 0, data = 8, > >>> udata = 0x801c4f980} &gt...

>From the log: Jul 11 13:12:42 mproxy dovecot: imap-login: Login: user=<hildeb>, method=PLAIN, rip=141.42.206.36, lip=141.42.206.11, mpid=27254, TLS, session=<TGwoO1o3id+NKs4k> Jul 11 13:12:44 mproxy dovecot: imap(hildeb)<TGwoO1o3id+NKs4k>: Panic: file imap-client.c: line 854 (client_check_command_hangs): assertion failed: ((io_loop_find_fd_conditions(current_ioloop,