similar to: Pigeonhole 0.4.20 source archive based on v. 0.4.20-rc1?

Op 8/31/2017 om 1:25 PM schreef Markus Sch?nhaber: > Hi, > > looking at the source archive of pigeonhole 0.4.20 > <https://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.20.tar.gz> > I noticed that the contained ChangeLog mentions v0.4.20.rc1 as first > entry and pigeonhole-version.h defines git revision 7cd71ba as version > where I'd expect 4a55e6c.

Hello Dovecot users, Here's the definitive 0.4.20 release. There were no changes since the release candidate. Changelog v0.4.20: + Made the retention period for redirect duplicate identifiers configurable. For accounts that perform many redirects, the lda-dupes database could grow to impractical sizes. Changed the default retention period from 24 to 12 hours. - sieve-filter: Fixed

Hello Dovecot users, Here's the definitive 0.4.20 release. There were no changes since the release candidate. Changelog v0.4.20: + Made the retention period for redirect duplicate identifiers configurable. For accounts that perform many redirects, the lda-dupes database could grow to impractical sizes. Changed the default retention period from 24 to 12 hours. - sieve-filter: Fixed

Hello Dovecot users, Here's a release candidate for a quick Pigeonhole release, mostly containing fixes. One fix addresses a problem caused by the previous release. Changelog v0.4.20: + Made the retention period for redirect duplicate identifiers configurable. For accounts that perform many redirects, the lda-dupes database could grow to impractical sizes. Changed the default

Hello Dovecot users, Here's a release candidate for a quick Pigeonhole release, mostly containing fixes. One fix addresses a problem caused by the previous release. Changelog v0.4.20: + Made the retention period for redirect duplicate identifiers configurable. For accounts that perform many redirects, the lda-dupes database could grow to impractical sizes. Changed the default

Hi, at the moment I see only packages named *2.2.26* on xi.dovecot.fi. Can we expect packages for v2.2.27 to appear there? -- Regards mks

Aki Tuomi, Fri, 02 Mar 2018 20:06:35 +0200: > the problem is default > ?protocols = imap pop3? Ah, OK. I wasn't aware that the default had changed. It seems to be protocols = imap pop3 lmtp now. > packaging should use > protocols = > protocols = $protocols imap Yep, explicitly setting protocols = before !include_try /usr/share/dovecot/protocols.d/*.protocol helps. IMO

Hi i have a problem compiling as mantioned on object of this mail: i'm changing dovecot on my debian 6 from version 2.2.32 to 2.2.36 and pigeonhole from 0.4.20 to 0.4.24 this is output of dovecot -n for listing versions installed dovecot -n # 2.2.32 (dfbe293d4): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.4.20 (7cd71ba) # OS: Linux 2.6.32-5-amd64 x86_64 Debian 6.0.10 i have

Hi, i have Dovecot Director and Dovecot Backends with 2.2.32. i have found a email that my web server send with only one character "=" in the body of the email and it generate a log error in Dovecot log like this: Oct 23 13:16:50 dovecot_2.2.32 dovecot: imap(user at domain): Panic: file index-mail-binary.c: line 358 (blocks_count_lines): assertion failed: (block_count == 0 ||

Stephan Bosch, Mon, 25 Apr 2016 15:16:55 +0200: > Oops. Turned off package composer for maintenance, but didn't turn it > back on. > > It is building now..... Is there something to turn on to build packages in /debian/pool/wheezy-auto/dovecot-2.2 ? Or don't you provide packages for wheezy anymore? > Op 25-4-2016 om 14:47 schreef Harald Leithner: >> Hi, >>

There is some underlying problem with imap-login but in order to debug it I'd like to see a core file. On error dovecot reports "core not dumped". If I put "abort()" in the code at the point it is reporting then a core file is written, so there is no OS reason why a core can not be written. It appears to be dovecot's choice to control the child. In an attempt

Hi! We are pleased to release Pigeonhole release v0.4.24.2 Tarball is available at https://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.24.2.tar.gz https://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.24.2.tar.gz.sig Changes ------- * CVE-2019-11500: ManageSieve protocol parser does not properly handle NUL byte ? when scanning data in quoted strings, leading

Aki Tuomi <aki.tuomi at dovecot.fi> writes: > On 24 February 2018 at 12:45 Neil Jerram < neil at ossau.homelinux.net> wrote: > > Please could you help me to understand and fix why my dovecot IMAP > performance is so bad? I've read through a lot of the > performance-related material on the website, but I don't think that any > of it could account for

Hi, This (hopefully!) might be a case of user error, as I'm new to dovecot... Alternatively it might be some confusion in an index, since I've been mucking about trying different things in my configuration files and had frequent crashes. I'm trying to sync 2 (LAN) hosts, ideally to have full automatic replication happening. They both have hybrid mbox INBOX and maildir++ folders,

Very minor bug; not specifying the user mask with 'doveadm replicator replicate -f' causes a segfault: server:~# doveadm replicator replicate -f Segmentation fault server:~# doveadm replicator replicate -f '*' 123 users updated server:~# gdb /usr/bin/doveadm core.2418 GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-100.el7 This GDB was configured as

Dear Dovecot and community, We run a small email service for our customers, based on two machines that are made ?redundant or clustered? by using the replication feature of Dovecot. This works well, for most emails. Sometimes the following happends: Email to our support database arrives at the inbox. Every period a cronjob looks into that mailbox and parses the information and makes a support

Hello, given a Debian 9 system with Dovecot 2.2.34 installed from self-built packages made from the official tarball combined with Stephan Bosch's debian files (upgraded multiple times from packages made in a similar way). Today, I updated this system to 2.3.0.1 from the official repository at repo.dovecot.org. After the update, dovecot wouldn't start because of: > dovecot: master:

Maybe you could not delete the message instantly, but keep track of last seen UID. UIDs increase monotonically, so you can rest assured that next arriving email has larger UID. Then you can bulk delete mails that are older than one day. Aki > On October 20, 2017 at 8:01 PM Remko Lodder <remko at FreeBSD.org> wrote: > > > Hi, > > Anyone has suggestions? The situation

Hello, I'm trying to get dovecot to listen on specific interfaces. On the server itself I've got webmail going so am needing imap on 143. I do not want this on the external server interface, so I am wanting imaps port 993 external only. The configuration looks right, but Dovecot isn't showing anything listening on port 993 at all. Unrelated, my public and shared folders are not

Yep On 10.08.2018 11:06, davide marchi wrote: > Thanks Aki for your quick response!! I'm sorry, so i have to compile > and install dovecot version 2.2.36 before compiling and install > pigeonhole 0.4.24? If so sorry for my noob approach > > Il giorno ven 10 ago 2018 alle ore 09:55 Aki Tuomi > <aki.tuomi at dovecot.fi <mailto:aki.tuomi at dovecot.fi>> ha scritto: