- dovecot - dovecot.org

Pigeonhole v0.4.8.rc3 compilation error (bad mail-deliver.h)
by Jacques Distler 14 May '15

14 May '15

Got a /usr/local/include/dovecot/mail-deliver.h:30:17: error: field has incomplete type 'struct timeval' struct timeval delivery_time_started; ^ error. This is because mail-deliver.h in dovecot-2.2.17 is missing an #include <sys/time.h> Adding that line to mail-deliver.h fixes the problem. Oddly, I had no problem compiling dovecot itself.

2 1

v2.2.17 released
by Timo Sirainen 14 May '15

14 May '15

http://dovecot.org/releases/2.2/dovecot-2.2.17.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.17.tar.gz.sig A few director improvements since RC2, some fixes and a new plugin: http://wiki2.dovecot.org/Plugins/QuotaClone * 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. + Implemented initial Cassandra CQL support as lib-sql backend. It's only usable as dict backend currently. + Added quota-clone plugin to copy current quota usage to a dict. - 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

2 1

Released Pigeonhole v0.4.8.rc3 for Dovecot v2.2.17
by Stephan Bosch 14 May '15

14 May '15

Hello Dovecot users, RC2 had one more important bug caused by the new sieve_default_name feature. To prevent causing more of such rather stupid bugs in the future, I created an external shell-based test suite to test dovecot-lda delivery, the doveadm sieve tools and ManageSieve. These kind of tests aren't possible with the current Sieve-based test suite that is included in the Pigeonhole tarball. Now I can test most basic top-level Pigeonhole functionality in one go. Additionally, I created one new feature for ManageSieve. It allows logging various statistics at client disconnect, much like POP3 currently supports. This is e.g. useful for debugging. In the process, I fixed a few ManageSieve bugs as well. If RC3 doesn't cause any more issues, I will release 0.4.8 this Friday. Changelog v0.4.8 (updated): * 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 updates to the global sieve_default script would be ignored that way. + ManageSieve: Implemented support for reporting command statistics at disconnect. Statistics include the number of bytes and scripts uploaded/downloaded/checked and the number of scripts deleted/renamed. - 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 - ManageSieve: Used "managesieve" rather than "sieve" as login service name, which means that all managesieve-specific settings where ignored. - Managesieve: Storage quota was not always enforced properly for scripts uploaded as quoted string. Nobody uses that, but it is allowed in the specification and we support it, so it should work properly. The release is available as follows: http://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.8.rc3… http://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.8.rc3… 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

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

13 May '15

http://dovecot.org/releases/2.2/rc/dovecot-2.2.17.rc2.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.17.rc2.tar.gz.sig Changes since rc1: - Compiling fix for fs-compress in Solaris and maybe others. - Implemented Cassandra CQL support as lib-sql backend. This is mainly usable as dict-sql backend. - lib-fts fixes and improvements - Some other small random changes If no new issues are found, v2.2.17 final should be out in a day or two. (Actually looks like I have a few more bugs that probably will be fixed for it.) Changes 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. + Implemented initial Cassandra CQL support as lib-sql backend. It's only usable as dict backend currently. - 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.

2 3

dovecot-lda panics when postmaster_address is given on command line
by Onno Molenkamp 13 May '15

13 May '15

Hi, When passing a postmaster_address to dovecot-lda on the command line with -o, it panics: $ ./dovecot-lda -o postmaster_address=anything lda(onno,)Panic: file lda-settings.c: line 80 (lda_settings_check): assertion failed: (set->postmaster_address[0] == SETTING_STRVAR_UNEXPANDED[0]) It looks like postmaster_address has already been expanded at that point when it's given on the command line. (set->postmaster_address[0] is "1") I'm running v2.2.15, but with v2.2.17.rc1 the same thing happens. Regards, Onno

2 1

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 12 May '15

12 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