ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Learn how to enable Gitpod Prebuilds, trigger a snapshot, and verify that workspace startup drops from several seconds to under a second.
Dovecot’s built‑in quota plugin lets providers enforce size and message limits per mailbox or domain with minimal overhead. This blog explains why it’s practical, shows how to configure file‑based or SQL backends, walks through a 100 MB domain quota example, and discusses trade‑offs and next steps.
The documented quota_rule capability sets mailbox size limits that Dovecot evaluates using file-system metadata. On a local ext4 volume the check is reliable and deliveries are rejected once the limit is reached. When the same mail directory is hosted on an NFS share the metadata can become stale or unsupported, causing the quota plugin to silently skip the
I'm evaluating whether to enable lazy_expunge = yes on a Dovecot 2.3.x server that hosts busy mailboxes in mdbox format. The documented behavior is clear in principle: expunged messages stay in storage and in the index until a later expunge pass, which avoids immediate disk I/O on the hot path. What I cannot pin down is the practical timing. If deleted messa
dovecot