- dovecot - dovecot.org

Possible bug about the SPECIAL-USE / CREATE-SPECIAL-USE extensions
by Jeff Stedfast 20 Dec '15

20 Dec '15

Hi all, I've locally got Dovecot 2.2.21 (5345f22) installed on my MacBook (via homebrew) that I've been using to test my IMAP library against. What is interesting is that even though Dovecot does not advertise CREATE-SPECIAL-USE, it supports creation of special-use folders via the "CREATE FolderName (USE (\Whatever))" syntax. According to rfc6154, a server is supposed to advertise the CREATE-SPECIAL-USE extension if it supports this: An IMAP server that supports this OPTIONAL feature will advertise the "CREATE-SPECIAL-USE" capability string. Clients MUST NOT use the "USE" parameter unless the server advertises the capability. Note that this capability string is different from the "SPECIAL-USE" string defined above, and a server that supports both functions MUST advertise both capability strings. Has this been fixed in a newer version, perhaps? Or could it be a misconfiguration on my part? Attached is my dovecot configuration (gotten via dovecot -n). Thanks, Jeff

2 2

Multiple IPs and hostname
by Thilo Engelbracht 18 Dec '15

18 Dec '15

Hi, I'm running postfix as SMTP-server and dovecot as IMAP-server. The server has multiple IPs, and postfix is configured that every domain is using a separate IPv4-address. Examle: foo1.com --> 11.22.33.44 foo2.com --> 22.33.44.55 foo3.com --> 33.44.55.66 bar.org --> 66.77.88.99 The hostname of the server is: mail.bar.org Now I have a request from one of my customers, who is using 3 different domains: - foo1.com - foo2.com - foo3.com If he receives a mail to "user(a)foo1.com", the header of the mail looks like this: Return-Path: <somebody(a)web.de> Delivered-To: <user(a)foo1.com> (II) Received: from mail.bar.org by mail.bar.org (Dovecot) with LMTP id V[...]wAAvP/pag for <user(a)foo1.com>; Sun, 29 Nov 2015 13:45:37 +0100 (I) Received: from mout.web.de (mout.web.de [212.227.17.11]) (using TLSv1.2 with cipher ECDHE-[...]-SHA384 (256/256 bits)) (No client certificate requested) by mail.foo1.com (Postfix) with ESMTPS id A[...]9 for <user(a)foo1.com>; Sun, 29 Nov 2015 13:45:36 +0100 (CET) As you can see in (I), postfix receives the mail and added a header with the correct hostname: mail.foo1.com But dovecot adds an additional header (see II). Here, the hostname of the system is visible. This is correct, because dovecot -n | grep -i hostname returns: hostname = mail.bar.org But my customer asks me if it's possible that only his domain is visible in the header: So, if somebody sends a mail to "user(a)foo1.com", only the hostname "mail.foo1.com" should be visible in the mail header. And if somebody sends a mail to "user(a)foo2.com", only the hostname "mail.foo2.com" should be visible in the mail header. Is there a way to do this? Thank you in advance. Kind regards Thilo

2 3

Merry Christmas
by IT Security Inc. 18 Dec '15

18 Dec '15

Merry Christmas from IT Security Inc. 12/18/2015 Visit us online Merry Christmas to you and your family from Hugh Haggerty, myself and everyone else at IT Security,Inc. Albert Whale Hugh Haggerty IT Security Inc. Merry Christmas! IT Security, Inc. 519 Nichols Road Pittsburgh, PA 15237 | in2contact.co/front/tracking.jsp?clientID=858&campaignID=188&userID=731&linkID=B710C911120204FA&emailID=689&sendID=307&triggerID= | in2contact.co/front/tracking.jsp?clientID=858&campaignID=188&userID=731&linkID=EB9D07803CDFE734&emailID=689&sendID=307&triggerID=

1 0

limiting autoexpunge to a service
by Burckhard Schmidt 18 Dec '15

18 Dec '15

Hello, like described at wiki "Mailbox settings": protocol imap { namespace inbox { mailbox Spam { autoexpunge = 10d } } } I tried to use autoexpunge inside lmtp: 20-lmtp.conf: protocol lmtp { mail_plugins = $mail_plugins sieve postmaster_address = ... info_log_path = /var/log/dovecot-lmtp.log sendmail_path = /opt/csw/sbin/sendmail namespace inbox { mailbox Junk { autoexpunge = 10d } } (line 23) } But I get an error during start of dovecot (same with service imap): doveconf: Fatal: Error in configuration file /usr/dovecot/etc/dovecot/conf.d/20-lmtp.conf line 23: Garbage after '{' /usr/dovecot/sbin/dovecot -n # 2.2.21 (): /usr/dovecot-2.2.21/etc/dovecot/dovecot.conf # Pigeonhole version 0.4.10 Is it only a problem of doveconf? -- Regards --- Burckhard Schmidt Abteilung Systemsoftware und Kommunikation ZE Computer- und Medienservice der Humboldt-Universität zu Berlin Postanschrift: Unter den Linden 6, 10099 Berlin Standort: Rudower Chaussee 26; 12489 Berlin Tel.: +49-30-2093-70058 Fax: +49-30-2093-70199 Mail: bschmidt(a)cms.hu-berlin.de

1 0

Last chance to order the Dovecot book
by Peer Heinlein 18 Dec '15

18 Dec '15

Hi, as some people migth know I've written a book about Dovecot that has also been translated and published in English. Thanks for Timos great help and detailled background informations he provided to me. Unfortunately my book publisher has to shutdown his business at the end of 2015 -- right now. During the next few days you'll have the last chance to order the english version of the dovecot book at amazon, if you're interested in. Please don't wait too long. I think they'll stop offering the book before christmas and then it's gone. http://www.dovecot-book.com/online-shop/als-e-book-bestellen/ MAYBE we'll be able to re-publish it next year. Maybe. If not -- this will be the last chance to order it. Peer (The german version of the book will be still available at http://www.dovecot-buch.de) -- Heinlein Support GmbH Schwedter Str. 8/9b, 10119 Berlin http://www.heinlein-support.de Tel: 030 / 405051-42 Fax: 030 / 405051-19 Zwangsangaben lt. §35a GmbHG: HRB 93818 B / Amtsgericht Berlin-Charlottenburg, Geschäftsführer: Peer Heinlein -- Sitz: Berlin

2 1

Deleting Public Mailbox?
by Dag Nygren 17 Dec '15

17 Dec '15

