similar to: Released Pigeonhole v0.4.11 for Dovecot v2.2.21

Displaying 20 results from an estimated 1000 matches similar to: "Released Pigeonhole v0.4.11 for Dovecot v2.2.21"

2019 May 06
2
Question about GIT repository
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
2019 May 06
2
Question about GIT repository
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
2019 May 06
0
Question about GIT repository
On 6 May 2019, at 02:28, Juan C. Blanco via dovecot <dovecot at dovecot.org> wrote: > +-------------------------------------------------------------------+ > | Juan C. Blanco | > | | > | Centro de Calculo | | > |
2018 May 30
2
Fatal: nfs flush requires mail_fsync=always
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
2007 Dec 11
2
quota_wrning not working for me (quota_rewrite patch for dovecot 1.0.8)
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"
2016 Mar 30
3
Pigeonhole 0.4.13 does not compile against dovecot 2.2.23
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
2016 Jul 01
2
v2.2.25 released
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
2016 Jan 08
0
Released Pigeonhole v0.4.11 for Dovecot v2.2.21
Hello Dovecot users, Here is the final v0.4.11 release of Pigeonhole for Dovecot v2.2.21. Nothing of consequence changed since the RC. Changelog v0.4.11: - Sieve mime extension: Fixed the header :mime :anychild test to work properly outside a foreverypart loop. - Several fixes in message body part handling: - Fixed assert failure occurring when text extraction is attempted on an empty
2016 Jan 08
0
Released Pigeonhole v0.4.11 for Dovecot v2.2.21
Hello Dovecot users, Here is the final v0.4.11 release of Pigeonhole for Dovecot v2.2.21. Nothing of consequence changed since the RC. Changelog v0.4.11: - Sieve mime extension: Fixed the header :mime :anychild test to work properly outside a foreverypart loop. - Several fixes in message body part handling: - Fixed assert failure occurring when text extraction is attempted on an empty
2016 Jan 04
0
Released Pigeonhole v0.4.11.rc1 for Dovecot v2.2.21
Hello Dovecot users, First, a happy new year to you all! :) In the last few weeks I got quite a few bug reports. I also found a few things myself. Some of the bugs are quite annoying, so a new release is necessary. First, I release RC1. If all is well, I'll release the definitive Pigeonhole v0.4.11 within the next few days. Changelog v0.4.11: - Sieve mime extension: Fixed the header :mime
2016 Jan 04
0
Released Pigeonhole v0.4.11.rc1 for Dovecot v2.2.21
Hello Dovecot users, First, a happy new year to you all! :) In the last few weeks I got quite a few bug reports. I also found a few things myself. Some of the bugs are quite annoying, so a new release is necessary. First, I release RC1. If all is well, I'll release the definitive Pigeonhole v0.4.11 within the next few days. Changelog v0.4.11: - Sieve mime extension: Fixed the header :mime
2018 May 30
0
Fatal: nfs flush requires mail_fsync=always
This fix is part of next release. ---Aki TuomiDovecot oy -------- Original message --------From: "Juan C. Blanco" <jcblanco at fi.upm.es> Date: 30/05/2018 19:31 (GMT+02:00) To: Dovecot Mailing List <dovecot at dovecot.org> Subject: Re: Fatal: nfs flush requires mail_fsync=always Hello, any news about the attached error? I'm preparing the 2.2 to 2.3 upgrade and
2019 May 06
0
Question about GIT repository
<!doctype html> <html> <head> <meta charset="UTF-8"> </head> <body> <div> Hi , </div> <div> <br> </div> <div> sorry they were accidentically not pushed. Will do so soon. </div> <div> <br> </div> <div> Aki </div> <blockquote
2011 Apr 15
0
Problem login in managesieve with email address
Hello all, I have a installation of dovecot 1.2.16, sieve-0.1.18, managesieve-0.11.12 in dovecot-ldap.conf auth_bind=yes user_attrs = irisMailbox=home,fiMailQuotaSize=quota_rule=*:storage user_filter = (|(uid=%u)(mail=%u)) pass_attrs = userPassword=password,irisMailbox=userdb_home,fiMailQuotaSize=userdb_quota_rule=*:storage pass_filter = (|(uid=%u)(mail=%u)) I'm doing some test to
2016 Jun 30
3
v2.2.25 release candidate released
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..
2008 Jun 09
1
v1.1.rc9 released
http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc9.tar.gz http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc9.tar.gz.sig Not many bug reports these last few days, so maybe this release will be a good one. + Maildir: When hardlink-copying a file, copy the W=<vsize> in the filename if it exists in the original filename. - mbox: With rc8 empty lines were inserted in the middle of saved
2008 Jun 09
1
v1.1.rc9 released
http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc9.tar.gz http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc9.tar.gz.sig Not many bug reports these last few days, so maybe this release will be a good one. + Maildir: When hardlink-copying a file, copy the W=<vsize> in the filename if it exists in the original filename. - mbox: With rc8 empty lines were inserted in the middle of saved
2014 Feb 07
1
Problem rebuilding Centos 5/6 pigeonhole RPM from mercurial version
Hi Stephan, I'm traying to rebuild the RH (Centos) EL5 and EL6 RPM with the last mercurial pigeonhole 0.4.2 version, but I'm having problems with the build. I think that I've isolated the problem outside rpmbuild context. I've downloaded dovecot and pigeonhole mercurial versions and built dovecot with the commands: dovecot-2.2.10$ ./autogen.sh dovecot-2.2.10$ ./configure
2009 Feb 12
2
(Somewhat urgent) Problem with maildir++ quota
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
2019 Mar 08
1
Dovecot v2.3.5 released
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