February 2016 - dovecot

Error: istream-seekable: safe_mkstemp(/tmp/dovecot.imap.) failed
by Thomas Leuxner 05 Sep '16

05 Sep '16

I'm seeing these recently: Feb 27 09:24:01 nihlus dovecot: imap(tlx(a)leuxner.net): Error: istream-seekable: safe_mkstemp(/tmp/dovecot.imap.) failed: No such file or directory Feb 27 09:24:01 nihlus dovecot: imap(tlx(a)leuxner.net): Error: istream-seekable: safe_mkstemp(/tmp/dovecot.imap.) failed: No such file or directory Feb 27 09:24:01 nihlus dovecot: imap(tlx(a)leuxner.net): Error: istream-seekable: safe_mkstemp(/tmp/dovecot.imap.) failed: No such file or directory Feb 27 09:24:01 nihlus dovecot: imap(tlx(a)leuxner.net): Error: istream-seekable: safe_mkstemp(/tmp/dovecot.imap.) failed: No such file or directory Feb 27 09:24:01 nihlus dovecot: imap(tlx(a)leuxner.net): Error: istream-seekable: safe_mkstemp(/tmp/dovecot.imap.) failed: No such file or directory Feb 27 09:24:01 nihlus dovecot: imap(tlx(a)leuxner.net): Error: istream-seekable: safe_mkstemp(/tmp/dovecot.imap.) failed: No such file or directory $ doveconf -n | head # 2.2.devel (f1a9b58): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.devel (0de2a19) Regards Thomas

2 3

[Dovecot] How to disable SSL and TLSv1.1?
by Darren Pilgrim 16 Aug '16

16 Aug '16

I'm running Dovecot 2.2.5 and want to make it refuse SSLv2, SSLv3 and TLSv1.0. Clients will opportunistically use TLS 1.1 and 1.2, but now I want require they do so. Is it enough to set ssl_cipher_list = HIGH:!SSLv2:!SSLv3:!TLSv1.0:!aNULL:!MD5 or are there additional settings I need to specify?

8 12

Re: [g.danti@assyoma.it: [Dovecot] Re: Questions about hardlinks, alternate storage and compression]
by Gionatan Danti 08 Jun '16

08 Jun '16

Il 26-11-2015 15:15 John R. Dennison ha scritto: > You are strongly encouraged to update that CentOS system. Current is > 6.7 (released some 3 months ago) and dovecot-2.0.9-19. Ouch! I copied outdated information from my old post. My current system _is_ CentOS 6.7 with dovecot dovecot-2.0.9-19.el6_7.2.x86_64 Sorry for the confusion. Still, the problems remain > If you find you need a more modern dovecot version you will find that > dovecot-2.2.19-1 is in the GhettoForge 3rd-party repo, packaged and > maintained by a respected CentOS community member. Information > on this repo can be found by following the links off of: > > http://wiki.centos.org/AdditionalResources/Repositories > The point is that I _don't know_ if more recent Dovecot version have the same problem or not. Moreover, as this is a production machine, I would like to leave a key package as Dovecot as near as possible to the shipping O.S. Thanks. -- Danti Gionatan Supporto Tecnico Assyoma S.r.l. - www.assyoma.it email: g.danti(a)assyoma.it - info(a)assyoma.it GPG public key ID: FF5F32A8

3 10

Option to not add "Received" header ?
by Florent B 27 Apr '16

27 Apr '16

Hi everyone, I use Dovecot in lmtp mode to receive mails. I would like an option to tell Dovecot to not add a "Reveived" header on each server (I use a director, so Director also adds this header). Is it possible to do this ? Or could it be a future feature ? Thank you. Florent

5 6

[Dovecot] Patch: 2.0 support for URLAUTH, BURL, CATENATE
by Mike Abbott 18 Apr '16

18 Apr '16

Thank you Timo for beginning the port of URLAUTH, BURL, and CATENATE from 1.2 to 2.0. Attached please find two patches that finish the port to 2.0. One patch updates the dovecot-2.0-urlauth branch and is based on the tip of that branch. The other patch adds the full support to dovecot-2.0.beta5. The resulting URLAUTH/BURL/CATENATE code is the same. Please let me know if you have any questions about these patches. Thanks.

4 9

[Dovecot] Replication and public namespaces
by Markus Weippert 11 Apr '16

11 Apr '16

