search for: managesieved

I've found this in my dovecot.log: ,--[ /path/to/dovecot.log ]-- | Jul 11 01:44:29 dovecot: Info: Dovecot v1.2.1 starting up | ... | Jul 11 01:50:21 auth(default): Info: client in: AUTH 1 PLAIN service=sieve lip=192.168.111.222 rip=192.168.111.122 lport=12000 rport=35084 resp=<hidden> | Jul 11 01:50:21 auth(default): Info: sql(j.doe at

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

Hello, I use the debian packages from http://xi.rename-it.nl/debian/ version 1.1.7-0~auto+17 If I put a sieve script into /home/vmail/sieve-scripts/test.de/test.sieve it is used, so cmusieve works. But if I activate managesieve I get in the log: dovecot: 2008-12-14 21:24:49 Fatal: managesieve-login: USER environment missing dovecot: 2008-12-14 21:24:49 Error: managesieve-login: BYE

http://dovecot.org/releases/1.2/dovecot-1.2.4.tar.gz http://dovecot.org/releases/1.2/dovecot-1.2.4.tar.gz.sig I'll be on vacation for the rest of this week. I'll read my mails once in a while though. * acl: When looking up ACL defaults, use global/local default files if they exist. So it's now possible to set default ACLs by creating dovecot-acl file to the mail root

http://dovecot.org/releases/1.2/dovecot-1.2.4.tar.gz http://dovecot.org/releases/1.2/dovecot-1.2.4.tar.gz.sig I'll be on vacation for the rest of this week. I'll read my mails once in a while though. * acl: When looking up ACL defaults, use global/local default files if they exist. So it's now possible to set default ACLs by creating dovecot-acl file to the mail root

building, dovecot-2.0, HEAD:10054:5cb162da8708 dovecot-2.0-sieve, 1051:1d194d46d6e6 both build fine. @, dovecot-2.0-managesieve, 159:2236331aa0a3 cd /usr/local/src/dovecot-2.0-managesieve/ ./configure \ --with-dovecot=/usr/local/src/dovecot-2.0 \ --with-dovecot-sieve=/usr/local/src/dovecot-2.0-sieve make fails @, ... gcc -DHAVE_CONFIG_H -I. -I../..

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

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

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.

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

hi, i can't compile managesieve-0.11.11 on Solaris 10 against Sieve 0.1.17 and Dovecot 1.2.13: [...] gcc -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -I/usr/sfw/include -o managesieve-login client.o client-authenticate.o managesieve-capability.o managesieve-proxy.o cmd-noop.o

Hi, I've just tried to compile dovecot & pigeonhole in my openbsd box, and got this: gcc -DHAVE_CONFIG_H -I. -I../.. -I/home/seajob/build/dovecot-2.1.5 -I/home/seajob/build/dovecot-2.1.5/src/lib -I/home/seajob/build/dovecot-2.1.5/src/lib-dict -I/home/seajob/build/dovecot-2.1.5/src/lib-dns -I/home/seajob/build/dovecot-2.1.5/src/lib-mail

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

Hello, After upgrading to dovecot 2.3.0, my sieve filtering is broken. I managed it via roundcube's managesieve plugin. my emails are not being filtered accordingly into their folders and when i attempt to access the filter interface in roundcube, my maillog reports: Dec 28 12:05:07 mail roundcube: <gs7miohh> PHP Error: Unable to connect to managesieve on 127.0.0.1:4190 in

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 dovecot users, I have updated the MANAGESIEVE patch to the latest stable version of dovecot (1.0.7). This new version also adds extra configuration settings to explicitly specify the location of the sieve storage and the active sieve script. Additionally, the README now more clearly explains the configuration of the daemon. It currently won't compile with 1.1 due to significant changes

Hello dovecot users, I have updated the MANAGESIEVE patch to (hopefully) fix the compilation issues reported by Robin Breathe. 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 V6 ------------- - Corked the client output stream while producing the capability greeting and on other some

Hello, I've been trying to get managesieve to work for our LAN, but when I try to login from a remote host i always get the following line in the log file: dovecot: child 26014 (login) killed with signal 11 When i enable debuging, it just gives me that line, nothing more. I can only login from the localhost through telnet but not from a remote host. My conf: # 1.1.6: