On 04/25/2016 10:51 AM, Teemu Huovila wrote:
On 23.04.2016 10:01, giova...@giovannisfois.net wrote:
On 2016-04-22 09:07 PM, Timo Sirainen wrote:
On 22 Apr 2016, at 15:17, Giovanni S. Fois wrote:
In order to tell if a mailbox is enabled to send out the notification, the
plugin
looks out for
On 23.04.2016 10:01, giova...@giovannisfois.net wrote:
>
>
> On 2016-04-22 09:07 PM, Timo Sirainen wrote:
>> On 22 Apr 2016, at 15:17, Giovanni S. Fois
>> wrote:
>>> In order to tell if a mailbox is enabled to send out the notification, the
>>> plugin
>>> looks out for the following mailbox
On 2016-04-22 09:07 PM, Timo Sirainen wrote:
On 22 Apr 2016, at 15:17, Giovanni S. Fois wrote:
In order to tell if a mailbox is enabled to send out the notification, the
plugin
looks out for the following mailbox metadata key:
/private/vendor/vendor.dovecot/pvt/server/vendor/vendor.dovecot/h
On 22 Apr 2016, at 15:17, Giovanni S. Fois wrote:
>
> In order to tell if a mailbox is enabled to send out the notification, the
> plugin
> looks out for the following mailbox metadata key:
> /private/vendor/vendor.dovecot/pvt/server/vendor/vendor.dovecot/http-notify
>
> If the key is set then
[cut]
On 04/22/2016 02:57 PM, Teemu Huovila wrote:
Why cant I set the following mailbox metadata key?
/private/vendor/vendor.dovecot/pvt/server/vendor/vendor.dovecot/http-notify
Why do you want to set it there? Have you tried setting it on some mailbox path?
Do you mean by editing directly th
On 22.04.2016 15:17, Giovanni S. Fois wrote:
> Ultra short version:
>
> Why cant I set the following mailbox metadata key?
> /private/vendor/vendor.dovecot/pvt/server/vendor/vendor.dovecot/http-notify
Why do you want to set it there? Have you tried setting it on some mailbox path?
>
> Let me e