Hello Dovecot users,
The new Dovecot v2.0.8 release has a few changes that prompted changes
in Pigeonhole as well. This means that a new release of Pigeonhole is
also necessary, because otherwise things will not compile anymore.
Apart from a few rather minor bugfixes, some of which originate in
Dovecot, one TODO item has finally been resolved: the reject action uses
the LDA mail reject API, meaning that the associated LDA settings now
also work for Pigeonhole, as would be expected.
Changelog v0.2.2:
* LDA Sieve plugin: started using Dovecot LDA reject API for the
reject extension. This means that the LDA reject_reason and
reject_subject settings now also work for Pigeonhole's LDA Sieve
plugin.
* Did some work on the new sieve-filter tool. It is mostly
functional, but it is not finished yet.
* Dovecot change: services' default vsz_limits weren't being enforced
correctly in earlier v2.0 releases. Now that they are enforced, you
might notice that the default limits are too low and you need to
increase them. This problem will show up in logs as "out of memory"
errors. See default_vsz_limit and service { vsz_limit } settings.
- Imap4flags: fixed segfault bug occurring in multiscript context.
- Added version checking to the ManageSieve settings plugin. This
plugin was forgotten when the LDA plugin was updated with this
change in the previous release.
- LDA Sieve plugin: fixed memory leak at deinitialization.
The release is available as follows:
http://www.rename-it.nl/dovecot/2.0/dovecot-2.0-pigeonhole-0.2.2.tar.gzhttp://www.rename-it.nl/dovecot/2.0/dovecot-2.0-pigeonhole-0.2.2.tar.gz.sig
Refer to http://pigeonhole.dovecot.org and the Dovecot v2.0 wiki for
more information. Have fun testing this new release and don't hesitate
to notify me when there are any problems.
Regards,
--
Stephan Bosch
stephan(a)rename-it.nl
http://dovecot.org/releases/2.0/dovecot-2.0.8.tar.gzhttp://dovecot.org/releases/2.0/dovecot-2.0.8.tar.gz.sig
There are many small fixes all around, plus some more noticeable
changes:
* Services' default vsz_limits weren't being enforced correctly in
earlier v2.0 releases. Now that they are enforced, you might notice
that the default limits are too low and you need to increase them.
This problem will show up in logs as "out of memory" errors.
See default_vsz_limit and service { vsz_limit } settings.
* LMTP: In earlier versions if mail was delivered to user+detail@domain
address, LMTP server always attempted to deliver the mail to mailbox
named "detail". This was rather unintentional and shouldn't have been
the default. lmtp_save_to_detail_mailbox=yes setting now preserves
this behavior (default is no).
+ Added systemd support (configure --with-systemdsystemunitdir).
Based on patch by Christophe Fergeau.
+ Replaced broken mbox-snarf plugin with a new more generic snarf
plugin.
- dbox: Fixes to handling external mail attachments
- verbose_proctitle=yes didn't work for all processes in v2.0.7
- imap, pop3: When service { client_count } was larger than 1, the
log messages didn't use the correct prefix. Last logged in user's
prefix was always used, regardless of what user's session actually
logged it. Now the proper log prefix is always used.
- MySQL: Only the first specified host was ever used