similar to: issues with doveadm sieve commands

Hi, > ------------------------------ > > Message: 2 > Date: Mon, 2 Apr 2018 22:06:07 +0200 > From: Michael Grimm <trashcan at ellael.org> > To: Dovecot Mailing List <dovecot at dovecot.org> > Subject: 2.3.1 Replication is throwing scary errors > Message-ID: <29998016-D62F-4348-93D1-613B13DA90DB at ellael.org> > Content-Type: text/plain; charset=utf-8

Ah yes. The hash I put below is wrong but the commit message I quoted was right. This is the last known working good commit, which was on Mar 6: https://github.com/dovecot/core/commit/ff5d02182573b1d4306c2a8c36605c98f217ef3b "doveadm: Unref header search context after use Fixes memory leak, found by valgrind" I've subsequently been able to determine that the bad commit was one of

Hi Andy, Funny you say that - I've been testing this very problem for some time today to narrow down the commits where I think the problem started occurring. So far I have been able to roll forward to commit from git: 74ef8506dcb946acc42722683e49fdcb964eed19 >> "doveadm: Unref header search context after use" . So far I have been running on that code for a few hours

Hello, I supose that a new version of pigeonhole is on the way because version 0.4.13 does not compile against dovecot 2.2.23 This is the error that I get gcc -DHAVE_CONFIG_H -I. -I. -I../../.. -I../../.. -I../../../src/lib-sieve -I../../../src/lib-sieve/util -I../../../src/lib-sieve/plugins/environment -I/home/jc/rpmbuild/BUILD/dovecot-2.2.23/src/imap

On 31/03/2016 02:06, Stephan Bosch wrote: > Hi, > > Op 3/30/2016 om 5:34 PM schreef Juan C. Blanco: >> Hello, I supose that a new version of pigeonhole is on the way because >> version 0.4.13 does not compile against dovecot 2.2.23 >> >> This is the error that I get >> >> gcc -DHAVE_CONFIG_H -I. -I. -I../../.. -I../../.. >>

Hi [This is Dovecot 2.3.1 at FreeBSD STABLE-11.1 running in two jails at distinct servers.] I did upgrade from 2.2.35 to 2.3.1 today, and I do become pounded by error messages at server1 (and vice versa at server2) as follows: | Apr 2 17:12:18 <mail.err> server1.lan dovecot: doveadm: Error: dsync(server2.lan): I/O has stalled, \ no activity for 600 seconds (last sent=mail_change, last

> On 14.05.2015, at 19:21, Stephan Bosch <stephan at rename-it.nl> wrote: > > On 5/14/2015 2:46 PM, Michael Grimm wrote: >> Hi ? >> >> I do have replication between two servers running, and mail is replicated without any issues. >> I do have sieve running at both servers without any issues. >> >> But replication of sieve scripts doesn't

On 5/15/2015 1:03 PM, Stephan Bosch wrote: > On 5/14/2015 9:32 PM, Michael Grimm wrote: >> On 14.05.2015, at 19:21, Stephan Bosch <stephan at rename-it.nl> wrote: >> On 5/14/2015 2:46 PM, Michael Grimm wrote: >>>> I do have replication between two servers running, and mail is replicated without any issues. >>>> I do have sieve running at both servers

Hi ? I do have replication between two servers running, and mail is replicated without any issues. I do have sieve running at both servers without any issues. But replication of sieve scripts doesn't work as "expected": Whenever I do modify my default script und upload it via "doveadm sieve put -u abc -a default < default" it becomes uploaded to the home directory of

I did eventually was forced to do this and setup a 2 node test environment with the latest dovecot: /usr/dovecot/sbin/dovecot --version 2.2.25 (7be1766) /usr/dovecot/sbin/dovecot --build-options Build options: ioloop=epoll notify=inotify ipv6 openssl io_block_size=8192 Mail storages: shared mdbox sdbox maildir mbox cydir imapc pop3c raw fail SQL drivers: mysql Passdb:

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

Hi -- I'm used to dsync my two mailservers running 2.0.16. Today, I did upgrade one server to 2.1, and doveadm sync is throwing to following error: mail> doveadm sync -f -u test ssh vmail at remote-host.tld dsync -v -f -u test doveadm(test): Fatal: All your namespaces have a location setting. It should be empty (default mail_location) in the namespace to be converted. Same error with

On 1/08/2016 10:01 AM, Stephan Bosch wrote: > Op 7/31/2016 om 4:27 AM schreef Reuben Farrelly: >> Hi, >> >> I've observed some odd behaviour with dsync replication between two >> hosts, specifically to do with sieve script replication. >> Has anyone else experienced the replication problem? Are sieve >> scripts actually replicating in live time for

Hi, I've observed some odd behaviour with dsync replication between two hosts, specifically to do with sieve script replication. In short, I have two hosts which replicate in a master-master type setup where almost all of the reads and writes happen to just one of the two hosts. They are both running 2.2.devel (9dc6403), which is close to the latest 2.2 -git . Pigeonhole is running

Still not quite right for me. Jun 7 15:11:33 thunderstorm.reub.net dovecot: doveadm: Error: dsync(lightning.reub.net): I/O has stalled, no activity for 600 seconds (last sent=mail, last recv=mail (EOL)) Jun 7 15:11:33 thunderstorm.reub.net dovecot: doveadm: Error: Timeout during state=sync_mails (send=mails recv=recv_last_common) I'm not sure if there is an underlying replication error

Hi all, New to the mailing lists but have joined up because of above */2.3.1 Replication is throwing scary errors /*Brief system configuration ??? MX1 - Main ??? ??? Freebsd 11.1-Release-p9 ??? ??? Hosted on a Vultr VM in Sydney AU ??? ??? MTA = Postfix 3.4-20180401 ??? ??? Dovecot = 2.3.1 ??? ??? File system = ufs ??? MX2 - Backup ??? ??? Freebsd 11.1-Release-p9 ??? ???? Running on

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

Hello, Thanks for the advice. I have looked for the libs and here is the difference: Dovecot production env 2.2.10: /usr/lib/dovecot/modules/doveadm rw-r--r-- 1 root root 18560 Jan 9 2014 lib10_doveadm_acl_plugin.so -rw-r--r-- 1 root root 14256 Jan 9 2014 lib10_doveadm_expire_plugin.so -rw-r--r-- 1 root root 10232 Jan 9 2014 lib10_doveadm_quota_plugin.so -rw-r--r-- 1 root root

Dear all, I encounter a strange issue with the *doveadm user* command. (dovecot 2.1.16) I try to retrieve information about a specific user but dovecot says it doesn't exist (whereas I just created it). The following command fails: $ sudo -u vmail doveadm user pouet at domain.tld userdb lookup: user pouet at domain.tld doesn't exist If I try a more global lookup, the user is properly

I would like to run various doveadm commands that involves all (mail) users like doveadm expunge -A mailbox Trash savedbefore 30d but any doveadm command that uses "-A" to iterate through all users will stop processing at the first account with UID<first_valid_uid. doveadm(sysdaemon): Error: user sysdaemon: Couldn't drop privileges: Mail access for users with GID 5551