-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
SPAM_TRAP makes spam delivered to other recipients #5897
Comments
I'm also having this happen. It took awhile to realise why it was happening, as the headers on the non spam trap users just show SPAM_TRAP as the rules, and a score of 0. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
Still an issue |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
Still an issue |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
Still an issue. Can someone please Triage this so milkmaker leaves it open |
Contribution guidelines
I've found a bug and checked that ...
Description
Logs:
Steps to reproduce:
Which branch are you using?
master
Which architecture are you using?
x86
Operating System:
Ubuntu 22.04 LTS
Server/VM specifications:
15Gi, 4 cores
Is Apparmor, SELinux or similar active?
yes
Virtualization technology:
KVM
Docker version:
26.0.1
docker-compose version or docker compose version:
v2.26.1
mailcow version:
2024-04
Reverse proxy:
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:
The text was updated successfully, but these errors were encountered: