- dovecot - dovecot.org

[Dovecot] get_disconnect_reason() gets called with NULL ctx->litinput
by Tomasz Potega 06 Nov '13

06 Nov '13

Hi, I have found get_disconnect_reason() to be called with NULL ctx->litinput at times, making dovecot crash when accessing v_offset: src/imap/cmd-append.c: 83 switch (i_stream_read(client->input)) { 84 case -1: 85 /* disconnected */ 86 reason = get_disconnect_reason(ctx, ctx->litinput->v_offset); 87 cmd_append_finish(cmd->context); 88 /* Reset command so that client_destroy() doesn't try to call 89 cmd_append_continue_message() anymore. */ Best regards, Tomasz Potęga [Wirtualna Polska] <http://www.wp.pl> Znajdziesz nas tutaj: [Wp na Facebooku] <https://www.facebook.com/WirtualnaPolska> [Wp na Twitterze] <https://twitter.com/wirtualnapolska> [Wp na SlideShare] <http://www.slideshare.net/wirtualnapolska> [Wp w Google+] <https://plus.google.com/+wppl> [Wp na YouTube] <https://www.youtube.com/user/wptvwppl> "WIRTUALNA POLSKA" Spółka Akcyjna z siedzibą w Gdańsku przy ul. Traugutta 115 C, wpisana do Krajowego Rejestru Sądowego - Rejestru Przedsiębiorców prowadzonego przez Sąd Rejonowy Gdańsk - Północ w Gdańsku pod numerem KRS 0000068548, o kapitale zakładowym 67.980.024,00 złotych opłaconym w całości oraz Numerze Identyfikacji Podatkowej 957-07-51-216.

2 1

[Dovecot] ssl-params regeneration with dovecot 2.2.7
by Frank Elsner 06 Nov '13

06 Nov '13

Hello, after switching from version 2.2.7 to 2.2.7 I miss the loglines which say: ssl-params: Generating SSL parameters ssl-params: SSL parameters regeneration completed The configuration has not been changed and reads: | # 2.2.7: /usr/local/dovecot/etc/dovecot/dovecot.conf | # OS: Linux 2.6.35.14-106.fc14.i686.PAE i686 Fedora release 14 (Laughlin) ext3 | auth_mechanisms = plain login | default_vsz_limit = 512 M | first_valid_uid = 200 | last_valid_uid = 65534 | listen = * | lmtp_save_to_detail_mailbox = yes | login_greeting = c64.shuttle.de - IMAPs Service (dovecot) ready. | login_log_format_elements = %u %r %c | mail_location = maildir:/var/spool/mail/%u | mail_log_prefix = "%Us(%u,%r): " | mail_plugin_dir = /usr/dovecot/lib/dovecot/ | mail_plugins = notify quota fts fts_squat | namespace inbox { | inbox = yes | list = yes | location = | mailbox Drafts { | special_use = \Drafts | } | mailbox Gesendet { | special_use = \Sent | } | mailbox SPAM { | special_use = \Junk | } | mailbox Sent { | special_use = \Sent | } | mailbox Trash { | special_use = \Trash | } | prefix = | subscriptions = yes | type = private | } | passdb { | args = dovecot | driver = pam | } | plugin { | fts = squat | fts_squat = partial=4 full=10 | mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename flag_change append | mail_log_fields = uid box from subject msgid size flags | mail_log_group_events = yes | quota = maildir:User quota | quota_rule = *:storage=2G | quota_rule2 = Trash:storage=+100M | } | postmaster_address = postmaster(a)moltke28.b.shuttle.de | protocols = imap | service anvil { | client_limit = 1027 | } | service auth { | unix_listener auth-client { | group = exim | mode = 0660 | user = exim | } | } | service imap-login { | inet_listener imap { | port = 143 | } | inet_listener imaps { | port = 993 | ssl = yes | } | process_limit = 512 | process_min_avail = 10 | } | service imap-postlogin { | executable = script-login /usr/local/sbin/dovecot-imap-post-login | } | service imap { | executable = imap imap-postlogin | } | service lmtp { | inet_listener lmtp { | address = 0.0.0.0 | port = 24 | } | } | service pop3-login { | inet_listener pop3 { | port = 110 | } | inet_listener pop3s { | port = 995 | ssl = yes | } | } | service pop3 { | process_limit = 1024 | } | ssl_cert = </usr/local/etc/c64.shuttle.de.CRT | ssl_key = </usr/local/etc/c64.shuttle.de-dovecot.KEY | ssl_parameters_regenerate = 1 hours | userdb { | driver = passwd | } | verbose_proctitle = yes | protocol lmtp { | mail_plugins = notify quota fts fts_squat | } | protocol lda { | mail_plugins = notify quota fts fts_squat | } | protocol imap { | imap_client_workarounds = delay-newmail tb-extra-mailbox-sep tb-lsub-flags | imap_logout_format = [%i/%o] | mail_max_userip_connections = 0 | mail_plugins = notify quota fts fts_squat quota mail_log imap_quota listescape fts fts_squat | } What's going on? No more logging or no regeneration? Greetings, Frank Elsner

2 2

[Dovecot] 2.2.6 auth process crash using LMTP and LDAP on director.
by Olivier Girard 06 Nov '13

06 Nov '13

I'm upgrading my configuration to use director and lmtp for delivery. (doveconf -n at end of the mail). I use the same config for auth on mail backends and see no errors. My setup seem to work nicely but i have some auth process crashing when using lmtp protocol. Everything is working a sexpected then i've got 5-6 errors like this in logs and a crach of the auth process: dovecot: lmtp(47269): Error: passdb lookup(_mail_): Disconnected unexpectedly pid 47406 (auth), uid 143: exited on signal 11 Actually, i didn't configure to core dump. Do you think seting up lmtp protocol to static auth adding something like folow will be better for this problem? protocol lmtp { passdb { args = proxy=y nopassword=y driver = static } } Please note that my configuration is actually listening on inet fot LMTP but that the goal is to configure postfix on the same server and switch to socket, this expain the configuration of the service auth to provide a socket to postfix. Here is my director config: % doveconf -n # 2.2.6: /usr/local/etc/dovecot/dovecot.conf # OS: FreeBSD 8.4-RELEASE-p4 amd64 auth_cache_negative_ttl = 0 auth_cache_size = 16 M auth_mechanisms = plain login auth_verbose = yes auth_verbose_passwords = sha1 default_process_limit = 4000 director_mail_servers = 192.168.16.1 192.168.16.2 192.168.16.3 director_servers = 192.168.16.4 192.168.16.5 192.168.16.6 disable_plaintext_auth = no doveadm_port = 24245 info_log_path = syslog instance_name = director lmtp_proxy = yes mail_debug = 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 ihave passdb { args = /usr/local/etc/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin { mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename mail_log_fields = uid box msgid size } service anvil { client_limit = 12003 } service auth-worker { process_min_avail = 10 user = $default_internal_user } service auth { client_limit = 16000 unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { mode = 0666 user = $default_internal_user } user = $default_internal_user } service director { fifo_listener login/proxy-notify { mode = 0666 } inet_listener { address = 192.168.16.4 port = 9090 } unix_listener director-userdb { mode = 0600 } unix_listener login/director { mode = 0666 } } service doveadm { inet_listener { port = 24245 } } service imap-login { executable = imap-login director } service lmtp { inet_listener lmtp { address = * :: port = 24 } } service pop3-login { executable = pop3-login director } ssl_cert = </etc/ssl/cert/mail.univ-angers.fr.pem ssl_key = </etc/ssl/cert/mail.univ-angers.fr.key userdb { args = /usr/local/etc/dovecot/dovecot-ldap.conf.ext driver = ldap } protocol lmtp { auth_socket_path = director-userdb } protocol doveadm { auth_socket_path = director-userdb } local 192.168.16.0/24/24 { doveadm_password = mysecret } Last thing, in my config file, there is only one /24 on local network but this is another problem.

1 0

[Dovecot] Best way from Mbox to Maildir using 2.17?
by Regan Yelcich 06 Nov '13

06 Nov '13

Can someone advise the best way to convert mailboxes from Mbox to Maildir for Dovecot 2.17 on Ubuntu? Thanks.

9 20

Re: [Dovecot] Issue with postfix not handing over e-mails to dovecot
by Joseph Tam 05 Nov '13

05 Nov '13

Tru Pheenix writes: > posftconf output: https://gist.github.com/anonymous/7318863 > doveconf output: https://gist.github.com/anonymous/7318896 > tail -f /var/log/mail.* output (when receiving mail): > https://gist.github.com/anonymous/7318945 Unless these are exceeding long, you probably should inline the contents to save people from having to jump around to get the information to help you. It will also properly archive the context to the solution. >From your logs, it appears your mail system does not know what user is mapped to "someone(a)mydomain.com": Nov 5 13:21:06 localhost postfix/local[11185]: 5716D8007B: to=<someone(a)mydomain.com>, relay=local, delay=0.59, delays=0.57/0.01/0/0.01, dsn=5.1.1, status=bounced (unknown user: "someone") I don't know whether this message is produced by postfix or by dovecot, but one thing I did notice is that your postfix configuration mailbox_command = /usr/lib/dovecot/deliver -c /etc/dovecot/conf.d/01-mail-stack-delivery.conf -m "${EXTENSION}" has upper-case "EXTENSION", whereas the Dovecot wiki uses lower case: http://wiki2.dovecot.org/LDA/Postfix If that's not it, maybe it's your SQL. You can also ask dovecot to look up user "somebody" and debug your way from there: doveadm user somebody Joseph Tam <jtam.home(a)gmail.com>

1 0

[Dovecot] squat assertion result core dump with imap process
by Kui Zhang 05 Nov '13

05 Nov '13

Hello, Recently, we had a file system problem. After fsck we started to get some core dump with imap process. Nov 4 15:15:04 mail_server1 dovecot: imap(user(a)domain.tld): Panic: file squat-trie.c: line 293 (squat_trie_lock): assertion failed: (trie->fd != -1) Nov 4 15:15:04 mail_server1 dovecot: imap(user(a)domain.tld): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x4892a) [0x7fe8b7c9392a] -> /usr/lib/dovecot/libdovecot.so.0(+0x48976) [0x7fe8b7c93976] -> /usr/lib/dovecot/libdovecot.so.0(i_error+0) [0x7fe8b7c66faf] -> /usr/lib/dovecot/modules/lib21_fts_squat_plugin.so(+0x4ef4) [0x7fe8b51d9ef4] -> /usr/lib/dovecot/modules/lib21_fts_squat_plugin.so(squat_trie_build_deinit+0x9d2) [0x7fe8b51dcc02] -> /usr/lib/dovecot/modules/lib21_fts_squat_plugin.so(+0x4150) [0x7fe8b51d9150] -> /usr/lib/dovecot/modules/lib21_fts_squat_plugin.so(+0x41b1) [0x7fe8b51d91b1] -> /usr/lib/dovecot/modules/lib20_fts_plugin.so(+0x6b7c) [0x7fe8b5a05b7c] -> /usr/lib/dovecot/modules/lib20_fts_plugin.so(fts_backend_update_deinit+0x2c) [0x7fe8b5a05bfc] -> /usr/lib/dovecot/modules/lib10_quota_plugin.so(+0xb65a) [0x7fe8b642765a] -> /usr/lib/dovecot/libdovecot-storage.so.0(mdbox_sync_begin+0x419) [0x7fe8b7f22069] -> /usr/lib/dovecot/libdovecot-storage.so.0(mdbox_sync+0x46) [0x7fe8b7f224a6] -> /usr/lib/dovecot/libdovecot-storage.so.0(mdbox_storage_sync_init+0x87) [0x7fe8b7f22587] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_sync_init+0x31) [0x7fe8b7f614d1] -> dovecot/imap [user(a)domain.tld 204.174.223.223 UID](imap_sync_init+0x67) [0x419397] -> dovecot/imap [user(a)domain.tld204.174.223.223 UID](cmd_sync_delayed+0x1c7) [0x419637] -> dovecot/imap [user(a)domain.tld 204.174.223.223 UID](client_handle_input+0x1fd) [0x41131d] -> dovecot/imap [user(a)domain.tld 204.174.223.223 UID](client_input+0x5f) [0x411b7f] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x36) [0x7fe8b7c9fb56] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x9f) [0x7fe8b7ca0b8f] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x28) [0x7fe8b7c9faf8] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7fe8b7c8b413] -> dovecot/imap [user(a)domain.tld 204.174.223.223 UID](main+0x2a4) [0x419dd4] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xfd) [0x7fe8b78dfead] -> dovecot/imap [user(a)domain.tld 204.174.223.223 UID Nov 4 15:15:04 mail_server1 dovecot: imap(user(a)domain.tld): Fatal: master: service(imap): child 28415 killed with signal 6 (core dumped) doveadm index -u user(a)domain.tld mailbox_name Removing index files and re index help with the crashes. From time to time we still get these in the log: Nov 5 10:52:53 mail_server1 dovecot: imap(user(a)domain.tld): Error: Corrupted squat uidlist file /media/drbd/user_name/mdbox/mailboxes/Drafts/dbox-Mails/dovecot.index.search.uids: wrong indexid Nov 5 11:40:00 mail_server1 dovecot: imap(user(a)domain.tld): Error: Corrupted squat uidlist file /media/drbd/user_name/mdbox/mailboxes/folder2/dbox-Mails/dovecot.index.search.uids: wrong indexid I am using: dovecot-dbg 2:2.1.16-0~auto+30 Thanks Kui.Z

1 0

[Dovecot] increased core dumps with v2.2.7
by Anand Kumria 05 Nov '13

05 Nov '13

Hi, After upgrading to v2.2.7 yesterday, I am starting to get a larger number of bugs occurring -- unfortunately I hadn't configured things to save core dumps (now done). But I am seeing things like: dovecot: imap(user(a)example.com): Fatal: master: service(imap): child 27931 killed with signal 11 (core dumped) kernel: [151706.763475] imap[4878]: segfault at 7fff53b0aff8 ip 00007fdc7ed65ece sp 00007fff53b0b000 error 6 in lib20_zlib_plugin.so[7fdc7ed61000+7000] dovecot: imap(user2(a)example.com): Fatal: master: service(imap): child 4870 killed with signal 11 (core dumped) As soon as I have more info., I'll let you know. A

2 2

[Dovecot] (Maybe stupid) question about selecting mailbox
by kjonca＠o2.pl 05 Nov '13

05 Nov '13

Does mailbox with "\NoSelect" can be select or examine? I'm not sure but IMVHO "select x" should not work. $/usr/lib/dovecot/imap * PREAUTH [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS THREAD=ORDEREDSUBJECT MULTIAPPEND UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS SPECIAL-USE COMPRESS=DEFLATE] Logged in as kjonca 2 LIST "x" "*" * LIST (\Noselect \HasChildren) "/" "x" * LIST (\HasNoChildren) "/" "x/y" 2 OK List completed. 3 SELECT x * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted. * 0 EXISTS * 0 RECENT * OK [UIDVALIDITY 1376977764] UIDs valid * OK [UIDNEXT 1] Predicted next UID * OK [NOMODSEQ] No permanent modsequences 3 OK [READ-WRITE] Select completed. 4 logout IMAP(kjonca): Info: Disconnected: Logged out in=35 out=813 * BYE Logging out 4 OK Logout completed. doveconf -n # 2.1.17 (d463fab6db95): /etc/dovecot/dovecot.conf # OS: Linux 3.8.9+1 x86_64 Debian wheezy/sid auth_debug = yes auth_mechanisms = plain digest-md5 cram-md5 login auth_username_format = %n auth_verbose = yes listen = alfa log_path = /var/log/dovecot mail_debug = yes mail_location = maildir:~/Mail/1:LAYOUT=fs:INBOX=~/Mail/1/INBOX mail_log_prefix = "%Us(%u): " mail_plugins = zlib passdb { args = scheme=PLAIN /etc/security/dovecot.pwd driver = passwd-file } plugin { mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename flag_change save mail_log_fields = uid box msgid size from flags sieve = ~/.dovecot.sieve sieve_execute_bin_dir = %h/sieve/bin sieve_execute_exec_timeout = 86400s sieve_extensions = +vnd.dovecot.pipe +vnd.dovecot.execute +vnd.dovecot.filter sieve_filter_bin_dir = %h/sieve/bin sieve_filter_exec_timeout = 86400s sieve_pipe_bin_dir = %h/sieve/bin sieve_pipe_exec_timeout = 86400s sieve_plugins = sieve_extprograms } protocols = " imap lmtp" service auth { user = root } ssl = no ssl_cert = </etc/dovecot/dovecot.pem ssl_key = </etc/dovecot/private/dovecot.pem userdb { driver = passwd } protocol lmtp { mail_plugins = zlib sieve } protocol lda { deliver_log_format = msgid=%m: %$ log_path = ~/log/deliver.log mail_plugins = zlib sieve postmaster_address = root@localhost } protocol imap { mail_max_userip_connections = 20 mail_plugins = zlib imap_zlib mail_log notify acl } -- http://blogdebart.pl/2009/12/22/mamy-chorych-dzieci/ The goal of Computer Science is to build something that will last at least until we've finished building it.

2 2

[Dovecot] Message parser loops on certain messages (e.g. with a trailing CR character)
by Tomasz Potega 05 Nov '13

05 Nov '13

Hi, dovecot's message parser enters an endless loop when fed with certain multipart messages with stray CR characters. parse_next_body_to_boundary() assumes the '\r' might be the beginning of a boundary line, reducing the block size by one: src/lib-mail/message-parser.c: 404 /* no linefeeds in this block. we can just skip it. */ 405 ret = 0; 406 if (block_r->data[block_r->size-1] == '\r') { 407 /* this may be the beginning of the \r\n--boundary */ 408 block_r->size--; 409 } For a block size of 1 (e.g. the trailing '\r' character), dovecot ends up processing zero-sized blocks, calling message_parser_read_more() without skipping the input stream: ... #6 0x00007f94f49374c7 in i_stream_read (stream=0xbe2fc8) at istream.c:167 #7 0x00007f94f49383d5 in i_stream_read_data (stream=0xbe2fc8, data_r=0x7fff2141d6b0, size_r=0x7fff2141d6b8, threshold=1) at istream.c:497 #8 0x00007f94f4918c2b in message_parser_read_more (ctx=0xbe7c10, block_r=0x7fff2141d6a0, full_r=0x7fff2141d667) at message-parser.c:128 #9 0x00007f94f491af67 in message_parser_parse_next_block (ctx=0xbe7c10, block_r=0x7fff2141d6a0) at message-parser.c:1012 #10 0x00007f94f491b2fb in message_parser_parse_body (ctx=0xbe7c10, hdr_callback=0x7f94f4c69a75 <parse_bodystructure_part_header>, context=0xbf0450) at message-parser.c:1075 #11 0x00007f94f4c6a876 in index_mail_parse_body (mail=0xbecd00, field=MAIL_CACHE_IMAP_BODYSTRUCTURE) at index-mail.c:895 #12 0x00007f94f4c6aedb in index_mail_parse_bodystructure (mail=0xbecd00, field=MAIL_CACHE_IMAP_BODYSTRUCTURE) at index-mail.c:1046 #13 0x00007f94f4c6b4a5 in index_mail_get_special (_mail=0xbecd00, field=MAIL_FETCH_IMAP_BODYSTRUCTURE, value_r=0x7fff2141d958) at index-mail.c:1170 #14 0x00007f94f4bfab53 in maildir_mail_get_special (_mail=0xbecd00, field=MAIL_FETCH_IMAP_BODYSTRUCTURE, value_r=0x7fff2141d958) at maildir-mail.c:570 #15 0x00007f94f4c36ea1 in mail_get_special (mail=0xbecd00, field=MAIL_FETCH_IMAP_BODYSTRUCTURE, value_r=0x7fff2141d958) at mail.c:269 #16 0x000000000041c5d7 in fetch_bodystructure (ctx=0xbd6a48, mail=0xbecd00, context=0x0) at imap-fetch.c:678 ... You will find a sample message attached to this mail. I have added a check to see if the parser is past the EOF (and omit reducing the block size then) as a band-aid fix, but this might call for a more elegant solution. Best regards, Tomasz Potêga [Wirtualna Polska] <http://www.wp.pl> Znajdziesz nas tutaj: [Wp na Facebooku] <https://www.facebook.com/WirtualnaPolska> [Wp na Twitterze] <https://twitter.com/wirtualnapolska> [Wp na SlideShare] <http://www.slideshare.net/wirtualnapolska> [Wp w Google+] <https://plus.google.com/+wppl> [Wp na YouTube] <https://www.youtube.com/user/wptvwppl> "WIRTUALNA POLSKA" Spółka Akcyjna z siedzibą w Gdańsku przy ul. Traugutta 115 C, wpisana do Krajowego Rejestru Sądowego - Rejestru Przedsiębiorców prowadzonego przez Sąd Rejonowy Gdańsk - Północ w Gdańsku pod numerem KRS 0000068548, o kapitale zakładowym 67.980.024,00 złotych opłaconym w całości oraz Numerze Identyfikacji Podatkowej 957-07-51-216.

2 1

[Dovecot] infinite loop (causing crash) whilst closing connection
by Anand Kumria 05 Nov '13

05 Nov '13

Hi Timo, As a follow-up to my earlier email, I've managed to get a few backtraces now. #305439 o_stream_close (stream=0x1680c10) at ostream.c:85 #305440 0x00007ff222f70f3c in o_stream_zlib_send_outbuf (zstream=0x1680b80) at ostream-zlib.c:97 #305441 0x00007ff222f70fef in o_stream_zlib_send_flush (zstream=0x1680b80) at ostream-zlib.c:182 #305442 0x00007ff222f711cb in o_stream_zlib_flush (stream=<optimized out>) at ostream-zlib.c:222 #305443 0x00007ff2243f142d in o_stream_flush (stream=0x1680c10) at ostream.c:147 #305444 0x00007ff222f70ddf in o_stream_zlib_close (stream=0x1680b80, close_parent=true) at ostream-zlib.c:35 #305445 0x00007ff2243f12ce in o_stream_close_full (close_parents=true, stream=0x1680c10) at ostream.c:49 #305446 o_stream_close (stream=0x1680c10) at ostream.c:85 #305447 0x00007ff222f70f3c in o_stream_zlib_send_outbuf (zstream=0x1680b80) at ostream-zlib.c:97 #305448 0x00007ff222f70fef in o_stream_zlib_send_flush (zstream=0x1680b80) at ostream-zlib.c:182 #305449 0x00007ff222f711cb in o_stream_zlib_flush (stream=<optimized out>) at ostream-zlib.c:222 #305450 0x00007ff2243f142d in o_stream_flush (stream=0x1680c10) at ostream.c:147 #305451 0x00007ff222f70ddf in o_stream_zlib_close (stream=0x1680b80, close_parent=true) at ostream-zlib.c:35 #305452 0x00007ff2243f12ce in o_stream_close_full (close_parents=true, stream=0x1680c10) at ostream.c:49 #305453 o_stream_close (stream=0x1680c10) at ostream.c:85 #305454 0x00007ff222f70f3c in o_stream_zlib_send_outbuf (zstream=0x1680b80) at ostream-zlib.c:97 #305455 0x00007ff222f710ff in o_stream_zlib_send_flush (zstream=0x1680b80) at ostream-zlib.c:193 #305456 0x00007ff222f71491 in o_stream_zlib_sendv (stream=0x1680b80, iov=0x7fff6b3e1870, iov_count=1) at ostream-zlib.c:257 #305457 0x00007ff2243f1785 in o_stream_sendv (stream=0x1680c10, iov=0x7fff6b3e1870, iov_count=1) at ostream.c:229 #305458 0x00007ff2243f186f in o_stream_nsendv (stream=0x1680c10, iov=<optimized out>, iov_count=<optimized out>) at ostream.c:263 #305459 0x00007ff2243f189a in o_stream_nsend (stream=<optimized out>, data=<optimized out>, size=<optimized out>) at ostream.c:255 #305460 0x00000000004157f0 in client_send_tagline (cmd=<optimized out>, data=0x423c82 "OK Close completed.") at imap-client.c:388 #305461 0x000000000040c833 in cmd_close (cmd=0x167c4d0) at cmd-close.c:37 #305462 0x000000000041707d in command_exec (cmd=0x167c4d0) at imap-commands.c:158 #305463 0x0000000000416110 in client_command_input (cmd=0x167c4d0) at imap-client.c:780 #305464 0x00000000004161f5 in client_command_input (cmd=0x167c4d0) at imap-client.c:841 #305465 0x000000000041649d in client_handle_next_command (remove_io_r=<synthetic pointer>, client=0x167b8f0) at imap-client.c:879 #305466 client_handle_input (client=0x167b8f0) at imap-client.c:891 #305467 0x00000000004165de in client_continue_pending_input (client=0x167b8f0) at imap-client.c:715 #305468 0x000000000040ed89 in idle_client_input (ctx=<optimized out>) at cmd-idle.c:112 #305469 0x00007ff2243e8686 in io_loop_call_io (io=0x16e67e0) at ioloop.c:387 #305470 0x00007ff2243e953f in io_loop_handler_run (ioloop=<optimized out>) at ioloop-epoll.c:220 #305471 0x00007ff2243e8198 in io_loop_run (ioloop=0x165d730) at ioloop.c:411 #305472 0x00007ff224397b93 in master_service_run (service=0x165d5c0, callback=<optimized out>) at master-service.c:566 #305473 0x000000000040af18 in main (argc=1, argv=0x165d390) at main.c:400 Let me know if you need further information. This is with dovecot v2.2.7 (1:2.2.7.0-1) Thanks, Anand

1 0

[Dovecot] Config problem: want SSL + local roundcube
by Rich 05 Nov '13

05 Nov '13

Hi, Have used dovecot for many years, happy that it worked well without me needing to do anything much! But since the upgrade from v1 to v2.1.7-7 I've come across some config probs. I want IMAP and to force TLS for all internet connections. However, I run RoundCube on the same server (over https) and this needs access too, but this doesn't need to be TLS because it's local anyway. The auto-config update script made some changes, it added the following to force SSL. service imap-login { inet_listener imap { port = 0 } } ssl = required But this seems to forbid the local roundcube service from logging in. Can anyone help me with my config? I had a stab, adding the following, but it didn't work. Was a complete guess anyway! remote 127.0.0.1 { ssl = no service imap-login { inet_listener imap { port = 143 } } } Here's my full config: # 2.1.7: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-amd64 x86_64 Debian 7.2 ext3 auth_default_realm = artfulrobot.com log_timestamp = "%Y-%m-%d %H:%M:%S " mail_location = maildir:/home/virtual/%d/%n mail_privileged_group = mail passdb { args = username_format=%n /etc/exim4/virtual_domains/%d/passwords driver = passwd-file } protocols = imap service auth { unix_listener auth-client { group = Debian-exim mode = 0660 } user = root } service imap-login { inet_listener imap { port = 0 } } ssl = required ssl_cert = </etc/ssl/certs/mail.artfulrobot.com-with-chain.crt ssl_key = </etc/ssl/private/mail.artfulrobot.com.key userdb { args = uid=1001 gid=1001 driver = static } userdb { driver = passwd } Thanks, Rich

3 5

[Dovecot] [bug] ssl-params hangs when FIPS is enabled
by Michal Hlavinka 05 Nov '13

05 Nov '13

Hi, we found a bug in ssl-params. It calls openssl DH generator for 512 and 1024 bits, but in FIPS mode, openssl won't generate anything for less than 1024, so it fails with: error:0506A06E:Diffie-Hellman routines:DH_BUILTIN_GENPARAMS:key size too small but when DH generator fails, ssl-params hangs forever in io_loop_run: __epoll_wait_nocancel() io_loop_handler_run(..) at ioloop-epoll.c:176 io_loop_run(..) at ioloop.c:406 master_service_run(..) at master-service.c:566 main(..) at main.c:156 Getting system in FIPS mode can be a little tricky, but DH_generator simulated failure can do the trick. Just change ssl-params/ssl-params-openssl.c:generate_dh_paramaters:39 - if (dh == NULL) { + if (1 || dh == NULL) { and when you run ssl-params (with no ssl-parameters.dat), it hangs. Let me know if you need more information. Regards, Michal Hlavinka

2 3

[Dovecot] Issue with postfix not handing over e-mails to dovecot
by Tru Pheenix 05 Nov '13

05 Nov '13

Hello! I have installed postfix with dovecot and postgresql. I have set up SASL authentication for postfix and dovecot and been able to test them successfully. I am able to send sasl authenticated emails through smtpd on postfix using a mail client like Thunderbird. However, now I am unable to receive any e-mails. When I respond to the emails, I get a not delivered failure from postfix. I cannot figure out why postfix is not handing over the e-mails to dovecot. So here are some links to follow: posftconf output: https://gist.github.com/anonymous/7318863 doveconf output: https://gist.github.com/anonymous/7318896 tail -f /var/log/mail.* output (when receiving mail): https://gist.github.com/anonymous/7318945 Any help to solve this would be highly appreciated. Regards Tru Pheenix

1 0

Re: [Dovecot] dovecot Digest, Vol 127, Issue 7
by DV Henkel-Wallace 05 Nov '13

05 Nov '13

> Date: Tue, 5 Nov 2013 08:22:57 +0100 (CET) > From: Steffen Kaiser <skdovecot(a)smail.inf.fh-brs.de> > >> >> My specific application: I am running spamassassin and would like users >> to be able to submit spam (and ham) directly by moving it into special >> folders. > I did this before switching to antispam. > I use antispam with spool2dir now, that central directory has a inotify > watcher that trains the messages instantly. This is a great idea. In my case I think I will get away with a five minute cron job since the pickup latency should be manageable to the users and there is less to install. But I like in principle the idea of an immediate, fs-driven trigger, which would probably use fewer CPU cycles in the aggregate. > [...]all my users moved messages into spam/yes, > but copied them into spam/no Unfortunately I can't rely on users getting this right, much less understanding the difference between copy and move semantics. And I'm probably not going to be able to upgrade my users. Thanks for your advice! -d

1 0

[Dovecot] s it safe to manipulate Maildir files directly?
by DV Henkel-Wallace 05 Nov '13

05 Nov '13

> Date: Tue, 5 Nov 2013 08:40:31 +0100 > From: Oli Schacher <dovecot(a)lists.wgwh.ch> > > On Mon, 4 Nov 2013 21:49:59 -0800 > David Henkel-Wallace <gumby(a)henkel-wallace.org> wrote: > >> Having the cron job find the messages and train spamassassin is no >> problem. The question is how to move the messages. Is it safe to >> simply rename the files from my cron job? > [...] >> If I have to go through to Dovecot I am afraid I'd need the user's >> credentials, which is not appropriate. > > you can do all this with doveadm scripts. Oli, thanks for the suggestion. It hadn't occured to me to consider doveadm. That's exactly the right tool. Regards, David

1 0

[Dovecot] Is it safe to manipulate Maildir files directly?
by David Henkel-Wallace 05 Nov '13

05 Nov '13

Dovecoters, is it safe to manipulate files in Maildir/xxx directly or will Dovecot become unstable if I don't make these changes by talking to Dovecot and having it make the changes? (I'm running 2.1.7 under Wheezy, IMAP only) My specific application: I am running spamassassin and would like users to be able to submit spam (and ham) directly by moving it into special folders. A cron job can then find it and take action: feed spam messages to the bayesian trainer and then delete them; feed ham messages to the trainer and then move them into ~/Maildir/cur/ Having the cron job find the messages and train spamassassin is no problem. The question is how to move the messages. Is it safe to simply rename the files from my cron job? The dovecot wiki implies that dovecot will notice a change in mtime and deal with it safely. Am I reading this correctly? Changing a message flags (i.e. name) and/or directory will change mtime. If I have to go through to Dovecot I am afraid I'd need the user's credentials, which is not appropriate. Thanks! -d

