On Mon, Jul 13, 2009 at 4:03 PM, Stephan Bosch wrote:
>> This page on dovecot.org: http://dovecot.org/releases/sieve/ has
>> tarballs that track the various Dovecot releases. So you can
>> understand why I might wonder if the lack of a 1.1.17 means that
>> 1.1.16 is okay :-)
>>
> Look closer. The v
Jeff Mitchell wrote:
On Mon, Jul 13, 2009 at 2:50 PM, Stephan Bosch wrote:
What do you mean? The CMUSieve version used for Dovecot v1.1.x is
dovecot-sieve-1.1.6. This is a non-specific release that should (and does)
work fine with the new 1.1.17 Dovecot release.
This page on dovecot.org: http:
On Mon, Jul 13, 2009 at 2:50 PM, Stephan Bosch wrote:
> What do you mean? The CMUSieve version used for Dovecot v1.1.x is
> dovecot-sieve-1.1.6. This is a non-specific release that should (and does)
> work fine with the new 1.1.17 Dovecot release.
This page on dovecot.org: http://dovecot.org/relea
Jeff Mitchell wrote:
On Sun, Jul 12, 2009 at 8:07 PM, Stephan Bosch wrote:
Hello Dovecot users,
This release is entirely composed of bug fixes, most of which were found and
fixed earlier in the implementation for Dovecot v1.2.
Great!
Does anyone know if the actual sieve tarball for 1.1.16 wo
On Sun, Jul 12, 2009 at 8:07 PM, Stephan Bosch wrote:
> Hello Dovecot users,
>
> This release is entirely composed of bug fixes, most of which were found and
> fixed earlier in the implementation for Dovecot v1.2.
Great!
Does anyone know if the actual sieve tarball for 1.1.16 works okay
with 1.1.
