Michael, 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. Regards, Frederik 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
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
Thanks again. Final question: how do I configure this plugin? 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