- dovecot - dovecot.org

Messed up dovecot mail store, need some repair advice
by Gerben Wierda 23 Oct '16

23 Oct '16

Hello folks, I have an older dovecot 2.0 (which I will migrate to a 2.2 asap, but at this point in time I need a fix). This is a dovecot 2.0 that came with Mac OS X 10.8.5 Server 2.2.5. Today, my spam/virus filtering (clamav) on the Server broke down. As a result, all my meesages got the ***UNCHECKED*** tag added to each subject. That was clearly unacceptable. SO, for the tim ebeing I have set that tag to undef so the tag is no longer added. But I also wanted to repair the messages that already ended up in dovecot 2.0 So, I did something simple: stopped all mail services on the server, went into the dovecot mail store and edited the messages. I first tried with one small ccount and it seemed OK. But now my mail client is experiencing problems with the messages (cannot display) and I think I've been to simplistic. I have for instance notedthat th esizeof the message is part of the filename. So, I can change these of course, but probably I need to change more. Can someone enlighten me how I can repair the broken data store? Thanks, (Foolish) Gerben

2 3

More informations in doveadm proxy ring status
by Peer Heinlein 22 Oct '16

22 Oct '16

I would love to have a) the number of active users b) the number of active TCP sessions (pop3, imap, lmtp, sieve, doveadm) included in the output of "doveadm director ring status". This would be helpful to get a good overview over load and usage of the whole director ring and would help to plan downtimes and maintenance work. Peer -- 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

MFA 2FA TOTP razz-ma-tazz!
by WJCarpenter 22 Oct '16

22 Oct '16

I'd like to start offering my server's users multi-factor authentication. Right now, I funnel all authentication through dovecot. Before I get too far down the fantasy design path, I'm wondering if anyone else has already done this and could share some details or code. (I loaded up the subject line with acronyms to show how serious I am. :-)) I am specifically thinking of two-factor authentication using TOTP (time-based one-time passwords) as described in RFC-6238. Those are the ones compatible with Google Authenticator and compatible apps. I already am a user of those at several sites. Some of them don't have a separate opportunity to enter the 6-digit code. Instead, you append the 6-digit code to your normal password. If your config on the site shows you as a user of TOTP, they peel those trailing 6 digits off your password and then validate the rest of the password in the normal way. That is what I think I would do for dovecot authentication. So, who's already done this or something like it?

1 0

Dovecot does not close connections
by Benedikt Carda 22 Oct '16

22 Oct '16

Hello, I am running into this error: /Maximum number of connections from user+IP exceeded (mail_max_userip_connections=10)/ The suggested solution in hundreds of support requests on this mailing list and throughout the internet is to increase the number of maximum userip connections. But this is not curing the problem, it is just postponing it to the moment when the new limit is reached. When i type: /doveadm who// / I can see that some accounts have several pids running: /someaccount 10 imap (25396 25391 25386 25381 25374 7822 7817 5559 5543 5531) (xxx.xxx.xxx.xxx)/ Now when I check these pids with /ps aux/ I find out that the oldest pid (5531) has a lifetime of already over 12 hours. Anyway I know that the clients that initiated the connections are not connected anymore, so there is no way that there is a valid reason why this connection should still be open. Also I never had this problem before, it appeared some months ago. Does anybody know how to solve this? Thanks in advance, Benedikt.

3 4

keent() from Tika - with doveadm
by Larry Rosenman 21 Oct '16

21 Oct '16

getting the following: Oct 21, 2016 12:04:25 PM org.apache.tika.server.resource.TikaResource logRequest INFO: tika/ (application/vnd.openxmlformats-officedocument.wordprocessingml.document) doveadm(ctr): Debug: http-client: conn 127.0.0.1:9998 [1]: Got 200 response for request [Req69: PUT http://localhost:9998/tika/] (took 91 ms + 210 ms in queue) doveadm(ctr): Panic: kevent(): Invalid argument Abort trap (core dumped) if I turn off tika, I do NOt get it. 2.2.26-RC1 what else do you need? -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 (c) E-Mail: larryrtx(a)gmail.com US Mail: 17716 Limpia Crk, Round Rock, TX 78664-7281

2 2

Released Pigeonhole v0.4.16.rc1 for Dovecot v2.2.26.rc1.
by Stephan Bosch 21 Oct '16

21 Oct '16

Hello Dovecot users, The upcoming release includes quite a few new features for a change. The most important ones are the Sieve discard-script feature and the new vnd.dovecot.config environment items. Documentation for these features can be found in the package itself. Please test these thoroughly. Changelog v0.4.16: * Part of the Sieve extprograms implementation was moved to Dovecot, which means that this release depends on Dovecot v2.2.26+. * ManageSieve: The PUTSCRIPT command now allows uploading empty Sieve scripts. There was really no good reason to disallow doing that. + Sieve vnd.dovecot.report extension: + Added a Dovecot-Reporting-User field to the report body, which contains the e-mail address of the user sending the report. + Added support for configuring the "From:" address used in the report. + LDA sieve plugin: Implemented support for a "discard script" that is run when the message is going to be discarded. This allows doing something other than throwing the message away for good. + Sieve vnd.dovecot.environment extension: Added vnd.dovecot.config.* environment items. These environment items map to sieve_env_* settings from the plugin {} section in the configuration. Such values can of course also be returned from userdb. + Sieve vacation extension: Use the Microsoft X-Auto-Response-Suppress header to prevent unwanted responses from and to (older) Microsoft products. + ManageSieve: Added rawlog_dir setting to store ManageSieve traffic logs. This replaces at least partially the rawlog plugin (mimics similar IMAP/POP3 change). - doveadm sieve plugin: synchronization: Prevent setting file timestamps to unix epoch time. This occurred when Dovecot passed the timestamp as 'unknown' during synchronization. - Sieve exprograms plugin: Fixed spurious '+' sometimes returned at the end of socket-based program output. - imapsieve plugin: Fixed crash occurring in specific situations. - Performed various fixes based on static analysis and Clang warnings. The release is available as follows: http://pigeonhole.dovecot.org/releases/2.2/rc/dovecot-2.2-pigeonhole-0.4.16… http://pigeonhole.dovecot.org/releases/2.2/rc/dovecot-2.2-pigeonhole-0.4.16… 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

v2.2.26 release candidate released
by Timo Sirainen 21 Oct '16

21 Oct '16

http://dovecot.org/releases/2.2/rc/dovecot-2.2.26.rc1.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.26.rc1.tar.gz.sig There are quite a lot of changes since v2.2.25. Please try out this RC so we can get a good and stable v2.2.26 out. * master: Removed hardcoded 511 backlog limit for listen(). The kernel should limit this as needed. * doveadm import: Source user is now initialized the same as target user. Added -U parameter to override the source user. * Mailbox names are no longer limited to 16 hierarchy levels. We'll check another way to make sure mailbox names can't grow larger than 4096 bytes. + Added a concept of "alternative usernames" by returning user_* extra field(s) in passdb. doveadm proxy list shows these alt usernames in "doveadm proxy list" output. "doveadm director&proxy kick" adds -f <passdb field> parameter. The alt usernames don't have to be unique, so this allows creation of user groups and kicking them in one command. + auth: passdb/userdb dict allows now %variables in key settings. + auth: If passdb returns noauthenticate=yes extra field, assume that it only set extra fields and authentication wasn't actually performed. + auth: passdb static now supports password={scheme} prefix. + imapc: Added imapc_max_line_length to limit maximum memory usage. + imap, pop3: Added rawlog_dir setting to store IMAP/POP3 traffic logs. This replaces at least partially the rawlog plugin. + dsync: Added dsync_features=empty-header-workaround setting. This makes incremental dsyncs work better for servers that randomly return empty headers for mails. When an empty header is seen for an existing mail, dsync assumes that it matches the local mail. + doveadm sync/backup: Added -I <max size> parameter to skip too large mails. + doveadm sync/backup: Fixed -t parameter and added -e for "end date". + doveadm mailbox metadata: Added -s parameter to allow accessing server metadata by using empty mailbox name. - master process's listener socket was leaked to all child processes. This might have allowed untrusted processes to capture and prevent "doveadm service stop" comands from working. - auth: userdb fields weren't passed to auth-workers, so %{userdb:*} from previous userdbs didn't work there. - auth: Each userdb lookup from cache reset its TTL. - auth: Fixed auth_bind=yes + sasl_bind=yes to work together - auth: Blocking userdb lookups reset extra fields set by previous userdbs. - auth: Cache keys didn't include %{passdb:*} and %{userdb:*} - auth-policy: Fixed crash due to using already-freed memory if policy lookup takes longer than auth request exists. - lib-auth: Unescape passdb/userdb extra fields. Mainly affected returning extra fields with LFs or TABs. - lmtp_user_concurrency_limit>0 setting was logging unnecessary anvil errors. - lmtp_user_concurrency_limit is now checked before quota check with lmtp_rcpt_check_quota=yes to avoid unnecessary quota work. - lmtp: %{userdb:*} variables didn't work in mail_log_prefix - autoexpunge settings for mailboxes with wildcards didn't work when namespace prefix was non-empty. - Fixed writing >2GB to iostream-temp files (used by fs-compress, fs-metawrap, doveadm-http) - director: Ignore duplicates in director_servers setting. - zlib, IMAP BINARY: Fixed internal caching when accessing multiple newly created mails. They all had UID=0 and the next mail could have wrongly used the previously cached mail. - doveadm stats reset wasn't reseting all the stats. - auth_stats=yes: Don't update num_logins, since it doubles them when using with mail stats. - quota count: Fixed deadlocks when updating vsize header. - dict-quota: Fixed crashes happening due to memory corruption. - dict proxy: Fixed various timeout-related bugs. - doveadm proxying: Fixed -A and -u wildcard handling. - doveadm proxying: Fixed hangs and bugs related to printing. - imap: Fixed wrongly triggering assert-crash in client_check_command_hangs. - imap proxy: Don't send ID command pipelined with nopipelining=yes - imap-hibernate: Don't execute quota_over_script or last_login after un-hibernation. - imap-hibernate: Don't un-hibernate if client sends DONE+IDLE in one IP packet. - imap-hibernate: Fixed various failures when un-hibernating. - fts: fts_autoindex=yes was broken in 2.2.25 unless fts_autoindex_exclude settings existed. - fts-solr: Fixed searching multiple mailboxes (patch by x16a0) - doveadm fetch body.snippet wasn't working in 2.2.25. Also fixed a crash with certain emails. - pop3-migration + dbox: Various fixes related to POP3 UIDL optimization in 2.2.25. - pop3-migration: Fixed "truncated email header" workaround.

10 17

Migrating users from a 2.0.19 to a 2.2.24 installation
by Gerben Wierda 21 Oct '16

21 Oct '16

Hello, I am currently still running an older dovecot (2.0.19apple1 on Mac OS X 10.8.5) and I want to migrate my users to a new server (macOS 10.12 with Server 5, which contains dovecot 2.2.24 (a82c823)). Basically, I want to create a new server installation on the new server so I don't bring any junk over (new user accounts, with the same uid/gid (still need to figure that one out), but after I have done that I need to move the data over from the old instalation to the new. Has anything changed in the formats between 2.0 and 2.2 that will stop me from doing this? Thanks, G

2 1

Extending IMAP daemon to comply with legacy Proxy
by Thorsten Hater 21 Oct '16

21 Oct '16

Hello, I am currently investigating if and how to migrate a legacy setup based on a modified Courier installation to Dovecot. So far I am really liking Dovecot. however, I will have to work with an existing IMAP proxy for the time being. In particular, the proxy authenticates the user and looks up the location of the mail directory and transfers the data to the actual server via an extension of the IMAP protocol. This extension will have to stay and the information transferred is not easily recoverable. Further database lookups on the real server would be possible to solve the issue, but I would prefer to keep the design intact at least for now. Is it possible to handle IMAP commands after LOGIN/AUTHENTICATE but before opening any mailboxes? Basically these commands aim to replace the userdb lookup. Any pointers on how to implement this, perhaps as a plugin? Best regards, Thorsten

1 0

sieve duplicate locking
by Alexander 'Leo' Bergolth 20 Oct '16

20 Oct '16

Hi! Does the duplicate sieve plugin do any locking to avoid duplicate parallel delivery of the same message? I sometimes experience duplicate mail delivery of messages with the same message-id, despite the use of a sieve duplicate filter. According to the log files, those messages are delivered in the same second by two parallel dovecot-lda processes. (Duplicate filtering works fine in all other cases.) RFC7352 states that the ID of a message may only be committed to the duplicate tracking list at the _end_ of a successful script execution, which may lead to race conditions. Maybe I am running into this? Is there an easy way to serialize mail delivery using some locking inside sieve? Or do I have to serialize per-user dovecot-lda delivery? Any experiences with that? I am using dovecot-2.2.25 and pidgeonhole-0.4.15. Mail is delivered using postfix-2.10 and dovecot-lda as mailbox_command. Mailbox format is maildir with LAYOUT=fs. Cheers, --leo -- e-mail ::: Leo.Bergolth (at) wu.ac.at fax ::: +43-1-31336-906050 location ::: IT-Services | Vienna University of Economics | Austria

2 2

Re: Massive LMTP Problems with dovecot
by Ralf Hildebrandt 20 Oct '16

20 Oct '16

> We'll need the `dovecot -n` output first. Here we go: > # 2.2.devel (933d16f): /etc/dovecot/dovecot.conf > # Pigeonhole version 0.4.devel (63f9b42) > # OS: Linux 3.13.0-98-generic x86_64 Ubuntu 14.04.5 LTS > default_vsz_limit = 2 G > lmtp_user_concurrency_limit = 10000 > mail_attachment_dir = /home/copymail/attachments > mail_location = mdbox:~/mdbox > mail_plugins = zlib fts fts_lucene > mdbox_rotate_size = 128 M > 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 = username_format=%u /etc/dovecot/passwd > driver = passwd-file > } > plugin { > fts = lucene > fts_autoindex = yes > fts_languages = de,en > fts_lucene = whitespace_chars=@. > sieve = file:~/sieve;active=~/.dovecot.sieve > zlib_save = gz > zlib_save_level = 5 > } > protocols = " imap lmtp" > service imap-login { > inet_listener imap { > address = 127.0.0.1 > port = 143 > } > inet_listener imaps { > port = 993 > ssl = yes > } > } > service lmtp { > inet_listener lmtp { > address = 141.42.1.208 > port = 1025 > } > unix_listener /var/spool/postfix/private/dovecot-lmtp { > group = postfix > mode = 0660 > user = postfix > } > } > ssl_ca = /etc/ssl/certs/ca-certificates.crt > ssl_cert = </etc/ssl/certs/mail-cbf.pem > ssl_cipher_list = EECDH+ECDSA+AESGCM:EECDH+aRSA+AESGCM:EECDH+ECDSA+SHA384:EECDH+ECDSA+SHA256:EECDH+aRSA+SHA384:EECDH+aRSA+SHA256:EECDH+aRSA+RC4:EECDH:EDH+aRSA:!aNULL:!eNULL:!LOW:!3DES:!MD5:!EXP:!PSK:!SRP:!DSS:!RC4 > ssl_key = # hidden, use -P to show it > ssl_prefer_server_ciphers = yes > ssl_protocols = !SSLv2 !SSLv3 > userdb { > args = username_format=%u /etc/dovecot/passwd > driver = passwd-file > } > protocol lmtp { > mail_plugins = zlib fts fts_lucene > } Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebrandt(a)charite.de | http://www.charite.de

2 6

Lmtp Fatal Error
by Sven Roellig 19 Oct '16

19 Oct '16

Hi,dovecot is create an Fatal Panik Error. <AM5DMwaCBlgpDQAAWm89Cw>: Fatal: master: service(lmtp): child 3369 killed with signal 6 (core dumps disabled) <1jx3DhuCBlg1DQAAWm89Cw>: Panic: file lda-sieve-plugin.c: line 447 (lda_sieve_execute_scripts): assertion failed: (script != NULL) <1jx3DhuCBlg1DQAAWm89Cw>: Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x93fae) [0x7f547f6a3fae] -> /usr/lib/dovecot/libdovecot.so.0(+0x9409c) [0x7f547f6a409c] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f547f63d56e] -> /usr/lib/dovecot/modules/lib90_sieve_plugin.so(+0x3ae8) [0x7f547d765ae8] -> /usr/lib/dovecot/libdovecot-lda.so.0(mail_deliver+0x49) [0x7f547fc709a9] -> dovecot/lmtp(+0x7201) [0x7f54800a1201] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x5f) [0x7f547f6b88bf] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x10a) [0x7f547f6b9d8a] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x25) [0x7f547f6b8965] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x30) [0x7f547f6b8b00] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f547f643ac3] -> dovecot/lmtp(main+0x1c9) [0x7f548009f2c9] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7f547f286b45] -> dovecot/lmtp(+0x53ae) [0x7f548009f3ae] Normal Mails are not deliverd but filterd mails are deliverd. System is Debian 8.6 Dovecot Core is 2%3a2.3.0-alpha0-1-auto+385 AMD64 can anyone help. Sven

