Search results

  1. D

    Exclude Quarantine and Spam for mailinglists

    Hello, We use the Spam quarantine and spam report from ProxMox. In our domain there are numerous mailinglists with sometimes more than 50 recipients. Now when we receive a SpamReport, the mail is forwarded to all 50 recipients, which is of course very inconvenient. Also turning off the...
  2. D

    Stop processing more rules

    Thank you, that seems to work.
  3. D

    Stop processing more rules

    Hello, we have a filter rule (Priotiry 81) that quarantines spams with a score higher than 3. Domains are defined in the WHO object. But now I want that for single email addresses within these domains spams are only marked and not moved to quarantine. Therefore I have created a new rule with...
  4. D

    Mail Header [X-Envelope-To] Problem

    The behavior is the same - with and without ProxMox. But in ProxMox I can change the header. I hoped with this I could solve the problem. Plesk support says: To be honest, I don't understand the behavior of Plesk with a catch-all. I guess that's because it actively forwards the mails to the...
  5. D

    Mail Header [X-Envelope-To] Problem

    We forward mails from ProxMox to a Plesk catch-all mailbox and download it from there with a mail client (Tobit). If an email with two or more recipients is now sent to Plesk, Plesk stores a separate mail in the system for each recipient. All these mails are completely identical. Unfortunately...
  6. D

    Mail Header [X-Envelope-To] Problem

    Hi Stoiko, theres nothing more than this in the rule: I just analyzed the logs again. I noticed that the sending mail server makes the difference. In one case, the mail server already initiates two sessions and transfers two individual mails to ProxMox. In the second case, the sending mail...
  7. D

    Mail Header [X-Envelope-To] Problem

    Hello, we have problems with mail delivery at one of our customers. Therefore, we have created a rule that creates the X-Envelope-To in the header and inserts the __RECIEVER__ there. This actually works quite well. However, depending on who sends the mail, we have different behavior, which the...
  8. D

    Forward spam mails to other recipient

    Thanks for your answer, but that's not what I want. So Proxmox can not do what I want unfortunately?
  9. D

    Forward spam mails to other recipient

    Hello, we have a mailserver behind the Proxmox which manages many mailinglists. If the Proxmox now detects a spam, all recipients of the mailing list get the spam report. I would like to prevent this. In best case I would like that only one spam administrator gets the spam report...
  10. D

    BAYES Training

    Hello all, we see in our PMG that more and more explicit spam mails are delivered to the recipients. Checking the logs, I see that these are getting a score of (-1.9) through BAYES_00. If I understand this correctly, BAYES should learn which mails are wanted and which are not. But by which...
  11. D

    ProxMox log4j / CVE-2021-44228

    Hi, can anyone tell if IceWarp is also affected by the log4j zero-day exploit? https://nvd.nist.gov/vuln/detail/CVE-2021-44228
  12. D

    Daily Spamreport Calendar

    Hello Stoiko, that was the solution. Thanks for the quick help
  13. D

    Daily Spamreport Calendar

    Hi, we want the email recipients to get the spam reports daily at 08am and at 4pm. We have used systemctl edit pmgspamreport.timer to modify the config file as described to: [Timer] OnCalendar=8,16:00 Persistent=false However, we still get another report every night at 00:05. Where is this...