similar to: Released ManageSieve v0.10.5 for Dovecot v1.1.9

Hello Dovecot users, It has been about two months since the last release of the new Sieve implementation and the ManageSieve service for Dovecot v1.2. Therefore, this release contains quite a few changes. It adds new sieve features like the enotify extension and multiscript support. Also, quite a few (user-reported) bugs were fixed since the last release. Changelog Sieve v0.1.3: *

Hello Dovecot users, It has been about two months since the last release of the new Sieve implementation and the ManageSieve service for Dovecot v1.2. Therefore, this release contains quite a few changes. It adds new sieve features like the enotify extension and multiscript support. Also, quite a few (user-reported) bugs were fixed since the last release. Changelog Sieve v0.1.3: *

You can also write to mailing list without subscribing. Anyway, I haven't written managesieve-login code, Ccing Stephan. On Thu, 2009-01-15 at 17:00 +0100, Wolfgang.Friebel at desy.de wrote: > Hi, > > sorry that do not write to the list, I am not subscribed yet. I have read > the november 2008 thread where managesieve-login does a segfault. As it > happened to me as well and

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

I am building dovecot-2.0-pigeonhole-0.2.1 (dovecot-2.0.5, but that does not matter) with dovecot-config in place (in /usr/lib64/dovecot) on a 64bit Linux (RHEL5): ./configure --with-dovecot=/usr/lib64/dovecot The libs needed for several executables in libexec such as /usr/libexec/dovecot/managesieve-login are not installed in /usr/lib64 but in /usr/lib64/dovecot. Therefore the executable

Hello, While updating the ManageSieve implementation to the latest draft specification I noticed a major omission in the way script names are handled. Essentially, script names are directly appended to the sieve storage directory path and suffixed with '.sieve'. This does not take the use of '../' in script names into account. Therefore, clever virtual users that know the

Hello, While updating the ManageSieve implementation to the latest draft specification I noticed a major omission in the way script names are handled. Essentially, script names are directly appended to the sieve storage directory path and suffixed with '.sieve'. This does not take the use of '../' in script names into account. Therefore, clever virtual users that know the

In order to let users construct a sieve filter using a GUI I have taken websieve.pl from Alain Turbide (for use with Cyrus) and modified it to work with dovecot. In order to get it working quickly I have removed all the code I did not need (e.g. ldap support, password authentication) and coded Kerberos5 auth (via GSSAPI or SASL) in. I understand that this makes the work mostly useless to

http://dovecot.org/releases/1.1/dovecot-1.1.9.tar.gz http://dovecot.org/releases/1.1/dovecot-1.1.9.tar.gz.sig Lots of small dbox fixes, hopefully migrations from Maildir are now working correctly. I'm also planning on releasing v1.2.beta1 in a few days. + Sending SIGUSR2 to dovecot-auth now also logs statistics about cache inserts. This could help figuring out auth cache size. +

http://dovecot.org/releases/1.1/dovecot-1.1.9.tar.gz http://dovecot.org/releases/1.1/dovecot-1.1.9.tar.gz.sig Lots of small dbox fixes, hopefully migrations from Maildir are now working correctly. I'm also planning on releasing v1.2.beta1 in a few days. + Sending SIGUSR2 to dovecot-auth now also logs statistics about cache inserts. This could help figuring out auth cache size. +

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

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

Hello Dovecot users, Since v8, I have updated the MANAGESIEVE patch to fix various issues reported by users. Although I planned to upgrade the next release after v8 to Dovecot v1.1, I release these changes for Dovecot 1.0 first. If no further major issues are found, I can upgrade to Dovecot 1.1. Change Log V9 ------------- + Definitively fixed the segfault mentioned in V8. It proved to be

Op 2/5/2017 om 8:53 PM schreef dovelist: > Hi, > > I am trying to get sieve working on a new OpenSuse leap 42.2 install. > On my 'old' OpenSuse 13.2 machine it worked fine. > > The problem is that Managesieve can't access the script store and > won't let me create any script. It says permission denied on ~/sieve > directory. See log below. I 've

tonight dovecot 1.2beta4 crashed for the first time with an assertion failed. See attached log file. Around that time nobody was logged in into dovecot and there were no other mail deliveries going on. The mail in question should have been delivered to three recipients, one got the mail, the two others not. There is unfortunately no core dump file. I have attached the dovecot -n output as

Using dovecot 1.2beta (but earlier versions should behave similarly) we have a problem in conjunction with empty To: headers and the RT request tracker. RT sends mail out using Bcc: and no To: header at all. To make some mailers happy one can configure to send a dummy To: header, which we do. Our To header looks like: To: "AdminCc of rt Ticket #123456":; The message_address_parse

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, I have composed a release of the ManageSieve service for Dovecot v1.2. I also added two new capabilities that were added to the ManageSieve specification. Just like the last few releases, this new release supports the new Sieve plugin already. Change Log v0.11.0 ------------------- * Upgraded to Dovecot v1.2 * Added support for new ManageSieve capabilities RENAME

Hello Dovecot users, I have composed a release of the ManageSieve service for Dovecot v1.2. I also added two new capabilities that were added to the ManageSieve specification. Just like the last few releases, this new release supports the new Sieve plugin already. Change Log v0.11.0 ------------------- * Upgraded to Dovecot v1.2 * Added support for new ManageSieve capabilities RENAME

Hello Dovecot users, Recently, I was pointed towards a problem in the managesieve SASL implementation. As it turns out there was a bug in handling mechanisms that expect more than a single client response. That is why the PLAIN mechanism works and the (obsolete) LOGIN mechanism fails (along with probably many others). This problem was present in both v9.2 and v0.10.1 for Dovecot 1.0 and 1.1