similar to: 1.0.rc32 released

http://dovecot.org/releases/dovecot-1.0.rc32.tar.gz http://dovecot.org/releases/dovecot-1.0.rc32.tar.gz.sig Pretty late for changes if v1.0 is supposed to come out tomorrow, but I can't really leave these LDAP bugs unfixed. They shouldn't anyway break anything, so here's one more day for you people to find out about any bugs. One thing that I'm a bit concerned about is the

http://dovecot.org/releases/2.2/dovecot-2.2.10.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.10.tar.gz.sig I've been really busy the last few months, as I guess people in Dovecot mailing list have seen since I haven't been very responsive. There are at least some dsync bugs I haven't had time to look into yet. The busyness probably continues for a while more, but the next year is

http://dovecot.org/releases/dovecot-1.0.rc11.tar.gz http://dovecot.org/releases/dovecot-1.0.rc11.tar.gz.sig Hopefully the last RC release? As far as I know there are no major problems left now. If nothing big shows up, v1.0 should be out in a couple of weeks. * Renamed default_mail_env to mail_location. default_mail_env still works for backwards compatibility. * deliver: When sending

Hi List Looks like OpenLDAP 2.3 doesn't define LDAP_DEPRECATED [1] anymore which causes a few warnings in Gentoo [2]. Attached is a patch that re-defines this so that dovecot can continue using simple functions like ldap_bind(). Thanks Roy [1] http://www.mail-archive.com/openldap-devel at openldap.org/msg00487.html [2] http://bugs.gentoo.org/show_bug.cgi?id=162437 -------------- next

http://dovecot.org/releases/2.2/dovecot-2.2.10.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.10.tar.gz.sig I've been really busy the last few months, as I guess people in Dovecot mailing list have seen since I haven't been very responsive. There are at least some dsync bugs I haven't had time to look into yet. The busyness probably continues for a while more, but the next year is

http://dovecot.org/releases/dovecot-1.0.rc18.tar.gz http://dovecot.org/releases/dovecot-1.0.rc18.tar.gz.sig I think we're quite near v1.0 now. * ACL plugin + Maildir: Moved dovecot-acl file from control directory to maildir. To prevent accidents caused by this change, Dovecot kills itself if it finds dovecot-acl file from the control directory. * When opening a maildir, check if

I've noticed that if a user's maildir gets created by deliver or pop/imap without the convert plugin running, the maildir structure is fine (no maildirfolder file). But, if a user gets converted, there is a maildirfolder file in the user's base maildir directory. As far as I can tell, that doesn't cause any problems, but I just wanted to mention it. I've looked at the code

The git master branch starts tracking Dovecot v2.3 development from now on. There are soon going to be several API changes there that might break plugins. If you wish to keep tracking latest v2.2.x development instead, switch to master-2.2 branch. The nightly releases at http://dovecot.org/nightly/ will also track v2.3 tree.

Hello Dovecot users, Here is the Pigeonhole release candidate that goes with the Dovecot v2.3 release candidate. Of course, a large part of this release consists of compatibility changes for Dovecot v2.3. Apart from that, not much changed, just a few additions and fixes that accumulated over the last few months. Most of these changes will be back-ported to Pigeonhole v0.4, but that release will

Hello, I need some guidance with setting up a public namespace with per-user \Seen flags. What I want to do is that a group of users access the public namespaces and if user A reads a message, user B should still see it as new until he reads it himself. This is not happening now, and I can't figure out why. Here's the config: # 1.2.9: /etc/dovecot/dovecot.conf # OS: Linux

Am 12.02.2015 um 15:47 schrieb Martin ?tefany: > Hello, > > I've ran into problem with Dovecot and dsync replication. Everything > works perfectly, including replication of sieve scripts, except fact > that if user activates the 'managesieve' ruleset (I'm using currently > Roundcubemail) on "mail1" host, it wouldn't be activated on

Somehow I doubt there are any Dovecot setups left that unknowingly have this problem, but it still counts as a security hole. The possibility to cause this problem exists in Dovecot v1.0.rc11 and later. If you use: 1. passdb ldap with settings: - auth_bind = yes - auth_bind_userdn = no - base containing %variables required for unique user identification, e.g. base = dc=%d,dc=org -

Hello, I've ran into problem with Dovecot and dsync replication. Everything works perfectly, including replication of sieve scripts, except fact that if user activates the 'managesieve' ruleset (I'm using currently Roundcubemail) on "mail1" host, it wouldn't be activated on "mail2" host, by creating symlink ".dovecot.sieve ->

Hi, I'm using version 1.0.13 of dovecot. I know it's somewhat dated, but that's the latest that Debian etch offers, and I would like to avoid compiling by myself if possible. dovecot is not creating the 'maildirfolder' in folders that are created via IMAP. Looking at the NEWS file, this was implemented in v1.0.rc7, so my version should have that working already. Is

http://dovecot.org/releases/dovecot-1.0.rc7.tar.gz http://dovecot.org/releases/dovecot-1.0.rc7.tar.gz.sig Can everyone now agree that there are no more hangs? :) * Require that Dovecot master process's version number matches the child process's, unless version_ignore=yes. Usually it's an accidental installation problem if the version numbers don't match. * Maildir: Create

Hi, Currently using dovecot 2.3.2.1 and pigeonhole 0.5.2 on two identical hosts. I recently noticed ".dovecot.sieve" and ".sieve/managesieve.sieve" are not replicating from one host to the other in either direction. Mail is having no trouble replicating on both hosts with dsync, it is only sieve files that are not replicating for unclear reasons. # doveconf -n host 1:

Hi, I have configured dovecot for auth_bind against an LDAP server on the localhost and I'm seeing the following error in my dovecot logs: dovecot: Apr 30 09:03:18 Error: auth(default): LDAP: ldap_result() failed: Can't contact LDAP server dovecot: Apr 30 09:03:27 Error: auth(default): LDAP: ldap_result() failed: Can't contact LDAP server ... and so on ... When I turned on LDAP

On 1/6/2016 3:29 PM, Timo Sirainen wrote: > On 05 Jan 2016, at 15:36, Bill Shirley <Bill at knoxvillechristian.org> wrote: >> >> [0:root at elmo ~]$ rpm -q dovecot >> dovecot-2.2.18-2.fc22.x86_64 >> >> I got a surprise today when I tried the doveadm search function from: >> http://wiki2.dovecot.org/Plugins/Expire >> >> [0:root at elmo ~]$

Hi folks. I was doing some testing this morning and realized Dovecot RC2 isn't fully compliant with the maildir++ specification. Most notably, it appears that Dovecot isn't creating a "maildirfolder" file (0 byte length) in folders it creates. >From http://www.inter7.com/courierimap/README.maildirquota.html "Within each subdirectory there's an empty file,

http://dovecot.org/releases/dovecot-1.0.rc11.tar.gz http://dovecot.org/releases/dovecot-1.0.rc11.tar.gz.sig Hopefully the last RC release? As far as I know there are no major problems left now. If nothing big shows up, v1.0 should be out in a couple of weeks. * Renamed default_mail_env to mail_location. default_mail_env still works for backwards compatibility. * deliver: When sending