3 4

Iteration base for LDAP
by Taso N. Devetzis 19 Oct '16

19 Oct '16

Greetings, The iteration machinery uses the LDAP search base set with the "base" directive (typically from dovecot-ldap.conf.ext); the same base used during nominal operations (e.g., passdb/userdb searches). Consider a directory: dc=ROOT |_ dc=foo,dc=com,dc=ROOT (foo.com subtree) |_ dc=bar,dc=net,dc=ROOT (bar.net subtree) A search base setting appropriate for mail operations might be: base = dc=%Dd,dc=ROOT # e.g. dc=foo,dc=com,dc=ROOT for user(a)foo.com This fails when iterating, as the variable substitution is meaningless in this context (and even a static subtree search base would only cover a portion of the overall directory during iterative searches). Setting the base to "dc=ROOT" obviously solves the issue at the expense of searching the entire directory for all operations. This is less than optimal. I could not find a way to override this setting at runtime via a doveadm option or similar. Ideally, a separate "iterate_base" setting would solve this issue. Any other solutions? Thanks, /taso

1 0

RE: First steps in Dovecot; IMAP not working
by Joseph Tam 19 Oct '16

19 Oct '16

> > doveadm user mailtest > field value > uid 1002 > gid 8 > home /home/mailtest > mail mbox:~/mail:INBOX=/var/mail/mailtest > system_groups_user mailtest Looks fine. > [log files] I'll try to locate them. Your best hope. Maybe this helps doveconf -n | grep log_ Or just force it somewhere by settings the *log_path configuration values. Also your mail server's log when trying to deliver. Joseph Tam <jtam.home(a)gmail.com>

