similar to: [pigeonhole] disregards --with-ldap=no during compilation

FreeBSD 9.3 Dovecot 2.25 (7be1766) I'm trying to install Dovecot2-pigeonhole-0.4.14_2 from ports. Get an error: cc1: error: unrecognized command line option "-Wno-duplicate-decl-specifier" With options MAKE_JOBS_UNSAFE=yes: cc1: error: unrecognized command line option "-Wno-duplicate-decl-specifier" *** [edit-mail.lo] Error code 1 Stop in

Hi ? 1) I'm trying to compile a recent hg dovecot version (008632bdfd2c) at a FBSD10-STABLE system without success: libtool: compile: cc -DHAVE_CONFIG_H -I. -I../.. -I../../src/lib -I../../src/lib-test -I/usr/local/include -DUDHRDIR=\"../../src/lib-fts\" -DDATADIR=\"/usr/local/share/dovecot\" -DTEST_STOPWORDS_DIR=\"../../src/lib-fts\" -I/usr/local/include

http://dovecot.org/releases/2.0/dovecot-2.0.0.tar.gz http://dovecot.org/releases/2.0/dovecot-2.0.0.tar.gz.sig As promised last Friday, here's the v2.0.0 release finally. I'm cautiously optimistic that v2.0.1 won't (have to) be released for a few weeks, since there was quite a lot of testing and fixing going on in the RC stage. Remember to read http://wiki2.dovecot.org/Upgrading/2.0

http://dovecot.org/releases/2.0/dovecot-2.0.0.tar.gz http://dovecot.org/releases/2.0/dovecot-2.0.0.tar.gz.sig As promised last Friday, here's the v2.0.0 release finally. I'm cautiously optimistic that v2.0.1 won't (have to) be released for a few weeks, since there was quite a lot of testing and fixing going on in the RC stage. Remember to read http://wiki2.dovecot.org/Upgrading/2.0

http://dovecot.org/releases/2.2/dovecot-2.2.23.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.23.tar.gz.sig This is a bugfix-only release with various important fixes on top of v2.2.22. - Various fixes to doveadm. Especially running commands via doveadm-server was broken. - director: Fixed user weakness getting stuck in some situations - director: Fixed a situation where directors keep

http://dovecot.org/releases/2.2/dovecot-2.2.23.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.23.tar.gz.sig This is a bugfix-only release with various important fixes on top of v2.2.22. - Various fixes to doveadm. Especially running commands via doveadm-server was broken. - director: Fixed user weakness getting stuck in some situations - director: Fixed a situation where directors keep

I have dovecot 2.2.33 installed. When trying to install dovecot2-pigeonhole (v 0.4.19) I get the following when it tries to install dovecot 2.2.31_1 I run portsnap fetch update daily, and I ran it again after this error, but same result. ===> Installing for dovecot2-2.2.31_1 ===> Checking if dovecot2 already installed ===> Registering installation for dovecot2-2.2.31_1 as automatic

Am I correct: pigeonhole now wants the symlink to the filter file to use an absolute path instead of the relative paths we had? i.e.) sieve-filterfile@ -> /home/mail/domain/user at domain/roundcube.sieve instead of sieve-filterfile@ -> roundcube.sieve Dovecot logs these: dovecot: managesieve(user at domain.org): Warning: sieve-storage: Active sieve script symlink

I'm attempting to build Pigeonhole 0.2.3 for use with my Dovecot 2.0.12 installation on Slackware. I've downloaded the sources and unzipped into a folder which sits alongside the folder in which I built Dovecot. When I ./configure, the configuration appears to complete without error. However, when I make, the compiler throws lots of errors all stemming, I believe from its failure

