Differences

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

--- doc:appunti:linux:sa:postfix_spamassassin_clamav_dovecot [2021/05/24 16:58] – [Checking Dovecot Quota] niccolo
+++ doc:appunti:linux:sa:postfix_spamassassin_clamav_dovecot [2021/05/24 17:54] – [Troubleshoting Postfix quota-status service] niccolo
@@ Line 806: / 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
@@ Line 879: / Line 896: @@
 action=554 5.2.2 Quota exceeded (mailbox for user is full)
 </file>
+The **554 Quota exceeded error** should be returned when the **actual user's quota** plus the announced **size** will exceed the filesystem **soft quota** plus the **quota_grace** percentage.
 Another way to check the service using a single command line is using **netcat**: