- dovecot - dovecot.org

doveadm-server does NOT know fts commands
by SATOH Fumiyasu 16 Dec '15

16 Dec '15

Hi, I'm using Dovecot 2.2.13 with Dovecot Director, Doveadm server and FTS. I want to run doveadm on Director hosts, but Dovecot server on backend hosts reject "fts *" commands. On Dovecot Director hosts: # doveadm fts optimize -u u0001(a)example.jp # echo $? 75 # doveadm fts rescan -u u0001(a)example.jp # echo $? 75 doveadm index -u u0001(a)example.jp INBOX # echo $? 0 On Dovecot backend hosts: # grep doveadm /var/log/maillog Jul 14 10:25:40 backend dovecot: doveadm: Error: doveadm: Client sent unknown command: fts optimize Jul 14 10:25:51 backend dovecot: doveadm: Error: doveadm: Client sent unknown command: fts rescan Is this doveadm-server restriction? On Dovecot backend hosts (2): # doveadm fts optimize -u u0001(a)example.jp -S /var/run/dovecot/doveadm-server # echo $? 75 # doveadm fts rescan -u u0001(a)example.jp -S /var/run/dovecot/doveadm-server # echo $? 75 # doveadm index -u u0001(a)example.jp -S /var/run/dovecot/doveadm-server INBOX # echo $? 0 # doveadm fts optimize -u u0001(a)example.jp # echo $? 0 # doveadm fts rescan -u u0001(a)example.jp # echo $? 0 # doveadm index -u u0001(a)example.jp INBOX # echo $? 0 -- -- Name: SATOH Fumiyasu @ OSS Technology Corp. (fumiyas @ osstech co jp) -- Business Home: http://www.OSSTech.co.jp/ -- GitHub Home: https://GitHub.com/fumiyas/ -- PGP Fingerprint: BBE1 A1C9 525A 292E 6729 CDEC ADC2 9DCA 5E1C CBCA

2 3

Assert failure in 2.2.20: imap-fetch.c:554 (ctx->client->output_cmd_lock || ctx->client->output_cmd_lock == cmd)
by Peter Eriksson 16 Dec '15

16 Dec '15

