Closed Coronon closed 1 year ago
A mailbox rate limit overrides a domain-wide rate limit. And disabled ratelimit is '0' and not '-1'
Thank you for the clarification :)
I knew about the override, but what does the default -1
imply then, and why do two emails minutes apart trigger a rate limit (mailcows defaults)? Could the fact that both domains are hosted on the same instance play a role in that?
-1 isn't default, maybe you changed your template? I don't know what -1 will do maybe @DerLinkman knows it?
I definitely didn’t change it for that user as it was freshly created. I also can’t remember changing anything like it on a higher level. But if the solution is to simply set them all to 0
, that’s simple enough I guess ^^
The question then becomes: Why does a value of -1
trigger a ratelimit ‘mailcow’ so fast, but not instantly?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
Contribution guidelines
I've found a bug and checked that ...
Description
Logs:
Steps to reproduce:
Which branch are you using?
master
Operating System:
Ubuntu 22.04.2 LTS
Server/VM specifications:
8GB Ram, 2 CPU cores
Is Apparmor, SELinux or similar active?
no
Virtualization technology:
Hetzner VPS
Docker version:
24.0.2
docker-compose version or docker compose version:
v2.11.2
mailcow version:
2023-05a
Reverse proxy:
Nginx
Logs of git diff:
Logs of iptables -L -vn:
Logs of ip6tables -L -vn:
Logs of iptables -L -vn -t nat:
Logs of ip6tables -L -vn -t nat:
DNS check: