Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Quota per domain #2887

Open
Quiwy opened this issue Jul 21, 2023 · 1 comment
Open

Quota per domain #2887

Quiwy opened this issue Jul 21, 2023 · 1 comment
Labels
priority/p2 Minor bug / Could have type/documentation Add or updates the documentation

Comments

@Quiwy
Copy link

Quiwy commented Jul 21, 2023

Environment & Version

Environment

https://test.mailu.io

Version

  • Version: master

Description

Not sure about domain quota vs user quota.

Replication Steps

  1. When editing a domain, set the Maximum user quota
    image
  2. On domain list, we see a filed named Quota
    image
  3. On user list, when checking individual quotas, we can see we are far above the quota defined in the domain
    image

Observed behaviour

It's not clear between steps 1 and 2 if this is a per domain quota limit or not, as fields don't have the same name.

Seeing 100 MB in domain list let me think that whatever the quota is for every user on that domain, the total number of emails can not be superior to the value set on the domain list. The field is more explicit when editing the domain as it says Maximum user quota

Expected behaviour

As the cli doc mentioned a max_quota_byte variable, I was thinking it was a max for all the domain. The variable name does not clearly mention it's for each user.

I was expecting to not receive new emails if the domain quota was reached.
Like we can do in postfix admin for example : image

So I'm uncertain if this is a bug, or a feature request (maybe both (label on domain list + having a global quota limit per domain)). As far as I didn't understand everything, I prefer to create an issue here.

Logs

@stale
Copy link

stale bot commented Aug 11, 2023

Issues not for bugs, enhancement requests or discussion go stale after 21 days of inactivity. This issue will be automatically closed after 14 days.
For all metrics refer to the stale.yml file.
Github issues are not meant for user support. For user-support questions, reach out on the matrix support channel.

Mark the issue as fresh by simply adding a comment to the issue.
If this issue is safe to close, please do so now.

@stale stale bot added the status/response_needed Waiting for a response from the author label Aug 11, 2023
@nextgens nextgens added priority/p2 Minor bug / Could have type/documentation Add or updates the documentation and removed status/response_needed Waiting for a response from the author labels Aug 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority/p2 Minor bug / Could have type/documentation Add or updates the documentation
Projects
None yet
Development

No branches or pull requests

2 participants