Just got another core-dump from Dovecot's imap process on our mail server. Dovecot 2.2.20 Solaris 10 / x86 Maildir Output from syslog: Dec 14 10:58:12 mail dovecot: [ID 583609 mail.crit] imap(oling): Panic: file imap-fetch.c: line 554: assertion failed: (ctx->client->output_cmd_lock == NULL || ctx->client->output_cmd_lock == cmd) Dec 14 10:58:15 mail dovecot: [ID 583609 mail.crit] imap(oling): Fatal: master: service(imap): child 2167 killed with signal 6 (core dumped) Checked the users' Maildir for files modified around this time and found: -rw------- 1 oling root 15743 Dec 14 10:54 .Deleted Messages/cur/1450099463.M318113P13582.mail,S=15743,W=16026:2,RSbcd Don't know if it's related though. Data from the core-dump / debugger: # /pkg/studio/default/bin/dbx /ifm/pkg/dovecot/default/libexec/dovecot/imap imap.2167.306 ... program terminated by signal ABRT (Abort) 0xfffffd7ffeb81eca: __lwp_kill+0x000a: jae __lwp_kill+0x18 [ 0xfffffd7ffeb81ed8, .+0xe ] Current function is default_fatal_finish 201 abort(); (dbx) where [1] __lwp_kill(0x1, 0x6, 0xfffffe88d2948e40, 0xfffffd7ffeb827be, 0x4552555443, 0x0), at 0xfffffd7ffeb81eca [2] _thr_kill(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0xfffffd7ffeb7a7d3 [3] raise(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0xfffffd7ffeb26fe9 [4] abort(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0xfffffd7ffeb05f60 =>[5] default_fatal_finish(type = LOG_TYPE_PANIC, status = 0), line 201 in "failures.c" [6] i_internal_fatal_handler(ctx = 0xfffffd7fffdff858, format = 0x492df0 "file %s: line %d: assertion failed: (%s)", args = 0xfffffd7fffdff840), line 670 in "failures.c" [7] i_panic(format = 0x492df0 "file %s: line %d: assertion failed: (%s)", ... = 0x467f4f, ...), line 275 in "failures.c" [8] imap_fetch_more(ctx = 0x736b00, cmd = 0x7369a8), line 554 in "imap-fetch.c" [9] cmd_fetch(cmd = 0x7369a8), line 297 in "cmd-fetch.c" [10] command_exec(cmd = 0x7369a8), line 172 in "imap-commands.c" [11] client_command_input(cmd = 0x7369a8), line 948 in "imap-client.c" [12] client_command_input(cmd = 0x7369a8), line 1008 in "imap-client.c" [13] client_handle_next_command(client = 0x4d16c0, remove_io_r = 0xfffffd7fffdffa7d), line 1022 in "imap-client.c" [14] client_handle_input(client = 0x4d16c0), line 1058 in "imap-client.c" [15] client_input(client = 0x4d16c0), line 1105 in "imap-client.c" [16] io_loop_call_io(io = 0x5bab00), line 559 in "ioloop.c" [17] io_loop_handler_run_internal(ioloop = 0x4b2580), line 211 in "ioloop-poll.c" [18] io_loop_handler_run(ioloop = 0x4b2580), line 607 in "ioloop.c" [19] io_loop_run(ioloop = 0x4b2580), line 583 in "ioloop.c" [20] master_service_run(service = 0x4b2450, callback = 0x482690 = &`imap`main.c`client_connected(struct master_service_connection *conn)), line 640 in "master-service.c" [21] main(argc = 1, argv = 0xfffffd7fffdffcb8), line 442 in "main.c" (dbx) print cmd cmd = 0x7369a8 (dbx) print ctx->client->output_cmd_lock ctx->client->output_cmd_lock = 0x72e0f8 (dbx) print *cmd *cmd = { prev = (nil) next = 0x72e0f8 client = 0x4d16c0 pool = 0x4d1eb0 tag = 0x736ac0 "150.11" name = 0x736ac8 "UID FETCH" args = 0x736ad8 "12663:12665 (BODY.PEEK[] BODYSTRUCTURE)" cmd_flags = COMMAND_FLAG_BREAKS_SEQS func = 0x437220 = &cmd_fetch(struct client_command_context *cmd) context = (nil) module_contexts = { arr = { buffer = 0x736a58 element_size = 8U } v = 0x736a58 v_modifiable = 0x736a58 } parser = 0x4d3d40 state = CLIENT_COMMAND_STATE_WAIT_INPUT start_time = { tv_sec = 1450087092 tv_usec = 924042 } start_ioloop_wait_usecs = 119688401U running_usecs = 0 bytes_in = 0 bytes_out = 0 sync = (nil) uid = 1U cancel = 0 param_error = 0 search_save_result = 0 search_save_result_used = 0 temp_executed = 0 tagline_sent = 0 } (dbx) print *(ctx->client->output_cmd_lock) *ctx->client->output_cmd_lock = { prev = 0x7369a8 next = 0x72d8c8 client = 0x4d16c0 pool = 0x4d1eb0 tag = 0x72e208 "149.11" name = 0x72e210 "UID FETCH" args = 0x72e220 "12666 (BODY.PEEK[] BODYSTRUCTURE)" cmd_flags = COMMAND_FLAG_BREAKS_SEQS func = 0x4371b0 = &`imap`cmd-fetch.c`cmd_fetch_continue(struct client_command_context *cmd) context = 0x72e248 module_contexts = { arr = { buffer = 0x72e1a8 element_size = 8U } v = 0x72e1a8 v_modifiable = 0x72e1a8 } parser = 0x5bb410 state = CLIENT_COMMAND_STATE_WAIT_OUTPUT start_time = { tv_sec = 1450087092 tv_usec = 923420 } start_ioloop_wait_usecs = 119688382U running_usecs = 538U bytes_in = 33U bytes_out = 32994U sync = (nil) uid = 1U cancel = 0 param_error = 0 search_save_result = 0 search_save_result_used = 0 temp_executed = 1U tagline_sent = 0 } -- [Ll.U] Peter Eriksson KITVS-IFM & ITI-NET IT.LiU.SE +46-70 518 2786

