similar to: Released ManageSieve v0.10.7 for Dovecot v1.1.17

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 Dovecot users, The recent Dovecot v1.2.1 release broke ManageSieve compilation. Today, I release new packages to fix this and additionally a few bugs are resolved. Changelog Sieve v0.1.8: - Fixed AIX compile problem. For portability, the typeof operator is not used anymore. + Added partial support for the deprecated notify extension. However, it turns out that the implementation

Hello Dovecot users, The recent Dovecot v1.2.1 release broke ManageSieve compilation. Today, I release new packages to fix this and additionally a few bugs are resolved. Changelog Sieve v0.1.8: - Fixed AIX compile problem. For portability, the typeof operator is not used anymore. + Added partial support for the deprecated notify extension. However, it turns out that the implementation

-----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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I'm trying to compile dovecot-1.2-managesieve from hg repo with Dovecot v1.2 and I found that managesieve uses another "install" target/prefix than I've configured in Dovecot. Is this intentional? Because you must specify the compiled Dovecot sources, is managesieve just "loosly" connected to Dovecot so it

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

Ok, sorry to bother again, but i am going crazy to make work cmusieve with dovecot. I intend to use it for the vacation system, but...seems the system ignores the .dovecot.sieve file into the user dir... I am doing something wrong, but i don't know what... Here is my configs: I use OpenSuse 11.0. # 1.1.7: /etc/dovecot/dovecot.conf # OS: Linux 2.6.25.20-0.1-pae i686 openSUSE 11.0 (i586) ext3

Hello Dovecot users, I finally managed to upgrade the ManageSieve implementation to dovecot-1.1. This also resulted in major restructuring of the code. The actual ManageSieve implementation is now available as a separate package and the patch now only contains the changes to the dovecot-1.1 tree that are necessary to use the ManageSieve service. The patch and the new package no longer

Hello Dovecot users, Finally, after little more than a year, I finished the first release of the new Sieve implementation for Dovecot. The main reason for rewriting the Sieve engine is to provide more reliable script execution and to provide better error messages to users and system administrators. Also, since the Sieve language evolves quickly, with new language extensions published every

Hello Dovecot users, Finally, after little more than a year, I finished the first release of the new Sieve implementation for Dovecot. The main reason for rewriting the Sieve engine is to provide more reliable script execution and to provide better error messages to users and system administrators. Also, since the Sieve language evolves quickly, with new language extensions published every

Hi Stephan, ManageSieve uses the wrong? service name for the authdb lookup. With dovecot-1.2-managesieve the service name was changed from 'managesieve' to 'sieve'. So I altered my table layout in order to make the query "SELECT userid AS "user", password FROM dovecotpassword('%Ln', '%Ld') WHERE %Ls" work again. When I try to login on the sieve

After some help with debugging tips on #dovecot, I have established that a sieve script on Dovecot 1.1.16 has to be less than 8kB in order to be retrieved by a managesieve client. I have been using managesieve for about 6 months over as many 1.1.n versions of dovecot as have been around during that time and hit this problem when I upgraded to Dovecot 1.1.16. I have gone back to Dovecot 1.1.15

Hello This is my dovecot.conf : /etc/dovecot/dovecot.conf log_path: /var/log/dovecot.log info_log_path: /var/log/dovecot.info protocols: imap imaps managesieve login_dir: /var/run/dovecot/login login_executable(default): /usr/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(managesieve): /usr/lib/dovecot/managesieve-login mail_location:

Hello Dovecot users, Due to personal matters I haven't had time to do anything in the last few weeks. Before that I provided some pre-releases and since nobody indicated problems with those, I release them definitively now. I hope the shit storm has blown over, so that I can dedicate more of my time towards Pigeonhole development. The Sieve release involves a large architectural change,

Hello Dovecot users, Due to personal matters I haven't had time to do anything in the last few weeks. Before that I provided some pre-releases and since nobody indicated problems with those, I release them definitively now. I hope the shit storm has blown over, so that I can dedicate more of my time towards Pigeonhole development. The Sieve release involves a large architectural change,

http://dovecot.org/releases/1.1/dovecot-1.1.17.tar.gz http://dovecot.org/releases/1.1/dovecot-1.1.17.tar.gz.sig - IMAP: Don't crash if IDLE command is pipelined after a long-running UID FETCH or UID SEARCH. - IMAP: Some FETCH command parameters were broken with in some OSes. - mbox: New mailboxes were created with UIDVALIDITY 1. - mbox: Don't write garbage to mbox if message

http://dovecot.org/releases/1.1/dovecot-1.1.17.tar.gz http://dovecot.org/releases/1.1/dovecot-1.1.17.tar.gz.sig - IMAP: Don't crash if IDLE command is pipelined after a long-running UID FETCH or UID SEARCH. - IMAP: Some FETCH command parameters were broken with in some OSes. - mbox: New mailboxes were created with UIDVALIDITY 1. - mbox: Don't write garbage to mbox if message

Hi, when switching from Dovecot 1.1 + cmusieve to Dovecot 1.2 + sieve I stumbled upon the following problem: My sieve files, generated with Dovecot 1.1's managesieve, did not compile anymore with sieve's sievec. The error message was: error: end of file before end of hash comment. Looking a bit closer I found that the last line, which was a comment, did not have a trailing newline.

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