[Dovecot] patching dovecot for sieve/managesieve support, centos 5.6?
Scott Lewis
scott_the_musician at yahoo.com.au
Thu Nov 10 06:09:02 EET 2011
----- Forwarded Message -----
From: Scott Lewis <scott_the_musician at yahoo.com.au>
To: "dovecot at dovecot.org" <dovecot at dovecot.org>
Sent: Thursday, 3 November 2011 4:31 PM
Subject: patching dovecot for sieve/managesieve support, centos 5.6?
Hi all,
I am having real trouble when attempting to patch dovecot 1.2 to include the Pidgeonhole sieve support on my CentOS 5.6 x64 mail server. I am relatively new to the programming side of linux, but I am not having a lot of luck when trying to get this thing to compile.
Here's what happens:
[root at mail ~]# whereis dovecot
dovecot: /usr/sbin/dovecot /etc/dovecot.conf /usr/lib/dovecot /usr/libexec/dovecot /usr/share/man/man8/dovecot.8.gz
[root at mail dovecot-1.2-sieve-0.1.19]# ./configure --with-dovecot=/usr/lib/dovecot
...
checking whether to build static libraries... yes
dovecot-config not found from /usr/lib/dovecot, use --with-dovecot=PATH
to give path to compiled Dovecot sources or to a directory with the
installed dovecot-config file. configure: error:
dovecot-config not found
--
I get this message regardless of whether I set --with-dovecot as /usr/sbin/dovecot, or /etc, or /usr/libexec/dovecot.
I have SquirrelMail 1.4.22 running, and the avelsieve front-end seems happy enough. when I visit https://mail.mydomain.com/src/configtest.php, I get:
Avelsieve plugin details: backend = ManageSieve
ERROR: I could not determine the capabilities for Sieve Mail Filtering. Perhaps connectivity with ManageSieve server (if backend=Managesieve) is bad?
thanks in advance!
More information about the dovecot
mailing list