similar to: Sieve and ManageSieve for Dovecot v2.0 merged into one repository

Hello Dovecot users, Recently I was asked to use Mercurial for the ManageSieve development just like Dovecot. As a matter of fact I have been using Mercurial for some time now. Now that I am back from a short and active vacation I am ready to publish my repositories. The repositories are publicly available at: http://hg.rename-it.nl/ The -patch repositories are so-called Mercurial Queues (MQ)

Hello Dovecot users, For those of you who like to live on the edge, there is now a Debian-testing repository available with hourly updates from recent Dovecot-1.1 changes in the Mercurial repositories. It automatically releases a new set of packages if it notices any changes in any of the repositories. The packages are built with dovecot-sieve-1.1 and dovecot-1.1-managesieve included.

Hello, i have a problem with the managesieve plugin and a virtual namespace in v2.0. The managesieve plugin complains about an unknown storage driver virtual when i try to log intot the managesieve. I don't know if this is quite a recent problem or if it exists for a while, as i configured the virtual namspace from scratch. (The virtual namespace itself is working.) Jun 28 13:55:54

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,

Hi, I'm currently running version v2.0.x in production (using Maildir storage) and it's been working well. I'm interested in moving to version 2.2.x and am preparing a test server to do so. As I have been merging the conf file changes between the two versions I noticed syntax changes for the 90-sieve.conf file. There are now 'locations' and presumably to keep referring to

Hi Timo, I've just tried to convert my v1.2 configuration to a v2.0 configuration. Below a few obsolete warnings, among others "mail_executable has been replaced by service { executable }", was an interesting error: "doveconf: Error: duplicate listener: 198:" The broken parts of the converted configuration: # 2.0.beta4 (84ffb38839b9): /etc/dovecot/dovecot.conf # OS: Linux

Hi, I've changed the name of the Sieve Mercurial repository form dovecot-libsieve to dovecot-1.2-sieve, to signify the Dovecot version it applies to. The URL thus looks as follows: http://hg.rename-it.nl/dovecot-1.2-sieve Note that there are already dovecot-2.0-sieve and dovecot-2.0-managesieve repositories, but these are still somewhat broken in multiple ways and I wouldn't call

I'm integrating Sieve (the new one) and ManageSieve into wip/dovecot. Currently, this works as dovecot options because dovecot must be built before sieve can be configured and sieve must be built before managesieve can be configured/built. Now, the question arose what the long-term solution (in pkgsrc) should be. To my understanding, with dovecot 2.0, ManageSieve will no longer need to patch

Hi, latest Mercurial seems to have problems with the Config Module unloads: May 5 19:18:16 spectre dovecot: master: Dovecot v2.0.beta4 (5d76f5b13883) starting up May 5 19:18:34 spectre dovecot: managesieve: Error: fd_read() partial input (54/88) May 5 19:18:34 spectre dovecot: imap-login: Fatal: Error reading configuration: read(/var/run/dovecot/config) failed: EOF May 5 19:18:34 spectre

Hi, Yesterday night I upgraded the automated packages built at Xi to the latest experimental Debian packages for v2.0. This unfortunately causes a problem upon upgrade. I've contacted the maintainer, so this issue should resolve itself soon. The issue manifests as follows: Setting up dovecot-imapd (2:2.0.11-0~auto+25) ... ucfr: Attempt from package dovecot-imapd to take

Hi all, ok, I am running version v2.0.beta6 and the latest pigeonhole build to run managesieve and the sieve delivery filters... I am getting the following response from the managesieve port when connecting : Escape character is '^]'. "IMPLEMENTATION" "Dovecot" "SIEVE" "" "SASL" "PLAIN" "STARTTLS" "VERSION"

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

Hi, As the "new Sieve implementation" is using a "gratefully stolen copy of deliver.c from dovecot" (i.e. a dirty code in mail-raw.c), would it be possible for the Sieve piece 1 - to be using files from dovecot directly rather than copying&changing it (which is very bad for maintenance) 2 - to be incorporated in the hg/mercurial tree of dovecot ? Thanks a lot

Hello Timo, I'm playing around with the new Dovecot v2.0.beta3 and don't seem to be able to get quotas working from userdb. I didn't change the SQL query which was working for 1.2.10. Feb 20 19:34:06 ubuntu-test dovecot: auth: sql(test,192.168.156.99): SELECT home, mail, uid, gid, concat('*:storage=', quota_limit, 'MB') AS quota_rule FROM users WHERE username =

http://dovecot.org/releases/2.0/beta/dovecot-2.0.beta1.tar.gz http://dovecot.org/releases/2.0/beta/dovecot-2.0.beta1.tar.gz.sig Now that v2.0 is in beta stage I don't expect anything big to change anymore. The configuration and the APIs shouldn't change in non-backwards compatible ways. There are still bugs left to be fixed and some small features to be implemented, but I'd like to

http://dovecot.org/releases/2.0/beta/dovecot-2.0.beta1.tar.gz http://dovecot.org/releases/2.0/beta/dovecot-2.0.beta1.tar.gz.sig Now that v2.0 is in beta stage I don't expect anything big to change anymore. The configuration and the APIs shouldn't change in non-backwards compatible ways. There are still bugs left to be fixed and some small features to be implemented, but I'd like to

I'm reading http://wiki.dovecot.org/ManageSieve/Install . I already use mercurial queues. These are the steps I see to install: hg clone http://hg.dovecot.org/dovecot-1.2 cd dovecot-1.2 hg clone http://hg.rename-it.nl/dovecot-1.2-managesieve-patch .hg/ patches hg qpush Do the steps change? Thanks, Jonathan -------------- next part -------------- A non-text attachment was scrubbed... Name:

Hello Dovecot users, This is a simultaneous release of new versions of Sieve-related software for Dovecot v1.1 and v1.2. Only the Sieve implementation itself has seen significant development. The ManageSieve packages only have small fixes and the ManageSieve patches are updated as usual to match the new Dovecot releases. Changelog Sieve v0.1.5: * Ported the implementation of the Sieve