2 2

LIST command should not interpret wildcards in reference
by Robert Siemer 16 Dec '15

16 Dec '15

Hello everyone, I believe this is erroneously implemented in Dovecot: >>> for i in c.list_folders('deleteme.*.folder', '%'): ... print(i) ... ((b'\\HasNoChildren',), b'.', 'deleteme.*.folder') ((b'\\HasNoChildren',), b'.', 'deleteme.deleteme.deleteme.folder') We see here an interactive python session, which launches LIST "deleteme.*.folder" "%" over the wire and receives two mailboxes as answer. The response is already parsed, but that’s not important for my point: according to RFC3501 section 6.3.8 LIST Command, the arguments are “reference name” and “mailbox name with possible wildcards”. Both arguments are allowed to contain wildcard characters, but they have no special meaning in the reference. Dovecot 2.2.18 doesn’t do that right: the second mailbox should not be listed, because it is not a subfolder of reference. Is this a known issue? Regards, Robert

2 2

And one more core-dump in imap:str.c str_append(cstr = NULL)
by Peter Eriksson 16 Dec '15

16 Dec '15

Dovecot 2.2.20 Solaris 10 / x86 Maildir q (dbx) where [1] strlen(0x0, 0x0, 0x491baa, 0x0, 0x4d1ed0, 0x4d1ed0), at 0xfffffd7ffeaf6dd0 =>[2] str_append(str = 0x4a9120, cstr = (nil)), line 96 in "str.c" [3] client_get_commands_status(client = 0x4d16c0), line 282 in "imap-client.c" [4] client_log_disconnect(client = 0x4d16c0, reason = 0xfffffd7ffee24d80 "Connection closed"), line 322 in "imap-client.c" [5] client_default_destroy(client = 0x4d16c0, reason = (nil)), line 336 in "imap-client.c" [6] client_destroy(client = 0x4d16c0, reason = (nil)), line 263 in "imap-client.c" [7] client_input(client = 0x4d16c0), line 1099 in "imap-client.c" [8] io_loop_call_io(io = 0x5073b0), line 559 in "ioloop.c" [9] io_loop_handler_run_internal(ioloop = 0x4b2580), line 211 in "ioloop-poll.c" [10] io_loop_handler_run(ioloop = 0x4b2580), line 607 in "ioloop.c" [11] io_loop_run(ioloop = 0x4b2580), line 583 in "ioloop.c" [12] master_service_run(service = 0x4b2450, callback = 0x482690 = &`imap`main.c`client_connected(struct master_service_connection *conn)), line 640 in "master-service.c" [13] main(argc = 1, argv = 0xfffffd7fffdffcb8), line 442 in "main.c" (dbx) frame 3 Current function is client_get_commands_status 282 str_append(str, cmd->name); (dbx) print *cmd *cmd = { prev = (nil) next = (nil) client = 0x4d16c0 pool = 0x4d1eb0 tag = (nil) name = (nil) args = (nil) cmd_flags = <unknown enum member 0> func = (nil) context = (nil) module_contexts = { arr = { buffer = 0x4d1f80 element_size = 8U } v = 0x4d1f80 v_modifiable = 0x4d1f80 } parser = 0x4b8f90 state = CLIENT_COMMAND_STATE_WAIT_INPUT start_time = { tv_sec = 0 tv_usec = 0 } start_ioloop_wait_usecs = 0 running_usecs = 0 bytes_in = 0 bytes_out = 0 sync = (nil) uid = 0 cancel = 0 param_error = 0 search_save_result = 0 search_save_result_used = 0 temp_executed = 0 tagline_sent = 0 executing = 0 } (dbx) list 280 str_append(str, " ("); 281 for (cmd = client->command_queue; cmd != NULL; cmd = cmd->next) { 282 str_append(str, cmd->name); 283 if (cmd->next != NULL) 284 str_append_c(str, ','); 285 running_usecs += cmd->running_usecs; 286 bytes_in += cmd->bytes_in; 287 bytes_out += cmd->bytes_out; 288 last_cmd = cmd; 289 } Probably related to these entries in the syslog: Dec 11 16:18:47 mail dovecot: [ID 583609 mail.info] imap-login: Login: user=<perje>, method=PLAIN, rip=81.233.116.192, lip=130.236.160.9, mpid=9238, TLS, session=<CUwE16Am3fhR6X TA> Dec 11 16:18:50 mail dovecot: [ID 583609 mail.info] imap(perje): Connection closed in=196 out=995 Dec 11 16:18:50 mail dovecot: [ID 583609 mail.info] imap(perje): Connection closed in=168 out=5683 Dec 11 16:18:50 mail dovecot: [ID 583609 mail.info] imap(perje): Connection closed in=168 out=4713 Dec 11 16:18:50 mail dovecot: [ID 583609 mail.info] imap(perje): Connection closed in=194 out=1016 Dec 11 16:18:50 mail dovecot: [ID 583609 mail.info] imap(perje): Connection closed in=182 out=970 Dec 11 16:18:50 mail dovecot: [ID 583609 mail.info] imap(perje): Connection closed in=193 out=895 Dec 11 16:18:50 mail dovecot: [ID 583609 mail.info] imap(perje): Connection closed in=196 out=995 Dec 11 16:18:50 mail dovecot: [ID 583609 mail.info] imap(perje): Connection closed in=184 out=894 Dec 11 16:18:51 mail dovecot: [ID 583609 mail.info] imap-login: Login: user=<perje>, method=PLAIN, rip=81.233.116.192, lip=130.236.160.9, mpid=9273, TLS, session=<1uJB16AmtOhR6X TA> Dec 11 16:18:52 mail dovecot: [ID 583609 mail.info] imap-login: Login: user=<perje>, method=PLAIN, rip=81.233.116.192, lip=130.236.160.9, mpid=9278, TLS, session=<kR5Q16AmaOZR6X TA> Dec 11 16:18:52 mail dovecot: [ID 583609 mail.info] imap(perje): Connection closed in=150 out=491 Dec 11 16:23:08 mail dovecot: [ID 583609 mail.info] imap-login: Login: user=<perje>, method=PLAIN, rip=130.236.172.166, lip=130.236.160.9, mpid=10796, TLS, session=<GvSJ5qAms9CC 7Kym> Dec 11 16:23:08 mail dovecot: [ID 583609 mail.info] imap-login: Login: user=<perje>, method=PLAIN, rip=130.236.172.166, lip=130.236.160.9, mpid=10803, TLS, session=<nVqS5qAmttCC 7Kym> Dec 11 16:23:08 mail dovecot: [ID 583609 mail.info] imap(perje): Connection closed in=150 out=491 Dec 11 16:23:13 mail dovecot: [ID 583609 mail.info] imap(perje): Connection closed in=150 out=491 Dec 11 16:24:10 mail dovecot: [ID 583609 mail.crit] imap(perje): Fatal: master: service(imap): child 9006 killed with signal 11 (core dumped) (Would have been nice with a pid number in the syslog output :-) -- [Ll.U] Peter Eriksson KITVS-IFM & ITI-NET IT.LiU.SE +46-70 518 2786

2 1

Error: fcntl(write-lock) locking failed
by Marcin Janowski 16 Dec '15

16 Dec '15

Hello, one month ago I moved my smtp and imap server to other environment with /var/vmail on NFS. After this move i have warnings about too long "Locking transaction log", but today i have errors about "fcntl(write-lock) locking failed ". What this means? This is my dovecot config: # 2.2.9: /etc/dovecot/dovecot.conf doveconf: Warning: service auth { client_limit=1000 } is lower than required under max. load (2000) doveconf: Warning: service anvil { client_limit=1000 } is lower than required under max. load (1603) # OS: Linux 3.19.0-31-generic x86_64 Ubuntu 14.04.3 LTS nfs auth_mechanisms = plain login auth_worker_max_count = 300 default_process_limit = 400 mail_location = maildir:/var/vmail/%d/%n/Maildir mail_plugins = zlib managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { sieve = ~/.dovecot.sieve sieve_default = /var/vmail/globalsieverc sieve_dir = ~/sieve } postmaster_address = postmaster(a)smtp.DOMAIN protocols = " imap lmtp sieve pop3" service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { group = vmail mode = 0666 user = vmail } } service imap { process_limit = 1024 } ssl_cert = </etc/ssl/private/DOMAIN.crt ssl_key = </etc/ssl/private/DOMAIN.key userdb { args = uid=vmail gid=vmail home=/var/vmail/%d/%n driver = static } protocol lda { mail_plugins = zlib sieve } protocol imap { mail_max_userip_connections = 100 } And this is errors from few day: 2015-12-14 15:33:35 1450103615 Dec 14 15:32:44 smtp-atena dovecot: imap(...): Error: fcntl(write-lock) locking failed for file /var/vmail/.../Maildir/dovecot.index.log: No locks available Dec 14 15:32:44 smtp-atena dovecot: imap(...): Error: mail_index_wait_lock_fd() failed with file /var/vmail/.../Maildir/dovecot.index.log: No locks available 2015-12-14 12:36:35 1450092995 Dec 14 12:36:06 smtp-atena dovecot: imap(...): Error: fcntl(write-lock) locking failed for file /var/vmail/.../Maildir/dovecot.index.log: No locks available Dec 14 12:36:06 smtp-atena dovecot: imap(...): Error: mail_index_wait_lock_fd() failed with file /var/vmail/.../Maildir/dovecot.index.log: No locks available 2015-12-14 12:18:35 1450091915 Dec 14 12:18:25 smtp-atena dovecot: imap(...): Error: fcntl(write-lock) locking failed for file /var/vmail/.../Maildir/dovecot.index.log: No locks available Dec 14 12:18:25 smtp-atena dovecot: imap(...): Error: mail_index_wait_lock_fd() failed with file /var/vmail//Maildir/dovecot.index.log: No locks available Dec 14 12:18:25 smtp-atena dovecot: imap(...): Error: fcntl(write-lock) locking failed for file /var/vmail/.../Maildir/dovecot.index.log: No locks available Dec 14 12:18:25 smtp-atena dovecot: imap(...): Error: mail_index_wait_lock_fd() failed with file /var/vmail/.../Maildir/dovecot.index.log: No locks available 2015-12-14 09:10:35 1450080635 Dec 14 09:10:19 smtp-atena dovecot: imap(...): Error: fcntl(write-lock) locking failed for file /var/vmail/.../Maildir/dovecot.index.cache: No locks available 2015-12-13 13:40:35 1450010435 Dec 13 13:40:06 smtp-atena dovecot: imap(...): Error: fcntl(write-lock) locking failed for file /var/vmail/.../Maildir/dovecot.index.log: No locks available Dec 13 13:40:06 smtp-atena dovecot: imap(...): Error: mail_index_wait_lock_fd() failed with file /var/vmail/.../Maildir/dovecot.index.log: No locks available 2015-12-13 10:48:35 1450000115 Dec 13 10:48:19 smtp-atena dovecot: imap(...): Error: fcntl(write-lock) locking failed for file /var/vmail/.../Maildir/dovecot.index.log: No locks available Dec 13 10:48:19 smtp-atena dovecot: imap(...): Error: mail_index_wait_lock_fd() failed with file /var/vmail/.../Maildir/dovecot.index.log: No locks available 2015-12-12 08:36:35 1449905795 Dec 12 08:36:30 smtp-atena dovecot: imap(...): Warning: Locking transaction log file /var/vmail/.../Maildir/dovecot.index.log took 60 seconds Dec 12 08:36:31 smtp-atena dovecot: imap(...): Warning: Locking transaction log file /var/vmail/.../Maildir/dovecot.index.log took 31 seconds 2015-12-12 08:35:35 1449905735 Dec 12 08:35:29 smtp-atena dovecot: imap(...): Warning: Locking transaction log file /var/vmail/.../Maildir/dovecot.index.log took 60 seconds 2015-12-12 08:34:36 1449905676 Dec 12 08:34:27 smtp-atena dovecot: imap(...): Warning: Locking transaction log file /var/vmail/.../Maildir/dovecot.index.log took 60 seconds 2015-12-11 11:48:36 1449830916 Dec 11 11:47:48 smtp-atena dovecot: imap(...): Warning: Locking transaction log file /var/vmail/.../Maildir/dovecot.index.log took 60 seconds 2015-12-11 08:55:35 1449820535 Dec 11 08:55:03 smtp-atena dovecot: imap(...): Warning: Locking transaction log file /var/vmail/.../Maildir/dovecot.index.log took 90 seconds Dec 11 08:55:33 smtp-atena dovecot: imap(...): Warning: Locking transaction log file /var/vmail/.../Maildir/dovecot.index.log took 120 seconds Dec 11 08:55:33 smtp-atena dovecot: imap(...): Warning: Locking transaction log file /var/vmail/.../Maildir/dovecot.index.log took 120 seconds 2015-12-11 08:54:35 1449820475 Dec 11 08:54:33 smtp-atena dovecot: imap(...): Warning: Locking transaction log file /var/vmail/.../Maildir/dovecot.index.log took 60 seconds 2015-12-11 08:53:35 1449820415 Dec 11 08:53:32 smtp-atena dovecot: imap(...): Warning: Locking transaction log file /var/vmail/.../Maildir/dovecot.index.log took 60 seconds 2015-12-11 08:52:35 1449820355 Dec 11 08:51:59 smtp-atena dovecot: imap(...): Warning: Locking transaction log file /var/vmail/.../Maildir/dovecot.index.log took 90 seconds Dec 11 08:51:59 smtp-atena dovecot: imap(...): Warning: Locking transaction log file /var/vmail/.../Maildir/dovecot.index.log took 90 seconds 2015-12-11 08:51:35 1449820295 Dec 11 08:51:29 smtp-atena dovecot: imap(...): Warning: Locking transaction log file /var/vmail/.../Maildir/dovecot.index.log took 60 seconds Dec 11 08:51:29 smtp-atena dovecot: imap(...): Warning: Locking transaction log file /var/vmail/.../Maildir/dovecot.index.log took 60 seconds

2 1

Dovecot SASL and GSSAPI (IPA)
by Ranbir 15 Dec '15

15 Dec '15

Hi Everyone, I'm currently using dovecot SASL in postfix and passwd-file in dovecot for authenticating my users. I want to switch to using IPA instead. I have both the postfix (mailman01) and dovecot (mailman02) servers joined to the IPA domain. I have GSSAPI working in dovecot for IMAP. But, the SASL GSSAPI authentication in postfix fails with this error: warning: unknown[10.200.5.100]: SASL GSSAPI authentication failed: This is what dovecot logs: Dec 12 22:31:54 mailman02 dovecot: auth: Debug: auth client connected (pid=0) Dec 12 22:31:54 mailman02 dovecot: auth: Debug: client in: AUTH 1 GSSAPI service=smtp nologin lip=10.200.9.14 rip=10.200.5.100 secured resp=<hidden> Dec 12 22:31:54 mailman02 dovecot: auth: Debug: gssapi(?,10.200.5.100): Obtaining credentials for smtp(a)mailman02.theinside.rnr Dec 12 22:31:54 mailman02 dovecot: auth: gssapi(?,10.200.5.100): While processing incoming data: Unspecified GSS failure. Minor code may provide more information Dec 12 22:31:54 mailman02 dovecot: auth: gssapi(?,10.200.5.100): While processing incoming data: Wrong principal in request Dec 12 22:31:56 mailman02 dovecot: auth: Debug: client passdb out: FAIL 1 I've tried changing the "smtpd_sasl_local_domain" in postfix's main.cf file to "mailman02.theinside.rnr", but I get the same errors in dovecot and postfix. Right now the config in postfix looks like this: import_environment="KRB5_KTNAME=/etc/postfix/smtp.keytab" smtpd_sasl_local_domain = mailman01.theoutside.rnr Does what I'm trying to do make sense? If so, how do I fix it? Do I have to stop using dovecot sasl in postfix and switch to cyrus sasl? -- Ranbir

2 3

Ideas needed for archiving
by Ben 15 Dec '15

15 Dec '15

I've been asked by a user whether it's possible to stop their IMAP client downloading messages older than a given date. Whilst I'm guessing it may well be possible to do this client-side using folders and subscriptions, it got me thinking .... is there a way to do this server side on dovecot ? i.e. is there a way to "hide" messages from a user without having to archive them off into a seperate account ? thanks

2 2

Released Pigeonhole v0.4.10 for Dovecot v2.2.21
by Stephan Bosch 14 Dec '15

14 Dec '15

Hello Dovecot users, I got a bit stalled by our recent switch to Git, but here is the final v0.4.10 release of Pigeonhole for Dovecot v2.2.21. Nothing of consequence changed since the last RC. Changelog v0.4.10: + Implemented the Sieve mime and foreverypart extensions (RFC 5703). These are fully implemented. The interaction with the editheader extension needs some work, but this should not influence most uses; i.e., changes by the editheader extension are not always visible using foreverypart/mime. + Sieve body extension: Properly implemented the `:text' body transform. It now extracts text for HTML message parts. + Sieve enotify extension: mailto method: Implemented the sieve_notify_mailto_envelope_from setting. This allows configuring the source of the notification sender address for e-mail notifications. This is similar to what already can be configured for redirect. + Added a sieve_enabled (defaults to 'yes') setting that allows explicitly disabling Sieve processing for particular users. This used to be possible by setting `sieve=', but ever since the sieve_before, sieve_after and sieve_default settings were added, this method was not reliable anymore. - variables extension: Fixed handling of empty string by the `:length' set modifier. An empty string yielded an empty string rather than "0". - Fixed memory leak in the Sieve script byte code dumping facility. Extension contexts were never actually freed. - Fixed handling of implicit keep when the last Sieve script is a global one. In that case the implicit keep action was executed in global context, which could mean that trivial (quota) errors ended up in the system log file, rather than the user log file. - doveadm sieve plugin: Fixed crashes caused by incorrect context allocation in the sieve command implementations. The release is available as follows: http://pigeonhole.dovecot.org/releases/2.2/rc/dovecot-2.2-pigeonhole-0.4.10… http://pigeonhole.dovecot.org/releases/2.2/rc/dovecot-2.2-pigeonhole-0.4.10… Refer to http://pigeonhole.dovecot.org and the Dovecot v2.x wiki for more information. Have fun testing this release and don't hesitate to notify me when there are any problems. Regards, -- Stephan Bosch stephan(a)rename-it.nl

2 2

v2.2.21 released
by Timo Sirainen 13 Dec '15

13 Dec '15

http://dovecot.org/releases/2.2/dovecot-2.2.21.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.21.tar.gz.sig Due to a bit bad doveadm bugs in v2.2.20 here's a fixed v2.2.21. Also from this release forward we're finally using git with branches to make new releases. So new releases will have a bit more time to stabilize in the branch before they're being released (while still allowing new features to be developed in the master development branch). We already did something like this for the enterprise releases, but now it's done for community releases as well. - doveadm mailbox list (and some others) were broken in v2.2.20 - director: Fixed making backend changes when running with only a single director server. - virtual plugin: Fixed crash when trying to open nonexistent autocreated backend mailbox.

2 3

2.2.21: doveadm expunge is broken
by Alexander Moisseev 13 Dec '15

13 Dec '15

# doveadm expunge -u user(a)example.com MAILBOX Trash ALL Fatal: expunge: To avoid accidents, each branch in search query must contain something else besides MAILBOX (e.g. just add "all" if you want everything) -- Alexander

2 1