1 0

Dict proxy client returning empty string instead of multiline string
by Pierre Jaury 18 Oct '16

18 Oct '16

Hello, I am using a dict proxy for my sieve extdata plugin to access some fields from an SQLite database (autoreply text and other database-configured items). All tests are performed against version 2.2.25. $ dovecot --version 2.2.25 (7be1766) My configuration looks like: dict { sieve = sqlite:/etc/dovecot/pigeonhole-sieve.dict } [...] sieve_extdata_dict_uri = proxy::sieve I am able to read pretty much any attribute without any issue, except when the value contains a special character like "\r" or "\n". By using the doveadm dict client, I narrowed it down to the dictionary management part (either server, protocol or client). I was suspecting escaping functions from "lib/strescape.c" (mostly str_tabescape and its counterpart, used by "lib-dict/client.c"), so I monitored socket communications. It seems that escaping is done properly on the server and the socket is not an issue either. The following strace dump results from running "doveadm dict get" against the dict socket: connect(8, {sa_family=AF_UNIX, sun_path="..."}, 110) = 0 fstat(8, {st_mode=S_IFSOCK|0777, st_size=0, ...}) = 0 [...] write(8, "H2\t0\t0\tadmin(a)domain.tld\tsieve\n", 30) = 30 [...] read(8, "Otest\1r\1ntest\n", 8192) = 14 Indeed "\1r" and "\1n" are the escape sequences used by "lib/strescape.c". I went deeped and debugged the call to "dict_lookup" performed by doveadm. Indeed the client gets the proper string from the socket and to my surprise, it is properly unescaped. Then, in "client_dict_lookup" ("lib-dict/dict-client.c"), the call to "p_strdup" returns an empty string (null byte set at the target address). Before the call to the dict "->lookup" attribute (client_dict_lookup): RAX: 0x7ffff73a37c0 (push r14) RBX: 0x6831b8 ("priv/reply_body") RCX: 0x7fffffffe240 --> 0x682a60 --> 0x6831b8 ("priv/reply_body") RDX: 0x6831b8 ("priv/reply_body") RSI: 0x683288 --> 0x7ffff7653120 --> 0x7ffff73ea620 ([...]) RDI: 0x690ad0 --> 0x7ffff7400713 --> 0x75250079786f7270 ('proxy') 0x7ffff73a1f10 <dict_lookup+32>: mov rcx,r11 (value_r) 0x7ffff73a1f13 <dict_lookup+35>: mov rdx,r8 (key) 0x7ffff73a1f16 <dict_lookup+38>: mov rsi,r10 (pool) 0x7ffff73a1f19 <dict_lookup+41>: mov rdi,r9 (dict) 0x7ffff73a1f1c <dict_lookup+44>: add rsp,0x8 => 0x7ffff73a1f20 <dict_lookup+48>: jmp rax Before the call to p_strdup in "client_dict_lookup": RSI: 0x6832d8 ("test\r\ntest") (lookup.result.value) RDI: 0x683288 --> 0x7ffff7653120 --> [...] (pool) RAX: 0x0 (result) 0x7ffff73a384f: nop 0x7ffff73a3850: mov rsi,QWORD PTR [rsp+0x8] 0x7ffff73a3855: mov rdi,r14 => 0x7ffff73a3858: call 0x7ffff736d3c0 <p_strdup@plt> 0x7ffff73a385d: mov QWORD PTR [r13+0x0],rax 0x7ffff73a3861: mov rsi,QWORD PTR [rsp+0x18] 0x7ffff73a3866: xor rsi,QWORD PTR fs:0x28 0x7ffff73a386f: mov eax,ebx After the call: 0x7ffff73a3850: mov rsi,QWORD PTR [rsp+0x8] 0x7ffff73a3855: mov rdi,r14 0x7ffff73a3858: call 0x7ffff736d3c0 <p_strdup@plt> => 0x7ffff73a385d: mov QWORD PTR [r13+0x0],rax 0x7ffff73a3861: mov rsi,QWORD PTR [rsp+0x18] 0x7ffff73a3866: xor rsi,QWORD PTR fs:0x28 0x7ffff73a386f: mov eax,ebx 0x7ffff73a3871: jne 0x7ffff73a38da RSI: 0x0 RDI: 0x6832d8 --> 0x0 RAX: 0x6832d8 --> 0x0 (result) It is worth noting that I can reproduce the exact same execution flow with a non-multiline result string (lookup.result.value) that is properly copied by "p_strdup" and returned in RAX, then displayed by doveadm. I am not familiar with the pooling mechanism hidden behind the call to p_strdump and not quite sure why this behaviour is emerging. Maybe I am even miles away from an understanding of the issue here, but it sounds to me like something is wrong in the way "p_strdup" performs the copy. Hope this helps, kaiyou.

