- dovecot - dovecot.org

Re: STAT command failure
by Joseph Tam 25 Oct '17

25 Oct '17

Andrew Charnley <ac(a)igaro.com> writes: >>> Regarding STAT which appears to have an issue with Dovecot:- >>> >>> [23:50:46] POP< +OK Dovecot ready. >>> [23:50:46] POP> USER xxxxx >>> [23:50:46] POP< +OK >>> [23:50:46] POP> PASS ******** >>> [23:50:46] POP< +OK Logged in. >>> [23:50:46] POP> STAT >>> [23:50:46] POP< -ERR Unknown command: >> >> user xxxxx >> pass *** >> stat > > I can confirm this works. > 2. Likely an issue with CLAWS email. If you can arrange a network capture of a non-SSL remote CLAWS connection, try checking whether there's a hidden character (NULL, .etc.) being sent. It's also telling that it works for some accounts, and not for others. Try rebuilding the user's index cache by removing it (save a copy!) and see if that makes it work. If it does, you can send the buggy caches to the developer and see if they can figure it out. Joseph Tam <jtam.home(a)gmail.com>

2 1

Fwd: master/master replications v. 2.2.32
by Jorge Canto E. 24 Oct '17

24 Oct '17

doveconf -n # 2.2.32 (dfbe293d4): /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-696.1.1.el6.x86_64 x86_64 CentOS release 6.9 (Final) ext3 auth_socket_path = /var/run/dovecot/auth-userdb doveadm_password = # hidden, use -P to show it doveadm_port = 61800 first_valid_uid = 150 last_valid_uid = 150 mail_location = maildir:/var/vmail/%d/%n mail_plugins = notify replication mail_privileged_group = mail mbox_write_locks = fcntl passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { mail_replica = tcp:xxx.xxx.xxx.xxx } postmaster_address = postmaster(a)it911.mx service aggregator { fifo_listener replication-notify-fifo { mode = 0666 user = vmail } unix_listener replication-notify { mode = 0666 user = vmail } } service auth { unix_listener /var/spool/postfix/private/auth { mode = 0666 user = postfix } unix_listener auth-userdb { group = mail mode = 0600 user = vmail } } service config { unix_listener config { user = vmail } } service doveadm { inet_listener { port = 61800 } user = vmail } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0666 } } ssl = required ssl_cert = </etc/pki/tls/certs/mailnew.it911.crt ssl_key = # hidden, use -P to show it userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } Thank you Jorge C. On Mon, Oct 23, 2017 at 1:19 PM, Jorge Canto E. <jorge.canto(a)gmail.com> wrote: > Hi, here is doveconf -n > > # 2.2.32 (dfbe293d4): /etc/dovecot/dovecot.conf > # OS: Linux 2.6.32-696.1.1.el6.x86_64 x86_64 CentOS release 6.9 (Final) > ext3 > auth_socket_path = /var/run/dovecot/auth-userdb > first_valid_uid = 150 > last_valid_uid = 150 > mail_location = maildir:/var/vmail/%d/%n > mail_privileged_group = mail > mbox_write_locks = fcntl > passdb { > args = /etc/dovecot/dovecot-sql.conf.ext > driver = sql > } > postmaster_address = postmaster(a)it911.mx > service auth { > unix_listener /var/spool/postfix/private/auth { > mode = 0666 > user = postfix > } > unix_listener auth-userdb { > group = mail > mode = 0600 > user = vmail > } > } > ssl = required > ssl_cert = </etc/pki/tls/certs/mailnew.it911.crt > ssl_key = # hidden, use -P to show it > userdb { > args = /etc/dovecot/dovecot-sql.conf.ext > driver = sql > } > > > Thank you > > Jorge C. > > On Mon, Oct 23, 2017 at 1:07 PM, Aki Tuomi <aki.tuomi(a)dovecot.fi> wrote: > >> >> > On October 23, 2017 at 7:29 PM "Jorge Canto E." <jorge.canto(a)gmail.com> >> wrote: >> > >> > >> > Hi, in the past I set up a master/master replication through TCP using >> > dovecot 2.2.10 on both servers and everything is running fine, I filter >> the >> > users to replicate using the iterate_query on file dovecot-sql.con.ext; >> now >> > I want to set up a new replication between two new servers running >> dovecot >> > 2.2.32 but the replicator service tries to replicate every user on my >> > database even when the iterate_query is correctly set up and the command >> > "doveadm user '*' " shows only the users I want to replicate, I think >> I am >> > missing something but I do not know what. >> > >> > Thank you so much for your help. >> > >> > Jorge C. >> >> Please provide doveconf -n >> >> Aki >> > >

1 0

Post-login scripting
by j.emerlik 24 Oct '17

24 Oct '17

Hi , I would like to save every authentication IP addresses to database, for IMAP and POP3 everything working correct but I don't know how to configure Post-login script for SMTP AUTH. Can you help me ? Regards, Jack

5 11

STAT command failure
by Andrew Charnley 24 Oct '17

24 Oct '17

Hi, Regarding STAT which appears to have an issue with Dovecot:- [23:50:46] POP< +OK Dovecot ready. [23:50:46] POP> USER xxxxx [23:50:46] POP< +OK [23:50:46] POP> PASS ******** [23:50:46] POP< +OK Logged in. [23:50:46] POP> STAT [23:50:46] POP< -ERR Unknown command: I have enabled the logging as previously instructed for pop3 however this is only up to the point of login. After this there is no further information. Login is successful. Other commands are working fine, I can use Evolution which doesn't use STAT and access email fine. The issue only came to light due to an attempt to change to Claws email. Strangely one of my four accounts on the same server does work. There is no difference in the settings and I've tried recreating them on both Claws and the server. The Claws team are 100% sure it's a Dovecot issue. This is the latest version available with Centos 7 so not the most up-to-date but I can't see anything in the logs which would suggest a change for 2.2. Regards, Andrew

2 2

master/master replications v. 2.2.32
by Jorge Canto E. 23 Oct '17

23 Oct '17

Hi, in the past I set up a master/master replication through TCP using dovecot 2.2.10 on both servers and everything is running fine, I filter the users to replicate using the iterate_query on file dovecot-sql.con.ext; now I want to set up a new replication between two new servers running dovecot 2.2.32 but the replicator service tries to replicate every user on my database even when the iterate_query is correctly set up and the command "doveadm user '*' " shows only the users I want to replicate, I think I am missing something but I do not know what. Thank you so much for your help. Jorge C.

2 1

Panic: file index-mail-binary.c
by grupo correo 23 Oct '17

23 Oct '17

Hi, i have Dovecot Director and Dovecot Backends with 2.2.32. i have found a email that my web server send with only one character "=" in the body of the email and it generate a log error in Dovecot log like this: Oct 23 13:16:50 dovecot_2.2.32 dovecot: imap(user@domain): Panic: file index-mail-binary.c: line 358 (blocks_count_lines): assertion failed: (block_count == 0 || block_idx+1 == block_count) Oct 23 13:16:50 dovecot_2.2.32 dovecot: imap(user@domain): Error: Raw backtrace: /usr/local/lib/dovecot/libdovecot.so.0(+0x9a340) [0x7fc22c186340] -> /usr/local/lib/dovecot/libdovecot.so.0(+0x9a41e) [0x7fc22c18641e] -> /usr/local/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7fc22c11c04b] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(+0xaeaab) [0x7fc22c4c4aab] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(index_mail_get_binary_stream+0x3c2) [0x7fc22c4c4f32] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(mail_get_binary_size+0x4b) [0x7fc22c45349b] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(imap_msgpart_size+0x70) [0x7fc22c504ca0] -> dovecot/imap() [0x41d6ea] -> dovecot/imap() [0x41b8d2] -> dovecot/imap(imap_fetch_more+0x35) [0x41cbf5] -> dovecot/imap(cmd_fetch+0x2fb) [0x40f76b] -> dovecot/imap(command_exec+0x5c) [0x41a4ac] -> dovecot/imap() [0x418c6f] -> dovecot/imap() [0x418cff] -> dovecot/imap(client_handle_input+0x175) [0x419085] -> dovecot/imap(client_input+0x72) [0x419552] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x52) [0x7fc22c19a432] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xe7) [0x7fc22c19b977] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x3c) [0x7fc22c19a4cc] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7fc22c19a688] -> /usr/local/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7fc22c125eb3] -> dovecot/imap(main+0x2e7) [0x40cb37] -> /lib64/libc.so.6(__libc_start_main+0xf5) [0x7fc22bd4cb15] -> dovecot/imap() [0x40ccb9] Oct 23 13:16:50 dovecot_2.2.32 dovecot: imap(user@domain): Fatal: master: service(imap): child 1636 killed with signal 6 (core dumps disabled) Oct 23 13:16:50 imapintranetmol1v dovecot: imap-login: proxy(user@domain): disconnecting 10.1.21.253 (Disconnected by server(0s idle, in=303, out=869)): user=<user@domain>, method=PLAIN, rip=xxx.xxx.xxx.xxx, lip=xxx.xxx.xxx.xxx, TLS, session=<fJRD8zRc4PwKARX9> The error happens when the client sends this comnand to the Director or to the Backends directly: C: 34 UID FETCH 7059 (BINARY.PEEK[1] BINARY.SIZE[1]) Thank you

1 0

dovecot, winbind and user folders
by Kristian Rink 23 Oct '17

23 Oct '17

Folks; I'm in the process of migrating an existing IMAP infrastructure to something that should be dovecot based. We live inside a Windows AD 2012 realm and the servers use winbind for user authentication as well as pam configurations to automatically create user home dirs whenever the user logs in first. Can something like this (mailbox is automatically generated whenever user logs in first) be done with dovecot too? Any best practises on how to work in such setups? I want to keep setup effort required for new users as low as possible... ;) Thanks in advance and all the best, Kristian

2 1

postfix -1 read errors
by Alef Veld 23 Oct '17

23 Oct '17

