Displaying 20 results from an estimated 100 matches similar to: "Lua Push Notification Plugin"
2019 Apr 11
3
Lua Push Notification Plugin
Thanks AKI! I'm a step closer to achieving my goals.
However, I'm getting a new error as indicated from below:
Apr 11 01:45:34 lmtp(user at mydomain.com)<20801><pVlIEJ7wrlxBUQAAUdwEFQ>:*Debug: push-notification-ox: Skipped because not active
(/private/vendor/vendor.dovecot/pvt/server/vendor/vendor.dovecot/http-notify
METADATA not set)*
Apr 11 01:45:34 lmtp(user at
2020 Oct 16
2
lib22_push_notification_lua_plugin.so: undefined symbol: dlua_dovecot_register
I downloaded Dovecot from https://repo.dovecot.org/DOVECOT-REPO-GPG for /debian/buster. The library lib22_push_notification_lua_plugin.so is present but it doesn't have dlua_dovecot_register function.
Thanks,
Mrinal
-----Original Message-----
From: Aki Tuomi <aki.tuomi at open-xchange.com>
Sent: Friday, October 16, 2020 12:58 AM
To: Mrinal Sharma <msharma at smithmicro.com>;
2022 May 10
5
Dovecot v2.3.19 released
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
2022 May 10
5
Dovecot v2.3.19 released
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
2020 Aug 03
3
How to access mailbox metadata in Lua push driver
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
2020 Oct 15
2
lib22_push_notification_lua_plugin.so: undefined symbol: dlua_dovecot_register
I am trying to use Lua Notification plugin for Event push But saw this error. Can anyone help me on this issue. Error In the logs when I receive an Email is given below.
==========================================
Oct 15 21:55:41 master: Info: Dovecot v2.3.11.3 (502c39af9) starting up for imap, lmtp
Oct 15 21:56:51 lmtp(36): Fatal: Couldn't load required plugin
2020 Oct 16
0
lib22_push_notification_lua_plugin.so: undefined symbol: dlua_dovecot_register
Does it work if you load mail_lua as well?
So it would be something like
mail_plugins = ... mail_lua notify push_notification push_notification_lua
Aki
> On 16/10/2020 17:26 Mrinal Sharma <msharma at smithmicro.com> wrote:
>
>
> I downloaded Dovecot from https://repo.dovecot.org/DOVECOT-REPO-GPG for /debian/buster. The library lib22_push_notification_lua_plugin.so is
2020 Jan 26
0
Number of imap-login processes always keeps growing, never goes down
Hi all!
I've bumped into an issue which Dovecot which has me a bit stumped; All of a
sudden (ie. no obvious changes made to the config as far as I know) Dovecot
seems to never stop 'imap-login' processes. This continues to the point where
it will hit the 'process_limit'. For a 50-ish user install the limit was set to
100 but I increased it to 512. The only thing this changes
2020 Jul 21
2
Sieve and OX push_notification_drive seem to not work together
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
2015 Oct 28
1
events
Il 26.10.2015 12:04 Teemu Huovila ha scritto:
> On 26.10.2015 12:44, Frederik Bosch | Genkgo wrote:
>> 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
2020 Aug 03
2
How to access mailbox metadata in Lua push driver
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.
>>
>>
2015 Oct 26
3
events
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>
}
2020 Jul 21
0
Sieve and OX push_notification_drive seem to not work together
<!doctype html>
<html>
<head>
<meta charset="UTF-8">
</head>
<body>
<div>
</div>
<blockquote type="cite">
<div>
On 21/07/2020 13:35 Ralf Becker <<a href="mailto:rb@egroupware.org">rb@egroupware.org</a>> wrote:
</div>
<div>
</div>
2015 Oct 26
0
events
On 26.10.2015 12:44, Frederik Bosch | Genkgo wrote:
> 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/
2020 Jul 16
1
Questions about Dovecot push notifications
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.
2019 Oct 05
1
Home Directory Creation
<!doctype html>
<html>
<head>
<meta charset="UTF-8">
</head>
<body>
<div>
<br>
</div>
<blockquote type="cite">
<div>
On 05/10/2019 05:20 Asai via dovecot <
<a href="mailto:dovecot@dovecot.org">dovecot@dovecot.org</a>> wrote:
</div>
<div>
2019 Oct 04
2
Home Directory Creation
> On 04/10/2019 21:34 Asai via dovecot <dovecot at dovecot.org> wrote:
>
>
> On 10/4/2019 12:58 AM, Sami Ketola via dovecot wrote:
>
> > It depends heavily on how do you add users to your system. If you are using LDAP to store the user information then you can create the home directory at the same time you add the user to ldap.
> >
> > Sami
>
2020 Aug 03
2
How to access mailbox metadata in Lua push driver
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
2023 Jan 06
1
replicator: Panic: data stack: Out of memory when allocating 268435496 bytes
How problematic is it to have
default_vsz_limit = 0
in dovecot.conf? macOS+MacPorts had this as a requirement even.
Gerben
> On 6 Jan 2023, at 16:49, Paul Kudla <paul at scom.ca> wrote:
>
>
> i ran into this as well
>
> here is the full config for mine with replication
>
> # cat dovecot.conf
> # 2.3.14 (cee3cbc0d): /usr/local/etc/dovecot/dovecot.conf
> #
2023 Jan 07
1
replicator: Panic: data stack: Out of memory when allocating 268435496 bytes
ok a little bit more info ....
My servers all run under FreeBSD 12.xx
which was also the base for the apple operating system origionally.
setting default_vsz_limit = 0 i seem to remember trying with no so great
results
setting to zero can cause memory over runs (espically with replication)
etc i found that when i used the config i sent eariler (vsz_limit is
defaulted (not set )) everything