similar to: Error compiling pigeonhole 0.3.0 with dovecot-2.1.5 in openbsd 5.0

Trying to build nut 2.6.0 on OpenBSD 4.8, I get a compiler error. Here's my configure: ./configure --with-user=_ups --with-group=_ups \ --sysconfdir=/etc/ups --with-usb=no ... and the result: -e Configuration summary: ====================== build serial drivers: yes build USB drivers: no build SNMP drivers: no build neon based XML driver: no build Powerman PDU client driver:

Hello all, I've squirrelmail-webmail-1.4.22, dovecot 2.1.1, dovecot-2.1-pigeonhole-0.3.0 installed and working. But I've problems to get the avelsieve plugin for squirrelmail working with dovecot. The "Message Filters" show up in "Options" of squirrelmail, but "Could not log on to timsieved daemon on your IMAP server ........." dovecot log shows: Mar 6

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.

I'm seeing a few warnings emitted when building for x86. They're pretty obvious, but if you want the configure options etc, I can provide those. In Dovecot 2.1.2 (I also see some of these in 2.1.1): 1) src/lib-index/mail-cache-fields.c (comparison between two last_used fields) mail-cache-fields.c: In function 'mail_cache_header_fields_read': mail-cache-fields.c:406: warning:

Hello Dovecot users, It's been a few months since the last Pigeonhole release. The main reason is that I've introduced a few big new features. Although the new features themselves probably haven't seen much testing so far, I'm now pretty confident that existing configurations are not broken by these changes. The biggest change is the addition of dict support for Sieve script

Hello Dovecot users, It's been a few months since the last Pigeonhole release. The main reason is that I've introduced a few big new features. Although the new features themselves probably haven't seen much testing so far, I'm now pretty confident that existing configurations are not broken by these changes. The biggest change is the addition of dict support for Sieve script

Hi, I recently compiled dovecot-2.1.1 on Solaris 10 with Sun Studio, but when I want to compile Sieve for this version (dovecot-2.1-pigeonhole-0.3.0) I get an error: "sieve.c", line 578: identifier redeclared: sieve_multiscript_run and I see that declaration in sieve.h is different from definition in sieve.c, so compilation process fails with SunStudio cc compiler. I have done a

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

How do you enable the imapsieve plugin? I added sieve_plugins = imapsieve and it whines: hebighonker.lerctr.org /usr/local/etc/dovecot/conf.d # service dovecot restart managesieve: Fatal: Plugin 'imapsieve' not found from directory /usr/local/lib/dovecot/sieve doveconf: Error: managesieve-login: dump-capability process returned 89 Stopping dovecot. Waiting for PIDS: 97491. managesieve:

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

Op 11/6/2016 om 5:39 PM schreef Larry Rosenman: > ok, I found: > https://github.com/dovecot/pigeonhole/blob/master/doc/plugins/imapsieve.txt > and that helps. > > Can this be added to the Wiki? Yes: http://wiki.dovecot.org/Pigeonhole/Sieve/Plugins/IMAPSieve > > On Sun, Nov 6, 2016 at 10:30 AM, Larry Rosenman <larryrtx at gmail.com> wrote: > >> How do you

We have used the great managesieve you have merged together, with sieve, to create pigeonhole. However, when a user creates a custom script through a GUI of ours, the default, as we expected, would be ignored. Maybe you could add a retain_sieve_global=yes|no setting OR be more complex by having the sieve_global_dir copied to the users sieve_dir on first managesieve script save, if another

it also appears that the above-captioned file is *NOT* in the tarball :( On Sun, Nov 6, 2016 at 10:39 AM, Larry Rosenman <larryrtx at gmail.com> wrote: > ok, I found: > https://github.com/dovecot/pigeonhole/blob/master/doc/ > plugins/imapsieve.txt > and that helps. > > Can this be added to the Wiki? > > On Sun, Nov 6, 2016 at 10:30 AM, Larry Rosenman <larryrtx

Hi Stephan, many thanks for all the work you do on the new sieve parts to dovecot. As a (downstream) packager I have some questions: a) pigeonhole is called a working title - will the final release be called something else like dovecot-sieve again? b) The versioning seems to go from 0.1.15 to 0.1.13. From a packager's POV it would be better to allow a natural version upgrade path.

http://dovecot.org/releases/2.0/beta/dovecot-2.0.beta1.tar.gz http://dovecot.org/releases/2.0/beta/dovecot-2.0.beta1.tar.gz.sig Now that v2.0 is in beta stage I don't expect anything big to change anymore. The configuration and the APIs shouldn't change in non-backwards compatible ways. There are still bugs left to be fixed and some small features to be implemented, but I'd like to

http://dovecot.org/releases/2.0/beta/dovecot-2.0.beta1.tar.gz http://dovecot.org/releases/2.0/beta/dovecot-2.0.beta1.tar.gz.sig Now that v2.0 is in beta stage I don't expect anything big to change anymore. The configuration and the APIs shouldn't change in non-backwards compatible ways. There are still bugs left to be fixed and some small features to be implemented, but I'd like to

Hello, I have two systems one with dovecot 2.2.31/Pigeonhole 0.4.19 selfcompiled through the src.rpms from ghettoforge on a CentOS 6.9 server and a second system of SOGo (3.2.9, nightly) on CentOS 7. Everything worked together until I made the update to Dovecot 2.2.31 Pigeonhole 0.4.19. Since then I get an error message when I try to upload a sieve-script. SOGo shows a message popup that

I got around to trying the 0.2.2 managesieve listener and it's not working for me. As soon as the client authenticates, the connection is closed and the following is logged on the server: > Dec 13 11:48:30 managesieve(xx at yy.com): Error: user xx at yy.com: Initialization failed: Namespace 'Mobile/': Unknown mail storage driver virtual > Dec 13 11:48:30 managesieve(xx at

Hi Folks, I am having a problem configuring imapsieve via dovecot-pidgeonhole on CentOS7. After following the docs here: https://wiki2.dovecot.org/Pigeonhole/Sieve/Plugins/IMAPSieve I get: dovecot[22026]: managesieve: Fatal: Plugin 'sieve_imapsieve' not found from directory /usr/lib64/dovecot/sieve dovecot[22026]: doveconf: Error: managesieve-login: dump-capability process returned 89