Hi all. I’m a bit worried about the following read errors i see in my log lately. Mails still arrive and get sent fine, but what is going on with this? It doesn’t look good. Nothing has change on server side and i restarted all services (dovecot, postfix, saslauthd, sql ). Maybe it’s a temporary iPhone thing (the device im using to read and send mails, not the first time that happened. Maybe changing the port will do the trick). Thanks for looking. Oct 22 20:19:00 www postfix/smtpd[16117]: SSL_accept:SSLv3 flush data Oct 22 20:19:00 www postfix/smtpd[16117]: read from 58130D3F70 [58130FDA83] (5 bytes => -1 (0xFFFFFFFFFFFFFFFF)) Oct 22 20:19:00 www postfix/smtpd[16117]: read from 58130D3F70 [58130FDA83] (5 bytes => 5 (0x5)) Oct 22 20:19:00 www postfix/smtpd[16117]: 0000 16 03 03 00 86 ..... Oct 22 20:19:00 www postfix/smtpd[16117]: read from 58130D3F70 [58130FDA88] (134 bytes => -1 (0xFFFFFFFFFFFFFFFF)) Oct 22 20:19:00 www postfix/smtpd[16117]: read from 58130D3F70 [58130FDA88] (134 bytes => 134 (0x86)) Oct 22 20:19:00 www postfix/smtpd[16117]: 0000 10 00 00 82 00 80 6d 90|41 c3 d3 9f 15 ea 8f 1c ......m. A....... Oct 22 20:19:00 www postfix/smtpd[16117]: 0010 a8 1c 08 ed a9 65 dc 5b|29 87 73 86 31 0e a9 d8 .....e.[ ).s.1... Oct 22 20:19:00 www postfix/smtpd[16117]: 0020 72 54 84 63 5f 9c 59 3e|cd aa da e7 a3 1f a9 b3 rT.c_.Y> ........ Oct 22 20:19:00 www postfix/smtpd[16117]: 0030 eb 0a 62 2b a4 26 65 d5|9d 63 2b c2 e2 8c a2 31 ..b+.&e. .c+....1 Oct 22 20:19:00 www postfix/smtpd[16117]: 0040 51 be ba a2 1e 73 45 7f|be 71 40 46 b9 01 bf 76 Q....sE. .q@F...v Oct 22 20:19:00 www postfix/smtpd[16117]: 0050 6e 77 a5 f5 c0 40 81 11|fa 95 57 e0 06 36 36 a8 nw...@.. ..W..66. Oct 22 20:19:00 www postfix/smtpd[16117]: 0060 21 c4 08 51 d5 d1 a5 98|6d dd f8 0b 79 a0 16 54 !..Q.... m...y..T Oct 22 20:19:00 www postfix/smtpd[16117]: 0070 4f 38 08 14 ab da a9 99|b7 69 b2 dc 81 4d aa 2e O8...... .i...M.. Oct 22 20:19:00 www postfix/smtpd[16117]: 0080 e8 26 57 8d 08 ea .&W... Oct 22 20:19:00 www postfix/smtpd[16117]: SSL_accept:SSLv3 read client key exchange A Oct 22 20:19:00 www postfix/smtpd[16117]: read from 58130D3F70 [58130FDA83] (5 bytes => -1 (0xFFFFFFFFFFFFFFFF)) Oct 22 20:19:00 www postfix/smtpd[16117]: read from 58130D3F70 [58130FDA83] (5 bytes => 5 (0x5)) Oct 22 20:19:00 www postfix/smtpd[16117]: 0000 14 03 03 00 01 ..... Oct 22 20:19:00 www postfix/smtpd[16117]: read from 58130D3F70 [58130FDA88] (1 bytes => -1 (0xFFFFFFFFFFFFFFFF)) Oct 22 20:19:00 www postfix/smtpd[16117]: read from 58130D3F70 [58130FDA88] (1 bytes => 1 (0x1)) Oct 22 20:19:00 www postfix/smtpd[16117]: 0000 01 . Oct 22 20:19:00 www postfix/smtpd[16117]: read from 58130D3F70 [58130FDA83] (5 bytes => -1 (0xFFFFFFFFFFFFFFFF)) Oct 22 20:19:00 www postfix/smtpd[16117]: read from 58130D3F70 [58130FDA83] (5 bytes => 5 (0x5)) Oct 22 20:19:00 www postfix/smtpd[16117]: 0000 16 03 03 00 28 ....( Oct 22 20:19:00 www postfix/smtpd[16117]: read from 58130D3F70 [58130FDA88] (40 bytes => -1 (0xFFFFFFFFFFFFFFFF)) Oct 22 20:19:00 www postfix/smtpd[16117]: read from 58130D3F70 [58130FDA88] (40 bytes => 40 (0x28)) Oct 22 20:19:00 www postfix/smtpd[16117]: 0000 89 eb f1 52 0c 38 5a 84|f8 ab 93 00 f4 ce dc c0 ...R.8Z. ........ Oct 22 20:19:00 www postfix/smtpd[16117]: 0010 04 6f 20 0b 55 d6 ea 85|15 d4 f0 85 c0 13 78 f4 .o .U... ......x. Oct 22 20:19:00 www postfix/smtpd[16117]: 0020 5c 87 1c ed 2a a0 51 56| \...*.QV Oct 22 20:19:00 www postfix/smtpd[16117]: SSL_accept:SSLv3 read finished A Oct 22 20:19:00 www postfix/smtpd[16117]: SSL_accept:SSLv3 write change cipher spec A Oct 22 20:19:00 www postfix/smtpd[16117]: SSL_accept:SSLv3 write finished A Oct 22 20:19:00 www postfix/smtpd[16117]: write to 58130D3F70 [581310B440] (51 bytes => 51 (0x33)) Oct 22 20:19:00 www postfix/smtpd[16117]: 0000 14 03 03 00 01 01 16 03|03 00 28 56 47 45 d2 74 ........ ..(VGE.t Oct 22 20:19:00 www postfix/smtpd[16117]: 0010 69 b8 8d f3 06 30 10 7e|64 42 a3 5b c8 bc a3 18 i....0.~ dB.[.... Oct 22 20:19:00 www postfix/smtpd[16117]: 0020 35 eb cc 50 f6 2e 9c 72|2e 3b 1f 8d 56 1e 1e 80 5..P...r .;..V... Oct 22 20:19:00 www postfix/smtpd[16117]: 0030 fa c7 6b ..k Oct 22 20:19:00 www postfix/smtpd[16117]: SSL_accept:SSLv3 flush data Oct 22 20:19:00 www postfix/smtpd[16117]: Anonymous TLS connection established from cpc98338-croy25-2-0-cust350.19-2.cable.virginm.net<http://cpc98338-croy25-2-0-cust350.19-2.cable.virginm.net>[82.45.65.95]: TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits) Oct 22 20:19:00 www postfix/smtpd[16117]: read from 58130D3F70 [58130FDA83] (5 bytes => -1 (0xFFFFFFFFFFFFFFFF)) Oct 22 20:19:00 www postfix/smtpd[16117]: read from 58130D3F70 [58130FDA83] (5 bytes => 5 (0x5)) Oct 22 20:19:00 www postfix/smtpd[16117]: 0000 17 03 03 00 2d ....- Oct 22 20:19:00 www postfix/smtpd[16117]: read from 58130D3F70 [58130FDA88] (45 bytes => -1 (0xFFFFFFFFFFFFFFFF)) Oct 22 20:19:00 www postfix/smtpd[16117]: read from 58130D3F70 [58130FDA88] (45 bytes => 45 (0x2D))

2 2

Proxy lmtps
by Matthias Kueth 22 Oct '17

22 Oct '17

Hi, when proxying lmtp from director to backend, director does not use STARTTLS. Delivering mails with postfix via lmtps to backend or director works encrypted. Is there a way to force the use of STARTTLS on dovecot director lmtp proxy? Regards, Matthias -- BOFH excuse #446: Mailer-daemon is busy burning your message in hell. (hbox storage?)

2 2

Question regarding replication - duplicate emails
by Remko Lodder 21 Oct '17

21 Oct '17

Dear Dovecot and community, We run a small email service for our customers, based on two machines that are made “redundant or clustered” by using the replication feature of Dovecot. This works well, for most emails. Sometimes the following happends: Email to our support database arrives at the inbox. Every period a cronjob looks into that mailbox and parses the information and makes a support ticket from that message. The cronjob deletes the email afterwards and sees whether there are more new mails or not. In between the deletion and the (next) check, the email gets “resynced” again from the “other machine”, and is seen as a new email by the cronjob and gets handled again. So basically we get two tickets for one email. After that second run the email is no longer replicated. This behaviour can also be seen via webmail and email clients, this suggests that the replication might not be aware (enough) that the replication is occurring or that an item already had been synced from A to B (and does not need to get back from B to A after A deleted it). Is there a way to fiddle with the acknowledgement timing or give the processes some more space/time to get on par with eachother? Below is the configuration of machine B, they are synchronised through puppet, so only the hostname and IP addresses are different. (so for replication, A has: tcps:hostname_of_b:12346 and B has tcps:hostname_of_a:12346). Also note that HAproxy is prepared but not in use at all. # 2.2.33.1 (e9afa7f18): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.4.20 (7cd71ba) # OS: FreeBSD 11.1-RELEASE amd64 auth_mechanisms = plain login disable_plaintext_auth = no doveadm_password = # hidden, use -P to show it haproxy_trusted_networks = IPv4_Haproxy IPv6_Haproxy lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes lmtp_save_to_detail_mailbox = yes mail_fsync = always mail_location = sdbox:~/sdbox mail_plugins = " quota notify replication" 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 extracttext imapsieve vnd.dovecot.imapsieve namespace { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { special_use = \Junk } 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 { driver = pam } plugin { imapsieve_mailbox1_before = file:/usr/local/lib/dovecot/sieve/report-spam.sieve imapsieve_mailbox1_causes = COPY imapsieve_mailbox1_name = Spam imapsieve_mailbox2_before = file:/usr/local/lib/dovecot/sieve/report-ham.sieve imapsieve_mailbox2_causes = COPY imapsieve_mailbox2_from = Spam imapsieve_mailbox2_name = * mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename mail_log_fields = uid box msgid size mail_replica = tcps:hostname_of_machine_a:12346 sieve = ~/.dovecot.sieve sieve_after = /usr/local/etc/dovecot/sieve/after/ sieve_before = /usr/local/etc/dovecot/sieve/global/ sieve_pipe_bin_dir = /usr/local/lib/dovecot/sieve sieve_plugins = sieve_imapsieve sieve_extprograms sieve_vacation_dont_check_recipient = yes } postmaster_address = postmaster(a)ourdomain.tld protocols = imap pop3 lmtp sieve replication_max_conns = 100 service aggregator { fifo_listener replication-notify-fifo { mode = 0666 } unix_listener replication-notify { mode = 0666 } } service auth { unix_listener /var/spool/postfix/private/auth { mode = 0666 } } service doveadm { inet_listener { port = 12346 ssl = yes } } service imap-login { inet_listener imap_haproxy { haproxy = yes port = 10143 } inet_listener imaps_haproxy { haproxy = yes port = 10144 ssl = yes } service_count = 1 } service imap { process_limit = 1024 } service lmtp { inet_listener lmtp { address = IPv4, IPv6, 127.0.0.1 ::1 port = 24 } unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service pop3 { process_limit = 1024 } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0666 } } ssl_ca = </usr/local/etc/letsencrypt/live/host.ourdomain.tld/fullchain.pem ssl_cert = </usr/local/etc/letsencrypt/live/host.ourdomain.tld/cert.pem ssl_client_ca_file = /usr/local/certificates/letsencrypt-ca.pem ssl_key = # hidden, use -P to show it ssl_protocols = !SSLv2 !SSLv3 userdb { driver = passwd } verbose_proctitle = yes protocol lmtp { auth_username_format = %n mail_plugins = quota sieve replication notify postmaster_address = postmaster(a)ourdomain.tld } protocol lda { mail_plugins = " quota notify replication sieve replication notify" } protocol imap { imap_client_workarounds = delay-newmail mail_max_userip_connections = 50 mail_plugins = " quota notify replication imap_quota imap_sieve" }

2 3

Re: IMAP stops responding.
by Joseph Tam 20 Oct '17

20 Oct '17

S?ren Peter Skou <sps(a)DanskKabelTV.dk> writes: > I've experienced that IMAP/IMAPS stops responding. To restore service > there is only one way, restart Dovecot completely. This leads to > services being interrupted for some people, so it seems to only affect > some of the users on the server. But POP3/POP3s is still running > happily. Also, it happens more as we approach Rush Hour. Help us help you: the problem is most likely pointed out in the log files. Also, a dump of your configurations (doveconf -n) would help. Offhand, it seems you've hit an IMAP resource limit, such as mail_max_userip_connections, or perhaps process/memory limits (e.g. process_limit, vsz_limit, etc.). Joseph Tam <jtam.home(a)gmail.com>

1 0

fts_solr: Indexing failed: 500 Server Error
by Kirill Ponomarev 20 Oct '17

20 Oct '17

Hi, running dovecot 2.2.33.2 with solr 7.1.0 (with new XML scheme instead of JSON) on FreeBSD produces this error message: Oct 20 20:58:29 krion postfix/smtpd[13371]: disconnect from mail-yw0-f169.google.com[209.85.161.169] ehlo=2 +starttls=1 mail=1 rcpt=1 data=1 quit=1 commands=7 Oct 20 20:58:29 krion dovecot: indexer-worker(krion(a)krion.cc): Error: fts_solr: Indexing failed: 500 Server Error Oct 20 20:58:29 krion dovecot: indexer-worker(krion(a)krion.cc): Error: fts_solr: Indexing failed: 500 Server Error Oct 20 20:58:29 krion dovecot: indexer-worker(krion(a)krion.cc): Error: Mailbox INBOX: Transaction commit failed: FTS +transaction commit failed: backend deinit (attempted to index 1 messages (UIDs 166..166)) Oct 20 20:58:30 krion dovecot: imap(krion(a)krion.cc): Connection closed (IDLE finished 451.007 secs ago) in=43 +out=812 K.

1 0

IMAP stops responding.
by Søren Peter Skou 20 Oct '17

20 Oct '17

Hiya all, I've experienced that IMAP/IMAPS stops responding. To restore service there is only one way, restart Dovecot completely. This leads to services being interrupted for some people, so it seems to only affect some of the users on the server. But POP3/POP3s is still running happily. Also, it happens more as we approach Rush Hour. All of this leads me to believe that we're facing a problem with clients somehow. I've searched the net for the problem, and dating back I've found references to Apple units being the culprit. So we've taken an old Apple client, and tried to see how many sessions it actually starts, the result of that test was that regardless what we tried it only opened one extra session. A bit of information, Debian OS : dovecot-core 2:2.2.27-1~auto+44 amd64 secure POP3/IMAP server - core files dovecot-imapd 2:2.2.27-1~auto+44 amd64 secure POP3/IMAP server - IMAP daemon dovecot-mysql 2:2.2.27-1~auto+44 amd64 secure POP3/IMAP server - MySQL support dovecot-pop3d 2:2.2.27-1~auto+44 amd64 secure POP3/IMAP server - POP3 daemon dovecot-sieve 2:2.2.27-1~auto+44 amd64 secure POP3/IMAP server - Sieve filters support the Config itself is fairly simple, lookup through MySQL to find username/password etc - I don't really see any obvious option. Also, limiting users/sessions per IP isn't really a good idea as we have a great deal of customers behind NAT. Med venlig hilsen/Best regards Søren P. Skou Netværkstekniker [logo] Teglholmsgade 1 0900 København C Tlf: 69 12 12 12 E-mail: sps(a)danskkabeltv.dk<mailto:sps@danskkabeltv.dk> Web: www.danskkabeltv.dk<http://www.danskkabeltv.dk/>

2 1

v2.2.33.2 released
by Timo Sirainen 20 Oct '17

20 Oct '17

https://dovecot.org/releases/2.2/dovecot-2.2.33.2.tar.gz https://dovecot.org/releases/2.2/dovecot-2.2.33.2.tar.gz.sig One more patch release with some fixes: - doveadm: Fix crash in proxying (or dsync replication) if remote is running older than v2.2.33 - auth: Fix memory leak in %{ldap_dn} - dict-sql: Fix data types to work correctly with Cassandra

1 0

Re: HTTPS for http://xi.dovecot.fi/debian/
by Aki Tuomi 20 Oct '17

20 Oct '17

> On October 20, 2017 at 12:37 PM Florent B <florent(a)coppint.com> wrote: > > > Hi, > > We use Dovecot packages from http://xi.dovecot.fi/debian/. > > Could it be possible to serve it with HTTPS ? > > Thank you. > > Florent Hi! It has now https enabled with valid certificate. Aki

1 0

quota only for oungoing
by Aidar Kamalov 20 Oct '17

20 Oct '17

Hello! I setup quota and quota warnings for my mail system(dovecot+exim). By I want to reject only outgoing messages if quota exceeded. Is it possible to congi dovecot to not reject incoming messages? I use dovecot-lda for mail delivery. ldap_delivery: driver = pipe command = /usr/lib/dovecot/deliver -d "${lookup ldap{user=**********))(mai -f $sender_address -a $original_local_part@$original_domain message_prefix = message_suffix = delivery_date_add envelope_to_add return_path_add log_output return_output user = mail group = mail temp_errors = 64 : 69 : 70: 71 : 72 : 73 : 74 : 75 : 78 -- Aydar A. Kamalov

2 5

Iteration for ldap userdb does not work
by Holger A. Brinkhaus 20 Oct '17

20 Oct '17

Hi, I have a working ldap authentification for dovecot (with ldap based userdb query) for my Active Directory but iterations by doveadm -A runs in timeout. I tried now for three days and get it not to work. Best regards Holger /etc/dovecot/dovecot-ldap-userdb.conf is symlink to /etc/doveconf/doveconf-ldap.conf debug_level = 0 uris = ldaps://server1.office.hb-os.de:636 dn = cn=BINDUSER,cn=Users,dc=SUBDOM,dc=DOM,dc=de dnpass = MYPASSWORD auth_bind = yes ldap_version = 3 deref = never base = cn=Users,dc=SUBDOM,dc=DOM,dc=de scope = subtree user_attrs = =home=/usr/data/vmail/%d/%n, =mail=maildir:/usr/data/vmail/%d/%n/Maildir user_filter = (&(objectClass=person)(mail=%u)) pass_filter = (&(objectClass=person)(mail=%u)) iterate_attrs = mail=user iterate_filter = (objectClass=person) doveconf -n # 2.2.13: /etc/dovecot/dovecot.conf # OS: Linux 3.16.0-4-amd64 x86_64 Debian 8.9 auth_mechanisms = plain login base_dir = /var/run/dovecot/ default_vsz_limit = 512 M dict { expire = mysql:/etc/dovecot/dovecot-dict-expire.conf.ext } first_valid_uid = 100 imap_idle_notify_interval = 16 mins lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes log_path = /var/log/dovecot.log log_timestamp = "%Y-%m-%d %H:%M:%S " mail_gid = vmail mail_home = /usr/data/vmail/%d/ mail_location = maildir:~/Maildir:LAYOUT=fs mail_plugins = expire mail_privileged_group = vmail 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 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-ldap.conf driver = ldap } plugin { antispam_backend = pipe antispam_debug_target = syslog antispam_pipe_program = /usr/data/vmail/spampipe.sh antispam_pipe_program_notspam_arg = --ham antispam_pipe_program_spam_arg = --spam antispam_pipe_tmp_dir = /tmp antispam_spam = Junk;SPAM;Spam antispam_trash = Trash expire = Trash expire2 = Trash/* expire3 = Junk expire_dict = proxy::expire sieve = /usr/data/vmail/%u/sieve/active-script.sieve sieve_before = /usr/data/vmail/sieve/spam-global.sieve sieve_dir = /usr/data/vmail/%d/%n/sieve/scripts/ sieve_max_redirects = 4 sieve_max_script_size = 1M sieve_quota_max_scripts = 128 } postmaster_address = ME(a)DOMAIN.de protocols = imap lmtp sieve service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { group = postfix mode = 0600 user = postfix } user = vmail } service dict { unix_listener dict { group = vmail mode = 0600 user = vmail } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } process_min_avail = 10 service_count = 1 } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } ssl_cert = </etc/ssl/certs/MY_CERT.crt ssl_key = </etc/ssl/private/MY_CERT.key userdb { args = /etc/dovecot/dovecot-ldap-userdb.conf driver = ldap } protocol lmtp { mail_plugins = expire sieve } protocol lda { mail_plugins = expire sieve } protocol imap { mail_max_userip_connections = 10 mail_plugins = expire antispam }

2 2

Dovecot >=2.2.29 + Filesystem quota = incorrect storage information
by Macka 18 Oct '17

18 Oct '17

Hi, I have problem with quota storage information in dovecot-2.2.29 (and newer versions, too - 2.2.30.2). I use FS quota backend. ............................ # 2.2.29.1 (e0b76e3): /etc/dovecot/dovecot.conf # OS: Linux 4.4.68-1 x86_64 mail_plugins = quota plugin { quota = fs:User quota:mount=/poczta:user quota2 = fs:Group quota:mount=/poczta:group } protocol imap { mail_max_userip_connections = 10 mail_plugins = "imap_quota mail_log notify antispam" } ................................. After upgrade from 2.2.27 to 2.2.29 (newest 2.2.30.2 too), dovecot returns incorrect informations about quota storage: # doveadm quota get -u myusername Quota name Type Value Limit % User quota STORAGE 10960896 100000 10960 or # ( echo "A1 GETQUOTAROOT INBOX"; echo "A2 logout" ) | /usr/lib64/dovecot/imap -u myusername * PREAUTH [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS THREAD=ORDEREDSUBJECT MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS BINARY MOVE NOTIFY SPECIAL-USE QUOTA] Logged in as myusername imap(myusername): Info: Logged out in=31 out=588 * QUOTAROOT INBOX "User quota" * QUOTA "User quota" (STORAGE 10960896 100000) A1 OK Getquotaroot completed (0.001 + 0.000 secs). * BYE Logging out A2 OK Logout completed (0.001 + 0.000 secs). Values are in BYTES and Limit in BLOCKS which gives insane information in % Other server with older version 2.2.27 returns correct numbers (both in BLOCKS) # doveadm quota get -u username2 Quota name Type Value Limit % user STORAGE 558336 614400 90 Is this a bug in new versions? How can I fix this? -- macka

3 6

Re: Last Login example
by Siarhei Chystsiakou 18 Oct '17

18 Oct '17

My config: config plugins: # cat /etc/dovecot/conf.d/90-last_login.conf > dict { > lastlogin = mysql:/etc/dovecot/dict.conf.d/90-lastlogin.conf > } > plugin { > last_login_dict = proxy::lastlogin > } config db connector: # cat /etc/dovecot/dict.conf.d/90-lastlogin.conf > connect=host=localhost dbname=mail_user user=userDB password=Pa$$w0rd > map { > pattern = shared/last-login/$user > table = mailbox > username_field = username > value_field = lastlogin > value_type = uint > fields { > username = $user > } > } config imap and pop3 # cat /etc/dovecot/dict.conf.d/20-imap.conf > protocol imap { > mail_plugins = $mail_plugins quota imap_quota imap_acl last_login > } > # cat /etc/dovecot/dict.conf.d/20-pop3.conf > protocol imap { > mail_plugins = $mail_plugins last_login > } In the database in the table with users to add a column. If you have questions, I'll try to answer 2017-10-14 20:20 GMT+02:00 Jorge Bastos <mysql.jorge(a)decimal.pt>: > Howdy, > > > > Where can i find a configuration example for the last login plugin, that > fits for latest dovecot version? > > Thanks in advanced! > > > > Jorge, >

1 0

Re: Last Login example
by Aki Tuomi 18 Oct '17

18 Oct '17

On 14.10.2017 21:20, Jorge Bastos wrote: > Howdy, > > > > Where can i find a configuration example for the last login plugin, that > fits for latest dovecot version? > > Thanks in advanced! > > > > Jorge, https://wiki.dovecot.org/Plugins/LastLogin Is there some problem you are experiencing? Aki

1 0

Replication between different versions of dovecot
by Dmitry Nezhevenko 18 Oct '17

18 Oct '17

Hi, Can't find any notes about this in documentation. Is replication supposed to work between different versions of dovecot? I've just found that dovecot 2.2.33.1 was uploaded to debian unstable and it crashes on every replication with older dovecot 2.2.27. (version 2.2.32.1 was probably ok) Summary: - 2.2.33.1 crashes when replicating from/to 2.2.27 - 2.2.32.1 probably ok when replicating from/to 2.2.27 I was able to capture backtrace of crashed doveadm-server: Program terminated with signal SIGSEGV, Segmentation fault. #0 i_stream_next_line (stream=stream@entry=0x0) at istream.c:428 428 istream.c: No such file or directory. (gdb) bt #0 i_stream_next_line (stream=stream@entry=0x0) at istream.c:428 #1 0x00007f60244306df in i_stream_read_next_line (stream=0x0) at istream.c:449 #2 0x0000560304f22e79 in server_connection_print_log (conn=0x560305e930f8) at server-connection.c:305 #3 0x0000560304f238af in server_connection_input_one (conn=<optimized out>) at server-connection.c:405 #4 server_connection_input (conn=<optimized out>) at server-connection.c:390 #5 0x00007f602443a572 in io_loop_call_io (io=0x560305e81e30) at ioloop.c:600 #6 0x00007f602443bc1e in io_loop_handler_run_internal (ioloop=ioloop@entry=0x560305e59ad0) at ioloop-epoll.c:223 #7 0x00007f602443a606 in io_loop_handler_run (ioloop=ioloop@entry=0x560305e59ad0) at ioloop.c:649 #8 0x00007f602443a7b8 in io_loop_run (ioloop=0x560305e59ad0) at ioloop.c:624 #9 0x0000560304f0de5a in dsync_connect_tcp (ctx=ctx@entry=0x560305e7e9e8, mail_set=mail_set@entry=0x560305e8ad50, target=0x560305e8b94c "inhex.vpn.local:9993", ssl=ssl@entry=false, error_r=error_r@entry=0x7fff8e40b9e8) at doveadm-dsync.c:850 #10 0x0000560304f0fbe3 in parse_location (error_r=0x7fff8e40b9e8, remote_cmd_args_r=0x7fff8e40b858, location=<optimized out>, mail_set=0x560305e8ad50, ctx=0x560305e7e9e8) at doveadm-dsync.c:875 #11 cmd_dsync_prerun (_ctx=0x560305e7e9e8, service_user=<optimized out>, error_r=0x7fff8e40b9e8) at doveadm-dsync.c:947 #12 0x0000560304f10891 in doveadm_mail_next_user (ctx=ctx@entry=0x560305e7e9e8, cctx=cctx@entry=0x7fff8e40b9f0, error_r=error_r@entry=0x7fff8e40b9e8) at doveadm-mail.c:414 #13 0x0000560304f11473 in doveadm_mail_single_user (ctx=ctx@entry=0x560305e7e9e8, cctx=cctx@entry=0x7fff8e40b9f0, error_r=error_r@entry=0x7fff8e40b9e8) at doveadm-mail.c:460 #14 0x0000560304f262fb in doveadm_mail_cmd_server_run (cctx=0x7fff8e40b9f0, mctx=0x560305e7e9e8, conn=0x560305e7a878) at client-connection.c:246 #15 doveadm_cmd_handle (cctx=0x7fff8e40b9f0, argv=<optimized out>, argc=<optimized out>, cmd_name=<optimized out>, conn=0x560305e7a878) at client-connection.c:329 #16 client_handle_command (args=<optimized out>, conn=0x560305e7a878) at client-connection.c:399 #17 client_connection_input (conn=<optimized out>) at client-connection.c:541 #18 0x00007f602443a572 in io_loop_call_io (io=0x560305e58c40) at ioloop.c:600 #19 0x00007f602443bc1e in io_loop_handler_run_internal (ioloop=ioloop@entry=0x560305e529a0) at ioloop-epoll.c:223 #20 0x00007f602443a606 in io_loop_handler_run (ioloop=ioloop@entry=0x560305e529a0) at ioloop.c:649 #21 0x00007f602443a7b8 in io_loop_run (ioloop=0x560305e529a0) at ioloop.c:624 #22 0x00007f60243bf893 in master_service_run (service=0x560305e52840, callback=<optimized out>) at master-service.c:719 #23 0x0000560304f011d5 in main (argc=<optimized out>, argv=<optimized out>) at main.c:143 -- WBR, Dmitry

2 4

Re: Limit the nuumber of mails POPped at a time
by Joseph Tam 18 Oct '17

18 Oct '17

> I have a piece of software with a mailclient that has problems when it > POP's large amounts of mail. Unfortunately the system can't be updated > or fixed.So I'm trying to figure out if I can limit the number of mails > that can be seen via Dovecot. > ... > So it would be a question of always presenting a maximum of 300 mails > via the POP3.Is it doable? You're probably solving the wrong problem -- the mail client really ought to be able to process 300+ messages. It may be a better use of time to fix that than to torture dovecot to give you what you want. You can try using a plugin to define a virtual INBOX https://wiki.dovecot.org/Plugins/Virtual with search/selection criteria to limit the number of messages. You can also try some LDA script (e.g. procmail) hackery to create INBOX volumes of 300 messages, then do some shuffling around when the INBOX gets emptied. Joseph Tam <jtam.home(a)gmail.com>

1 0

mdbox + director + nfs
by Raymond Sellars 17 Oct '17

17 Oct '17

Hi Matt We've been running this configuration for the past couple of years. Not noticed any locking issues. As I understand it that's the objective of using Director. As Aki notes make sure you have the appropriate NFS settings. Other lessons we encountered. Important to ensure NFS is NTP sync'd and aligned with your hosts, we hit some issues with file timestamps leading to problems. Replication, e.g. for perhaps a backup or DR site. Seems to work but we've had the odd occasion of the indexes drifting. Never tracked the reason down and believe its unrelated to the NFS. Just something to monitor. Regards Raymond ------------------------------ Message: 5 Date: Tue, 17 Oct 2017 08:50:18 +0300 From: Aki Tuomi <aki.tuomi(a)dovecot.fi> To: dovecot(a)dovecot.org Subject: Re: mdbox + director + nfs Message-ID: <70b54e75-14fe-2caa-eccb-1ffc05c2a1e5(a)dovecot.fi> Content-Type: text/plain; charset=utf-8 NFS with mdbox should work just fine, locking should not be an issue, but please read https://wiki.dovecot.org/NFS Aki On 17.10.2017 02:32, Matt Bryant wrote: > Anyone had any experience they can share using a director setup with > NFS and using the mdbox format instead of maildir. Is locking an issue > on index files ?? > > rgds > > Matt

1 0

Dovecot 2.2.31 Incorrect Search
by Siarhei Chystsiakou 17 Oct '17

17 Oct '17

Hi. I have installed dovecot 2.2.31 and fts plugin with Apache Solr 6.6.1. I have found that imap search is not correct in my dovecot. For example, I want to find email from user s.chistiakov(a)example.com. I run IMAP command "SEARCH FROM s.chi" and result is null. But if I run IMAP command "SEARCH FROM s.chistiakov" I get list of emails from this user. Why does this happen and how to fix it? Help me please ) Thanks. Result of my actions in telnet: https://hastebin.com/fewanacafu.md Dovecot config: https://hastebin.com/noqehimaxu.makefile

2 2

Re: Disable PAM
by Aki Tuomi 17 Oct '17

17 Oct '17

Yep. Just remove any passdb/userdb pam blocks ---Aki TuomiDovecot oy -------- Original message --------From: Travis Dolan <travis.dolan(a)gmail.com> Date: 17/10/2017 17:40 (GMT+02:00) To: dovecot(a)dovecot.org Subject: Disable PAM Can I disable PAM auth if all my username/password lookups are via a database connection? I would love to get rid of the following lines in my logs... Oct 17 14:32:14 auth-worker(7809): Info: pam(xxx-xxx-xxx,111.111.111.111,<sdfhgsdfgsd>): pam_authenticate() failed: Authentication failure (password mismatch?) Cheers.

1 0