similar to: Released Sieve v0.1.8 and ManageSieve v0.11.7 for Dovecot v1.2.1

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. Changelog ManageSieve v0.10.7: - Fixed generation of core dumps. - Fixed panic occurring when many errors are produced by the Sieve compiler (bug found by Pascal Volk). - Fixed potential memory leak in the PUTSCRIPT command. - Fixed

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. Changelog ManageSieve v0.10.7: - Fixed generation of core dumps. - Fixed panic occurring when many errors are produced by the Sieve compiler (bug found by Pascal Volk). - Fixed potential memory leak in the PUTSCRIPT command. - Fixed

I've found this in my dovecot.log: ,--[ /path/to/dovecot.log ]-- | Jul 11 01:44:29 dovecot: Info: Dovecot v1.2.1 starting up | ... | Jul 11 01:50:21 auth(default): Info: client in: AUTH 1 PLAIN service=sieve lip=192.168.111.222 rip=192.168.111.122 lport=12000 rport=35084 resp=<hidden> | Jul 11 01:50:21 auth(default): Info: sql(j.doe at

Hello! I'm trying for a lot of time to make managesieve working with dovecot 1.1.17 and virtual users on openSuSE 11.1. I think I'm doing some misconfiguration, but I can't figure it out. Perhaps it's something with the paths to the sieve scripts? In dovecot.conf I find in the comments: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ protocol

Hello Dovecot users, I hereby release new versions of the Sieve packages for the recently released Dovecot v1.2.0 (Congrats Timo!). Apart from small changes to make things compile with Dovecot again, a few other bugs were fixed as well. Unfortunately, the (FreeBSD-specific) 8kb script truncation bug remains. Although it is reported for Dovecot v1.1.16, I see no reason why it should not

Hello Dovecot users, I hereby release new versions of the Sieve packages for the recently released Dovecot v1.2.0 (Congrats Timo!). Apart from small changes to make things compile with Dovecot again, a few other bugs were fixed as well. Unfortunately, the (FreeBSD-specific) 8kb script truncation bug remains. Although it is reported for Dovecot v1.1.16, I see no reason why it should not

Hello Timo, Dispite the heat out here, I managed to come up with a new version of the managesieve patch for dovecot-1.0rc2: - Fixed the bug (missing CRLF) in the authenticate command - Modified the sieve storage library making the interface much less crude. - The scripts put on the server using the putscript command are now checked before they are accepted. - The reported SIEVE capability is

dovecot-2.1.8 sieve-0.3.1 binutils-2.22 When dovecot and sieve is linked with ld.gold I get a segfault in checkscript command: $ telnet localhost 4190 [some output] authenticate "PLAIN" "<base64_username_password>" [some more output] checkscript "foobarscript" connection closed Logs: 2012-07-12T19:30:23.624158+00:00 bob dovecot: master: Dovecot v2.1.8

Hello Dovecot users, The recent release of Dovecot v1.2.15 is a good opportunity to release new versions of Sieve and ManageSieve for Dovecot v1.2. These releases consist entirely of bugfixes and introduce no new features. Changelog Sieve v0.1.18: - Imap4flags: fixed segfault bug occuring in multiscript context. Occured in specific situations when a script using imap4flags was

Hello Dovecot users, The recent release of Dovecot v1.2.15 is a good opportunity to release new versions of Sieve and ManageSieve for Dovecot v1.2. These releases consist entirely of bugfixes and introduce no new features. Changelog Sieve v0.1.18: - Imap4flags: fixed segfault bug occuring in multiscript context. Occured in specific situations when a script using imap4flags was

Hi, I'm getting segfaults and unexpected disconnects from managesieve server, when the Thunderbird SIEVE extension tries to validate SIEVE scripts agains Pidgeonhole in Dovecot 2.1.8. The extension says: "Server terminated unexpectedly the connection, click on reconnect to try again." It can be reproduced by simply calling CHECKSCRIPT followed by a string: mail01:~# telnet

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello everybody, I would like to use managesieve protocol and cmusieve plugin at the same time. I have used the cmusieve plugin for years and I now also enabled the managesieve system. I got the managesieve system working but when I activate the managesieve filter for the user the cmusieve sieve filter is not used anymore. How can I have both sieve

Is there some simple textual frontend to the ManageSieve protocol somewhat easier to use than gnutls-cli? I.e. something to use like managesieve -u ef putscript myscript < /tmp/myscript Password: managesieve -u ef setactive myscript Password: simply doing the TLS authentication and length computation for me.

I do have two questions related to the managesieve setup in dovecot 1) I did setup a global sieve filter, that is invoked if a user has no other sieve filter. If a user installs a sieve filter and activates it (PUTSCRIPT, SETACTIVE) then the sieve filter gets compiled (.sievec) and deliver does use it. If I want to deactivate the filter (SETACTIVE "") only the symlink (to the .sieve

Hi everybody, dovecot-1.2 alpha3 with cmusieve, libsieve and managesieve are available as rpm packages for Sisyphus repository (http://ftp.altlinux.org/pub/distributions/ALTLinux/Sisyphus, and specs/patches are available at http://git.altlinux.org/people/seriv/packages/?p=dovecot.git and http://git.altlinux.org/people/seriv/packages/?p=dovecot-sieve.git). Thank you very much Timo and Stephan! I

Hi Stephan, > Normally, Dovecot permission errors are more helpful than that. So, > this > error message in itself is a bit of a bug: I'm glad to h've been able to help with this beta-test ;-) > About the cause of this error: keep in mind that the whole directory > path needs read/execute permission, not only the leaf directory. Have checked. They are... > You

Hello Dovecot users, Relatively many bugs and problems were reported recently in a short period of time. Apparently, now that Dovecot v1.2 is finally stable, the new Sieve plugin is also starting to get used much more. No known bugs remain. Let's hope I didn't spawn any new ones. Apart from the bugfixes I made the deprecated notify plugin implementation compatible with CMUSieve. You

Hello Dovecot users, Relatively many bugs and problems were reported recently in a short period of time. Apparently, now that Dovecot v1.2 is finally stable, the new Sieve plugin is also starting to get used much more. No known bugs remain. Let's hope I didn't spawn any new ones. Apart from the bugfixes I made the deprecated notify plugin implementation compatible with CMUSieve. You

Hello Dovecot users, Since the first release of the new Sieve implementation, not that many bugs were reported. This is probably due to the fact that it is not tried yet by that many people. In the mean time, I did find and fix some more bugs myself, I adapted to changes in Dovecot, wrote some more documentation and started work on the enotify extension. Both Sieve and ManageSieve were changed

Hello Dovecot users, Since the first release of the new Sieve implementation, not that many bugs were reported. This is probably due to the fact that it is not tried yet by that many people. In the mean time, I did find and fix some more bugs myself, I adapted to changes in Dovecot, wrote some more documentation and started work on the enotify extension. Both Sieve and ManageSieve were