similar to: vacation problem with sieve and sogo

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

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 folks, I'm setting up a dovecot server with managesieve support. I'd like to offer spamfiltering through a Sieve script to my users by default, but still allow them to modify the filtering rules through Managesieve. I found the sieve_global_path configuration option, which seems perfect for what I want. I can configure a default script there, which will work for all users until they

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, I'm testing dovecot replication alongside pigeonhole and liking it. Dovecot v2.2.13 Pigeonhole v0.4.3 If I create or edit a sieve script on one server (via managesieve, using the thunderbird plugin as it happens) then it does get replicated to the other - great! However, if I set a script to be active (SETACTIVE) on one side then this is not being replicated across to the other

With all the mess that my email has become, it makes sense for me to try to make use of Sieve, but I'm having quite the time finding out how to make it work. I'm running 1.0.13 on a Debian machine. Sieve appears to be compiled with it. I can access managesieve, and I have set up dovecot.conf with lda. I do not get a NO response when I PUTSCRIPI, but LISTSCRIPTS produces no result, so I

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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, well, I'm sort of sure that this was raised in the past, but I do not find the patch / answer of it: I'm running dovecot v1.0.15 from hg (5567:568687e4df02) with managesieve patch v9.2 (there is one change between this and v9.3 except in regards of AUTH so this should not matter.) and dovecot-sieve v1.0.3. When an user issues just

Hello Everyone, I am running Dovecot 2.0.15 with its Sieve plug-in, and Roundcube 0.5.3. I have a problem with just one particular user, who after creating a filters set and creating a filter in Roundcube, this user cannot activate the filters set. At first, this user could not create a filter at all. That was resolved by creating the "sieve" directory with the right permissions in

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

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

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 everybody: I'm using dovecot with pigeonhole sieve Plugin.everything goes well.but when i use vacation module,i found a problem: I write a sieve with a vacation module in, and put it to the sieve location ,used *PUTSCRIPT* comand with *ManageSieve* and *set it ACTIVE*.It's work!I use A email send mail to him and receive an auto-reply.then ,I modify the sieve only change