Closed gergernaut closed 3 months ago
That does not only apply to postmaster recipient addresses, it applies also to all outgoing mails from any defined forwarding host, even when spamcheck is on. Thats a pity if you are operating services which send noreply mails, as those are not signed, and can lead even to being blocked.
@esackbauer and @gergernaut, if this turns out to be indeed a more widespread issue, then changing the subject of this ticket might be in order.
In our case, I can confirm that we're now running 2024-04
and that the last mail that has been signed that I have is from April 10th, whereas the first that is no longer signed is from April 23rd. This gives us only a rough idea when a possible change has happened, but none of the rspamd
related commits in that time-span change anything about the current behavior for me.
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
Which architecture are you using?
x86
Operating System:
Ubuntu 22.04.4 LTS
Server/VM specifications:
VM, 8GB/6 Cores
Is Apparmor, SELinux or similar active?
no
Virtualization technology:
KVM
Docker version:
26.0.0
docker-compose version or docker compose version:
v2.25.0
mailcow version:
2024-02
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: