similar to: v1.1.rc9 released

Hello, just a question, I can't see a core "release-2.3.6" branch, nor a pigeonhole "release-0.5.6" branch on the GIT repository, it is outdated? or do you have changed your policy to create a new branch for each new release of dovecot and pigeonhole? Thanks and regards -- +-------------------------------------------------------------------+ | Juan C. Blanco

OK, thanks!! Juan C. Blanco On 06/05/2019 10:25, Aki Tuomi wrote: > Hi , > > sorry they were accidentically not pushed. Will do so soon. > > Aki >> On 6 May 2019 11:11 Juan C. Blanco via dovecot < dovecot at dovecot.org >> <mailto:dovecot at dovecot.org>> wrote: >> >> >> Hello, just a question, I can't see a core

Hello Stephan. > The release is available as follows: > > http://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.11.tar.gz > http://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.11.tar.gz.sig http://pigeonhole.dovecot.org/ seems to be down, right? Regards Juan C. > > Refer to http://pigeonhole.dovecot.org and the Dovecot v2.x wiki for > more

Hello, any news about the attached error? I'm preparing the 2.2 to 2.3 upgrade and having the same error. We have the mail stores in an NFS filer. Regards > On 19.01.2018 11:55, S?ren Skou wrote: >> Hiya all, >> >> I'm seeing this "Fatal: nfs flush requires mail_fsync=always" error on >> my testbed. The issue is that from what I can see, mail_fsync

On 01 Jul 2016, at 19:09, Juan C. Blanco <jcblanco at fi.upm.es> wrote: > > I Haven't had the time to check the sha1.h error with the new fixes but I've just done so after de 2.2.25 release was out and I'm having the same error: > > gcc -DHAVE_CONFIG_H -I. -I. -I../.. -std=gnu99 -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector

Hello, We are using dovecot 1.0.8 with LDAP authentication and extra variebles (like quota limit) storage. Since some of our users are asking for warning of quota use I have been playing around with the quota rewrite patch for dovecot 1.0.8 and found that it does not work for us as it is now. I've applied the patch recompiled dovecot reconfigured using the new "quota_warning"

On 30 Jun 2016, at 17:26, Odhiambo Washington <odhiambo at gmail.com> wrote: > > FreeBSD 9.3-STABLE FreeBSD 9.3-STABLE amd64: > > sha1.h:80: error: static or type qualifiers in abstract declarator What gcc version is this? It should have been valid C99 code, so I expected it to work without any special version checks..

Hi. I have an strange problem with dovecot's maildir quota and postfix. I've tested quota and it works fine but sometimes there are users that having their Maildir/ empty, they trigger the "quota exceeded" message when someone sends email to them. Some config / version info: ### Versions: ii dovecot-common 1:1.0.10-1ubuntu5.1 ii dovecot-imapd

http://dovecot.org/releases/dovecot-1.0.rc9.tar.gz http://dovecot.org/releases/dovecot-1.0.rc9.tar.gz.sig Most importantly this should fix the login process problems that people have been reporting. There were also some bugs in the proxying feature. Also note the 64bit change in dovecot.index.cache files. Unless you delete dovecot.index.cache files manually, you'll these kind of error

http://dovecot.org/releases/dovecot-1.0.rc9.tar.gz http://dovecot.org/releases/dovecot-1.0.rc9.tar.gz.sig Most importantly this should fix the login process problems that people have been reporting. There were also some bugs in the proxying feature. Also note the 64bit change in dovecot.index.cache files. Unless you delete dovecot.index.cache files manually, you'll these kind of error

I get the following error after patching the 1.0.8 src.rpm with the quota-rewrite-1.0.8.diff [root at test dovecot]# /etc/rc.d/init.d/dovecot start Starting Dovecot Imap: Edlopen(/usr/lib/dovecot/imap/lib02_imap_quota_plugin.so) failed: /usr/lib/dovecot/imap/lib02_imap_quota_plugin.so: undefined symbol: quota_set FCouldn't load required plugins Error: imap dump-capability process returned 89

Having tried and failed to get 1.0.8 with quota-rewrite to send warnings, I removed the 1.0.8 and installed the latest 1.1 - however I still can't get the warnings! Can someone advise what might be wrong - it must be my configuration?? To compile 1.1 I used ./configure --with-deliver --with-mysql. I've chopped and changed my conf till I'm blue in the face. My dovecot-mysql.conf file

Hello Dovecot users, There haven't been that many Pigeonhole developments lately, not even really significant bugs were reported. That is why this release is pretty small in terms of changes. However, one issue got some attention: the fact that not recompiling Pigeonhole for Dovecot v2.0.3 would result in rather interesting message delivery. Normally, Dovecot would complain about a

Hello Dovecot users, There haven't been that many Pigeonhole developments lately, not even really significant bugs were reported. That is why this release is pretty small in terms of changes. However, one issue got some attention: the fact that not recompiling Pigeonhole for Dovecot v2.0.3 would result in rather interesting message delivery. Normally, Dovecot would complain about a

I just had a thought. It's probably going to be too big of a change for v2.0, so something to think about for v3.0: Supporting multiple UIDs is difficult. Currently expire-tool and v2.0's LMTP server are implemented in a way that it's always running as root and only temporarily dropping privileges. So any security hole in there gives the attacker root privileges. Not very

Hello, I supose that a new version of pigeonhole is on the way because version 0.4.13 does not compile against dovecot 2.2.23 This is the error that I get gcc -DHAVE_CONFIG_H -I. -I. -I../../.. -I../../.. -I../../../src/lib-sieve -I../../../src/lib-sieve/util -I../../../src/lib-sieve/plugins/environment -I/home/jc/rpmbuild/BUILD/dovecot-2.2.23/src/imap

http://dovecot.org/releases/2.2/dovecot-2.2.25.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.25.tar.gz.sig Some minor fixes and (mainly logging) improvements since rc1. * lmtp: Start tracking lmtp_user_concurrency_limit and reject already at RCPT TO stage. This avoids MTA unnecessarily completing DATA only to get an error. * doveadm: Previously only mail settings were read from

http://dovecot.org/releases/2.2/dovecot-2.2.25.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.25.tar.gz.sig Some minor fixes and (mainly logging) improvements since rc1. * lmtp: Start tracking lmtp_user_concurrency_limit and reject already at RCPT TO stage. This avoids MTA unnecessarily completing DATA only to get an error. * doveadm: Previously only mail settings were read from

On 7.3.2019 23.37, A. Schulze via dovecot wrote: > > Am 07.03.19 um 17:33 schrieb Aki Tuomi via dovecot: > >>> test-http-client-errors.c:2989: Assert failed: FALSE >>> connection timed out ................................................. : FAILED > Hello Aki, > >> Are you running with valgrind or on really slow system? > I'm not aware my buildsystem

Hi This happens when email is copied/moved from the inbox to another folder on the same imap account. The mail client goes into a loop with the below errors logged. This is on a 64bit Linux machine using the Maildir storage format. After doing a 'rm dovecot*' from the Maildir folder of the account having the problem the client can log in again but if the client tries to copy again it