2 11

Re: First steps in Dovecot; IMAP not working
by Joseph Tam 18 Oct '16

18 Oct '16

Marnaud <anic297(a)mac.com> writes: > "mailtest", the new user, is in group mail(8). In addition, I've added > write permission for "others" to /var/mail. Now, I'm trying to send a > message to "mailtest" from another, working, e-mail account and nothing > happens. This time, "doveadm log errors" is empty. > > In short, I don't get any error but no mail either. Two things to check: # What does dovecot think user "mailtest" has? doveadm user mailtest # The sticky bit should be set on /var/mail (you didn't mention # setting it. It probably doesn't have bearing on this problem, # but it will make it a little more secure. chmod 1777 /var/mail > Since "doveadm log errors" returns an empty result, where should I look > for the problem? I usually don't use this command, I look at the log file which seems to have more details. Try looking there for more diagnostics. Also, look at your MTA's logs as well. Joseph Tam <jtam.home(a)gmail.com>

4 4

Warning: Sent SIGKILL to 100 imap-login processes
by Ximo Mira 18 Oct '16

18 Oct '16

Hi, Last night we tried a traffic bypass in an existing mail environment before migration to new Dovecot backend platfom using Dovecot proxy. We are using an LDAP value for checking the proxy host of the user. POP traffic was running flawlessly, but IMAP connections started to drop when few clients connected: Oct 17 22 :26:51 master: Warning: Sent SIGKILL to 100 imap-login processes There are hundreds of these lines, always between 99 and 100 processes. Looks like some kind of limit, but not sure if its related to the Dovecot proxy machines (pool of 3 in total) or the final destination (the same IMAP server for +10000 users). Concurrect IMAP connections may rise to around 2000. Thanks.

