May 2015 - dovecot - dovecot.org

Released Pigeonhole v0.4.8.rc1 for Dovecot v2.2.17.rc1
by Stephan Bosch 12 May '15

12 May '15

Hello Dovecot users, Here's the Pigeonhole RC that goes with the Dovecot RC. It includes a few small fixes and one new feature. Changelog v0.4.8.rc1: * LDA Sieve plugin: Dovecot changed the deliver_log_format setting to include %{delivery_time}. This prompted changes in Pigeonhole that make this release dependent on Dovecot v2.2.17. + Implemented magic to make sieve_default script visible from ManageSieve under a configurable name. This way, users can see the default rules, edit them and store a private adjusted version. This could also be achieved by copying the default script into the user's script storage, but that way updates to the global sieve_default script would be ignored. - Fixed problem in address test: erroneously decoded mime-encoded words in address headers. - extprograms plugin: Fixed failure occurring when connecting to script service without the need to read back the output from the external program. - Fixed bug in script storage path normalization occurring with relative symbolic links below root. - Fixed and updated various parts of the documentation. The release is available as follows: http://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.8.rc1… http://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.8.rc1… Refer to http://pigeonhole.dovecot.org and the Dovecot v2.x wiki for more information. Have fun testing this new release and don't hesitate to notify me when there are any problems. Regards, -- Stephan Bosch stephan(a)rename-it.nl

3 7

Re: Dovecot is not reading connections from iOS devices correctly. Any ideas?
by Joseph Tam 11 May '15

11 May '15

