similar to: Error compiling pigeonhole managesieve 0.4.24

Yep On 10.08.2018 11:06, davide marchi wrote: > Thanks Aki for your quick response!! I'm sorry, so i have to compile > and install dovecot version 2.2.36 before compiling and install > pigeonhole 0.4.24? If so sorry for my noob approach > > Il giorno ven 10 ago 2018 alle ore 09:55 Aki Tuomi > <aki.tuomi at dovecot.fi <mailto:aki.tuomi at dovecot.fi>> ha scritto:

Hi! I try to compile pigeonhole from git-sources and get this error: libtool: link: gcc -std=gnu99 -g -O2 -fstack-protector-strong -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -fno-builtin-strfti me -Wstrict-aliasing=2 -I../.. -pie -Wl,-z -Wl,relro -Wl,-z -Wl,now -o .libs/sievec

Hi, I'm trying to compile the last mercurial release of dovecot-pigeonhole 2.0 and get this error: gcc -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -Wstrict-aliasing=2 -I/usr/kerberos/include -o .libs/sievec sievec.o -Wl,--export-dynamic ../../src/lib-sieve/.libs/libdovecot-sieve.so

Did you installed openssh? Tobias Hachmer <lists at kokelnet.de>??? >Hello list, > >Although timos bugfix release this morning I can't build pigeonhole 0.3.3 for >dovecot 2.1.12 successfully. I don't know if it is a new bug or if I do >something wrong but with dovecot 2.1.10 all worked fine, with the same configure >options. > >configure options (out of

Hello list, Although timos bugfix release this morning I can't build pigeonhole 0.3.3 for dovecot 2.1.12 successfully. I don't know if it is a new bug or if I do something wrong but with dovecot 2.1.10 all worked fine, with the same configure options. configure options (out of debian/rules for building debian package): ./configure --with-dovecot=/usr/lib/dovecot \

I'm trying to setup Dovecot-LDA. I grab dovecot beta8 and compiled it with the following options. $ ./configure --without-deliver --with-mysql $ make # make install It builds fine, and I have it running fine now. I then tried to build dovecot-lda from cvs, with the following. $ ./configure --with-dovecot=../dovecot-1.0.beta8/ $ make and it then fails with the following gcc -std=gnu99 -g

I'm compiling as I normally do. The config line for Dovecot is: configure --with-ldap --with-ssl --with-bzlib --with-zlib --with-stemmer --with-lucene --with-ldap followed by make & make install Then a 'configure' for Pigeonhole, followed by make, yields: libtool: link: gcc -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith

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

Hi, This (hopefully!) might be a case of user error, as I'm new to dovecot... Alternatively it might be some confusion in an index, since I've been mucking about trying different things in my configuration files and had frequent crashes. I'm trying to sync 2 (LAN) hosts, ideally to have full automatic replication happening. They both have hybrid mbox INBOX and maildir++ folders,

I had to manually quote in dovecot-config LIBDOVECOT_LOGIN='-ldovecot-login -lssl -lcrypto ' by default was LIBDOVECOT_LOGIN=-ldovecot-login -lssl -lcrypto That cause pigeonhole to failed. Regards nanashi

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

Hello Dovecot users, I've been busy recently with some wholly unrelated Dovecot IMAP patches, so Sieve development moved a bit into the background. This release therefore consists mostly of small bugfixes. The most important change is the fix of a bug in ManageSieve's CHECKSCRIPT command that causes a segfault. Quite a few people have encountered this problem recently, so it is about

Hello Dovecot users, I've been busy recently with some wholly unrelated Dovecot IMAP patches, so Sieve development moved a bit into the background. This release therefore consists mostly of small bugfixes. The most important change is the fix of a bug in ManageSieve's CHECKSCRIPT command that causes a segfault. Quite a few people have encountered this problem recently, so it is about

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 In working with auto vacation replies I'd like to do a sieve script as follows: require ["vacation"]; vacation :days 30 :addresses "cj.keist at colostate.edu" :subject "Out of Office" "***************** Out of Office ****************** I'm away -- send mail to foo in my absence

Hi, the dovecot-sieve plugin from the hg repository (http://hg.dovecot.org/dovecot-sieve-1.0/) does not build against current dovecot-1.0 repository. /bin/bash ../../libtool --tag=CC --mode=link gcc -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -DENABLE_REGEX -o sievec sievec.o map.o imparse.o

Hello Dovecot users, Finally, after little more than a year, I finished the first release of the new Sieve implementation for Dovecot. The main reason for rewriting the Sieve engine is to provide more reliable script execution and to provide better error messages to users and system administrators. Also, since the Sieve language evolves quickly, with new language extensions published every

Hello Dovecot users, Finally, after little more than a year, I finished the first release of the new Sieve implementation for Dovecot. The main reason for rewriting the Sieve engine is to provide more reliable script execution and to provide better error messages to users and system administrators. Also, since the Sieve language evolves quickly, with new language extensions published every

Dovecot 2.2.36 + Pigeonhole 0.4.24 Is this an intended behavior? ``` # service dovecot status dovecot is stopped # doveconf mail_plugins mail_plugins = stats # ls foo.* foo.sieve # sievec foo.sieve sievec(root): Error: stats: open(/var/run/dovecot/stats-mail) failed: No such device or address # echo $? 0 # ls foo.* foo.sieve foo.svbin ``` -- -- Name: SATOH Fumiyasu @ OSS Technology Corp.

Hello, I'm trying to figure out if this is a configuration issue or an actual bug. Dovecot does start, but if anybody tries to log in or if you run sievec you get an assertion fail and a coredump. --- sievec(root): Panic: file mail-namespace.c: line 709 (mail_namespace_find): assertion failed: (ns != NULL) sievec(root): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x9c3a2)

I get the source from CVS: # cvs -d :pserver:anonymous@dovecot.org:/home/cvs co dovecot-sieve Edit configure.in to change - AC_CONFIG_HEADERS([dsieve-config.h]) + AC_CONFIG_HEADERS(dsieve-config.h) Launch autogen.sh, and I have some errors: configure.in: 4: `automake requires `AM_CONFIG_HEADER', not `AC_CONFIG_HEADER' configure.in: 11: automake requires `AM_PROG_LEX', not