similar to: Released Pigeonhole v0.4.7.rc1 for Dovecot v2.2.16.rc1

Hi Stephan, I'm running the current stable version (Dovecot 2.2.15 and Pigeonhole 0.4.6), all works fine except an issue. In my configuration I have this default sieve script (I'm using Maildir): === require ["vnd.dovecot.duplicate", "fileinto", "mailbox"]; if header :matches "X-Spam-Status" "Yes, *" { fileinto

On 10 Mar 2015, at 10:26, Alessio Cecchi <alessio at skye.it> wrote: > > Hi Stephan, > > I'm running the current stable version (Dovecot 2.2.15 and Pigeonhole 0.4.6), all works fine except an issue. > > Feb 16 03:23:41 mx03 dovecot: lda(user at domain.com): Panic: file mail-transaction-log.c: line 271 (mail_transaction_log_rotate): assertion failed: (file->locked)

Hello Dovecot users, Here is the final 0.4.7 release. No changes were committed since the last release candidate. Changelog v0.4.7: * editheader extension: Made protection against addition and deletion of headers configurable separately. Also, the `Received' and `Auto-Submitted' headers are no longer protected against addition by default. * Turned message envelope address parse

Hello Dovecot users, Here is the final 0.4.7 release. No changes were committed since the last release candidate. Changelog v0.4.7: * editheader extension: Made protection against addition and deletion of headers configurable separately. Also, the `Received' and `Auto-Submitted' headers are no longer protected against addition by default. * Turned message envelope address parse

Hello Dovecot users, The rc2 release had a couple of new, rather small, but very annoying bugs. First of all, the path for a file storage wasn't actually normalized, due to a stupid last-minute change before the release. This caused the personal script to be skipped with a warning when there were e.g. duplicate slashes in the path. Second, due to recent changes, the file storage would

Hello Dovecot users, The rc2 release had a couple of new, rather small, but very annoying bugs. First of all, the path for a file storage wasn't actually normalized, due to a stupid last-minute change before the release. This caused the personal script to be skipped with a warning when there were e.g. duplicate slashes in the path. Second, due to recent changes, the file storage would

> Last time I had a few stupid problems in the releases, so > I'll follow > Timo's example and I release an RC first. > > The highlights include the implementation of the index and > metadata > extensions. Quite a few bugs are fixed as well. When I compiled and installed this, Sieve scripts were being ignored. Not sure if it's my own stupid mistake, but when I

> > > However, I do see that Sieve was accessing the user home directory > > > because for some reason now it just created a ".pki" directory > > > therein, which inside of it has an empty "nssdb" directory. That > > > never happened before...? Not a big problem, but I'd prefer not > > > to have that there. > > > >

Hej folks, Today I upgraded from Dovecot 2.2.15 to 2.2.16 and while I was at it also went from pigeonhole 0.4.5 to 0.4.7-rc2. After upgrading I started getting these errors in the dovecot-deliver-error log: ===== lda(test at domain.nl): Error: sieve: file storage: Failed to normalize active script directory (path=/home/vpopmail/domains/domain.nl/test/.sieve): No such file or directory lda(test at

> >>> When I compiled and installed this, Sieve scripts were being ignored. Not > >>> sure if it's my own stupid mistake, but when I put v0.4.6 back in place, it > >>> worked fine. No configuration changes, only make install on the different > >>> sources and restart dovecot. > >> Could you show your dovecot -n output? > >> >

Hello Dovecot users, The rc1 release showed a few problems with the up-to-date checking of on-disk binary files. The binary files contain some metadata about the script these were compiled from. If this doesn't match the current script anymore, the script is recompiled. One of these metadata items is the script location. However, this location wasn't normalized, so when the binary would

Hello Dovecot users, The rc1 release showed a few problems with the up-to-date checking of on-disk binary files. The binary files contain some metadata about the script these were compiled from. If this doesn't match the current script anymore, the script is recompiled. One of these metadata items is the script location. However, this location wasn't normalized, so when the binary would

> >> Last time I had a few stupid problems in the releases, so > >> I'll follow > >> Timo's example and I release an RC first. > >> > >> The highlights include the implementation of the index and > >> metadata > >> extensions. Quite a few bugs are fixed as well. > > When I compiled and installed this, Sieve scripts were

On 3/10/2015 8:11 PM, E.B. wrote: >> Last time I had a few stupid problems in the releases, so >> I'll follow >> Timo's example and I release an RC first. >> >> The highlights include the implementation of the index and >> metadata >> extensions. Quite a few bugs are fixed as well. > When I compiled and installed this, Sieve scripts were being

On 3/11/2015 3:16 AM, E.B. wrote: >>>> Last time I had a few stupid problems in the releases, so >>>> I'll follow >>>> Timo's example and I release an RC first. >>>> >>>> The highlights include the implementation of the index and >>>> metadata >>>> extensions. Quite a few bugs are fixed as well.

On 3/6/2015 7:53 AM, Timo Sirainen wrote: > http://dovecot.org/releases/2.2/rc/dovecot-2.2.16.rc1.tar.gz > http://dovecot.org/releases/2.2/rc/dovecot-2.2.16.rc1.tar.gz.sig > > Looks like it's been a long time since v2.2.15. There have been a ton of changes since it was released though, so here's a release candidate first to find out if somebody can find any bugs before the

* Timo Sirainen <dovecot at dovecot.org>: > + LMTP server: Added lmtp_user_concurrency_limit setting to limit how > many LMTP deliveries can be done concurrently for a single user. That's broken! 0 doesn't remove the limit :( -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstra?e 15, 81669 M?nchen Sitz der Gesellschaft: M?nchen, Amtsgericht M?nchen:

This easy to correct errors is unfortunately still exists. I once hung my solution, but I can only test on a system. # dovecot --version 2.2.16.rc1 # doveadm -f table mailbox status "messages guid" -u flor_hardy "*" mailbox messages guid Trash 0 60a619171f66fd54035800004b126f5b Entw?rfe 0 62a619171f66fd54035800004b126f5b INBOX 0

Am 13.03.2015 um 11:23 schrieb Timo Sirainen: > On 12 Mar 2015, at 21:09, Reindl Harald <h.reindl at thelounge.net> wrote: >> >> /usr/lib64/dovecot/stats/libstats_mail.so >> >> why in the world a new sub-directory containing just one so-file enforcing pakcage buildsers to change SPEC files? > > So that external plugins can add more files in there and extend

On 06 Mar 2015, at 21:58, Daniel Miller <dmiller at amfes.com> wrote: > > On 3/6/2015 7:53 AM, Timo Sirainen wrote: >> http://dovecot.org/releases/2.2/rc/dovecot-2.2.16.rc1.tar.gz >> http://dovecot.org/releases/2.2/rc/dovecot-2.2.16.rc1.tar.gz.sig >> >> Looks like it's been a long time since v2.2.15. There have been a ton of changes since it was released