What am I missing here: OS = FreeBSD 8.4 Here is how it fails during `gmake`: mv -f .deps/test_auth_cache-test-auth-cache.Tpo .deps/test_auth_cache-test-auth-cache.Po gcc -DHAVE_CONFIG_H -I. -I../.. -I../../src/lib -I../../src/lib-auth -I../../src/lib-test -I../../src/lib-dict -I../../src/lib-dns -I../../src/lib-http -I../../src/lib-sql -I../../src/lib-settings -I../../src/lib-old-stats

I'm experiencing the same problem as mentioned earlier in the mailing list. - Is there some kind of workaround for this issue? http://dovecot.org/pipermail/dovecot/2015-April/100549.html /S?ren

Hi Michael, I know about that EoL, but I do believe it has nothing to do with the failure to compile Dovecot, or does it? I am moving to new hardware and latest FreeBSD version soon. In the meantime, I need to run Dovecot on it. On 21 December 2017 at 01:16, Michael Grimm <trashcan at ellael.org> wrote: > Hi, > > Odhiambo Washington <odhiambo at gmail.com> wrote: >

# portmaster mail/dovecot-sieve ===>>> The dependency for mail/dovecot seems to be handled by dovecot2-2.2.22 ===>>> Initial dependency check complete for mail/dovecot-sieve ===>>> Starting build for mail/dovecot-sieve <<<=== ===>>> All dependencies are up to date ===> Cleaning for dovecot-sieve-1.2+0.1.19_2 ===>>> Waiting on

http://dovecot.org/releases/2.0/alpha/dovecot-2.0.alpha1.tar.gz http://dovecot.org/releases/2.0/alpha/dovecot-2.0.alpha1.tar.gz.sig So here's the first alpha version of Dovecot v2.0. There are still a couple of things left to do, but in general it should work for most people. I started using it for my own mails a few days ago and it seems to work without errors. Largest changes since v1.2:

http://dovecot.org/releases/2.0/alpha/dovecot-2.0.alpha1.tar.gz http://dovecot.org/releases/2.0/alpha/dovecot-2.0.alpha1.tar.gz.sig So here's the first alpha version of Dovecot v2.0. There are still a couple of things left to do, but in general it should work for most people. I started using it for my own mails a few days ago and it seems to work without errors. Largest changes since v1.2:

Hello, I'm trying to compile the sieve plugin for dovecot2 Dovecot2-beta6 is allready running and working. i did a hg clone http://hg.renamie-it.nl/dovecot-2.0-pigeonhole and ran the autogen.sh script as mentioned in the INSTALL file configure options: /configure --prefix=/usr --localstatedir=/var --sysconfdir=/etc --with-dovecot=/usr/lib/dovecot/ --with-managesieve=no compiling gives an

Hello! I'm mounting Windows 2000/XP disk drives from Linux RedHat 7.3 using smbmount. No problems, the disks are mounted. However, it disregards the "uid" and "gid" options and leaves the smbfs owned by "root" giving the "uid" user read-only access and not read-write as expected. Adding the "rw" doesn't help either.

Hi there I'm using dovecot-1.1b2/b3 with deliver. All information is stored in an SQL database and no errors related to this issue are written to the logs (actually I get no errors at all). I've run into at problem; FETCH BODYSTRUCTURE is broken after upgrading to dovecot 1.1b2 (same issue with 1.1b3). BODUSTRUCTURE only returns information from the first section (with incorrect

Could you send your configuration (output from `dovecot -n`)? Also, please provide an example scenario; i.e., for one problematic delivery provide: - The values of the variables substituted below. - The incoming e-mail message. - The Sieve script (or at least that vacation command). Regards, Stephan. Op 19-10-2016 om 11:42 schreef Matthew Broadhead: > hi, does anyone have any ideas

Also, please provide an example scenario; i.e., for one problematic delivery provide: - The values of the variables substituted in the dovecot-lda command line; i.e., provide that command line. - The incoming e-mail message. Regards, Stephan. Op 19-10-2016 om 12:43 schreef Matthew Broadhead: > dovecot is configured by sentora control panel to a certain extent. if > you want those