similar to: [help]how to refresh pigeonhole sieve vacation days data

Hi, I have a problem with dovecot's sieve and SOGo ( http://www.sogo.nu/ ) I have installed last version of sogo ( 1.3.6) in one virtual machine with ubuntu, lucid. In another virtualmachine with ubuntu jaunty is running dovecot ( 1:1.1.11-0ubuntu4.1 ) When try to activate vacation function, after the "PUTSCRIPT "sogo" command, the manage-sieve answer: NO "Script name

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

This might be a PEBKAC on my end, but in our old server, "vacation" responses would only be sent back to an origin address once per day because we had ":days 1" in the rule. On the new server, even though we have ":days 1", pigeonhole is sending responses to every message, resulting in multiple vacation responses each day back to each origin address. The

Hello Dovecot users, Here's the definitive 0.4.16 release. There were no changes since the release candidate. The reported replication issues are still open, since we haven't been able to reproduce them so far. Changelog v0.4.16: * Part of the Sieve extprograms implementation was moved to Dovecot, which means that this release depends on Dovecot v2.2.26+. * ManageSieve: The PUTSCRIPT

Hello Dovecot users, Here's the definitive 0.4.16 release. There were no changes since the release candidate. The reported replication issues are still open, since we haven't been able to reproduce them so far. Changelog v0.4.16: * Part of the Sieve extprograms implementation was moved to Dovecot, which means that this release depends on Dovecot v2.2.26+. * ManageSieve: The PUTSCRIPT

Hello Dovecot users, The upcoming release includes quite a few new features for a change. The most important ones are the Sieve discard-script feature and the new vnd.dovecot.config environment items. Documentation for these features can be found in the package itself. Please test these thoroughly. Changelog v0.4.16: * Part of the Sieve extprograms implementation was moved to Dovecot,

Hello Dovecot users, The upcoming release includes quite a few new features for a change. The most important ones are the Sieve discard-script feature and the new vnd.dovecot.config environment items. Documentation for these features can be found in the package itself. Please test these thoroughly. Changelog v0.4.16: * Part of the Sieve extprograms implementation was moved to Dovecot,

Hello Dovecot users, Now that Dovecot v2.1.0 is out there, I release Pigeonhole v0.3.0. The most significant new features are support for the Sieve editheader extension and the sieve-filter tool. I haven't received much feedback on these new features, which can either mean that they are mostly bug-free or that not many people have tried these, so these are still considered experimental.

Hello Dovecot users, Now that Dovecot v2.1.0 is out there, I release Pigeonhole v0.3.0. The most significant new features are support for the Sieve editheader extension and the sieve-filter tool. I haven't received much feedback on these new features, which can either mean that they are mostly bug-free or that not many people have tried these, so these are still considered experimental.

hi all edit via vi editor to change dovecot.sieve and enotify works fine.but when I telnet 4190 port via managesieve to edit it with the same code,the managesieve said "NO "Error in MANAGESIEVE command CHECKSCRIPT: "", find many topic in wiki and maillist but not solved. need you help!thanks!!dovecot version 2.2.15,pigonhole version 0.4.4 here are more infos

Hello Dovecot users, I have finally finished the first release of Pigeonhole for Dovecot v2.0. The most notable change from previous Dovecot v1.2 Sieve/ManageSieve releases is that all is now integrated in a single package and there is no need to patch Dovecot anymore to gain ManageSieve support. Changelog v0.2.0: * Merged Sieve and ManageSieve packages into a single Pigeonhole

Hello Dovecot users, I have finally finished the first release of Pigeonhole for Dovecot v2.0. The most notable change from previous Dovecot v1.2 Sieve/ManageSieve releases is that all is now integrated in a single package and there is no need to patch Dovecot anymore to gain ManageSieve support. Changelog v0.2.0: * Merged Sieve and ManageSieve packages into a single Pigeonhole

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

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

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

Hi, I am going further with dovecot configuration. Finally managed to configure roundcube 0.3 with managesieve plugin. And it works, although... not perfectly :( For some issues probably roundcube-managesieve is guilty, but simply the sieve plugins seems to work wrong. Here is my sieve file: require ["vacation","fileinto"]; # rule:[wakacje] if anyof (true) {

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.

Hi, dont ask :) but I have two accounts for which I have to configure an auto reply for any e-mail send to it. As far as I understand Sieve yet, I do have to set sieve_vacation_min_period = 0 in the dovecot config and set the days value in the sieve rule. But as there is a limit of 1 day, I think this is not working. Right? Is there any other way to accomplish that? regards . G?tz -- G?tz