2 1

dovecot 2.2.25 BUG: local_name is not matching correctly
by Arkadiusz Miśkiewicz 18 Oct '16

18 Oct '16

Bug report: When using dovecot 2.2.25 SNI capability it doesn't always match proper vhost config. For example if we have such config: local_name imap.example.com { ssl_cert = </etc/certs/cert.imap.example.com.pem ssl_key = </etc/certs/cert.imap.example.com.pem } but imap client sends mixedcase SNI hostname like "IMAP.example.com" then dovecot won't match above local_name imap.example.coml config section. IMO dovecot should do case insensitive comparison. Case sensitive matching for DNS names makes little sense. -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org )

2 2

Massive LMTP Problems with dovecot
by Ralf Hildebrandt 17 Oct '16

17 Oct '16

Currently I'm having massive problems with LMTP delivery into dovcot. dovecot/lmtp processes are piling up, eas using considerable amounts of CPU: # ps auxwww|fgrep dove root 20537 0.0 0.0 18124 1196 ? Ss 15:18 0:00 /usr/sbin/dovecot -c /etc/dovecot/dovecot.conf dovecot 20541 0.0 0.0 9620 1084 ? S 15:18 0:00 dovecot/anvil root 20542 0.0 0.0 9752 1264 ? S 15:18 0:00 dovecot/log root 20544 0.0 0.0 21168 2276 ? S 15:18 0:00 dovecot/config copymail 20580 72.8 0.0 39556 7036 ? R 15:18 2:00 dovecot/lmtp dovecot 20582 0.0 0.0 18568 1756 ? S 15:18 0:00 dovecot/auth copymail 20597 77.2 0.0 35688 5136 ? R 15:18 2:06 dovecot/lmtp copymail 20598 39.3 0.0 38060 5596 ? R 15:18 1:04 dovecot/lmtp copymail 20613 62.3 0.0 38036 5600 ? R 15:18 1:41 dovecot/lmtp copymail 20619 56.4 0.0 37732 7448 ? R 15:18 1:31 dovecot/lmtp copymail 20620 75.9 0.0 35872 5336 ? R 15:18 2:03 dovecot/lmtp copymail 20627 37.8 0.0 36480 5892 ? R 15:18 1:01 dovecot/lmtp copymail 20838 60.5 0.0 35640 5036 ? R 15:19 0:59 dovecot/lmtp copymail 20840 66.3 0.0 35920 5296 ? R 15:19 1:04 dovecot/lmtp copymail 20841 66.0 0.0 37456 6852 ? R 15:19 1:04 dovecot/lmtp copymail 20842 64.5 0.0 36424 5808 ? R 15:19 1:02 dovecot/lmtp copymail 20843 67.6 0.0 39612 7064 ? R 15:19 1:05 dovecot/lmtp doveadm stop won't stop these, I have to use kill -9 on them. I already tried disabling fts (entirely), still things won't speed up. I can't strace: # strace -p 20841 Process 20841 attached (and that's it) # dpkg -l|grep dovecot ii dovecot-core 2:2.2.25-1~auto+57 amd64 secure POP3/IMAP server - core files ii dovecot-imapd 2:2.2.25-1~auto+57 amd64 secure POP3/IMAP server - IMAP daemon ii dovecot-lmtpd 2:2.2.25-1~auto+57 amd64 secure POP3/IMAP server - LMTP server ii dovecot-lucene 2:2.2.25-1~auto+57 amd64 secure POP3/IMAP server - Lucene support ii dovecot-sieve 2:2.2.25-1~auto+57 amd64 secure POP3/IMAP server - Sieve filters support I also tried deleting the mdboxes, that also didn't change anything. Ideas? -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebrandt(a)charite.de | http://www.charite.de

2 1

Re: First steps in Dovecot; IMAP not working
by Marnaud 17 Oct '16

17 Oct '16

Sorry, my previous message got mangled. I'm re-writing it, quoting manually. I apologize for the traffic. >(Sorry I read this list in digest form so frequently I'm half a step behind.) No problem. >No, it's quite explicit. User "webuser" has uid/gid = 1001(webuser)/1000(ftpusers). Your mail spool has permission uid/gid = root(0)/mail(8), neither of which allows webuser to write to this mail spool to creates its own mail folder. You're right (I don't have enough Unix habits, it seems...). I couldn't change this user (it must be in the ftpusers group for other purposes), so I tried adding another user for testing mail. "mailtest", the new user, is in group mail(8). In addition, I've added write permission for "others" to /var/mail. Now, I'm trying to send a message to "mailtest" from another, working, e-mail account and nothing happens. This time, "doveadm log errors" is empty. In short, I don't get any error but no mail either. >Aki Tuomi <aki.tuomi(a)dovecot.fi> replies with several solutions: >>In your configuration, dovecot uses whatever user/group returned by PAM. Since the webuser has never logged in, it has no directory under /var/mail. If you want, you can >>a) override mail_uid and mail_gid in userdb/passdb >>b) pre-create /var/mail/webuser and chown it to webuser:ftpusers >>c) you can let ftpusers write to /var/mail. Ok, I thought I had to do all of them (and didn't understand step a)). So I've done step c) by allowing everyone write access. >Or if you dynamically/frequently onboard mail accounts, and users cannot arbitrarily write into this directory, you can "chmod 1777 /var/mail/" and let dovecot auto-create it (might also want to set "lda_mailbox_autocreate = yes". I've done it right now; same problem. Since "doveadm log errors" returns an empty result, where should I look for the problem? Thank you.

1 0

Re: First steps in Dovecot; IMAP not working
by Joseph Tam 17 Oct '16

17 Oct '16

(Sorry I read this list in digest form so frequently I'm half a step behind.) > For sake of ?security?, I chose to not allow plaintext communication > (being new to this, I think being strict is a good choice). I?ve tried > with the openssl option and it successfully logged in. Yes, you've included some more log entries, which makes the problem clearer, as it usually does. > Oct 13 05:56:28 imap(webuser): Error: open(/var/mail/webuser) failed: > Permission denied (euid=1001(webuser) egid=1000(ftpusers) missing +w perm: > /var/mail, we're not in group 8(mail), dir owned by 0:8 mode=0775) > ... > I checked, using ls -l /var, and I get this: > drwxrwsr-x 2 root mail 4096 Apr 27 11:27 mail > so the group looks to be correctly set to 'mail', despite what the log says, > right? No, it's quite explicit. User "webuser" has uid/gid = 1001(webuser)/1000(ftpusers). Your mail spool has permission uid/gid = root(0)/mail(8), neither of which allows webuser to write to this mail spool to creates its own mail folder. Aki Tuomi <aki.tuomi(a)dovecot.fi> replies with several solutions: > In your configuration, dovecot uses whatever user/group returned by > PAM. Since the webuser has never logged in, it has no directory under > /var/mail. If you want, you can > > a) override mail_uid and mail_gid in userdb/passdb > b) pre-create /var/mail/webuser and chown it to webuser:ftpusers > c) you can let ftpusers write to /var/mail. Or if you dynamically/frequently onboard mail accounts, and users cannot arbitrarily write into this directory, you can "chmod 1777 /var/mail/" and let dovecot auto-create it (might also want to set "lda_mailbox_autocreate = yes". Joseph Tam <jtam.home(a)gmail.com>

2 1

Re: First steps in Dovecot; IMAP not working
by Aki Tuomi 17 Oct '16

17 Oct '16

On 13.10.2016 12:42, Marnaud wrote: > > "Aki Tuomi" <aki.tuomi(a)dovecot.fi> wrote: > >> doveconf -n shows what's there. if you have ssl=no somewhere else in the >> config after you set it to required, it gets overwritten. >> >> Aki > > Thanks, Aki. > It means I have to open each conf file (e.g. using nano) and search > for ssl=no; I'm right or there's a specific file to check? I see you replied to me only, please keep your replies on-list. Try grep -r ssl.*no /etc/dovecot Aki

4 13

Latest HG Changes (fac92b5) affect Sieve-Plugin/LMTP
by Thomas Leuxner 15 Oct '16

15 Oct '16

# 2.2.devel (c73322f): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.devel (fac92b5) # OS: Linux 3.16.0-4-amd64 x86_64 Debian 8.6 ==> /var/log/dovecot/dovecot.log <== Oct 15 09:50:15 nihlus dovecot: lmtp(11447): Connect from local Oct 15 09:50:15 nihlus dovecot: lmtp(tlx(a)leuxner.net): Panic: file lda-sieve-plugin.c: line 447 (lda_sieve_execute_scripts): assertion failed: (script != NULL) Oct 15 09:50:15 nihlus dovecot: lmtp(tlx(a)leuxner.net): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x938ae) [0x7fd161fc18ae] -> /usr/lib/dovecot/libdovecot.so.0(+0x9399c) [0x7fd161fc199c] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7fd161f5b6de] -> /usr/lib/dovecot/modules/lib90_sieve_plugin.so(+0x3af8) [0x7fd15fdf8af8] -> /usr/lib/dovecot/libdovecot-lda.so.0(mail_deliver+0x49) [0x7fd16258bb39] -> dovecot/lmtp [DATA tlx(a)leuxner.net](+0x724e) [0x7fd1629bc24e] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x4c) [0x7fd161fd5e4c] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x10a) [0x7fd161fd730a] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x25) [0x7fd161fd5ed5] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7fd161fd6078] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7fd161f61be3] -> dovecot/lmtp [DATA tlx(a)leuxner.net](main+0x1a2) [0x7fd1629ba382] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7fd161ba4b45] -> dovecot/lmtp [DATA tlx(a)leuxner.net](+0x5430) [0x7fd1629ba430] Oct 15 09:50:15 nihlus dovecot: lmtp(tlx(a)leuxner.net): Fatal: master: service(lmtp): child 11447 killed with signal 6 (core not dumped)

3 9

Re: First steps in Dovecot; IMAP not working
by Joseph Tam 14 Oct '16

14 Oct '16

Moi <anic297(a)mac.com> wrote: > I've made some more tests and I still can't receive mails; sending them > still works. I don't receive any error message, just the mails that are > supposed to be received won't come. > In the mail logs, I find only this relevant line: > dovecot: imap-login: Aborted login (no auth attempts in 2 secs): user=<> Did you post doveconf -n (I didn't catch the head of this thread)? That would be step 0. A good first step is to test whether you have basic authentication working (to separate out if you have a server or client issue). I assume you allow plaintext communication, but if not, substitute telnet with "openssl sclient -connect your-server:993": C: # telnet your-server 143 S: * OK [CAPABILITY ... C: x1 login testuser theirpassword If you get an OK response to this, it may be a client issue (check settings on client). If you get an error or failure, look inward: check logs and config. Joseph Tam <jtam.home(a)gmail.com>

2 1

Maildir Expunged GUID mismatch for UID
by Steven Xu 14 Oct '16

14 Oct '16

Dovecot version:2.2.25 Since we used to keep our email files on widows server, I made the following changes in maildir-storage.h #define MAILDIR_EXTRA_SEP ',' #define MAILDIR_INFO_SEP_S ":" to "+". Everything seems working except EXPUNG, The dovecot log is flooded by messages like following: imap(xxxxx): Error: Mailbox INBOX: Expunged GUID mismatch for UID 7039 Then I read the source code, and found the following lines in maildir-sync-index.c T_BEGIN { guid = maildir_uidlist_lookup_ext(ctx->mbox->uidlist, uid, MAILDIR_UIDLIST_REC_EXT_GUID); if (guid == NULL) guid = t_strcut(filename, ':'); mail_generate_guid_128_hash(guid, guid_128); } T_END; I have to change the code to guid = t_strcut(filename, '+'); So, should MAILDIR_EXTRA_SEP be used here instead of ':'? Thanks, Steven

2 1