Search results

  1. H

    Enable Before Queue filtering

    Many thanks for the feedback. Sounds good. @tom any ETA of the logs been available in the tracking center?
  2. H

    Enable Before Queue filtering

    Ah, ok, didn't read that. Then I will wait until that's "fixed" too. Do you have any ETA?
  3. H

    Enable Before Queue filtering

    @IEM would be happy for feedback on how/if it's working well/similar to my setup. Especially before queue is interesting for me, if I can then block (reject) in a legal manner on high spam score. And would be great, to see the logs in the tracking center as milter doesn't log there.
  4. H

    kam.cf

    Thanks, a bit too complicated for me. My script seems to work well. ;-) Thanks for bringing the loose updates to my attention.
  5. H

    [TUTORIAL] Advancing Proxmox Mail Gateway (especially Spam and Virus Detection)

    It should as it’s independent from DKIM. However, I don’t support it anymore as I won’t use it anymore. Too much effort for too less profit, ClamAV is worse, additional rules may get it a bit better but also introduce too much false positives. Avast is affordable and much better, where may still...
  6. H

    kam.cf

    Hi, I just was able now to upgrade the script somehow similar. And yes, spamassassin is part of my miltered setup. I will monitor now the update frequency, I just saw today, that were was an update yesterday. So I'm unsure on daily or hourly updates would be best or maybe I just hit "the date"...
  7. H

    kam.cf

    @Stoiko Ivanov Maybe you could also help? I got the script running, adjusted the paths as well and now also get the script "quiet", however, it's still recompiling every time, so I'm unsure on how to adjust the retval to get compilation only done on changes. #!/bin/sh # KatyComputer # # Simple...
  8. H

    kam.cf

    @KatyComputer I have two issues with the script, I try to get negotiated: 1. the download is been done "visible", so I get a mail on downloading, maybe I should need to adjust wget commands to include -q to be quite 2. I saw, that you added options for detecting changes and based on changes...
  9. H

    [TUTORIAL] Advancing Proxmox Mail Gateway (especially Spam and Virus Detection)

    After any changes on SpamAssassin handling you need to restart pmg-smtp-filter, to get them live, if you also also use my milter-reject you also need to restart spamassassin service. Rebooting is not required (but for sure also will restart the services). However, if you encounter any problems...
  10. H

    [TUTORIAL] Advancing Proxmox Mail Gateway (especially Spam and Virus Detection)

    A small update, I'm currently playing around with is https://forum.proxmox.com/threads/kam-cf.60114/ (however, adjusted it a bit, final setup will be posted, once I'm done). Thanks to @KatyComputer Short update on my plans BTW: PMG 6.1 has been released now with expected before-queue option...
  11. H

    Proxmox Mail Gateway 6.1 released!

    How is before-queue-filtering realized?
  12. H

    [TUTORIAL] Advancing Proxmox Mail Gateway (especially Spam and Virus Detection)

    Not my recommendation to purchase there. I believe, I posted https://www.antivirusedition.com/details_produit.php?p=avast_core_security_linux&lang=DE which was the cheapest pricing, I was able to find.
  13. H

    kam.cf

    Download URLs seems to be a bit outdated, if you look into KAM.cf. Does it help to work with the latest KAM.cf?
  14. H

    Konfiguration Plugins

    Hmm, das ist ja blöd. Ich dachte, dass die Slaves dann auch die Configs aus den Templatefiles schreiben, egal, ob da was zu rendern ist oder nicht. Soweit der Code nicht automatisch generell generierte Files synct, müsste man dann tricksen und im Zweifel in einen Kommentar bspw. eine Variable...
  15. H

    Spamassassin autolearn

    Train spam by yourself. Ham is working well, but spam need to be done manually. And It's better not to tweak as original setting is very conservative not to mis-train maybe-spam, which really may be no spam.
  16. H

    Konfiguration Plugins

    Thx, wenn es aber doch auf dem Master angelegt wird, wird es doch auch auf alle Nodes gesynct?
  17. H

    How about allow the GUI option to choose between reject_unknown_client_hostname and reject_unknown_reverse_client_hostname?

    +1 open a feature request in bugzilla.proxmox.com, I adjusted it manual. FCrDNS is really hard and not usable on business environments. On private, where you could loose mails because of lame administrators, everything is fine.