3 2

[Dovecot] Stuck with authentication for my dovecot installation.
by Tru Pheenix 04 Nov '13

04 Nov '13

Hello! I have been following instructions from here to setup dovecot along with postfix and postgresql and sasl2. I try to login but I keep getting the following messages in /var/log/mail.log Nov 2 19:51:39 localhost dovecot: ssl-params: Warning: Killed with signal 15 (by pid=1 uid=0 code=kill) Nov 2 19:51:39 localhost dovecot: anvil: Warning: Killed with signal 15 (by pid=1 uid=0 code=kill) Nov 2 19:51:39 localhost dovecot: config: Warning: Killed with signal 15 (by pid=1 uid=0 code=kill) Nov 2 19:51:39 localhost dovecot: log: Warning: Killed with signal 15 (by pid=1 uid=0 code=kill) Nov 2 19:51:39 localhost dovecot: master: Warning: Killed with signal 15 (by pid=1 uid=0 code=kill) Nov 2 19:51:44 localhost dovecot: master: Dovecot v2.0.19 starting up (core dumps disabled) Nov 2 19:53:11 localhost dovecot: master: Warning: Killed with signal 15 (by pid=1 uid=0 code=kill) Nov 2 19:53:11 localhost dovecot: log: Warning: Killed with signal 15 (by pid=1 uid=0 code=kill) Nov 2 19:53:11 localhost dovecot: master: Dovecot v2.0.19 starting up (core dumps disabled) Nov 2 19:53:29 localhost dovecot: auth: Debug: Loading modules from directory: /usr/lib/dovecot/modules/auth Nov 2 19:53:29 localhost dovecot: auth: Debug: Module loaded: /usr/lib/dovecot/modules/auth/libdriver_pgsql.so Nov 2 19:53:29 localhost dovecot: auth: Debug: auth client connected (pid=12718) Nov 2 19:53:29 localhost dovecot: auth: pgsql(localhost): Connected to database mails Nov 2 19:53:41 localhost dovecot: auth: Debug: client in: AUTH#0111#011PLAIN#011service=imap#011secured#011lip=127.0.0.1#011rip=127.0.0.1#011lport=143#011rport=58759#011resp=<hidden> Nov 2 19:53:41 localhost dovecot: auth: Debug: sql(someone(a)mydomain.com,127.0.0.1): query: SELECT userid as user, password FROM users WHERE userid = 'someone(a)mydomain.com' Nov 2 19:53:41 localhost dovecot: auth: sql(someone(a)mydomain.com,127.0.0.1): Password mismatch My doveconf -n gives the following output # 2.0.19: /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-24-virtual i686 Ubuntu 12.04 LTS auth_debug = yes auth_verbose = yes passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } passdb { driver = pam } protocols = " imap pop3" ssl_cert = </etc/ssl/certs/dovecot.pem ssl_key = </etc/ssl/private/dovecot.pem userdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } userdb { driver = passwd } Please let me know what is wrong. Regards Tru Pheenix

