<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On 20 Mar 2019, at 17.13, Tom Sommer via dovecot <<a href="mailto:dovecot@dovecot.org" class="">dovecot@dovecot.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">I realize quota-service on Director is not supported, which is a shame.<br class=""><br class="">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.<br class=""><br class="">This sort of defeats the purpose of the Director (having per-user assigned hot nodes), since now this one node running the quota-service will access all mailboxes to check the status of all inbound mail.<br class=""><br class="">Is this a problem though? In terms of NFS locking etc. etc.?<br class=""></div></div></blockquote></div><br class=""><div class=""><br class=""></div><div class="">Might be. Wouldn't it be just easier to use the overquota-flag available since 2.2.16 and set up overquota flag in LDAP or userdb of choice and configure postfix to check that flag?</div><div class=""><br class=""></div><div class=""><a href="https://wiki2.dovecot.org/Quota/Configuration" class="">https://wiki2.dovecot.org/Quota/Configuration</a></div><div class=""><br class=""></div><div class="">Sami</div><div class=""><br class=""></div></body></html>