events

[Teemu Huovila]

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/ <http://login:pass@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 can correct me, if Im wrong.

If you want some subset of the ox driver functionality, you could try implementing your own driver, based on the existing code.

br,
Teemu

> 
> 
> 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 without push_notification metadata plugins, right?
>> Im not sure I understand the question correctly. I understood from the thread that you would be writing a driver for the push-notification plugin, so you need to load that plugin. In case you mean the imap_metadata = yes setting, you do not need that, if your driver does not use metadata.
>>
>> Teemu
>>
>>> 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
>>>> http://oxpedia.org/wiki/index.php?title=AppSuite:OX_Mail#Setup_of_the_Dovecot_Push
>>>>
>>>> br,
>>>> Teemu Huovila
>>>>
>>>>>
>>>>> On 23-10-15 16:12, Michael M Slusarz wrote:
>>>>>> On 10/22/2015 12:46 AM, Frederik Bosch | Genkgo wrote:
>>>>>>
>>>>>>> Thanks a lot! After looking at the source, I guess the ox driver will
>>>>>>> do. Maybe, when other people find this thread, you could tell what dlog
>>>>>>> is. Because I do not know it, and googling came up with little results.
>>>>>> "dlog" is nothing more than a push-notification backend that will log various information and hook triggers (at a DEBUG level) to the Dovecot log.  It's meant for debugging and development purposes.
>>>>>>
>>>>>> "dlog" stands for either "Dovecot LOGging" or "Debug LOGging", whichever you prefer.
>>>>>>
>>>>>> michael
>>>>>>
>>>>>>
>>>>>>> On 21-10-15 23:33, Michael M Slusarz wrote:
>>>>>>>> On 10/21/2015 9:07 AM, Frederik Bosch | Genkgo wrote:
>>>>>>>>
>>>>>>>>> We want to trigger a script after certain actions by the user (event).
>>>>>>>>> This script inserts the action into message queue (e.g. Rabbit MQ)
>>>>>>>>> accompanied with some data. Then one or more workers picks up the action
>>>>>>>>> from the message queue and do something with it. The question is: how
>>>>>>>>> can I trigger the script from dovecot?
>>>>>>>> This is precisely what the new push-notification plugin is for
>>>>>>>> (2.2.19).  (You will need to write a driver to interact with your
>>>>>>>> notification handler, similar to the "dlog" or "ox" drivers.)
>>>>>>>>
>>>>>>>> michael
>