similar to: Support of INDEXPVT in Dovecot 2.3 with replication

We're currently using the OX push driver, which is straight forward (simple web hook) and allows to store (multiple) push tokens of our webmailer direct in mailbox metadata. Only drawback is that it only supports new arriving mails in the INBOX, even mails moved via Sieve to other folders are NOT reported. Therefore we updated now to Dovecot 2.3(.10.1) to also get mails moved by user or

Thanks Aki, I'll check it out :) Am 03.08.20 um 11:40 schrieb Aki Tuomi: >> On 03/08/2020 12:31 Ralf Becker <rb at egroupware.org> wrote: >> >> >> We're currently using the OX push driver, which is straight forward >> (simple web hook) and allows to store (multiple) push tokens of our >> webmailer direct in mailbox metadata. >> >>

Do both replication nodes need to be updated at the same time? Or can a 2.2(.36.4) node replicate with a 2.3(.10.1)? Ralf -- Ralf Becker EGroupware GmbH [www.egroupware.org] Handelsregister HRB Kaiserslautern 3587 Gesch?ftsf?hrer Birgit und Ralf Becker Leibnizstr. 17, 67663 Kaiserslautern, Germany Telefon +49 631 31657-0 -------------- next part -------------- A non-text attachment was

While it's documented that the OX push_notification_driver only supports MessageNew events, it does NOT generate any event if a Sieve script moves the message on arrival to an other folder, neither in INBOX were it original arrives by LMTP, nor in the folder Sieve moves the message. Is that a misconfiguration on my side, or a know / desired limitation or just a bug? I use LMTP to deliver

Some answers to my questions, a first version of my script and more questions ;) Am 03.08.20 um 18:15 schrieb Ralf Becker: > Currently looking into the following questions: > > - can I get the rfc 5423 type of event somehow (obviously I can set it > on the event myself depending of the function called) event.name > - looking at the example code, it looks like it can be called for

Hi Aki, Am 14.08.18 um 16:42 schrieb Aki Tuomi: > Hi, > > the thing I'm actually looking for is that whether the sync causes the folder to be restored, so it might be a better idea for you to try and spot this from the logs. I assume that as an SP that you are using mail_log plugin, so that might be useful to spot if this happens. You can also try looking at the UIDVALIDITY value of

I have a user who has several folders in his mailbox, which we can not delete, neither via IMAP nor via doveadm: root at ka-nfs-mail:~# doveadm mailbox list -u <username> | grep hbereiche | cat -v INBOX/[Fachbereiche ^M INBOX/Fachbereiche ^M INBOX/hbereiche^M INBOX/hbereiche/LAGen]^M INBOX/hbereiche/LAG^M INBOX/[Fachbereiche^M INBOX/[Fachbereiche/LAGen]^M INBOX/[Fachbereiche]^M

