-
-
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
Moving mails by functions.quarantine.inc.php to inbox failed #6104
Comments
m (PCRE_MULTILINE) '/^X-Spam-Flag: (.)/' , a mail has newlines. |
I had change Now X-Spam-Flag: is replaced and the mail is copied to inbox. From my point of view, may be a incomming mail has a X-Spam-Flag and respamd tag the mail as spam so X-Spam-Flag is in the mail. The preg_replace has never worked, but there is no problem with mails that are not tagged as X-Spam. I check mail from an other user, the mails in the junk folder has no X-Spam-Flag, so the moving works. I don't own exactly how mallow works. I think, it is a bug. |
A other thing. |
I'm not familiar with the quarantine code, so I am going to unassign this ticket from myself. |
From my point of view, the first step, independent of the source. |
I seem to have stumbled across the same problem: I'm usually very meticulous about sorting out my spam, and I'm very conscientious about moving spam that arrives in my Inbox to the Spam folder so that it will be treated as spam in the future. Similarly, I move emails that have been mistakenly treated as spam back to my Inbox. Unfortunately, with the current version (or maybe even earlier versions?), I can no longer move emails from the Spam folder back to the Inbox. Immediately after moving it from the Spam folder, the email is displayed in the Spam folder again and is missing in the Inbox. At the same time, I cannot find any errors in the container logs. I am relatively sure that this workflow worked in the past... Is this a bug or does it work as intended? Do I have to take the detour via quarantine in the Mailcow UI in the future? EDIT: The workflow should be valid according to the documentation:
|
take a look , with the soga webgui, in the raw maildata. so the problem could be that X-Spam-Flag: YES in some times are now in the mails. |
Yes, I can confirm. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
No php developer here? Question again: |
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:
Debian 6.1.90-1
Server/VM specifications:
8 GB / 4 core
Is Apparmor, SELinux or similar active?
no
Virtualization technology:
KVM
Docker version:
26.1.2
docker-compose version or docker compose version:
docker-compose version 1.29.2
mailcow version:
2024-08a
Reverse proxy:
ngnix
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: