search for: push_notification_driv

...i Admin, I hope you consider reading and addressing my concern promptly. For the past few days I've been setting up a VPS with cPanel and WHM pre-installed on Bluehost. I want to enable push notification plugin in Dovecot2.3.5. I tried OX and Lua plugins and got errors. For using OX plugin: push_notification_driver = ox:url=http://staging.mydomain.com/mail-notify/v1 user_from_metadata And got this error on runtime: *Error: push-notification-ox: Skipped because unable to get attribute: Mailbox attributes not enabled* When using Lua: mail_plugins = $mail_plugins mail_lua notify push_notification push_notif...

...g and addressing my concern promptly. > > For the past few days I've been setting up a VPS with cPanel and WHM > pre-installed on Bluehost. I want to enable push notification plugin in > Dovecot2.3.5. I tried OX and Lua plugins and got errors. > > For using OX plugin: > push_notification_driver = ox:url=http://staging.mydomain.com/mail-notify/v1 > user_from_metadata > And got this error on runtime: > Error: push-notification-ox: Skipped because unable to get attribute: Mailbox > attributes not enabled > mail_attribute_dict = file:%h/Maildir/dovecot-attributes > W...

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 o...

Teemu, If just need the http request, I will need something like the following configuration, right? So no meta data plugin, but with notify and push_notification? protocol lmtp { mail_plugins = $mail_plugins notify push_notification } plugin { push_notification_driver = ox:url=http://myurl/ <http://login:pass at node1.domain.tld:8009/preliminary/http-notify/v1/notify> } Regards, Frederik On 26-10-15 11:35, Teemu Huovila wrote: > > On 26.10.2015 09:45, Frederik Bosch | Genkgo wrote: >> Ah fantastic. Now I guess I can use notify plugin wi...

...est, I will need something like the >> following configuration, right? So no meta data plugin, but with >> notify and push_notification? >> >> protocol lmtp { >> mail_plugins = $mail_plugins notify push_notification >> } >> >> plugin { >> push_notification_driver = ox:url=http://myurl/ >> <http://login:pass at node1.domain.tld:8009/preliminary/http-notify/v1/notify> >> } > You could test that, but my understanding of the ox push driver code > is that it completely depends on metadata and will not do anything > useful, if no met...

...h > a different notifiction > - does anyone have a code snippet to send a JSON encoded message > (probably easy to figure out looking at Lua docu) these two I managed to solve im my current version of the script, which also support now all message event types: -- To use -- -- plugin { -- push_notification_driver = lua:file=/etc/dovecot/dovecot-push.lua -- push_lua_url = http://push.notification.server/handler -- } -- -- server is sent a PUT message with JSON body like push_notification_driver = ox:url=<push_lua_url> user_from_metadata -- local http = require "socket.http" local ltn12 = re...

...gt; <div> On 21/07/2020 13:35 Ralf Becker <<a href="mailto:rb@egroupware.org">rb@egroupware.org</a>> wrote: </div> <div> </div> <div> </div> <div> While it's documented that the OX push_notification_driver only supports </div> <div> MessageNew events, it does NOT generate any event if a Sieve script </div> <div> moves the message on arrival to an other folder, neither in INBOX were </div> <div> it original arrives by LMTP, nor in...

...gt; Teemu, > > If just need the http request, I will need something like the following configuration, right? So no meta data plugin, but with notify and push_notification? > > protocol lmtp { > mail_plugins = $mail_plugins notify push_notification > } > > plugin { > push_notification_driver = ox:url=http://myurl/ <http://login:pass at node1.domain.tld:8009/preliminary/http-notify/v1/notify> > } You could test that, but my understanding of the ox push driver code is that it completely depends on metadata and will not do anything useful, if no metadata is set. Perhaps Michael...

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

...{ special_use = \Sent } mailbox Trash { auto = no special_use = \Trash } prefix = } passdb { driver = pam } passdb { args = /etc/dovecot/dovecot-oauth2.plain.conf.ext driver = oauth2 mechanisms = plain login } plugin { push_lua_url = http://localhost:5678/mailnotify push_notification_driver = lua:file=/notify.lua quota = maildir:User quota quota_rule = *:storage=5MB quota_status_nouser = DUNNO quota_status_overquota = 552 5.2.2 Mailbox is full quota_status_success = DUNNO } protocols = imap lmtp service doveadm { inet_listener http { port = 80 } } service health-ch...

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.

Ah fantastic. Now I guess I can use notify plugin without push_notification metadata plugins, right? On 26-10-15 08:36, Teemu Huovila wrote: > > On 26.10.2015 08:59, Frederik Bosch | Genkgo wrote: >> Thanks again. Final question: how do I configure this plugin? > As the only existing driver at the moment is the OX one, the plugin is documented in OX wiki at >

...server -u%u > #dsync_remote_cmd = doveadm sync -d -u%u > > replication_dsync_parameters = -d -N -l 300 -U > > plugin { > mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename > mail_log_fields = uid, box, msgid, from, subject, size, vsize, flags > push_notification_driver = dlog > > sieve = file:~/sieve;active=~/sieve/.dovecot.sieve > #sieve = ~/.dovecot.sieve > sieve_duplicate_default_period = 1h > sieve_duplicate_max_period = 1h > sieve_extensions = +duplicate +notify +imapflags +vacation-seconds > sieve_global_dir = /usr/local/etc/do...

...h { special_use = \Trash } prefix = separator = / subscriptions = yes type = private } passdb { args = /etc/dovecot/dovecot-oauth2.conf.ext driver = oauth2 mechanisms = oauthbearer xoauth2 } passdb { args = /etc/dovecot/dovecot-ldap-passdb.conf.ext driver = ldap } plugin { push_notification_driver = ox:url=http://#hidden_use-P_to_show#@open-xchange.svc.sp-prod.nl1.cns.supersecretcorp.nl:8009/preliminary/http-notify/v1/notify user_from_metadata quota = count:User quota quota_rule2 = Trash:storage=+25M quota_vsizes = yes sieve = file:~/sieve;active=~/.dovecot.sieve sieve_max_action...

...doveadm sync -d -u%u >> >> replication_dsync_parameters = -d -N -l 300 -U >> >> plugin { >> ?mail_log_events = delete undelete expunge copy mailbox_delete >> mailbox_rename >> ?mail_log_fields = uid, box, msgid, from, subject, size, vsize, flags >> ?push_notification_driver = dlog >> >> ?sieve = file:~/sieve;active=~/sieve/.dovecot.sieve >> ?#sieve = ~/.dovecot.sieve >> ?sieve_duplicate_default_period = 1h >> ?sieve_duplicate_max_period = 1h >> ?sieve_extensions = +duplicate +notify +imapflags +vacation-seconds >> ?sieve_glo...

One step further in my quest to create a replacement mail server. I now have my old mail server (2.3.19.1, macOS + MacPorts) and my new (2.3.20, Alpine Linux, Docker, apk package). When I turn on replication it works, but, after a while I see: Jan 06 00:50:31 replicator: Panic: data stack: Out of memory when allocating 268435496 bytes Jan 06 00:50:32 replicator: Fatal: master:

Ultra short version: Why cant I set the following mailbox metadata key? /private/vendor/vendor.dovecot/pvt/server/vendor/vendor.dovecot/http-notify Let me explain the context: I'm using the Dovecot version 2.23.1, but the same happens for the 2.2.22 The push-notification plugin is supposed to send out a notification whenever a mailbox get a new email message. In order to tell if a mailbox

Hi all! We are pleased to release v2.3.19 of Dovecot. The docker images have been upgraded to use bullseye as base image. https://dovecot.org/releases/2.3/dovecot-2.3.19.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.19.tar.gz.sig Binary packages in https://repo.dovecot.org/ Docker images in https://hub.docker.com/r/dovecot/dovecot Regards, Aki Tuomi Open-Xchange oy -- + Added

Hi all! We are pleased to release v2.3.19 of Dovecot. The docker images have been upgraded to use bullseye as base image. https://dovecot.org/releases/2.3/dovecot-2.3.19.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.19.tar.gz.sig Binary packages in https://repo.dovecot.org/ Docker images in https://hub.docker.com/r/dovecot/dovecot Regards, Aki Tuomi Open-Xchange oy -- + Added