Hi, I'm having some issues with replicating public namespaces. Everything seems to work fine for private namespaces, but while importing some huge mailboxes (many small mails) into a public namespace via imapsync, something goes wrong. The expected mail flow is: old-server (imapsync)> new-server1 (replication)> new-server2 But then, dovecot seems to run into race conditions when the replications process tries to sync the same public mailbox under two or more different users at the same time. As a result, messages get duplicated, new-server2 sends those back to new-server1 which then starts to produce duplicates too. If I don't kill the processes in time and delete the faulty mailbox, they start to produce thousands of mails. In fact, server2 should not export messages at all, since it's not productive yet and does not get any mail except from the replication. The only thing getting logged (only few compared to the huge amount of duplicates produced): "dsync-server(user(a)example.com): Warning: Maildir /...: Expunged message reappeared, giving a new UID" Is there any way to fix this? Regards, Markus doveadm_password = *********** doveadm_port = ***** mail_home = /var/vmail/private/%d/%n mail_location = maildir:~/mail mail_plugins = acl virtual listescape notify replication namespace inbox { inbox = yes location = prefix = separator = / type = private } namespace legacy { alias_for = # ... } namespace ns_public { list = children location = maildir:/var/vmail/public/%d prefix = Public/ separator = / subscriptions = no type = public } namespace virtual { # ... } plugin { mail_replica = tcps:************** } protocols = imap lmtp sieve replication_dsync_parameters = -d -l 60 -N -x virtual -x ns_public -U replication_full_sync_interval = 4 hours replication_max_conns = 20 service aggregator { fifo_listener replication-notify-fifo { user = vmail } unix_listener replication-notify { user = vmail } } service doveadm { inet_listener { port = 8143 ssl = yes } process_min_avail = 5 user = vmail vsz_limit = 4 G } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0600 user = vmail } }

3 7

New feature: HTTP API
by aki.tuomi＠dovecot.fi 05 Apr '16

05 Apr '16

Hi all! We are bringing out HTTP API for doveadm-server in master HEAD. This feature is experimental, and can be expected to have bugs in it and might not always work. If you feel like trying it out though, you can enable it in your configuration file: doveadm_api_key = some-string service doveadm { inet_listener http { port = 8080 } } To use the API, you can go to http://host:8080/doveadm. GET request will print out possible commands, along with their parameters. If you have set API KEY, you need to include it in the request as X-API-Key header. This API has been designed to resemble JMAP API since we are planning to implement it in future version. The rule of thumb is that all the commands work as they would on cli, so the parameters are more or less the same. There are few exceptions, like 'field' parameter in some mail/mailbox commands. Commands are executed by POSTin JSON to /doveadm. The JSON format is [ ["command",{"parameter":"value"},"opaque identifier"], ["command",{"parameter":"value"},"opaque identifier"], ["command",{"parameter":"value"},"opaque identifier"], ... ] Be warned though that even if it supports multiple commands, some commands still use i_fatal to terminate the server if they are unhappy. This will mean you will lose the whole result set, and get no output, so at this point it is safest option to run only one command at a time. If you run into problems or discover issues, please report them in the usual manner to us. Kind regards, Aki Tuomi Dovecot Oy

2 3

imapc tries to fetch uid 0
by Nagy, Attila 30 Mar '16

30 Mar '16

Hi, This is a capture from an imapc client session (which is triggered by a message, received via LMTP): * OK [CAPABILITY IMAP4rev1 NAMESPACE] Ready 2 LOGIN "uid" "pass" 2 OK LOGIN succeeded 1 LIST "" "" * LIST (\Noselect) "/" "" 1 OK LIST completed 3 APPEND "INBOX" {568} + Ready for 568 octets of data [...] 3 OK APPEND complete 4 EXAMINE "INBOX" * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted. * 4 EXISTS * 0 RECENT * OK [UIDVALIDITY 1455885804] * OK [UIDNEXT 5] 4 OK [READ-ONLY] EXAMINE successful 5 UID FETCH 0 (RFC822.SIZE BODY.PEEK[HEADER.FIELDS (Message-ID)]) 5 BAD Illegal syntax: Bad message number 0 Dovecot 2.2.21 I don't see any problems with the conversation otherwise. Is it safe to assume this is a bug in imapc?

3 3

LMTP proxy does not pass RCPT TO: ... 5xx response back
by Heiko Schlittermann 22 Mar '16

22 Mar '16