2 2

[Dovecot] backup maildir mailbox bugs
by Anand Kumria 04 Nov '13

04 Nov '13

Hi, Using dovecot v2.2.5.5, I get the following: $ doveadm -v backup -R -u user(a)example.com maildir:/home/rsync/ example.com/user/Maildir/ [...] dsync(user(a)example.com): Panic: file dsync-mailbox-export.c: line 228 (export_save_change_get): assertion failed: (change->type == DSYNC_MAIL_CHANGE_TYPE_FLAG_CHANGE) dsync(user(a)example.com): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x59e6a) [0x7f91ad185e6a] -> /usr/lib/dovecot/libdovecot.so.0(default_fatal_handler+0x2a) [0x7f91ad185f2a] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f91ad144b89] -> doveadm [user(a)example.com Printing Quotes send:mailbox recv:mailbox](dsync_mailbox_export_init+0x8b8) [0x434028] -> doveadm [ user(a)example.com Printing Quotes send:mailbox recv:mailbox](dsync_brain_sync_mailbox_open+0x233) [0x42ba83] -> doveadm [ user(a)example.com Printing Quotes send:mailbox recv:mailbox](dsync_brain_slave_recv_mailbox+0x125) [0x42c615] -> doveadm [ user(a)example.com Printing Quotes send:mailbox recv:mailbox](dsync_brain_run+0x369) [0x42a929] -> doveadm [user(a)example.comPrinting Quotes send:mailbox recv:mailbox]() [0x42881b] -> doveadm [ user(a)example.com Printing Quotes send:mailbox recv:mailbox]() [0x411ad7] -> doveadm [user(a)example.com Printing Quotes send:mailbox recv:mailbox](doveadm_mail_try_run+0x260) [0x4127a0] -> doveadm [ user(a)example.com Printing Quotes send:mailbox recv:mailbox](main+0x3f0) [0x4116c0] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed) [0x7f91acd8e76d] -> doveadm [user(a)example.com Printing Quotes send:mailbox recv:mailbox]() [0x4118bd] Other lines emitted were Info lines indicating what message was being processed. Unfortunately this appears to stop the backup dead in it's tracks. Suggestions on how to proceed? I was (originally) doing this as an IMAP to IMAP copy, and when that failed I managed to get the raw Maildir. Now I appear stuck with that too. Regards, Anand -- “Don’t be sad because it’s over. Smile because it happened.” – Dr. Seuss

