similar to: MANAGESIEVE patch v6 for dovecot 1.0.3

Hello dovecot users, I have updated the MANAGESIEVE patch to fix a recently reported problem. This is a patch against the latest stable release 1.0.3. It currently won't compile with 1.1 due to significant changes in the master code. Change Log V7 ------------- - Robin Breathe indicated that the regex capability was missing in the server's SIEVE listing. It turns out I forgot to

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, occasionally Dovecot stops to accept new connections. Already existing ones do function properly. Strace'ing dovecot-auth reveals that it is running and is authentificating users, the logfile logs new connections. However, lots of other connects just stall, before the IMAP server responds with the greeting. My user backend is a LDAP

Hello list, I'm using Dovecot 1.0.0 on FreeBSD 6.2-RELEASE and applied the latest MANAGESIEVE patch v3 [1] which seems to have worked smoothly, i.e. all hunks succeeded and no compilation problems. Now this may be stupid question with an obvious answer, but I am at a loss at how to start the daemon? What's the binary called that starts the sieve server? Is there a special way to

Hi, I allow only TLS/SSL connection to dovecot. The managesieve doesn't work with TLS but it works without it. gladiac at magrathea:~> gnutls-cli -p 2000 -s --insecure -V milliways.cynapses.org Resolving 'milliways.cynapses.org'... Connecting to '213.239.217.124:2000'... - Simple Client Mode: - Received[194]: "IMPLEMENTATION" "dovecot"

Hello Dovecot users, Since the first release of the new Sieve implementation, not that many bugs were reported. This is probably due to the fact that it is not tried yet by that many people. In the mean time, I did find and fix some more bugs myself, I adapted to changes in Dovecot, wrote some more documentation and started work on the enotify extension. Both Sieve and ManageSieve were changed

cfb9d59a270b59fc485b14b7311762a60c6a922e=A0=A0=A0 refs/tags/v0.1.0=0A= 3d9024fafb0ca6413ab1287a417883d97dd186af=A0=A0=A0 refs/tags/v0.1.0^{}=0A= 55b70ccfaeb677ab4f579893de77cd9087449391=A0=A0=A0 refs/tags/v0.1.1=0A= 9ae4b5d0e765c366e9c019938157783504bfc738=A0=A0=A0 refs/tags/v0.1.1^{}=0A= ef62be5000a5742ed09527e170fd54c1897df054=A0=A0=A0 refs/tags/v0.1.2=0A=

Hello Dovecot users, Since the first release of the new Sieve implementation, not that many bugs were reported. This is probably due to the fact that it is not tried yet by that many people. In the mean time, I did find and fix some more bugs myself, I adapted to changes in Dovecot, wrote some more documentation and started work on the enotify extension. Both Sieve and ManageSieve were

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, I have finally updated the MANAGESIEVE patch to fix the currently known small problems with the protocol implementation. Also, I included a proxy implementation based on imap-proxy.c. This patch is designed for dovecot release 1.0.2 and it will not apply cleanly to the 1.1 versions yet. Change Log V5 ------------- - Applied patch by Uldis Pakuls to fix

I've been simultaneously learning about dovecot and experimenting with the 1.2.alpha4. To start I built an rpm under CentOS 5.2 from: dovecot-1.2.alpha4.tar.gz dovecot-1.2-managesieve-0.11.2.tar.gz dovecot-1.2.alpha4-managesieve-0.11.2.diff.gz dovecot-1.2.alpha4.tar.gz dovecot-1.2-sieve-0.1.2.tar.gz and then setup with mysql to use virtual users. Mail-wise, it all works. :)

download deb source http://ftp.debian.org/debian/pool/main/d/dovecot/dovecot_1.0.3-3.diff.gz http://ftp.debian.org/debian/pool/main/d/dovecot/dovecot_1.0.3.orig.tar.gz http://ftp.debian.org/debian/pool/main/d/dovecot/dovecot_1.0.3-3.dsc download managesieve patch http://sinas.rename-it.nl/~sirius/dovecot-1.0.3-MANAGESIEVE-v7.diff.gz extract deb source dpkg-source -x dovecot_1.0.3-3.dsc

Hello, I have here a problem with managesieve. With the login about webmail (roundcube) comes here in the log: --snip dovecot: managesieve-login: Fatal: pool_system_realloc(4294967296): Out of memory dovecot: managesieve-login: Fatal: master: service(managesieve-login): child 10157 returned error 83 (Out of memory (service managesieve-login { vsz_limit=1024 MB }, you may need to increase it))

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

Hello, On a dovecot 2.0.14 proxy, I found that proxying managesieve works well when using 'starttls' option in pass_attrs, but does not work when using 'ssl' option. The backend server is also dovecot 2.0.14; when using the ssl option, it reports "no auth attempts" in the logs about managesieve-login, and meanwhile the MUA, Thunderbird with sieve plugin, reports

> On 02 August 2018 at 16:08 Henrik Larsson <dovecot-user at spambox.dk> wrote: > > > On 15-07-2018 11:42, Henrik Larsson wrote: > > After upgrading Dovecot to 2.3.2.1 and Pigeonhole to 0.5.2, > > managesieve stopped working. > > > > I'm using FreeBSD ports tree, to build these. Only domains have been > > modified in below output. > >

Hi list I'm still trying to get managesieve running on centos x64 with the packages from atrpm. I used the 1.2.9 rpms (also rebuilt with the lastet managesieve patches) but I'm always getting the same error when trying to compile managesieve: ./configure --with-dovecot=/usr/lib64/dovecot/ --with-dovecot-sieve=/work/dovecot-1.2-sieve-0.1.14 (no errors) make gcc -DHAVE_CONFIG_H -I.

Hi, I?ve been a long-time user of Cyrus and started using sieve with Dovecot recently. A question that came up is: how do I access a users?s sieve scripts through managesieve without their credentials? Managesieve allows separating authentation and the corresponding mailbox identification, right? That?s what I used with cyrus sieve all the time. :) I didn?t find documentation in the wiki or

Hi, I have a "ubuntu10.04 + dovecot-2.0.13" configuration in my server. It works fine with ~50k accounts. Recently I enabled TLS: $ cat /etc/dovecot/dovecot.conf ... # Use SSL ? ssl = yes ... The goal was to provide only IMAPS and POP3S. But Managesieve says "STARTTLS": $ telnet _MY_IP_ 2000 Trying _MY_IP_... Connected to _MY_IP_. Escape character is '^]'.

Hi, does anyone got Dovecot ManageSieve and Horde/Ingo working together ? i'm running Dovecot 1.1.2 with managesieve patch (dovecot-1.1.2-managesieve-0.10.3.diff) following intructions at http://wiki.dovecot.org/ManageSieve now my Dovecot have ManageSieve available :-) I've setup Horde/Ingo (ingo-h3-1.1.5-1.el5) when I specify some new filtering rules in Ingo, they are successfully