Am 14.08.18 um 18:51 schrieb Aki Tuomi: > Try > > doveadm mailbox list -u user INBOX/* Hmm, posted that before, it lists all these undeletable mailboxes: root at ka-nfs-mail:~# doveadm mailbox list? -u <username> 'INBOX/*' | grep hbereich INBOX/[Fachbereiche INBOX/Fachbereiche INBOX/hbereiche INBOX/hbereiche/LAGen] INBOX/hbereiche/LAG INBOX/[Fachbereiche

I need to run a mail-migration from a Dovecot with mail_attachment_dir / single instance storage enabled. As mailboxes and mail_attachment_dir are rsynced I would normally run a doveadm backup -u <user> -R -d dbox:<path to rsynced mailbox>/dbox How can I tell it the mail_attachment_dir the rsynced source / (reverse) destination uses? Or do I have to start a Dovecot process and use

Hi Aki, thanks for looking into this :) Am 14.08.18 um 15:15 schrieb Aki Tuomi: > can you turn on mail_debug=yes and run doveadm -Dv mailbox delete and > provide output and logs from both servers? root at ka-nfs-mail:~# doveadm -Dv mailbox delete? -u h 'INBOX/Fachbereiche ' Debug: Loading modules from directory: /usr/lib/dovecot Debug: Module loaded:

Am 14.09.17 um 01:07 schrieb Timo Sirainen: > On 7 Sep 2017, at 17.42, Ralf Becker <rb at egroupware.org> wrote: >> Dovecot 2.2.31 with mailboxes in mdbox format. >> >> Since a couple of days some mailboxes have the problem, that sieve rules >> moving mails to folders stop working and .sieve.log in mailbox shows: >> >> sieve: info: started log at Sep 07

I read the docu available under: https://doc.dovecot.org/configuration_manual/push_notification/ I'm using Dovecot 2.2.36.4 with directors and a replicating pair of backends using a custom dict with proxy protocol for user- and passdb plus a userdb using sqlite for backup. I understand 2.2 only allows to notify about new arriving mails, not eg. flag-changes which would require 2.3 with LUA.

Dovecot 2.2.31 with mailboxes in mdbox format. Since a couple of days some mailboxes have the problem, that sieve rules moving mails to folders stop working and .sieve.log in mailbox shows: sieve: info: started log at Sep 07 13:57:17. error: msgid=<20170907155704.EGroupware.S4yThVJRr12WSiJLpKbK0Bz at somedomain.egroupware.de>: failed to store into mailbox 'INBOX/Munser': Mailbox

Hi Timo, update to 2.2.32 (suggested by Aki) did not change the situation ... Am 18.09.17 um 20:49 schrieb Timo Sirainen: > On 18 Sep 2017, at 20.12, Ralf Becker <rb at egroupware.org > <mailto:rb at egroupware.org>> wrote: >> >> Hi Timo, >> >> Am 18.09.17 um 12:03 schrieb Timo Sirainen: >>> On 18 Sep 2017, at 12.10, Ralf Becker <rb at

One more update, I tried renaming that "[Test " folder to just "Test", which creates an also not deletable folder "Test". Good news is, if I delete these folders on both replication nodes from mdbox/mailboxes and mdbox/subscriptions they seem to be really gone. I can event create the folder "Test" again and it behaves normal aka. I can delete it afterwards

I have to reject office files for a certain domain plus notifying the original recipient about the rejection too. require ["fileinto","reject","body","enotify","variables"]; if allof (address :contains ["To","TO","Cc","CC"] "@example.org", body :content? "application/msword" :contains

Hi Aki, Am 18.09.17 um 11:22 schrieb Aki Tuomi: > On 18.09.2017 12:20, Ralf Becker wrote: >> Hi Aki, >> >> Am 18.09.17 um 11:13 schrieb Aki Tuomi: >>> On 18.09.2017 12:10, Ralf Becker wrote: >>>> Am 14.09.17 um 01:07 schrieb Timo Sirainen: >>>>> On 7 Sep 2017, at 17.42, Ralf Becker <rb at egroupware.org> wrote:

It happened now twice that replication created folders and mails in the wrong mailbox :( Here's the architecture we use: - 2 Dovecot (2.2.32) backends in two different datacenters replicating via a VPN connection - Dovecot directors in both datacenters talks to both backends with vhost_count of 100 vs 1 for local vs remote backend - backends use proxy dict via a unix domain socket and socat

Hi Timo, Am 18.09.17 um 12:03 schrieb Timo Sirainen: > On 18 Sep 2017, at 12.10, Ralf Becker <rb at egroupware.org > <mailto:rb at egroupware.org>> wrote: >> >> Am 14.09.17 um 01:07 schrieb Timo Sirainen: >>> On 7 Sep 2017, at 17.42, Ralf Becker <rb at egroupware.org >>> <mailto:rb at egroupware.org>> wrote: >>>> Dovecot

Hi Aki, Am 18.09.17 um 11:13 schrieb Aki Tuomi: > On 18.09.2017 12:10, Ralf Becker wrote: >> Am 14.09.17 um 01:07 schrieb Timo Sirainen: >>> On 7 Sep 2017, at 17.42, Ralf Becker <rb at egroupware.org> wrote: >>>> Dovecot 2.2.31 with mailboxes in mdbox format. >>>> >>>> Since a couple of days some mailboxes have the problem, that sieve