2 4

[Dovecot] v2.2.7 released
by Timo Sirainen 04 Nov '13

04 Nov '13

http://dovecot.org/releases/2.2/dovecot-2.2.7.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.7.tar.gz.sig * Some usage of passdb checkpassword could have been exploitable by local users. You may need to modify your setup to keep it working. See http://wiki2.dovecot.org/AuthDatabase/CheckPassword#Security + auth: Added ability to truncate values logged by auth_verbose_passwords (see 10-logging.conf comment) + mdbox: Added "mdbox_deleted" storage, which can be used to access messages with refcount=0. For example: doveadm import mdbox_deleted:~/mdbox "" mailbox inbox subject oops + ssl-params: Added ssl_dh_parameters_length setting. - master process was doing a hostname.domain lookup for each created process, which may have caused a lot of unnecessary DNS lookups. - dsync: Syncing over 100 messages at once caused problems in some situations, causing messages to get new UIDs. - fts-solr: Different Solr hosts for different users didn't work.

4 4

[Dovecot] Shared mailbox help needed
by Alex Ferrara 04 Nov '13

04 Nov '13

Hi everyone, I am in the middle of a migration from Cyrus 2.4 to Dovecot 2.1.7, and I have everything mostly working. I set up Dovecot to authenticate against Active Directory (Samba4) using PAM and SSSD, and have also used the fantastic cyrus2dovecot perl script to do a test migration of all our mail, and that is now working flawlessly. I have the issue of shared IMAP accounts to deal with, and I am a little stuck. I see that Dovecot is very flexible, and I think I am getting stuck in this flexibility. I thought that if I explain what I am trying to achieve, someone might point me in the right direction. In the Cyrus regime, we have several imap accounts that are shared with a group of people. These groups are actual unix groups that actual unix users are a member of. If we want a person to access a mailbox, we add them to the group and then at next login, it pops up in Thunderbird automatically. SSSD does, from what I can tell, a decent job of binding to AD and mapping AD users to unix users, but since not all of the users have an NIS uid in AD, I decided to use a static mapping. This might have been the wrong decision, I am not sure. userdb { driver = static args = uid=900 gid=900 home=/mnt/mail/%u allow_all_users=yes } It probably isn't important at this stage, but the mail spool is stored on an NFS server and the indexes are stored locally. Thanks in advance, Alex Ferrara Director Receptive IT Solutions