Hello, I'm using dovecot 2.2.9 and a director/backend setup. On the director I've the LMTP in proxy mode, mapping the users to one of the backends. The backends to quota check and return the OverQuota message already at RCPT TO time. Here is what I typed, connected to the director Connection to director1 2525 port [tcp/*] succeeded! 220 director1.rz.hs-example.de Dovecot (Ubuntu) ready. LHLO mailhub1.rz.hs-example.de 250-director1.rz.hs-example.de 250-8BITMIME 250-ENHANCEDSTATUSCODES 250 PIPELINING MAIL FROM:<hs(a)schlittermann.de> 250 2.1.0 OK RCPT TO:<heiko(a)hs-example.de> 250 2.1.5 OK And here is, what TCPDUMP sees (cut for clarity): 00:22:23.029251 IP6 2001:638:914:f33::5:1.59466 > 2001:638:914:f33::5:ff.2525: Flags [S], 00:22:23.029376 IP6 2001:638:914:f33::5:ff.2525 > 2001:638:914:f33::5:1.59466: Flags [S.], 00:22:23.029660 IP6 2001:638:914:f33::5:1.59466 > 2001:638:914:f33::5:ff.2525: Flags [.], 00:22:23.051436 IP6 2001:638:914:f33::5:ff.2525 > 2001:638:914:f33::5:1.59466: Flags [P.], .7i`.7jN220 backend1.rz.hs-example.de Dovecot (Ubuntu) ready. 00:22:23.051805 IP6 2001:638:914:f33::5:1.59466 > 2001:638:914:f33::5:ff.2525: Flags [.], 00:22:23.052017 IP6 2001:638:914:f33::5:1.59466 > 2001:638:914:f33::5:ff.2525: Flags [P.], .7jT.7i`LHLO director1.rz.hs-example.de 00:22:23.052034 IP6 2001:638:914:f33::5:ff.2525 > 2001:638:914:f33::5:1.59466: Flags [.], 00:22:23.052114 IP6 2001:638:914:f33::5:ff.2525 > 2001:638:914:f33::5:1.59466: Flags [P.], .7ia.7jT250-backend1.rz.hs-example.de 250-XCLIENT ADDR PORT TTL TIMEOUT 250-8BITMIME 250-ENHANCEDSTATUSCODES 250 PIPELINING 00:22:23.052476 IP6 2001:638:914:f33::5:1.59466 > 2001:638:914:f33::5:ff.2525: Flags [P.], 0EH....d...... ..3........ ..8 ..3.........J ..... .7jT.7iaXCLIENT ADDR=2001:638:914:f33::7:1 PORT=60574 TTL=4 TIMEOUT=30 00:22:23.052540 IP6 2001:638:914:f33::5:ff.2525 > 2001:638:914:f33::5:1.59466: Flags [P.], 0EH...E....~e.....3........ ..8 ..3........ ..J .7ia.7jT220 backend1.rz.hs-example.de Dovecot (Ubuntu) ready. 00:22:23.052815 IP6 2001:638:914:f33::5:1.59466 > 2001:638:914:f33::5:ff.2525: Flags [P.], 0E.....s...... ..3........ ..8 ..3.........J ....E .7jT.7iaLHLO director1.rz.hs-example.de 00:22:23.052870 IP6 2001:638:914:f33::5:ff.2525 > 2001:638:914:f33::5:1.59466: Flags [P.], 0E....h....~......3........ ..8 ..3........ ..J .7ia.7jT250-backend1.rz.hs-example.de 250-8BITMIME 250-ENHANCEDSTATUSCODES 250 PIPELINING 00:22:23.053120 IP6 2001:638:914:f33::5:1.59466 > 2001:638:914:f33::5:ff.2525: Flags [P.], 0E.....qJ..... ..3........ ..8 ..3.........J ....h .7jT.7iaMAIL FROM:<hs(a)schlittermann.de> RCPT TO:<heiko(a)hs-example.de> 00:22:23.091824 IP6 2001:638:914:f33::5:ff.2525 > 2001:638:914:f33::5:1.59466: Flags [.], 0E.........~,.....3........ ..8 ..3........ ..J .7ik.7jT 00:22:23.119918 IP6 2001:638:914:f33::5:ff.2525 > 2001:638:914:f33::5:1.59466: Flags [P.], 0E.........~......3........ ..8 ..3........ ..J * .7ir.7jT250 2.1.0 OK * 552 5.2.2 <heiko(a)hs-example.de> Quota exceeded (mailbox for user is full) 00:22:23.158836 IP6 2001:638:914:f33::5:1.59466 > 2001:638:914:f33::5:ff.2525: Flags [.], 0F4....j...... ..3........ ..8 ..3.........J ..... .7jo.7ir 00:27:23.029008 IP6 2001:638:914:f33::5:1.59466 > 2001:638:914:f33::5:ff.2525: Flags [F.], 0F4....E...... ..3........ ..8 ..3.........J ..... It looks as if the backend tells the director/proxy about the full mailbox (552 5.2.2 <heiko(a)hs-example.de> Quota exceeded (mailbox for user is full)) already before the DATA phase starts, right as the response to the RCPT TO. But the proxy seems to ignore it… Any suggestion? Best regards from Dresden/Germany Viele Grüße aus Dresden Heiko Schlittermann -- SCHLITTERMANN.de ---------------------------- internet & unix support - Heiko Schlittermann, Dipl.-Ing. (TU) - {fon,fax}: +49.351.802998{1,3} - gnupg encrypted messages are welcome --------------- key ID: F69376CE - ! key id 7CBF764A and 972EAC9F are revoked since 2015-01 ------------ -

2 3

subscribe users mailbox with non-valid mutf7 chars
by Matthias Lay 16 Mar '16

16 Mar '16

Hi all, I got a question if its possible to subscribe a mailbox from another user, who contains non mutf7 valid chars in his mailbox path. I have a private namespace which can subscribe to mailboxes of a shared namespace with public/ prefix in this example username in private namespace is johnd public username is "a & p products group" when I try the subscription I get this one: ******************************************** # doveadm mailbox subscribe -u johnd "public/a & p products group/INBOX" doveadm(johnd): Error: Can't public/a & p products group/INBOX mailbox subscribe to: Invalid mailbox name 'public/a & p products group/INBOX': Missing namespace prefix 'public/a &- p products group/' ******************************************** is there a way to work around this? (except for not to use usernames like this) greetz matze

1 1