- dovecot - dovecot.org

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