> On 23 Mar 2019, at 14.28, Tom Sommer via dovecot wrote:
>
> On 2019-03-21 10:28, Sami Ketola via dovecot wrote:
>>> On 20 Mar 2019, at 18.17, Tom Sommer via dovecot
>>> wrote:
>>> On 2019-03-20 16:40, Sami Ketola via dovecot wrote:
> On 20 Mar 2019, at 17.13, Tom Sommer via dovecot
On 2019-03-21 10:28, Sami Ketola via dovecot wrote:
On 20 Mar 2019, at 18.17, Tom Sommer via dovecot
wrote:
On 2019-03-20 16:40, Sami Ketola via dovecot wrote:
On 20 Mar 2019, at 17.13, Tom Sommer via dovecot
wrote:
I realize quota-service on Director is not supported, which is a
shame.
> On 20 Mar 2019, at 18.17, Tom Sommer via dovecot wrote:
>
>
> On 2019-03-20 16:40, Sami Ketola via dovecot wrote:
>
>>> On 20 Mar 2019, at 17.13, Tom Sommer via dovecot
>>> wrote:
>>> I realize quota-service on Director is not supported, which is a shame.
>>> As a workaround I'm
On 2019-03-20 16:40, Sami Ketola via dovecot wrote:
On 20 Mar 2019, at 17.13, Tom Sommer via dovecot
wrote:
I realize quota-service on Director is not supported, which is a
shame.
As a workaround I'm thinking of setting up quota-service on one of my
backend nodes, and have all my
> On 20 Mar 2019, at 17.13, Tom Sommer via dovecot wrote:
>
> I realize quota-service on Director is not supported, which is a shame.
>
> As a workaround I'm thinking of setting up quota-service on one of my backend
> nodes, and have all my Postfix services ask this one node for the quota
>
I realize quota-service on Director is not supported, which is a shame.
As a workaround I'm thinking of setting up quota-service on one of my
backend nodes, and have all my Postfix services ask this one node for
the quota status.
This sort of defeats the purpose of the Director (having