Robert Chalmers writes: > dovecot-info.log > May 11 09:27:45 imap-login: Info: Aborted login (no auth attempts in 0 > secs): user=<>, rip=192.168.0.1, lip=192.168.0.15, > session=<pXcBJ8oVbgDAqAAB> > > When I try to connect using either the iOS Mail app, or Outlook mail > app, nothing happens at al with ssl, and if I use plain login the iOS > device tells me I have either the username or password wrong - which I > haven't. Some mail readers have auto-discover features that are rather stupid. If possible, manually configure the SSL style (TLS/STARTTLS) and port rather than letting it guess. To diagnose whether it is some dovecot config error, you can manually connect with both flavours of SSL openssl s_client -connect 192.168.0.15:993 ... or ... openssl s_client -starttls imap -connect 192.168.0.15:143 then if it gets past the SSL handshake, a login <user> <password> to test the authentication part. This will at least tell you whether it's a client side or server side issue. (However, since it is working with other client, it's probably a client side issue.) Joseph Tam <jtam.home(a)gmail.com>

1 0

v2.2.17 release candidate released
by Timo Sirainen 11 May '15

11 May '15

http://dovecot.org/releases/2.2/rc/dovecot-2.2.17.rc1.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.17.rc1.tar.gz.sig Quite a lot of changes, so here's a release candidate first. If no problems are reported I'll make v2.2.17 release early next week. Please test especially non-Linux systems as there are some larger configure/Makefile changes done since v2.2.16. * Dovecot no longer checks or warns if a mountpoint is removed. This was causing more trouble than it was worth. Make sure that all the mountpoints that Dovecot accesses aren't writable by mail processes when they're unmounted. * dict server wasn't properly escaping/unescaping data. Fixing this broke backwards compatibility with data that contains line feeds. This hopefully affects only very few installations. If you're using dict to save multiline data (Sieve scripts to SQL), you may be affected. * imap: SPECIAL-USE capability is no longer advertised if there are no special_use flags specified for any mailboxes. + lmtp: Added lmtp_hdr_delivery_address setting to specify whether to include email address in Delivered-To: and Received: headers. + Added initial version of full text search library, which includes language-specific text normalization and filtering. This is still in development, but it's already possible to use for testing with fts-lucene and fts-solr. + lda, lmtp: deliver_log_format can now include %{delivery_time}, which expands to how many milliseconds it took to deliver the mail. With LMTP %{session_time} also expands to how many milliseconds the LMTP session took, not including the delivery time. + lmtp proxy: Mail delivery logging includes timing information. + imap: Most IMAP commands now include in the tagged reply how many milliseconds it took to run the command (not counting the time spent on waiting for the IMAP client to read/write data). + director: Implemented director_proxy_maybe passdb extra field to be able to run director and backend in the same Dovecot instance. (LMTP doesn't support mixed proxy/non-proxy destinations currently.) + doveadm: Added -F <file> parameter to read a list of users from the given file and run the command for all the users. This is similar to -A parameter reading the list of users from userdb lookup. - auth: If auth_master_user_separator was set, auth process could be crashed by trying to log in with empty master username. - imap-login, pop3-login: Fixed crash on handshake failures with new OpenSSL versions (v1.0.2) when SSLv3 was disabled. - auth: If one passdb fails allow_nets check, it shouldn't have failed all the other passdb checks later on. - imap: Server METADATA couldn't be accessed - imapc: Fixed \Muted label handling in gmail-migration. - imapc: Various bugfixes and improvements. - Trash plugin fixes by Alexei Gradinari - mbox: Fixed crash/corruption in some situations when the first mail was expunged.

10 17

Released Pigeonhole v0.4.8.rc2 for Dovecot v2.2.17.rc1
by Stephan Bosch 11 May '15

11 May '15

Hello Dovecot users, Ok, RC1 contained one rather stupid bug that caused a segfault at delivery. It was caused by a new feature, so the list of changes is not updated. Changelog v0.4.8: * LDA Sieve plugin: Dovecot changed the deliver_log_format setting to include %{delivery_time}. This prompted changes in Pigeonhole that make this release dependent on Dovecot v2.2.17. + Implemented magic to make sieve_default script visible from ManageSieve under a configurable name. This way, users can see the default rules, edit them and store a private adjusted version. This could also be achieved by copying the default script into the user's script storage, but that way updates to the global sieve_default script would be ignored. - Fixed problem in address test: erroneously decoded mime-encoded words in address headers. - extprograms plugin: Fixed failure occurring when connecting to script service without the need to read back the output from the external program. - Fixed bug in script storage path normalization occurring with relative symbolic links below root. - Fixed and updated various parts of the documentation. The release is available as follows: http://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.8.rc2… http://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.8.rc2… Refer to http://pigeonhole.dovecot.org and the Dovecot v2.x wiki for more information. Have fun testing this new release and don't hesitate to notify me when there are any problems. Regards, -- Stephan Bosch stephan(a)rename-it.nl

1 0

Bug#776094: dovecot-imapd: corrupts mailbox after trying to retrieve it (fwd)
by Santiago Vila 11 May '15

11 May '15

Hello. I wrote about this three weeks ago but got no answer. I'm going to officially "forward" the Debian bug this time, with all the details. The test case is just 840 bytes long. Please give it a try. ---------- Forwarded message ---------- From: Santiago Vila <sanvila(a)unex.es> To: submit(a)bugs.debian.org Date: Fri, 23 Jan 2015 22:32:28 +0100 (CET) Subject: dovecot-imapd: corrupts mailbox after trying to retrieve it Package: dovecot-imapd Version: 1:2.2.13-11 Severity: serious The following mbox folder, when put in $HOME/mail, becomes corrupted after trying to retrieve it with fetchmail. The problem may be reproduced by using the same machine as server and client: * Put "inbox-b" in $HOME/mail * Put this in $HOME/.fetchmailrc server localhost proto imap port 143: user "someuser" pass "thepassword" * Retrieve email using this command line: fetchmail -a localhost --folder inbox-b -m "true" Note: By looking at the "true" above it is clear that whatever fetchmail does with the message is not important at all. You will see something like this: 12 messages for someuser at localhost (folder inbox-b). reading message someuser@localhost:1 of 12 (171 header octets) (3 body octets) flushed reading message someuser@localhost:2 of 12 (245 header octets) (3 body octets) flushed reading message someuser@localhost:3 of 12 (245 header octets) (3 body octets) flushed reading message someuser@localhost:4 of 12 (245 header octets) (3 body octets) flushed reading message someuser@localhost:5 of 12 (245 header octets) (3 body octets) flushed reading message someuser@localhost:6 of 12 (171 header octets) (3 body octets) flushed reading message someuser@localhost:7 of 12 (171 header octets) (3 body octets) flushed reading message someuser@localhost:8 of 12 (245 header octets) (3 body octets) flushed reading message someuser@localhost:9 of 12 (245 header octets) (3 body octets) flushed reading message someuser@localhost:10 of 12 (245 header octets) (3 body octets) flushed reading message someuser@localhost:11 of 12 (245 header octets) (3 body octets) flushed reading message someuser@localhost:12 of 12 (273 header octets)fetchmail: incorrect header line found - see manpage for bad-header option not flushed And in fact "inbox-b" in the server is now like this: [...] >From root(a)example.com Tue Jan 13 10:18:20 2015 rstuvwxyzabcdefghijklmnopqrstuvwxyz(a)example.com To: a(a)example.com Subject: a MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Message-Id: <20150113091737.B5ADA5F8B1(a)example.com> Date: Tue, 13 Jan 2015 10:17:25 +0100 (CET) X-UID: 16035 Status: O a Note how the From: line has been truncated from its original state. I have been suffering from this problem for months. At first I believed it was some misbehaving procmail/formail recipe I had on the server, but that's not the case as this example shows. Thanks.

6 23

Dovecot is not reading connections from iOS devices correctly. Any ideas?
by Robert Chalmers 11 May '15

11 May '15

From the dovecot logs. dovecot-info.log May 11 09:27:45 imap-login: Info: Aborted login (no auth attempts in 0 secs): user=<>, rip=192.168.0.1, lip=192.168.0.15, session=<pXcBJ8oVbgDAqAAB> dovecot-debug.log May 11 09:27:45 auth: Debug: auth client connected (pid=17388) When I try to connect using either the iOS Mail app, or Outlook mail app, nothing happens at al with ssl, and if I use plain login the iOS device tells me I have either the username or password wrong - which I haven't. Connection from Mac with MailMate works fine. iOS doesn't. so I'm stumped. I can't see why this is refusing the connection.

1 0

What is this message in appfirewall.log telling me ? on OSX
by Robert Chalmers 11 May '15

11 May '15

I'm on OS X What is this telling me? socketfilterfw[22097] <Info>: dovecot: Deny TCP CONNECT (in:7 out:0) Thanks Robert

2 3

Cant use doveadm to set ACL . [request for help]
by Kevin Laurie 11 May '15

11 May '15

Hi, i keep getting error for using doveadm acl get commands. Below is the output for grep 'socket_path' :- grep 'socket_path' /etc/dovecot/dovecot.conf auth_socket_path = /var/run/dovecot/auth-master auth_socket_path = /var/run/dovecot/auth-master [root@mail root]# doveadm acl get -u bob(a)mydomain.net -S /var/run/dovecot/auth-master -m Inbox doveadm(bob(a)mydomain.net): Error: doveadm server sent invalid handshake: VERSION 1 1 doveadm(bob(a)mydomain.net): Error: /var/run/dovecot/auth-master: Internal failure for bob(a)mydomain.net ID Global Rights

2 1

New York: Matilda, seit Jahren mit dem immer gleichen Outfit - DIE WELT
by Michael Grimm 10 May '15

10 May '15

Cool, und vor allem gut! > http://www.welt.de/vermischtes/article140736122/Matilda-seit-Jahren-mit-dem… <http://www.welt.de/vermischtes/article140736122/Matilda-seit-Jahren-mit-dem…>

1 1

Xi broken
by Stephan Bosch 10 May '15

10 May '15

Hi, Xi is broken at the moment. This XenServer version won't boot jessie kernel. Can't fix this myself, so this may take some time. Regards, Stephan.

4 5