On a second thought, the previous suggestion doesn't seem to be what you are looking for. It looks like it only performs selective quota checking.
Sorry.
On 27/06/2021 10:45, Kevin N. wrote:
For the first part of the issue maybe you could use Postfix's smtpd_restriction_classes combined with Dovecot's quota_grace, as described in this older thread: https://dovecot.markmail.org/thread/5sa563icpv2os2nb#query:+page:1+mid:gkhwg...
I haven't tried it though.
Cheers,
Kevin
On 27/06/2021 05:32, dovecot@ptld.com wrote:
On 06-26-2021 7:39 pm, dovecot@ptld.com wrote:
First question: Is this the best way to configure dovecot using quota verification for postfix to work will aliases?
Second question: How can i prevent directories and indexes being created for non found user (aliases) accounts?
I figured out i was doing it wrong, i removed the "result_failure = return-ok" and used "quota_status_nouser = DUNNO" instead. However, now i have another concern.
- I setup an email account for user@example.com
- I setup an alias alias@example.com to forward to user@example.com
- I filled up user@example.com inbox so it would fail quota.
- I sent an email to alias@example.com
Postfix did not reject the email, it accepted it and tried to deliver to dovecot/lmtp which then rejected the message for being over quota. This caused postfix to have to send a back splatter bounce email. Anyway to solve that?
But worse, the bounce email exposed the forwarded to address of user@example.com saying mailbox full. "user@example.com (expanded from alias@example.com)"
What can be done about that? Keep the bounce notice from exposing the forward to address? Or is there still a better way to set this up?