Differences

This shows you the differences between two versions of the page.

--- doc:appunti:linux:sa:postfix_spamassassin_clamav_dovecot [2021/05/24 13:07] – [Multiple Sieve Scripts] niccolo
+++ doc:appunti:linux:sa:postfix_spamassassin_clamav_dovecot [2021/05/24 17:47] – [Dovecot quota status service for Postfix] niccolo
@@ Line 776: / Line 776: @@
 </code>
+**NOTICE**: The Dovecot's quota limit is the **soft limit** imposed by the filesystem.
 ==== Dovecot quota status service for Postfix ====
@@ Line 805: / Line 806: @@
 <file>
+# === WARNING ===
+# Both "quota_over_flag_value" and "quota_over_script" are
+# required, otherwise the Postfix quota-status check will always
+# return DUNNO (i.e. user is under quota). This is because
+# without those two parameters the quota check is skipped
+# completely, as seen in the mail_debug = yes log:
+# Debug: quota: quota_over_flag check: quota_over_script unset - skipping
+#
+# Actually we don't have a "quota_over_flag" field in userdb;
+# when quota-status service is called by Postfix, the value
+# quota_over_flag=0(*dummy*) is assumed due the config values
+# below. Current quota status for the user is then checked by
+# querying the filesystem and it will be 1 for overquota, 0
+# otherwise.
+#
+# As a side effect, the quota-warning script is executed at
+# every check if the user is overquota because 0 mismatches 1.
 plugin {
   quota_over_flag_value = FALSE