Hi! What am I doing wrong here? Mission: Delete old empty sub mailboxes in our Public mailspace acl-file contents: MailingLists user=dag lrwstipekxa MailingLists/* user=dag lrwstipekxa Didn't work from my mail client so tried: Command tried: % doveadm mailbox delete -s MailingLists/Glibc -u dag doveadm(dag): Error: Can't delete mailbox MailingLists/Glibc: Permission denied % doveadm acl debug -u dag "MailingLists/Egcs" doveadm(dag): Info: Mailbox 'Egcs' is in namespace 'MailingLists/' doveadm(dag): Info: Mailbox path: /usr/local/var/mail/MailingLists/mailboxes/Egcs/dbox-Mails doveadm(dag): Info: All message flags are shared across users in mailbox doveadm(dag): Info: User dag has rights: lookup read write write-seen write-deleted insert post expunge create delete admin doveadm(dag): Error: Mailbox not found from dovecot-acl-list, rebuilding doveadm(dag): Info: Mailbox is in public namespace doveadm(dag): Info: Mailbox MailingLists/Egcs is visible in LIST Must be a config I have wrong. Would like to get rid of them... Best Dag

2 4

userdb username change ignored when using (My)SQL was: Re: userdb username changed
by Péter Márton 17 Dec '15

17 Dec '15

Hi! It works when using LDAP. I've duplicated the "username change" debug line, just to see that the variables are really updated: Apr 20 14:30:27 imap21 dovecot: auth-worker(27127): Debug: sql(ppp(a)example.net): username changed ppp(a)example.net -> uppp Apr 20 14:30:27 imap21 dovecot: auth-worker(27127): Debug: sql(uppp): username changed uppp -> uppp Apr 20 14:30:27 imap21 dovecot: auth: Debug: userdb out: USER#0111#011ppp@example.net#011home=/home/ppp#011uid=500#011gid=500#011quota_rule=*:storage=3100b:messages=1024 And the answer is of course yes. Just the userdb out string has the wrong value. The right value is lost somewhere. But where? Regards, Peter Log of the (for me unusable) LDAP query: Apr 20 14:28:07 imap21 dovecot: auth: Debug: master in: USER#0111#011m2500j6#011service=doveadm Apr 20 14:28:07 imap21 dovecot: auth: Debug: ldap(m2500j6): user search: base=ou=Users,ou=Mail,dc=bnet,dc=at scope=subtree filter=(uid=m2500j6) fields=mailHost Apr 20 14:28:07 imap21 dovecot: auth: Debug: ldap(m2500j6): result: mailHost=localhost; mailHost unused Apr 20 14:28:07 imap21 dovecot: auth: Debug: ldap(m2500j6): username changed m2500j6 -> localhost Apr 20 14:28:07 imap21 dovecot: auth: Debug: ldap(localhost): username changed localhost -> localhost Apr 20 14:28:07 imap21 dovecot: auth: Debug: ldap(localhost): result: mailHost=localhost Apr 20 14:28:07 imap21 dovecot: auth: Debug: userdb out: USER#0111#011localhost#011

2 4

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

2.2.21: panic in stats-plugin.c: line 324 (stats_user_deinit): assertion failed: (stats_global_user == user)
by Jakub Jankowski 13 Dec '15

13 Dec '15

Hi, I've just upgraded dovecot to 2.2.21 (from 2.2.18), and I'm getting a crash when doing dsync backup: $ dsync -v -u user(a)domain.com backup maildir:/backup/maildirs/domain.com/user/Maildir dsync(user(a)domain.com): Panic: file stats-plugin.c: line 324 (stats_user_deinit): assertion failed: (stats_global_user == user) dsync(user(a)domain.com): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0x7e4b4) [0x7f543d3c74b4] -> /usr/lib64/dovecot/libdovecot.so.0(+0x7e529) [0x7f543d3c7529] -> /usr/lib64/dovecot/libdovecot.so.0(i_fatal+0) [0x7f543d372300] -> /usr/lib64/dovecot/lib90_stats_plugin.so(+0x4116) [0x7f543c95a116] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_user_unref+0x35) [0x7f543d68efd5] -> /usr/bin/dsync [shasta(a)toxcorp.com done]() [0x420f90] -> /usr/bin/dsync [user(a)domain.com done](doveadm_mail_try_run+0x28c) [0x421edc] -> /usr/bin/dsync [user(a)domain.com done](main+0x2ff) [0x413a2f] -> /lib64/libc.so.6(__libc_start_main+0xf0) [0x7f543cd80870] -> /usr/bin/dsync [user(a)domain.com done](_start+0x29) [0x413bb9] Aborted This gets logged to syslog when it happens: Dec 13 02:12:33 host dovecot: imap-login: Login: user=<user(a)domain.com>, method=PLAIN, rip=A.B.C.D, lip=A.B.C.D, mpid=1576, TLS Dec 13 02:13:09 host dovecot: stats: Error: Mail server input error: CONNECT: Duplicate session ID 4rqRBSXGbFbDBgAAOpfmEQ for user user(a)domain.com service doveadm It definitely wasn't happening on 2.2.18 (I skipped .19 and .20). Here's my configuration (with some things sanitized): $ dovecot -n # 2.2.21 (5345f22): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.9 (357ac0a0e68b+) # OS: Linux 4.3.2 x86_64 Slackware 14.2 auth_cache_negative_ttl = 1 mins auth_cache_size = 4 k auth_mechanisms = plain login auth_socket_path = /var/run/dovecot/auth-userdb auth_verbose = yes auth_verbose_passwords = sha1 default_vsz_limit = 512 M deliver_log_format = msgid=%m psize=%p vsize=%w: %$ first_valid_gid = 500 first_valid_uid = 500 hostname = host.domain.com last_valid_gid = 500 last_valid_uid = 500 listen = * login_greeting = IMAP server ready. login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c mail_location = mdbox:~/mdbox:ALT=/var/vmail/altmdbox/%Ld/%Ln/altmdbox mail_plugins = " stats" mailbox_list_index = yes 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 index ihave duplicate 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 Spam { special_use = \Junk } mailbox Trash { special_use = \Trash } prefix = separator = / type = private } passdb { args = scheme=CRYPT username_format=%Lu /etc/dovecot/users driver = passwd-file } plugin { mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename mail_log_fields = uid box msgid size recipient_delimiter = + sieve = ~/.dovecot.sieve sieve_default = /var/vmail/_sieve/default.sieve sieve_dir = ~/sieve stats_refresh = 30 secs stats_track_cmds = yes } pop3_client_workarounds = outlook-no-nuls postmaster_address = postmaster(a)domain.com protocols = imap pop3 lmtp sieve quota_full_tempfail = yes service auth-worker { user = $default_internal_user } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } service dict { unix_listener dict { group = vmail mode = 0660 user = vmail } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } service_count = 1 } service imap { process_limit = 128 } service lmtp { inet_listener lmtp { address = 127.0.0.1 port = 2424 } unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0660 user = postfix } unix_listener lmtp-vmail { group = vmail mode = 0660 user = vmail } } service managesieve-login { inet_listener sieve { port = 4190 } service_count = 1 vsz_limit = 64 M } service managesieve { process_limit = 32 } service pop3-login { inet_listener pop3 { port = 110 } inet_listener pop3s { port = 995 ssl = yes } } service pop3 { process_limit = 64 } service stats { fifo_listener stats-mail { mode = 0600 user = vmail } } ssl_cert = </etc/ssl/certs/cert.pem ssl_key = </etc/ssl/private/key.pem stats_command_min_time = 1 days stats_domain_min_time = 1 days stats_ip_min_time = 1 days stats_memory_limit = 32 M stats_session_min_time = 1 days stats_user_min_time = 1 days userdb { args = uid=vmail gid=vmail home=/var/vmail/mdbox/%Ld/%Ln driver = static } verbose_proctitle = yes protocol lda { mail_plugins = " stats sieve" } protocol imap { mail_max_userip_connections = 20 mail_plugins = " stats imap_stats" } protocol lmtp { mail_plugins = " stats sieve" } $ Let me know if there's anything else that I can provide to help narrowing it down. Cheers, shasta -- Jakub Jankowski|shasta@toxcorp.com|http://toxcorp.com/ GPG: FCBF F03D 9ADB B768 8B92 BB52 0341 9037 A875 942D

2 1

System-user-controllable custom passwords and mail locations
by Michal Petrucha 12 Dec '15

12 Dec '15

Hello everyone, I'd like to set up dovecot so that it uses the standard system accounts, but with different passwords specific to email. Seems like a fairly common setup, but the catch is, I want the users to be able to set their passwords themselves, without needing any assistance from a server administrator. I'm wondering what's the easiest way of implementing this. From what I've understood, this requirement would probably rule out a separate passwd-file (since the standard Linux passwd doesn't seem to support using a custom passwd file), SQL, flat-file dict, and Redis (since you can't give users access only to their row, or dict key; it's either the entire database (or flat file), or nothing). (Of course, I could work around that limitation by writing a C program that I would install as SUID root, which would only change the invoking user's password, but I'd prefer not to start dumping arbitrary SUID binaries all over the place.) So, that would probably only leave me with LDAP, checkpassword, and the FS dict backend. I can imagine how I could get LDAP to do this -- add some extra attribute for each user, and put together a simple script to change passwords, say, in Python, that would bind as the user and write the new password. However, this would require me to store the system user account database in LDAP, which is kind of overkill on at least one of the servers I want this setup on, where I know for certain that there won't ever be more than a handful of users. Checkpassword would probably work, too; perhaps by looking into some file in the user's $HOME or such. I'm not entirely certain about the security, or performance implications of that approach. With the FS dict backend, I could probably point it to a directory, in which every user would own a file containing their password, that no one else could write to. I haven't been able to find any more details about the structure of this directory hierarchy, though, or the contents of the individual files, so I don't know whether this is a viable approach, or not. My questions are, then: Is there some other way of implementing separate passwords that the users can set themselves that I'm overlooking? Is one of the three approaches described above a bad idea for some reason I don't see? Is there some kind of “standard solution” to this problem? The other thing I wanted to ask about is marginally related; I'd like to be able to allow users to customize the layout in which they store their mail. For instance, some users like to have their INBOX as an mbox in /var/mail, and other maildirs in ~/Maildirs/, others prefer having everything as a mix maildirs and mboxes in ~/mail, etc. Looking at the MailLocation wiki page, it seems like the only option, if I want to customize the location per user, is to set it in the userdb, but since we only have system users everywhere, it seems we have to use the passwd userdb, which doesn't support this kind of per-user customization (even on servers where PAM/NSS are configured to use LDAP). Again, am I overlooking something here? Is there nothing similar to ~/.imaprc, which is supported by certain versions of some other IMAP servers? Thanks in advance for any insights, Michal

1 0

Dovecot 1.2.15 and Convert Password Schemes
by Chuck Peters 11 Dec '15

11 Dec '15

Can I convert the password hashes with the older Dovecot? http://wiki2.dovecot.org/HowTo/ConvertPasswordSchemes shows how it can potentially be done with Dovecot 2.1, but when I try it with Dovecot 1.2.15, I'm not seeing a way to make it work. Any suggestions? This is an old Debian 6 system that's overdue for an upgrade. In the test environment upgrading OpenLDAP to Debian 8 I discovered most of our users passwords probably won't work. The hashes appear to be a old Unix DES based hash, ie base64 decoded ldif shows something like the following: userPassword:: {crypt}Aipcuzoh3eiVE Passwords stored in the SSHA hash seem to work fine. If given the password, a shell script could create the hashes with slappasswd and/or a SHA512 hash (using doveadm or mkpasswd) for use on Debian 8. # cat /usr/local/bin/dovecot-environment.sh #!/bin/sh set > /tmp/dovecot-environment exec /usr/lib/dovecot/imap "$@" I can show the /tmp/dovecot-environment if you like, but it's not showing the password as a variable... This system is using Debian's Dovecot package 1.2.15-7+deb6u1. Dovecot 2.1.7-7~bpo60+1 is available as a backport, but I would prefer not to upgrade Dovecot on the production system if I don't need to, or have some other reason such as some features for using IMAP for the migration. https://packages.debian.org/search?keywords=dovecot-common Thanks, Chuck # dovecot -n # 1.2.15: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-686-bigmem i686 Debian 6.0.10 log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap imaps pop3 pop3s ssl_cert_file: /etc/lfrr/ca/thishost.crt ssl_key_file: /etc/lfrr/ca/thishost.key disable_plaintext_auth: no verbose_ssl: yes login_dir: /var/run/dovecot/login login_executable(default): /usr/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(pop3): /usr/lib/dovecot/pop3-login verbose_proctitle: yes mail_privileged_group: mail mail_location: mbox:%h:INBOX=/var/mail/%Lu mbox_write_locks: fcntl dotlock mail_executable(default): /usr/local/bin/dovecot-environment.sh mail_executable(imap): /usr/local/bin/dovecot-environment.sh mail_executable(pop3): /usr/lib/dovecot/pop3 mail_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): mail_plugin_dir(default): /usr/lib/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap mail_plugin_dir(pop3): /usr/lib/dovecot/modules/pop3 pop3_reuse_xuidl(default): no pop3_reuse_xuidl(imap): no pop3_reuse_xuidl(pop3): yes auth default: mechanisms: plain login debug_passwords: yes passdb: driver: ldap args: /etc/dovecot/dovecot-ldap.conf passdb: driver: pam args: session=yes dovecot userdb: driver: passwd args: /etc/passwd userdb: driver: ldap args: /etc/dovecot/dovecot-ldap.conf plugin: quota: dirsize quota_rule: *:storage=204800 I should note, I think the default_pass_scheme = CRYPT doesn't do anything with auth_bind = yes. # grep -v '^ *$#.*$\?$' /etc/dovecot/dovecot-ldap.conf hosts = 127.0.0.1 sasl_bind = no auth_bind = yes auth_bind_userdn = uid=%u,ou=People,dc=ccil,dc=org ldap_version = 3 base = ou=People,dc=ccil,dc=org pass_attrs = uid=user,userPassword=password,homeDirectory=userdb_home,uidNumber=userdb_uid,gidNumber=userdb_gid pass_filter = (&(objectClass=posixAccount)(uid=%u)) default_pass_scheme = CRYPT

1 0

autoexpunge creates special_use folder
by Tom Sommer 11 Dec '15

11 Dec '15

namespace inbox { mailbox Spam { special_use = \Spam auto = create autoexpunge = 30d } } This creates the "Spam" folder in the filesystem on login/logout, even though it shouldn't. If I remove autoexpunge, the folder is not created. -- Tom Sommer

2 1

Have the Dovecot Enterprise Edition packages been discontinued?
by deoren 10 Dec '15

10 Dec '15

Hi, I've been using the Dovecot EE packages for Ubuntu for some time now and just recently started getting 404 errors. Have those packages been discontinued or is this just a temporary issue? Thanks.

3 3

Re: Autoexpunge and special user namespace
by Joseph Tam 10 Dec '15

10 Dec '15

On Wed, 9 Dec 2015, Timo Siraine wrote: >> I'm interested in replacing my cron script that expunges old >> deleted mail with the new feature announced in 2.2.20 >> >>> + Added mailbox { autoexpunge=<time> } setting. See >>> http://wiki2.dovecot.org/MailboxSettings for details. >> >> To use it, I need to specify which mailbox needs them using >> the namespace configuration. For example >> >> namespace inbox { >> mailbox Trash { >> auto = no >> special_use = \Trash >> autoexpunge = 7d >> mailbox_list_index = yes >> } >> ... > > mailbox_list_index=yes is a global setting. You can't have it here. Oh, yes. Thanks for pointing that out. By the way, what does it do? The wiki states mailbox_list_index=yes can help a lot by replying to IMAP STATUS (and similar) lookups from a single index without having to open each mailbox index separately. So it create an uber-index that combines information from individual indices? Are there any drawback to using this? > > 1) Do I need the special_user configuration at all? Will some > > clients start using different mailboxes to store deleted mail > > if I keep the special_use lines? > > special_use is independent of the autoexpunge. I guess it wouldn't > necessarily hurt.. but it's also somewhat better to have only a single > \Trash mailbox so clients don't become confused when more than one of > those mailboxes exist. Got it. Thanks, Timo. Joseph Tam <jtam.home(a)gmail.com>

2 1

Re: EVP_PKEY_get1_EC_KEY:expecting a ec key
by Oliver Riesen-Mallmann 09 Dec '15

09 Dec '15

Hi Teemu, > Could you post your doveconf -n output? # 2.2.20.rc1 (ed41702f14c2): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.10.rc1 # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.9 auth_mechanisms = plain login log_timestamp = "%Y-%m-%d %H:%M:%S " login_greeting = Ready. login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c %k mail_location = maildir:%h/mails mail_plugins = zlib mail_privileged_group = mail 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 index ihave duplicate mime foreverypart namespace inbox { inbox = yes list = yes location = maildir:%h/mails mailbox Archiv { auto = subscribe special_use = \Archive } mailbox Archives { auto = no special_use = \Archive } mailbox Drafts { auto = create special_use = \Drafts } mailbox "Gelöschte Elemente" { auto = no special_use = \Trash } mailbox Gesendete { auto = no special_use = \Sent } mailbox "Gesendete Elemente" { auto = no special_use = \Sent } mailbox Junk-E-Mail { auto = no special_use = \Junk } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { auto = no special_use = \Sent } mailbox Trash { auto = create special_use = \Trash } prefix = type = private } passdb { driver = shadow } plugin { sieve = file:~/sieve;active=~/.dovecot.sieve zlib_save = gz zlib_save_level = 6 } postmaster_address = postmaster(a)langzeittest.de protocols = imap service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } user = root } ssl_cert = </etc/dovecot/ssl-cert-langzeittest-plus-cacert.crt ssl_cipher_list = ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA ssl_dh_parameters_length = 2048 ssl_key = </etc/dovecot/ssl-cert-langzeittest.key ssl_prefer_server_ciphers = yes ssl_protocols = !SSLv2 !SSLv3 userdb { driver = passwd } protocol lda { mail_plugins = zlib sieve } protocol imap { mail_max_userip_connections = 20 mail_plugins = zlib imap_zlib } protocol pop3 { pop3_uidl_format = %08Xu%08Xv } Regards Oliver

2 3

Sieve script replication glitches
by Apollon Oikonomopoulos 09 Dec '15

09 Dec '15

Hi, I'm running a replicated setup on Debian with Dovecot 2.2.18 and Pigeonhole 0.4.8 and run into some glitches with sieve script syncing. Replication is implemented via DSync/doveadm over SSL. While e-mail replication works as expected, sieve script replication is not always successful. In general I have observed the following behaviour re. sieve script replication: - Sometimes sieve scripts are replicated but have an mtime of 0 (Jan 1 1970) on the destination. - Subsequent updates to these "bad" scripts are not replicated at all. - Sometimes after creating *another* sieve script (which may or may not get the correct timestamp), the "bad" script's timestamp/contents are corrected on the receiving side. The following is a minimal real-world example of what happens (including transaction log entries): 1. On the master create a new sieve script: cat test.sieve | doveadm sieve put -u user(a)example.com test1 Sieve storage on the master: -rw------- 1 vmail vmail 2001 Dec 9 15:53 test1.sieve Transaction log on the master: record: offset=44756, type=attribute-update (ext), size=72, modseq=514 - add: private/vendor/vendor.dovecot/pvt/server/sieve/files/test1 : timestamp=2015-12-09 15:53:28 value_len=0 record: offset=44828, type=modseq-update (ext), size=20 - uid=0 modseq=723 Sieve storage on the slave: -rw------- 1 vmail vmail 2001 Jan 1 1970 test1.sieve Transaction log on the slave: record: offset=55356, type=attribute-update (ext), size=72, modseq=597 - add: private/vendor/vendor.dovecot/pvt/server/sieve/files/test1 : timestamp=2015-12-09 15:53:29 value_len=0 record: offset=55428, type=attribute-update (sync), size=72, modseq=598 - add: private/vendor/vendor.dovecot/pvt/server/sieve/files/test1 : timestamp=2015-12-09 15:53:29 value_len=0 2. Create a new script on the master: cat test.sieve | doveadm sieve put -u user(a)example.com test2 Sieve storage on the master: -rw------- 1 vmail vmail 2001 Dec 9 15:53 test1.sieve -rw------- 1 vmail vmail 2001 Dec 9 15:57 test2.sieve Transaction log on the master: record: offset=44848, type=attribute-update (ext), size=72, modseq=515 - add: private/vendor/vendor.dovecot/pvt/server/sieve/files/test2 : timestamp=2015-12-09 15:57:14 value_len=0 record: offset=44920, type=modseq-update (ext), size=20 - uid=0 modseq=725 record: offset=44940, type=modseq-update (ext), size=20 - uid=0 modseq=728 Sieve storage on the slave: -rw------- 1 vmail vmail 2001 Dec 9 15:53 test1.sieve -rw------- 1 vmail vmail 2001 Dec 9 15:57 test2.sieve Transaction log on the slave: record: offset=55500, type=attribute-update (ext), size=72, modseq=599 - add: private/vendor/vendor.dovecot/pvt/server/sieve/files/test2 : timestamp=2015-12-09 15:57:14 value_len=0 record: offset=55572, type=attribute-update (sync), size=72, modseq=600 - add: private/vendor/vendor.dovecot/pvt/server/sieve/files/test2 : timestamp=2015-12-09 15:57:14 value_len=0 record: offset=55644, type=attribute-update (ext), size=72, modseq=601 - add: private/vendor/vendor.dovecot/pvt/server/sieve/files/test1 : timestamp=2015-12-09 15:57:14 value_len=0 record: offset=55716, type=attribute-update (ext), size=72, modseq=602 - add: private/vendor/vendor.dovecot/pvt/server/sieve/files/test2 : timestamp=2015-12-09 15:57:14 value_len=0 record: offset=55788, type=attribute-update (sync), size=132, modseq=603 - add: private/vendor/vendor.dovecot/pvt/server/sieve/files/test1 : timestamp=2015-12-09 15:53:28 value_len=0 - add: private/vendor/vendor.dovecot/pvt/server/sieve/files/test2 : timestamp=2015-12-09 15:57:14 value_len=0 Apparently something gets messed up on the receiving side and strange things appear in the transaction log (e.g. test1 with a timestamp of 15:57:14 which it never had). The fact that it happens sometimes (around 30-40% of the time) likely indicates a race condition somewhere. Also I'm not at all sure sieve transactions should appear twice on the receiving side (ext and then sync); I see other entries (e.g. ext-intro) as a single "(ext) (sync)" record. Any ideas? Thanks, Apollon doveconf -n output follows: # 2.2.18: /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.8 (0c4ae064f307+) # OS: Linux 3.16.0-4-amd64 x86_64 Debian 8.2 auth_mechanisms = plain login default_vsz_limit = 320 M mail_location = mdbox:~/mdbox:ALT=/srv/mail/alt/%d/%n mail_plugins = " acl notify replication acl" 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 index ihave duplicate namespace { location = maildir:/home/vmail/example.com/staging/Maildir:INDEX=/home/vmail/%d/%n/sta… prefix = Staging. subscriptions = no type = public } 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 = separator = . type = private } passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } plugin { acl = vfile sieve = ~/.dovecot.sieve sieve_before = /home/vmail/global.sieve sieve_default = /home/vmail/global.sieve sieve_dir = ~/sieve } protocols = " imap sieve" service aggregator { fifo_listener replication-notify-fifo { user = vmail } unix_listener replication-notify { user = vmail } } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { group = vmail mode = 0777 } } service doveadm { inet_listener { port = 12345 ssl = yes } vsz_limit = 1 G } service imap-login { process_limit = 500 process_min_avail = 5 } service imap-postlogin { executable = script-login /usr/local/sbin/ldap-postlogin user = $default_internal_user } service imap { executable = imap imap-postlogin process_limit = 1024 } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0600 user = vmail } } ssl_cert = </etc/ssl/certs/dovecot.crt ssl_client_ca_dir = /etc/ssl/certs ssl_key = </etc/ssl/private/dovecot.key userdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } protocol lda { log_path = /var/log/dovecot/deliver.log mail_plugins = sieve replication notify } protocol imap { mail_max_userip_connections = 500 }

1 0

v2.2.20 released
by Timo Sirainen 09 Dec '15

09 Dec '15

http://dovecot.org/releases/2.2/dovecot-2.2.20.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.20.tar.gz.sig This could be (one of) the last v2.2.x release. We're starting v2.3 development soon. + Added mailbox { autoexpunge=<time> } setting. See http://wiki2.dovecot.org/MailboxSettings for details. + ssl_options: Added support for no_ticket + imap/pop3/managesieve-login: Added postlogin_socket=path passdb extra field. This allows replacing the default service imap/pop3/managesieve {} settings for specific users (e.g. running their imap process via valgrind or strace). + doveadm fetch: Added date.sent/received/saved.unixtime + fs-posix: Added mode=auto parameter to set the created files' and directories' mode based on the parent dir if it has setgid-bit. + director: Support backends having hostnames, which makes it possible to verify their SSL certificates. - director: Directors' state became desynchronized if doveadm director commands were used to modify the same backend in multiple directors at the same time with conflicting changes. This fix includes some extra checks, which makes sure that if such a conflict still happens it's automatically fixed. In some situations such an automatic fix may now be unnecessarily triggered and an error logged. - director: Backend tags weren't working correctly. - ldap: tls_* settings weren't used for ldaps URIs. - ldap, mysql: Fixed setting connect timeout. - auth: userdb lookups via auth-worker couldn't change username - dsync: Fixed handling deleted directories. Make sure we don't go to infinite mailbox renaming loop. - imap: Fixed crash in NOTIFY when there were watched namespaces that didn't support NOTIFY. - imap: After SETMETADATA was used, various commands (especially FETCH) could have started hanging when their output was large. - stats: Idle sessions weren't refreshed often enough, causing stats process to forget them and log errors about unknown sessions when they were updated later. - stats: Fixed "Duplicate session ID" errors when LMTP delivered to multiple recipients and fts_autoindex=yes. - zlib plugin: Fixed copying causing cache corruption when zlib_save wasn't set, but the source message was compressed. - fts-solr: Fixed escaping Solr query parameters. - lmtp: quota_full_tempfail=yes was ignored with lmtp_rcpt_check_quota=yes

9 12

core-dump in imap (Dovecot 2.2.19)
by Peter Eriksson 09 Dec '15

09 Dec '15

Just found a coredump from the imap process for one of our users on dovecot 2.2.19 on a Solaris 10/x86 system: > Dec 8 14:33:17 mail dovecot: [ID 583609 mail.crit] imap(leijo): Fatal: master: service(imap): child 14465 killed with signal 11 (core dumped) Please find attached dovecot -n output and some gdb backtrace. It seems that cmd->client was NULL when dereferencing it at line 178 in imap-commands.c (in the function command_exec): > 178 cmd->bytes_in += i_stream_get_absolute_offset(cmd->client->input) - > 179 cmd_start_bytes_in; Please let me know if you need more information. I don't know what the users was doing at that specific time. --- [Ll.U] Peter Eriksson KITVS-IFM & ITI-NET IT.LiU.SE +46-70 518 2786

2 1

Autoexpunge and special user namespace
by Joseph Tam 09 Dec '15

09 Dec '15

I'm interested in replacing my cron script that expunges old deleted mail with the new feature announced in 2.2.20 > + Added mailbox { autoexpunge=<time> } setting. See > http://wiki2.dovecot.org/MailboxSettings for details. To use it, I need to specify which mailbox needs them using the namespace configuration. For example namespace inbox { mailbox Trash { auto = no special_use = \Trash autoexpunge = 7d mailbox_list_index = yes } mailbox trash { auto = no special_use = \Trash autoexpunge = 7d mailbox_list_index = yes } mailbox "Deleted Messages" { auto = no special_use = \Trash autoexpunge = 7d mailbox_list_index = yes } mailbox "Deleted Items" { auto = no special_use = \Trash autoexpunge = 7d mailbox_list_index = yes } ... } Different readers use different mailboxes, so I include the common ones. Some questions: 1) Do I need the special_user configuration at all? Will some clients start using different mailboxes to store deleted mail if I keep the special_use lines? 2) I also expunge old mail in INBOX marked as deleted -- is there any way to handle this case? Create virtual mailbox? Joseph Tam <jtam.home(a)gmail.com>

2 1

v2.2.20 release candidate released
by Timo Sirainen 08 Dec '15

08 Dec '15

http://dovecot.org/releases/2.2/rc/dovecot-2.2.20.rc1.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.20.rc1.tar.gz.sig v2.2.20 probably will be released tomorrow or maybe during weekend. + Added mailbox { autoexpunge=<time> } setting. See http://wiki2.dovecot.org/MailboxSettings for details. + ssl_options: Added support for no_ticket + imap/pop3/managesieve-login: Added postlogin_socket=path passdb extra field. This allows replacing the default service imap/pop3/managesieve {} settings for specific users (e.g. running their imap process via valgrind or strace). + doveadm fetch: Added date.sent/received/saved.unixtime + fs-posix: Added mode=auto parameter to set the created files' and directories' mode based on the parent dir if it has setgid-bit. + director: Support backends having hostnames, which makes it possible to verify their SSL certificates. - director: Directors' state became desynchronized if doveadm director commands were used to modify the same backend in multiple directors at the same time with conflicting changes. This fix includes some extra checks, which makes sure that if such a conflict still happens it's automatically fixed. In some situations such an automatic fix may now be unnecessarily triggered and an error logged. - director: Backend tags weren't working correctly. - ldap: tls_* settings weren't used for ldaps URIs. - ldap, mysql: Fixed setting connect timeout. - auth: userdb lookups via auth-worker couldn't change username - dsync: Fixed handling deleted directories. Make sure we don't go to infinite mailbox renaming loop. - imap: Fixed crash in NOTIFY when there were watched namespaces that didn't support NOTIFY. - imap: After SETMETADATA was used, various commands (especially FETCH) could have started hanging when their output was large. - stats: Idle sessions weren't refreshed often enough, causing stats process to forget them and log errors about unknown sessions when they were updated later. - stats: Fixed "Duplicate session ID" errors when LMTP delivered to multiple recipients and fts_autoindex=yes. - zlib plugin: Fixed copying causing cache corruption when zlib_save wasn't set, but the source message was compressed. - fts-solr: Fixed escaping Solr query parameters.

6 11

Which mail does a certain attachment belong to?
by Ralf Hildebrandt 08 Dec '15

08 Dec '15

I'm seeing this: ./17/3c/173c81da2aab91f225f8eb5e8fcc87119be4eff0-b38d990442316a54a90c00008f4649af: SecuriteInfo.com.TR.Kryptik.180736.5155.16748.22498.UNOFFICIAL FOUND ./17/3c/173c81da2aab91f225f8eb5e8fcc87119be4eff0-bc70851b03216a54483f00008f4649af: SecuriteInfo.com.TR.Kryptik.180736.5155.16748.22498.UNOFFICIAL FOUND When scanning the "attachments" directory of my mdbox. How can I find out WHICH EMAIL these two attachments belong to? mail_location = mdbox:~/mdbox mail_plugins = zlib fts fts_lucene mdbox_rotate_size = 128M mdbox_rotate_interval = 0 mail_attachment_dir = /some/path/attachments mail_attachment_min_size = 128k mail_attachment_fs = sis posix mail_attachment_hash = %{sha1} -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstraße 15, 81669 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein

3 2

Released Pigeonhole v0.4.10.rc2 for Dovecot v2.2.20
by Stephan Bosch 08 Dec '15

08 Dec '15

Hello Dovecot users, Here's the Pigeonhole RC that goes with Dovecot v2.2.20. Due to the earlier described conflict, RC1 will not compile with the new Dovecot release. I am not really in hurry to make a definitive release of Pigeonhole, since v0.4.9 still compiles fine with Dovecot v2.2.20. Still, if no big bugs emerge in the next few days, I will make a final release. So, please test this new RC and especially the new features. 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 candidate and don't hesitate to notify me when there are any problems. Regards, -- Stephan Bosch stephan(a)rename-it.nl

1 0

EVP_PKEY_get1_EC_KEY:expecting a ec key
by Oliver Riesen-Mallmann 07 Dec '15

07 Dec '15

Hi, since my last update from the Dovecot Prebuilt Binary for Debian I get a lot of messages like this in mail.log: dovecot: imap-login: Error: SSL: Stacked error: error:0608308E:digital envelope routines:EVP_PKEY_get1_EC_KEY:expecting a ec key Nevertheless Dovecot seems to work normally. Email client doesn't mention any error. This was my last update: Start-Date: 2015-12-04 14:00:31 Commandline: apt-get upgrade Upgrade: dovecot-core:amd64 (2.2.19-1~auto+98, 2.2.20~rc1-1~auto+3), dovecot-managesieved:amd64 (2.2.19-1~auto+98, 2.2.20~rc1-1~auto+3), dovecot-sieve:amd64 (2.2.19-1~auto+98, 2.2.20~rc1-1~auto+3), dovecot-imapd:amd64 (2.2.19-1~auto+98, 2.2.20~rc1-1~auto+3), dovecot-pop3d:amd64 (2.2.19-1~auto+98, 2.2.20~rc1-1~auto+3), openssl:amd64 (1.0.1e-2+deb7u17, 1.0.1e-2+deb7u18), libssl1.0.0:amd64 (1.0.1e-2+deb7u17, 1.0.1e-2+deb7u18) End-Date: 2015-12-04 14:00:53 My current Dovecot version: 2.2.20.rc1 (0b81127e53da) on Linux 3.2.0-4-amd64 #1 SMP Debian 3.2.68-1+deb7u1 x86_64 Is it a bug in Dovecot or in openssl/libssl? Regards Oliver

2 1

Dovecot cluster using GlusterFS
by Filip Pytloun 07 Dec '15

07 Dec '15

Hello, I have recently setup mailserver solution using 2-node master-master setup (mainly based on MySQL M-M replication and GlusterFS with 2 replica volume) on Ubuntu 14.04 (Dovecot 2.2.9). Unfortunately even with shared-storage-aware setting: mail_nfs_index = yes mail_nfs_storage = yes mail_fsync = always mmap_disable = yes ..I have hit strange issues pretty soon especially when user was manipulating same mailbox from multiple devices at the same time. Most issues was about corrupted indexes which was solved easily by just putting them on local storage of each node: mail_location = maildir:/srv/mail/%d/%u:INDEX=/var/lib/dovecot/index/%d/%u But I still hit issues like this one: dovecot: lmtp(6276, user(a)example.com) Error: Broken file /srv/mail/example.com/user(a)example.com/dovecot-uidlist line 8529: UIDs not ordered (8527 >= 8527) Which I am not sure how serious it is or if it's possible to solve or workaround? Anyway because of the above and high possibility of GlusterFS split-brains, I have decided to setup Dovecot Director according to the docs [1] but I have a couple of questions: - is custom monitoring still required? Poolmon [2] is 4 year old so I would suppose there's some progress since that? - it's not possible to have same backends and directors in Dovecot <2.2.17. I can backport newer Dovecot for Ubuntu Trusty, so this is not an issue, but.. - documentation states that it still doesn't work for LMTP [3]? Which is probably important for my setup, because both Postfix servers are using dovecot-lmtp for mail delivery so there can be still some issues (but probably less frequent?) when both servers will deliver new mails for one user at once. So do I really have to split directors from backends? Anyone has experience with clustered Dovecot setup? Why is Dovecot behaving so bad when it pretends to be shared storage friendly? Are these issues only specific for older Dovecot? Or is there something wrong in my architecture design? Thanks for any help, Filip --- [1] http://wiki2.dovecot.org/Director [2] https://github.com/brandond/poolmon/ [3] "LMTP however doesn't currently support mixing recipients to both being proxied and store locally." --- BTW if someone is interested in SaltStack, here are Salt formulas for Dovecot + Postfix + GlusterFS + Roundcube + Mailman setup which we are using: https://github.com/tcpcloud/salt-formula-dovecot https://github.com/tcpcloud/salt-formula-postfix https://github.com/tcpcloud/salt-formula-roundcube https://github.com/tcpcloud/salt-formula-glusterfs

6 7

mmap_disable=yes not honored always
by Peter Benko 06 Dec '15

06 Dec '15

<Sorry for the resend, it seems that the formatting of my original mail got garbled> Hi all, I'm experimenting with having the mail store on a 9p file system that lacks mmap() functionality. So I disabled it in dovecot: mmap_disable = yes However, I keep getting the following error messages in my log: Oct 15 16:55:00 computer-name dovecot: imap user(a)domain.com[192.168.1.3] Error: mmap() failed with file /mail/mailboxes/domain.com/user/indexpvt-accounts/other-user/mailboxes/INBOX/dovecot.index.pvt.log: Invalid argument I only get those messages for the shared folder's private indexes. This setup works perfectly on an ext2/3/4 fs. Any opinions, is this a bug? Is mmap_disable not mandatory for all operations? Best regards, Peter

2 1

[PATCH] [dovecot 2.2.9] Quota warnings ignored with FS quotas
by Grzegorz Nosek 06 Dec '15

06 Dec '15

Hi all, I noticed that in some circumstances quota warnings are ignored. The bug arises when both of the following are used: 1. percentage-based quota warnings, i.e.: quota_warning = storage=1%% quota-warning 1 %u 2. filesystem quota backend (and probably others, except for quotas configured directly in dovecot config) Percentage-based quota warnings have rule.bytes_limit recalculated based on root_set->default_rule.bytes_limit, however this value is zero when FS quotas are in use. Real quota values (from quotactl) are fetched very late, in quota_warnings_execute() but at that point no recalculation happens. As the warning rules have bytes_limit==0, they're effectively ignored. The patch below enables quota warnings to be sent when using filesystem (and possibly maildirsize-based) quotas. Based and tested on Ubuntu 14.04's dovecot 2.2.9. Best regards, Grzegorz Nosek diff --git a/src/plugins/quota/quota.c b/src/plugins/quota/quota.c index adbd70d..8e4d7e0 100644 --- a/src/plugins/quota/quota.c +++ b/src/plugins/quota/quota.c @@ -1163,6 +1163,8 @@ static void quota_warnings_execute(struct quota_transaction_context *ctx, &count_current, &count_limit) < 0) return; + quota_root_recalculate_relative_rules(root->set, bytes_limit, count_limit); + bytes_before = bytes_current - ctx->bytes_used; count_before = count_current - ctx->count_used; for (i = 0; i < count; i++) {

3 3

SIS attachments compressed
by Juan Carlos Sanchez 06 Dec '15

06 Dec '15

Hello: In case it is defined to use zlib compression, does SIS save attachments compressed? I have found this question replied in the past (2012) and the answer was NO. I ask again just to know if there have been changes or if it is in the roadmap to add compression. I have been testing to migrate from maildir+zlib to mdbox+zlib+sis and the results, in terms of space used, and worst than using just mdbox+zlib (without SIS), and suppose the reason in the lack of compression in attachments. Thanks in advance. -- ------------------------------------------------------ Juan Carlos Sanchez Hernandez Responsable de Seguridad y Correo Electronico Servicio de Planificacion Informatica y Comunicaciones Universidad Politecnica de Madrid Rectorado Avda. Ramiro de Maeztu 7 28040 Madrid ------------------------------------------------------

2 1

[Dovecot] lmtp_rcpt_check_quota not working
by Bernhard Schmidt 06 Dec '15

06 Dec '15

Hi, Dovecot 2.2.9 (Debian package from backports) does not seem to respect lmtp_rcpt_check_quota # 2.2.9: /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.4 deliver_log_format = from=<%e>, size=%p, message-id=<%m>, status=%$ disable_plaintext_auth = no lmtp_rcpt_check_quota = yes mail_debug = yes mail_gid = mstore mail_location = maildir:~/Maildir:INDEX=/var/cache/dovecot/index/%-1.1u/%u mail_plugins = quota mail_uid = mstore 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 mmap_disable = yes namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = INBOX. separator = . type = private } passdb { args = /etc/dovecot/dovecot-ldap.conf driver = ldap } plugin { quota = maildir quota_rule = ?:storage=512M quota_rule2 = INBOX.Trash:ignore quota_status_nouser = DUNNO quota_status_overquota = 452 4.2.2 Mailbox is full quota_status_success = DUNNO quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=85%% quota-warning 85 %u sieve = ~/currently-active-script.sieve sieve_dir = ~/sieve } pop3_uidl_format = %08Xv%08Xu protocols = imap lmtp sieve pop3 quota_full_tempfail = yes service anvil { client_limit = 3000 unix_listener anvil { group = sudo mode = 0660 } } service auth { client_limit = 3000 unix_listener auth-userdb { group = mstore mode = 0660 user = mstore } } service imap-login { client_limit = 1024 inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } process_limit = 2500 process_min_avail = 4 service_count = 0 } service lmtp { inet_listener lmtp { address = xxx port = 24 } } service managesieve-login { inet_listener sieve { port = 2000 } service_count = 1 } service managesieve { process_limit = 1024 } service pop3-login { inet_listener pop3 { port = 110 } inet_listener pop3s { port = 995 ssl = yes } } service quota-status { client_limit = 5 executable = quota-status -p postfix inet_listener { address = xxx port = 12340 } } service quota-warning { executable = script /etc/dovecot/quotawarnmsg.sh unix_listener quota-warning { user = mstore } user = mstore } ssl_cert = </etc/dovecot/dovecot.pem ssl_key = </etc/dovecot/private/dovecot.pem userdb { driver = prefetch } userdb { args = /etc/dovecot/dovecot-ldap.conf driver = ldap } verbose_proctitle = yes protocol imap { mail_plugins = quota imap_quota imap_zlib } protocol lda { mail_plugins = quota sieve } protocol lmtp { mail_plugins = quota sieve } so Dovecot should reject in RCPT TO phase, but according to the logs of the upstream Postfix it does so after END-OF-DATA (host xxx[2001:xxx] said: 452 4.2.2 <user(a)domain.de> Quota exceeded (mailbox for user is full) (in reply to end of DATA command)) I haven't seen any commits regarding to this in 2.2.10 or tip. Regards, Bernhard

3 6

Dovecot 2.2.18.2: Panic: file fs-api.c: line 756 (fs_copy): assertion failed: (src->fs == dest->fs)
by Frank Mehrtens 06 Dec '15

06 Dec '15

Hello, a colleague found some strange messages in the logs: Oct 27 13:08:43 mail postfix/qmgr[1618]: E83C8180F56: from=<user1(a)domain.de>, size=298937, nrcpt=2 (queue active) Oct 27 13:08:43 mail dovecot: lmtp(6740): Connect from local Oct 27 13:08:43 mail dovecot: lmtp(user2(a)domain.de): gYFbBEdpL1ZUGgAA0nA0dQ: message-id=<035901d110b0$3929bc20$ab7d3460$(a)domain.de>: saved mail to INBOX (from: user1(a)domain.de, subject: WG: Matthias, size: 295392) Oct 27 13:08:43 mail postfix/lmtp[6702]: E83C8180F56: to=<user2(a)domain.de>, relay=mail.domain.de[private/dovecot-lmtp], delay=0.41, delays=0.36/0/0/0.05, dsn=2.0.0, status=sent (250 2.0.0 <user2(a)domain.de> gYFbBEdpL1ZUGgAA0nA0dQ Saved) Oct 27 13:08:43 mail dovecot: lmtp(mailarchiv(a)domain.de): Panic: file fs-api.c: line 756 (fs_copy): assertion failed: (src->fs == dest->fs) Oct 27 13:08:43 mail dovecot: lmtp(mailarchiv(a)domain.de): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0x7b53a) [0x7f10419e553a] -> /usr/lib64/dovecot/libdovecot.so.0(+0x7b5a6) [0x7f10419e55a6] -> /usr/lib64/dovecot/libdovecot.so.0(+0x281ea) [0x7f10419921ea] -> /usr/lib64/dovecot/libdovecot.so.0(+0x3163a) [0x7f104199b63a] -> /usr/lib64/dovecot/libdovecot-storage.so.0(sdbox_copy+0x4c4) [0x7f1041cbad94] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_copy+0x7a) [0x7f1041c9f37a] -> /usr/lib64/dovecot/libdovecot-lda.so.0(mail_deliver_save+0x1a7) [0x7f1041f891b7] -> /usr/lib64/dovecot/libdovecot-lda.so.0(mail_deliver+0x11b) [0x7f1041f8956b] -> dovecot/lmtp() [0x406922] -> dovecot/lmtp() [0x40730d] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x5b) [0x7f10419f7fbb] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xaf) [0x7f10419f918f] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x9) [0x7f10419f8049] -> /usr/lib64/dovecot/libdovec ot.so.0(io_loop_run+0x38) [0x7f10419f80c8] -> /usr/lib64/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f1041997043] -> dovecot/lmtp(main+0x18b) [0x404dbb] -> /lib64/libc.so.6(__libc_start_main+0xfd) [0x7f10415f4d5d] -> dovecot/lmtp() [0x404b49] Oct 27 13:08:43 mail dovecot: lmtp(mailarchiv(a)domain.de): Fatal: master: service(lmtp): child 6740 killed with signal 6 (core dumps disabled) Oct 27 13:08:43 mail postfix/lmtp[6702]: E83C8180F56: to=<mailarchiv(a)domain.de>, relay=mail.domain.de[private/dovecot-lmtp], delay=0.41, delays=0.36/0/0/0.05, dsn=4.4.2, status=deferred (lost connection with mail.domain.de[private/dovecot-lmtp] while sending end of data -- message may be sent more than once) Postfix always_bcc set to mailarchiv(a)domain.de. [root@mail ~]# rpm -qa | grep dove dovecot-ee-2.2.18.2-1.el6.x86_64 dovecot-ee-managesieve-0.4.8-1.el6.x86_64 dovecot-ee-pigeonhole-0.4.8-1.el6.x86_64 [root@mail ~]# doveconf -n # 2.2.18.2 (866bffbafde7): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.8 (73d4f6cd676a) # OS: Linux 2.6.32-573.7.1.el6.x86_64 x86_64 CentOS release 6.7 (Final) ext4 auth_cache_negative_ttl = 0 auth_mechanisms = plain login deliver_log_format = message-id=%m: %$ (from: %f, subject: %s, size: %p) dict { quota = pgsql:/etc/dovecot/dovecot-dict-sql.conf.ext } disable_plaintext_auth = no imap_client_workarounds = tb-extra-mailbox-sep mail_attachment_dir = /storage/mail/attachments mail_attachment_hash = %{sha512} mail_gid = vmail mail_location = sdbox:/storage/mail/%d/%n mail_plugins = acl quota mail_uid = vmail 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 index ihave duplicate namespace { list = children location = sdbox:/storage/mail/%%d/%%n/ prefix = shared/%%u/ separator = / subscriptions = no type = shared } namespace { list = children location = maildir:/storage/mail/public:INDEX=/storage/mail/%d/%n/public prefix = public/ separator = / subscriptions = no type = public } namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox "Gelöschte Objekte" { special_use = \Trash } mailbox "Gesendete Objekte" { special_use = \Sent } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = subscriptions = yes type = private } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { acl = vfile acl_shared_dict = file:/storage/mail/shared-mailboxes sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } protocols = imap lmtp sieve service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } } service dict { unix_listener dict { group = vmail mode = 0660 user = vmail } } service imap-login { inet_listener imaps { ssl = yes } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0660 user = postfix } } service pop3-login { inet_listener pop3s { ssl = yes } } ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = </etc/pki/dovecot/private/dovecot.pem userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol lmtp { mail_plugins = acl quota sieve } protocol imap { mail_plugins = acl quota imap_acl imap_quota } Best regards Frank -- DECOIT GmbH Fahrenheitstraße 9 D-28359 Bremen Tel.: +49-421-596064-0 Fax: +49-421-596064-09 E-Mail: info(a)decoit.de <mailto:info@decoit.de> Web: http://www.decoit.de <http://www.decoit.de/> Amtsgericht Bremen, HRB 21533 Geschäftsführer: Prof. Dr.-Ing. Kai-Oliver Detken

2 1

mailbox_list_index and maildir_very_dirty_syncs are in conflicts?
by Alessio Cecchi 06 Dec '15

06 Dec '15

Hi, I’m running Dovecot 2.2.19 with Maildir as storage and LDA for delivery. I noticed that if I set mailbox_list_index=yes and maildir_very_dirty_syncs=yes when I login via IMAP the STATUS command don’t “see” new messages in sub-folders (like Spam). Example, a new message as arrived in Spam folder (I can see in Maildir/new/) but IMAP STATUS don’t see it: . STATUS Spam (MESSAGES UNSEEN) * STATUS Spam (MESSAGES 139 UNSEEN 0) (in this case the date of “dovecot.list.index” files is not updated) If I comment out mailbox_list_index=yes or maildir_very_dirty_syncs=yes I can see the new message: . STATUS Spam (MESSAGES UNSEEN) * STATUS Spam (MESSAGES 140 UNSEEN 1) (in this case the date of “dovecot.list.index” files is updated after the STATUS command) Instead the SELECT command works fine always. An importante note, my dovecot LDA configuration (on MX servers) don’t update index files: protocol lda { mail_location = maildir:~/Maildir:INDEX=MEMORY mail_plugins = quota acl expire fts fts_solr zlib sieve } These because I need to filter incoming email via Sieve but since I cannot use LMTP (and Director) on MX (but I have Director for POP/IMAP access) the only way for not corrupting dovecot.index files is not update their on delivery emails. But reading http://wiki2.dovecot.org/MailLocation/Maildir this shouldn’t be a problem (Optimizations “maildir_very_dirty_syncs=yes” … It's still safe to deliver new mails to new/ …) since MX deliver new emails in new/. Is a Dovecot limit or is a problem of my configuration? Thanks my configuration: # 2.2.19 # Pigeonhole version 0.4.9 auth_cache_negative_ttl = 5 mins auth_cache_size = 10 M auth_cache_ttl = 20 mins auth_master_user_separator = * auth_worker_max_count = 50 deliver_log_format = msgid=%m, from=%f, subject="%s": %$ dict { acl = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext expire = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext sqlquota = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext } disable_plaintext_auth = no first_valid_gid = 89 first_valid_uid = 89 imap_client_workarounds = delay-newmail tb-extra-mailbox-sep tb-lsub-flags imap_idle_notify_interval = 29 mins imap_logout_format = in=%i out=%o session=<%{session}> last_valid_gid = 89 last_valid_uid = 89 lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes listen = 10.96.3.156 login_trusted_networks = 10.0.0.0/24 mail_fsync = always mail_location = maildir:~/Maildir mail_plugins = quota acl expire fts fts_solr zlib mailbox_list_index = yes maildir_very_dirty_syncs = yes managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate vnd.dovecot.duplicate mmap_disable = yes namespace { list = children location = maildir:%%h/Maildir:INDEX=~/Maildir/shared/%%u prefix = shared/%%n/ separator = / subscriptions = no type = shared } namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Spam { auto = subscribe special_use = \Junk } mailbox Trash { auto = subscribe special_use = \Trash } prefix = separator = / } passdb { args = /etc/dovecot/dovecot-deny-sql.conf.ext deny = yes driver = sql } passdb { args = /etc/dovecot/extra/master-users driver = passwd-file master = yes pass = yes } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { acl = vfile acl_shared_dict = proxy::acl antispam_backend = mailtrain antispam_mail_notspam = --ham antispam_mail_sendmail = /usr/bin/sa-learn antispam_mail_spam = --spam antispam_spam = Spam antispam_trash = Trash expire = Trash expire2 = Spam expire_dict = proxy::expire fts = solr fts_solr = url=http://10.0.0.1:8983/solr/ quota = maildir:UserQuota quota2 = dict:Quota Usage::noenforcing:proxy::sqlquota quota_grace = 10M quota_rule2 = Trash:storage=+100M quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=80%% quota-warning 80 %u sieve = ~/.dovecot.sieve sieve_before = /etc/dovecot/sieve/before.sieve sieve_dir = ~/sieve sieve_extensions = +vnd.dovecot.duplicate -vacation zlib_save = gz zlib_save_level = 6 } pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_fast_size_lookups = yes pop3_logout_format = top=%t/%p, retr=%r/%b, del=%d/%m, size=%s, bytes=%i/%o, session=<%{session}> protocols = imap pop3 sieve sendmail_path = /var/qmail/bin/sendmail service auth { client_limit = 6524 unix_listener auth-userdb { group = vchkpw mode = 0660 user = vpopmail } } service dict { process_limit = 500 unix_listener dict { group = vchkpw mode = 0660 user = vpopmail } } service imap-login { process_min_avail = 4 service_count = 0 } service imap-postlogin { executable = script-login /etc/dovecot/scripts/imap-postlogin.sh unix_listener imap-postlogin { group = vchkpw mode = 0660 user = vpopmail } user = vpopmail } service imap { executable = imap imap-postlogin process_limit = 5000 service_count = 100 vsz_limit = 384 M } service managesieve-login { inet_listener sieve { port = 4190 } } service pop3-login { process_min_avail = 4 service_count = 0 } service pop3-postlogin { executable = script-login /etc/dovecot/scripts/pop3-postlogin.sh unix_listener pop3-postlogin { group = vchkpw mode = 0660 user = vpopmail } user = vpopmail } service pop3 { executable = pop3 pop3-postlogin process_limit = 1024 service_count = 100 } service quota-warning { executable = script /etc/dovecot/scripts/quota-warning.sh unix_listener quota-warning { user = vpopmail } user = vpopmail } ssl_cert = </etc/dovecot/ssl/wildcard.pem ssl_key = </etc/dovecot/ssl/wildcard.key ssl_protocols = !SSLv2 !SSLv3 submission_host = 127.0.0.1 userdb { driver = prefetch } userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } verbose_proctitle = yes protocol lda { mail_location = maildir:~/Maildir:INDEX=MEMORY mail_plugins = quota acl expire fts fts_solr zlib sieve } protocol imap { mail_max_userip_connections = 25 mail_plugins = quota acl expire fts fts_solr zlib imap_quota imap_acl imap_zlib } protocol sieve { mail_max_userip_connections = 2 } protocol pop3 { mail_max_userip_connections = 5 } -- Alessio Cecchi Postmaster AT http://www.qboxmail.it http://www.linkedin.com/in/alessice

2 1

ACL Troubles
by Bobber 06 Dec '15

06 Dec '15

Using dovecot version 2.2.19. In the config file I have the following to set up acls: > mail_plugins = $mail_plugins acl > protocol imap { > mail_plugins = $mail_plugins imap_acl > } > plugin { > acl = vfile:/usr/local/etc/dovecot/acls:cache_secs=300 > } And here's my acl file: > * anyone rl I am getting the following error in the dovecot log file: > Error: Global ACL file /usr/local/etc/dovecot/acls line 1: Unknown ID 'anyone rl' Also, my subfolders in the shared mailbox area are no longer visible or accessible. Any ideas what I am doing wrong? -- *Bob Wooldridge* Blog: http://kc0dxf.net/blog/

2 1

LIST MANAGEMENT BROKEN
by Edwardo Garcia 06 Dec '15

06 Dec '15

Timo I have for two days try to unsubscribe from this list using email mailman. The list server does not send me confirmation request. Please fix your server and remove me

2 1

Released Pigeonhole v0.4.10.rc1 for Dovecot v2.2.20.rc1
by Stephan Bosch 05 Dec '15

05 Dec '15

Hello Dovecot users, Here's the Pigeonhole RC that goes with the Dovecot RC. There is a conflict with the t_str_trim() function. To be able to quickly release Dovecot, Timo has reverted the involved change so that 0.4.9 will still compile with the final Dovecot v2.2.20 release. This Pigeonhole RC will therefore not compile against the final Dovecot release (only against v2.2.20.rc1), which I will mend quickly once Dovecot v2.2.20 is released. Changelog v0.4.10.rc1: + 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 candidate and don't hesitate to notify me when there are any problems. Regards, -- Stephan Bosch stephan(a)rename-it.nl

1 0

Content-Enconding
by Leander Schäfer 05 Dec '15

05 Dec '15

Hi, With Apache one may use "mod_deflate" in order to reduce bandwidth by using e.g. gzip to compress the http traffic. I would like to use something similar for email traffic between mail clients to dovecote and postfix. My questions are: a) Is this established well enough in most mail clients? b) Can you recomment a good tutorial for this? Thank you very much

2 3

object storage
by Bradley Giesbrecht 04 Dec '15

04 Dec '15

Is the Dovecot Object Storage plugin still available for purchase? Clicking the store link [2] from this page [1] does not show any info about purchasing the plugin. [1] http://www.dovecot.fi/dovecot-object-storage-plugins-available-for-online-p… [2] http://shop.dovecot.fi/ Regards, Bradley Giesbrecht (pixilla)

7 7

FTS solr issue.
by Vijay Sarvepalli 04 Dec '15

04 Dec '15

Hello Dovecot admins, I seem to have a problem ever since recent upgrades to dovecot. The solr engine complains about some variable not being long. Although it does not say which variable. I havve updated the solr-schema.xml file from current dovecot install 2.2.15 ! Any ideas would be very helpful INFO: [] webapp=/solr path=/select params={fl=uid,score&sort=uid+asc&q=from:"modracon"+OR+to:"modracon"+OR+cc:"modracon"+OR+subject:"modracon"&fq=%2Bbox:1483350010e1de52e93800004bc94032+%2Buser:" user-psmail.net"&rows=106375} status=500 QTime=6 Dec 04, 2015 5:04:26 PM org.apache.solr.common.SolrException log SEVERE: java.lang.NumberFormatException: Invalid shift value in prefixCoded string (is encoded value really a LONG?) at org.apache.lucene.util.NumericUtils.prefixCodedToLong(NumericUtils.java:205)

1 0

Interpreting keywords
by Mark Foley 04 Dec '15

04 Dec '15

I've marked several messages in Thunderbird using tags. Tags used are: 0 Important 1 Work 2 To Do 3 Personal 4 Later The messages so tagged appear to have the flag fields set in the IMAP Maildir: cur/1449002162.8993_0.mail:2,Sb cur/1449001929.28087_0.mail:2,Sad I've looked in dovecot-keywords and find: $ more dovecot-keywords 0 $label1 1 $label2 2 $label3 3 $label4 I assume these "$label" values are macros that possibly refer to "Important", "Work", etc., but where are these $label's defined? Are they defined in the dovecot configs somewhere or does the mail client just "know" what these correspond to? --Mark

4 3

Trouble setting replication over TCP
by Борис Кукушкин 04 Dec '15

04 Dec '15

Good day, everyone. I'm playing around with replication to create a backup host. I have hosts backend3 (192.168.100.112) and backend3-replica (192.168.100.113). backend3 acts as a mail-receiving host, backend3-replica is a backup for the case of failure. Both versions are 2.2.13 (form Debian Jessie repository). backend3 receives mail via LMTP-proxy. So far I've managed to setup replication via ssh, but didn't have success with TCP replication. Any help would be much appreciated. Here is what I have in logs when processing a newly delivered e-mail. backend3: Dec 4 17:04:07 backend3 dovecot: lmtp(5451): Debug: none: root=, index=, indexpvt=, control=, inbox=, alt= Dec 4 17:04:07 backend3 dovecot: lmtp(5451): Connect from 192.168.100.101 Dec 4 17:04:07 backend3 dovecot: lmtp(5451): Debug: Loading modules from directory: /usr/lib/dovecot/modules Dec 4 17:04:07 backend3 dovecot: lmtp(5451): Debug: Module loaded: /usr/lib/dovecot/modules/lib15_notify_plugin.so Dec 4 17:04:07 backend3 dovecot: lmtp(5451): Debug: Module loaded: /usr/lib/dovecot/modules/lib20_replication_plugin.so Dec 4 17:04:07 backend3 dovecot: auth: Debug: master in: USER#0111#011postmaster(a)mailnet.local #011service=lmtp#011lip=192.168.100.112#011lport=24#011rip=127.0.0.1#011rport=33133 Dec 4 17:04:07 backend3 dovecot: auth-worker(5446): Debug: sql(postmaster(a)mailnet.local,127.0.0.1): SELECT pop AS home, uid, gid, CONCAT('*:bytes=', CAST(quota*1024*1024 AS CHAR)) AS quota_ rule FROM users WHERE username = 'postmaster(a)mailnet.local' Dec 4 17:04:07 backend3 dovecot: auth: Debug: userdb out: USER#0111#011postmaster(a)mailnet.local #011home=/usr/local/mail/mailnet.local/postmaster#011uid=8#011gid=8#011quota_rule=*:bytes=1048 57600 Dec 4 17:04:07 backend3 dovecot: lmtp(5451): Debug: auth input: postmaster(a)mailnet.local home=/usr/local/mail/mailnet.local/postmaster uid=8 gid=8 quota_rule=*:bytes=104857600 Dec 4 17:04:07 backend3 dovecot: lmtp(5451): Debug: Added userdb setting: plugin/quota_rule=*:bytes=104857600 Dec 4 17:04:07 backend3 dovecot: lmtp(5451): Debug: Effective uid=8, gid=8, home=/usr/local/mail/mailnet.local/postmaster Dec 4 17:04:07 backend3 dovecot: lmtp(5451): Debug: Namespace inbox: type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:/usr/local/mail/mailnet. local/postmaster/Maildir Dec 4 17:04:07 backend3 dovecot: lmtp(5451): Debug: maildir++: root=/usr/local/mail/mailnet.local/postmaster/Maildir, index=, indexpvt=, control=, inbox=/usr/local/mail/mailnet.local/postma ster/Maildir, alt= Dec 4 17:04:07 backend3 dovecot: lmtp(5451, postmaster(a)mailnet.local) Debug: Effective uid=8, gid=8, home=/usr/local/mail/mailnet.local/postmaster Dec 4 17:04:07 backend3 dovecot: lmtp(5451, postmaster(a)mailnet.local) Debug: Namespace inbox: type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildi r:/usr/local/mail/mailnet.local/postmaster/Maildir Dec 4 17:04:07 backend3 dovecot: lmtp(5451, postmaster(a)mailnet.local) Debug: maildir++: root=/usr/local/mail/mailnet.local/postmaster/Maildir, index=, indexpvt=, control=, inbox=/usr/local /mail/mailnet.local/postmaster/Maildir, alt= Dec 4 17:04:07 backend3 dovecot: lmtp(5451, postmaster(a)mailnet.local) F0skIVedYVZLFQAAamJeGw: msgid=unspecified: saved mail to INBOX Dec 4 17:04:07 backend3 dovecot: lmtp(5451): Disconnect from 127.0.0.1: Successful quit Dec 4 17:04:07 backend3 dovecot: auth: Debug: master in: PASS#0111#011postmaster(a)mailnet.local#011service=doveadm Dec 4 17:04:07 backend3 dovecot: auth-worker(5446): Debug: sql(postmaster(a)mailnet.local): query: SELECT username AS user, crypt AS password, proxy_maybe, host FROM users WHERE username = 'postmaster(a)mailnet.local' AND enabled = 1 Dec 4 17:04:07 backend3 dovecot: auth: Debug: passdb out: PASS#0111#011user=postmaster(a)mailnet.local#011host=192.168.100.112#011proxy Dec 4 17:04:07 backend3 dovecot: doveadm(postmaster(a)mailnet.local): Debug: auth input: user=postmaster(a)mailnet.local host=192.168.100.112 proxy Dec 4 17:04:07 backend3 dovecot: auth: Debug: master in: PASS#0111#011postmaster(a)mailnet.local #011service=doveadm#011lip=192.168.100.112#011lport=12345#011rip=192.168.100.112#011rport=58217 Dec 4 17:04:07 backend3 dovecot: auth-worker(5446): Debug: sql(postmaster(a)mailnet.local,192.168.100.112): query: SELECT username AS user, crypt AS password, proxy_maybe, host FROM users WHERE username = 'postmaster(a)mailnet.local' AND enabled = 1 Dec 4 17:04:07 backend3 dovecot: auth: Debug: passdb out: PASS#0111#011user=postmaster(a)mailnet.local Dec 4 17:04:07 backend3 dovecot: doveadm(192.168.100.112,postmaster(a)mailnet.local): Debug: auth input: user=postmaster(a)mailnet.local Dec 4 17:04:07 backend3 dovecot: auth: Debug: master in: USER#0112#011postmaster(a)mailnet.local #011service=doveadm#011lip=192.168.100.112#011lport=12345#011rip=192.168.100.112#011rport=58217 Dec 4 17:04:07 backend3 dovecot: auth-worker(5446): Debug: sql(postmaster(a)mailnet.local,192.168.100.112): SELECT pop AS home, uid, gid, CONCAT('*:bytes=', CAST(quota*1024*1024 AS CHAR)) AS quota_rule FROM users WHERE username = 'postmaster(a)mailnet.local' Dec 4 17:04:07 backend3 dovecot: auth: Debug: userdb out: USER#0112#011postmaster(a)mailnet.local #011home=/usr/local/mail/mailnet.local/postmaster#011uid=8#011gid=8#011quota_rule=*:bytes=1048 57600 Dec 4 17:04:07 backend3 dovecot: doveadm(192.168.100.112,postmaster(a)mailnet.local): Debug: auth input: postmaster(a)mailnet.local home=/usr/local/mail/mailnet.local/postmaster uid=8 gid=8 quo ta_rule=*:bytes=104857600 Dec 4 17:04:07 backend3 dovecot: doveadm(192.168.100.112,postmaster(a)mailnet.local): Debug: Added userdb setting: plugin/quota_rule=*:bytes=104857600 Dec 4 17:04:07 backend3 dovecot: auth: Debug: master in: PASS#0111#011postmaster(a)mailnet.local #011service=doveadm#011lip=192.168.100.112#011lport=12345#011rip=192.168.100.113#011rport=43001 Dec 4 17:04:07 backend3 dovecot: auth-worker(5446): Debug: sql(postmaster(a)mailnet.local,192.168.100.113): query: SELECT username AS user, crypt AS password, proxy_maybe, host FROM users WHE RE username = 'postmaster(a)mailnet.local' AND enabled = 1 Dec 4 17:04:07 backend3 dovecot: auth: Debug: passdb out: PASS#0111#011user=postmaster(a)mailnet.local Dec 4 17:04:07 backend3 dovecot: doveadm(192.168.100.113,postmaster(a)mailnet.local): Debug: auth input: user=postmaster(a)mailnet.local Dec 4 17:04:07 backend3 dovecot: auth: Debug: master in: USER#0112#011postmaster(a)mailnet.local #011service=doveadm#011lip=192.168.100.112#011lport=12345#011rip=192.168.100.113#011rport=43001 Dec 4 17:04:07 backend3 dovecot: auth-worker(5446): Debug: sql(postmaster(a)mailnet.local,192.168.100.113): SELECT pop AS home, uid, gid, CONCAT('*:bytes=', CAST(quota*1024*1024 AS CHAR)) AS quota_rule FROM users WHERE username = 'postmaster(a)mailnet.local' Dec 4 17:04:07 backend3 dovecot: auth: Debug: userdb out: USER#0112#011postmaster(a)mailnet.local #011home=/usr/local/mail/mailnet.local/postmaster#011uid=8#011gid=8#011quota_rule=*:bytes=1048 57600 Dec 4 17:04:07 backend3 dovecot: doveadm(192.168.100.113,postmaster(a)mailnet.local): Debug: auth input: postmaster(a)mailnet.local home=/usr/local/mail/mailnet.local/postmaster uid=8 gid=8 quo ta_rule=*:bytes=104857600 Dec 4 17:04:07 backend3 dovecot: doveadm(192.168.100.113,postmaster(a)mailnet.local): Debug: Added userdb setting: plugin/quota_rule=*:bytes=104857600 Dec 4 17:04:07 backend3 dovecot: doveadm(192.168.100.113,postmaster(a)mailnet.local): Debug: Effective uid=8, gid=8, home=/usr/local/mail/mailnet.local/postmaster Dec 4 17:04:07 backend3 dovecot: doveadm(192.168.100.113,postmaster(a)mailnet.local): Debug: Namespace inbox: type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes lo cation=maildir:/usr/local/mail/mailnet.local/postmaster/Maildir Dec 4 17:04:07 backend3 dovecot: doveadm(192.168.100.113,postmaster(a)mailnet.local): Debug: maildir++: root=/usr/local/mail/mailnet.local/postmaster/Maildir, index=, indexpvt=, control=, inb ox=/usr/local/mail/mailnet.local/postmaster/Maildir, alt= Dec 4 17:04:07 backend3 dovecot: doveadm(192.168.100.112,postmaster(a)mailnet.local): Debug: Effective uid=8, gid=8, home=/usr/local/mail/mailnet.local/postmaster Dec 4 17:04:07 backend3 dovecot: doveadm(192.168.100.112,postmaster(a)mailnet.local): Debug: Namespace inbox: type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes lo cation=maildir:/usr/local/mail/mailnet.local/postmaster/Maildir Dec 4 17:04:07 backend3 dovecot: doveadm(192.168.100.112,postmaster(a)mailnet.local): Debug: maildir++: root=/usr/local/mail/mailnet.local/postmaster/Maildir, index=, indexpvt=, control=, inb ox=/usr/local/mail/mailnet.local/postmaster/Maildir, alt= Dec 4 17:04:07 backend3 dovecot: doveadm(192.168.100.112,postmaster(a)mailnet.local): Debug: Namespace : Using permissions from /usr/local/mail/mailnet.local/postmaster/Maildir: mode=0700 gid =default Dec 4 17:04:07 backend3 dovecot: dsync-local(postmaster(a)mailnet.local): Error: read(backend3-replica.mailnet.local) failed: EOF (version not received) Dec 4 17:04:07 backend3 dovecot: dsync-server(postmaster(a)mailnet.local): Error: read(192.168.100.113) failed: EOF (version not received) Here is what goes to backend3-replica's log: Dec 4 17:04:07 backend3-replica dovecot: auth: Debug: master in: PASS#0111#011postmaster(a)mailnet.local #011service=doveadm#011lip=192.168.100.113#011lport=12345#011rip=192.168.100.112#011rport=46266 Dec 4 17:04:07 backend3-replica dovecot: auth-worker(4057): Debug: sql(postmaster(a)mailnet.local,192.168.100.112): query: SELECT username AS user, crypt AS password, proxy_maybe, host FROM users WHERE username = 'postmaster(a)mailnet.local' AND enabled = 1 Dec 4 17:04:07 backend3-replica dovecot: auth: Debug: passdb out: PASS#0111#011user=postmaster(a)mailnet.local#011host=192.168.100.112#011proxy Dec 4 17:04:07 backend3-replica dovecot: doveadm(192.168.100.112,postmaster(a)mailnet.local): Debug: auth input: user=postmaster(a)mailnet.local host=192.168.100.112 proxy Dec 4 17:04:07 backend3-replica dovecot: doveadm(192.168.100.112,postmaster(a)mailnet.local): Error: doveadm client: Unknown flag: V Dec 4 17:09:07 backend3-replica dovecot: auth: Debug: master in: PASS#0111#011postmaster(a)mailnet.local #011service=doveadm#011lip=192.168.100.113#011lport=12345#011rip=192.168.100.112#011rport=46269 Dec 4 17:09:07 backend3-replica dovecot: auth-worker(4062): Debug: Loading modules from directory: /usr/lib/dovecot/modules/auth Dec 4 17:09:07 backend3-replica dovecot: auth-worker(4062): Debug: Module loaded: /usr/lib/dovecot/modules/auth/libdriver_mysql.so Dec 4 17:09:07 backend3-replica dovecot: auth-worker(4062): Debug: sql(postmaster(a)mailnet.local,192.168.100.112): query: SELECT username AS user, crypt AS password, proxy_maybe, host FROM users WHERE username = 'postmaster(a)mailnet.local' AND enabled = 1 Dec 4 17:09:07 backend3-replica dovecot: auth: Debug: passdb out: PASS#0111#011user=postmaster(a)mailnet.local#011host=192.168.100.112#011proxy Dec 4 17:09:07 backend3-replica dovecot: doveadm(192.168.100.112,postmaster(a)mailnet.local): Debug: auth input: user=postmaster(a)mailnet.local host=192.168.100.112 proxy Dec 4 17:09:07 backend3-replica dovecot: doveadm(192.168.100.112,postmaster(a)mailnet.local): Error: doveadm client: Unknown flag: V Here is the output of dovecot -n for backend3: # 2.2.13: /etc/dovecot/dovecot.conf # OS: Linux 3.16.0-4-amd64 x86_64 Debian 8.2 ext4 auth_cache_negative_ttl = 0 auth_cache_size = 100 M auth_cache_ttl = 0 auth_debug = yes auth_mechanisms = plain login auth_verbose = yes disable_plaintext_auth = no doveadm_password = doveadmpass doveadm_port = 12345 first_valid_gid = 8 first_valid_uid = 8 last_valid_gid = 8 last_valid_uid = 8 lda_mailbox_autocreate = yes lmtp_rcpt_check_quota = yes login_trusted_networks = 192.168.100.100/32 192.168.100.101/32 mail_debug = yes mail_gid = 8 mail_location = maildir:/usr/local/mail/%d/%n/Maildir mail_plugins = " notify replication" mail_uid = 8 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 } mailbox name { auto = subscribe } prefix = } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { mail_replica = tcp:backend3-replica.mailnet.local sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } pop3_client_workarounds = oe-ns-eoh postmaster_address = postmaster@%d protocols = " imap lmtp sieve pop3" service aggregator { fifo_listener replication-notify-fifo { user = mail } unix_listener replication-notify { user = mail } } service doveadm { inet_listener { port = 12345 } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } process_min_avail = 10 } service lmtp { inet_listener lmtp { port = 24 } } service pop3-login { inet_listener pop3 { port = 110 } inet_listener pop3s { port = 995 ssl = yes } } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0600 } } ssl = no userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } For backend3-replica: # 2.2.13: /etc/dovecot/dovecot.conf # OS: Linux 3.16.0-4-amd64 x86_64 Debian 8.2 ext4 auth_cache_negative_ttl = 0 auth_cache_size = 100 M auth_cache_ttl = 0 auth_debug = yes auth_mechanisms = plain login auth_verbose = yes disable_plaintext_auth = no doveadm_password = doveadmpass doveadm_port = 12345 first_valid_gid = 8 first_valid_uid = 8 last_valid_gid = 8 last_valid_uid = 8 lda_mailbox_autocreate = yes lmtp_rcpt_check_quota = yes login_trusted_networks = 192.168.100.100/32 192.168.100.101/32 mail_debug = yes mail_gid = 8 mail_location = maildir:/usr/local/mail/%d/%n/Maildir mail_plugins = " notify replication" mail_uid = 8 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 } mailbox name { auto = subscribe } prefix = } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql plugin { mail_replica = tcp:backend3.mailnet.local sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } pop3_client_workarounds = oe-ns-eoh postmaster_address = postmaster@%d protocols = " imap lmtp sieve pop3" service aggregator { fifo_listener replication-notify-fifo { user = mail } unix_listener replication-notify { user = mail } } service doveadm { inet_listener { port = 12345 } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } process_min_avail = 10 } service lmtp { inet_listener lmtp { port = 24 } } service pop3-login { inet_listener pop3 { port = 110 } inet_listener pop3s { port = 995 ssl = yes } } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0600 } } ssl = no userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql }

1 0

Missing processes
by Ervin Hegedüs 04 Dec '15

04 Dec '15

Hi list, I'm new on dovecot mailing list, this is my second dovecot installation. I'm using Debian 8, dovecot packages cames from repository. I'm using it with Postfix - postfix uses dovecot as virtual transport. Looks like everything is fine: dovecot starts, and I see this line in syslog: Dec 4 00:57:04 myserver dovecot: master: Dovecot v2.2.13 starting up for imap, lmtp, pop3 (core dumps disabled) but there isn't any imap nor pop3 process: # ps ax | grep dovecot 23723 ? Ss 0:00 /usr/sbin/dovecot -F 23732 ? S 0:00 dovecot/anvil 23733 ? S 0:00 dovecot/log 23735 ? S 0:00 dovecot/config In logs, there isn't any relevant info. If I send a mail to Postfix, it uses dovecot/auth, ant it starts _only_when_ postfix used it: # ps ax | grep dovecot 23723 ? Ss 0:00 /usr/sbin/dovecot -F 23732 ? S 0:00 dovecot/anvil 23733 ? S 0:00 dovecot/log 23735 ? S 0:00 dovecot/config 25049 ? S 0:00 dovecot/lmtp 25050 ? S 0:00 dovecot/auth 25052 ? S 0:00 dovecot/auth -w But there still isn't the dovecot/imap... Why? Thanks, a. -- I � UTF-8

1 1

How do we disable LOGIN-REFERRALS?
by sb 03 Dec '15

03 Dec '15

> Network Working Group M. Gahrns > Request for Comments: 2221 Microsoft > Category: Standards Track October 1997 > > IMAP4 Login Referrals ... > 6. Security Considerations > > The IMAP4 login referral mechanism makes use of IMAP URLs, and as > such, have the same security considerations as general internet URLs > [RFC-1738], and in particular IMAP URLs [IMAP-URL]. > > A server MUST NOT give a login referral if authentication for that > user fails. This is to avoid revealing information about the user's > account to an unauthorized user. > > With the LOGIN-REFERRALS capability, it is potentially easier to > write a rogue 'password catching' server that collects login data and > then refers the client to their actual IMAP4 server. Although > referrals reduce the effort to write such a server, the referral > response makes detection of the intrusion easier.

2 7

[patch] Fix for bug in TLS/SSL for LMTP with chained certificates
by NederHost/Sebastiaan Hoogeveen 03 Dec '15

03 Dec '15

Hi, In case of tl;dr: I fixed a bug in TLS support for LMTP which caused chained certificates not to work, and another one which caused certificate read errors to be ignored; the patches are attached to this email. While testing LMTP with TLS and certificate verification by Postfix I discovered that certificate chains are not exchanged properly when using LMTP, even though everything works fine for POP3 and IMAP (both with or without STARTTLS). On LMTP only the server certificate is included in the TLS handshake, no intermediate certificates are provided by the server. The first problem I fixed is that in lib-ssl-iostream/iostream-openssl-context.c errors from the ssl_ctx_use_certificate_chain function are silently ignored because the function returns 0 for a failure but the caller checks for values smaller than 0. This problem is fixed in the tiny patch dovecot-2.2.19-ssl_ctx_certificate_chain_returnvalue.diff. After applying this patch the following error message appears in the logs for LMTP only (IMAP and POP3 still work fine): dovecot: lmtp(20683): Error: SSL context initialization failed, disabling SSL: Can't load SSL certificate: error:0608308E:digital envelope routines:EVP_PKEY_get1_EC_KEY:expecting a ec key It turns out this issue is not related to the reading of the certificate or its associated chain. Somewhere before ssl_ctx_use_certificate_chain is called an error is put in the OpenSSL error queue which is never retrieved. Only after loading the server certificate is the queue checked and because of the previously existing error the chain is not loaded. I think the error is related to setting specific protocol options in ssl_iostream_context_set (which may be different for LMTP than for IMAP or POP3) but I did not investigate this. I made the problem go away by making the following two changes: 1. The ssl_ctx_use_certificate_chain function now empties the OpenSSL error queue before doing its work by calling ERR_get_error() until the queue is empty. 2. The openssl_iostream_error function in a similar fashion empties the queue and returns only the error message for the most recent error (this prevent earlier errors from 'hiding' later/more relevant ones). After applying this second patch LMTP now works properly with certificate chains. Note that this patch makes previously unhandled errors simply 'disappear' from the queue, which may be a Very Bad Thing. I guess there is a more elegant way of handling this "queued error" issue but this works for me now and I'm actually not a C programmer. These two fixes are included in dovecot-2.2.19-lmtp_ssl_bug.diff. I suspect this is the same issue as the one reported by Piotr Rotter to this list on July the 27th. Kind regards, -- Sebastiaan Hoogeveen NederHost https://www.nederhost.nl/ KvK: 34099781

2 1