1 0

Re: [Dovecot] Doveadm with a 2nd Instance
by Chris Lasater 03 Nov '13

03 Nov '13

While testing some more I found out something else. I have an alias set for doveadm so it was running with sudo and that ended up being part of the issue. If doveadm is run as a regular user then the problem goes away [user@server ~]$ doveadm -i Director log find Debug: /home/user/apps/logs/director/director_debug.log Info: /home/user/apps/logs/director/director_info.log Warning: /home/user/apps/logs/director/director.log Error: /home/user/apps/logs/director/director.log Fatal: /home/user/apps/logs/director/director.log [user@server ~]$ sudo doveadm -i Director log find Debug: /home/user/apps/logs/dovecot_debug.log Info: /home/user/apps/logs/dovecot_info.log Warning: /home/user/apps/logs/dovecot.log Error: /home/user/apps/logs/dovecot.log Fatal: /home/user/apps/logs/dovecot.log Also if I run "sudo doveadm stop" to stop the main instance, I now have the ability to use the -i Director using sudo. Unfortunately this makes it difficult to manage two instances. Does anyone have an idea of getting this to work with sudo? Chris

2 2

[Dovecot] Encryption solution for messages at rest
by Douglas Mortensen 03 Nov '13

03 Nov '13

Hi, We have clients with various security & compliance requirements. Although not required, it would be ideal to have messages encrypted at rest. We already use SSL/TLS to secure the transmission of most email. However, it would be nice to have them encrypted sitting on our server. Is anyone doing this? I think that ideally, rather than full-disk encryption, we should use an encryption that encrypts the actual email messages as they sit on our file system. This way even if we ever had our server breached by an attacker, they wouldn't be able to do anything with the messages. However, this would also mean that if the attacker can't decrypt the files, than dovecot and postfix still would need to. This means that the encryption key would need to be available to the dovecot deamon. We'd either need to have it in a file that is restricted to access only by dovecot (less secure), or use an encryption passphrase for the certificate which would have to be typed in manually each time that dovecot starts or restarts (more secure, but also more work and possibility of disruption because the server can't restart gracefully without a human being having to be present [although I don't think we have issues with unexpected restarts anyway]). Is anyone doing anything like this with dovecot? Thanks!! - Doug Mortensen Network Consultant Impala Networks Inc CCNA, MCSA, Security+, A+ Linux+, Network+, Server+ A.A.S. Information Technology . www.impalanetworks.com P: (505) 327-7300 F: (505) 327-7545

6 6

[Dovecot] Assertion error in Dovecot 2.2.6
by Mark Sapiro 03 Nov '13

03 Nov '13

Background. A while back I upgraded my phone to one currently using Android 4.1.2 and K9 mail 4.409. This phone/MUA combination seems at times to go crazy making IMAP connections. At first, I had mail_max_userip_connections = 30 (my largest imap account has 19 folders). The issue I had at that time was multiple errors like Oct 14 17:45:16 sbh16 dovecot: imap-login: Maximum number of connections from user+IP exceeded (mail_max_userip_connections=30): user=<xxx>, method=PLAIN, rip=xx.xx.xx.xx, lip=xx.xx.xx.xx, TLS, session=<c63x5bzowQBi0uQR> I then set mail_max_userip_connections = 50 This greatly reduced but didn't completely eliminate these messages, but then I would see multiple Oct 31 16:13:40 sbh16 dovecot: master: Warning: service(imap-login): process_limit (100) reached, client connections are being dropped and Oct 31 16:13:40 sbh16 dovecot: imap-login: Disconnected: Connection queue full (no auth attempts in 4 secs): user=<>, rip=xx.xx.xx.xx, lip=xx.xx.xx.xx, TLS handshaking, session=<s26xmRHqVQBi0uQR> followed finally by Oct 31 16:13:40 sbh16 dovecot: imap-login: Panic: file client-common.c: line 190 (client_destroy): assertion failed: (!client->authenticating) Oct 31 16:13:40 sbh16 dovecot: auth: Warning: auth client 19669 disconnected with 1 pending requests: EOF Oct 31 16:13:40 sbh16 dovecot: imap-login: Fatal: master: service(imap-login): child 19669 killed with signal 6 (core not dumped - add -D parameter to service imap-login { executable } I then set default_process_limit = 200, and things seem to have settled down, but I thought the panic should be reported. Possibly this is relevant - the above only seem to occur when the phone is connecting via wifi and possibly only when the phone has just switched from the phone data network to wifi. Current doveconf -n # 2.2.6: /usr/local/etc/dovecot/dovecot.conf # OS: Linux 2.6.18-8.1.14.el5 i686 CentOS release 5 (Final) auth_mechanisms = plain apop login auth_worker_max_count = 5 default_process_limit = 200 mail_location = mbox:~/Mail:INBOX=/var/spool/mail/%u mail_privileged_group = mail mbox_write_locks = fcntl dotlock 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 = /usr/local/etc/dovecot.passwd driver = passwd-file } passdb { driver = pam } protocols = imap pop3 service auth { unix_listener /var/spool/postfix/private/auth { mode = 0666 } } ssl_cert = </etc/httpd/conf/ssl/combined.crt ssl_key = </etc/httpd/conf/ssl/www.grizz.org.key userdb { driver = passwd } protocol imap { mail_max_userip_connections = 50 } -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 1

[Dovecot] METADATA for v2.2.7
by Timo Sirainen 02 Nov '13

02 Nov '13

In case someone wants to try: http://hg.dovecot.org/dovecot-2.2/rev/0a08efeb3f40 The commit message lists the TODO. So for example if you want to enable it just for webmail (because quota limits aren’t there yet): mail_attribute_dict = file:%h/dovecot-attributes local 10.0.0.0/24 { imap_metadata = yes } Compared to the old metadata plugin, there are some improvements: - Uses lib-storage attributes internally, which means: - dsync replicates METADATA - it will be easy to add support for untagged METADATA notifications to clients when they change - SETMETADATA atomically either updates all or none of the changes Things that work in the METADATA code, but still require lib-dict changes to work properly: - Values with unlimited sizes - Values with binary data (NULs)

1 0

[Dovecot] DH parameter length too small?
by Jörg Lübbert 02 Nov '13

02 Nov '13

Hello, from my understanding, using 1024bit DH parameters results in a not sufficiently secure key exchange for DH(E). Therefore I think it would be advisable to have parameters of at least 2048bit . In fact, I would see a great benefit in chosing parameter length arbitrarily. I also do not see the benefit of parameter regeneration. What were the design goals here? Thanks, Jörg Lübbert

2 1