Search results

I opened a new thread here: https://forum.proxmox.com/threads/how-to-adjust-kam_from_uribl_pccc-as-of-many-false-positives.133059/ I tried the solution and it works. Need to be done by root account of the system (unsure about which Administrator you mentioned alternatively, this is Linux, here...

Got it and found my wrong setting on the wrong SA rule. So I removed and will retry and will then try to add the right one.

Thanks for response, I will retry and check, which entry result in the high scores. Meanwhile I restarted the system because of kernel updates, so pmg-smtp-filter also should have been restarted. However, I expected, that this will be done by the setting via UI?

Hi, somehow all my false-positives are resulting on KAM_FROM_URIBL_PCCC blacklisting them with very high score. I set as attached, but didn't change behavior, still score of 9. Regards Christian

I saw, you found it?

Please file a feature request at bugzilla.proxmox.com, so that this feature will be realized. In my advancing thread you can find a solution via header checks adding given from, subject as well. However, this is an adjustment and result in changing default behavior. Still looking for both since...

However, I would follow up on that, KAM_BODY_URIBL_PCCC has many false positives on my side. Anyone else has this issues? I was required to adjust the score to 0.

As of my last very time consuming thread on optimizing PMG I started a new philosophie with a fresh installation with somehow only adjustments via GUI or shell, which don’t change/touch the system itself, as all such changes like here break any time. So if you’re (also) looking for such feature...

I upgraded from a very old hard customized PMG based on Debian 9 as described in my Advancing Thread to a low customized new PMG based on Debian 11. This old version of PMG and Debian I had no issues with huge journal logs, but with the new PMG and Debian 11 I got now. I do a local backup and...

Thanks, that makes sense.

Addition: Thanks for the hint, checking the config values possible, I see, that it isn’t unlimited. The value per default is 10% of diskspace and keep 15% of diskspace free.

Before changing here anything, what are the Proxmox recommendations on this? Recently I rejoined an old discussion on how long log files should be stored because on privacy, storage and performance. An unlimited journal log then completely runs the opposite way than recommending smaller rotation...

root@pmg:~# pmgversion -v proxmox-mailgateway: 7.2-1 (API: 7.2-2/fe97dfd3, running kernel: 5.15.83-1-pve) pmg-api: 7.2-2 pmg-gui: 3.2-2 pve-kernel-5.15: 7.3-1 pve-kernel-helper: 7.3-1 pve-kernel-5.15.83-1-pve: 5.15.83-1 pve-kernel-5.15.74-1-pve: 5.15.74-1 clamav-daemon: 0.103.7+dfsg-0+deb11u1...

I‘m quite unsure, but won‘t believe that was the same for my recent PMG installation on Debian 9 (first PMG open source release)? I can’t remember such huge logfiles there. If I would set as above a limit on journald, will the tracking center still work as the syslog itself after relaying is...

This kernel update I was required to reboot. Will keep an eye on. However, apt(-get) autoremove doesn’t show anything for removal, but pvekclean does and sure, after rebooting, I switched the kernel and there is something to remove? Will keep trying what unattendedupgrades will do on old kernel...

Thanks, yes, I added it like this, however my question to the Proxmox team was more about if there are other options for updating (as if adding the PMG repository to the UI for e.g. non-subscription on no subscription) it is stating, that updates are encountered, however, nothing is telling...

I got a mail from apticron, next hours the kernel will be updated. I currently have this output: root@pmg:~# uname -a Linux pmg 5.15.74-1-pve #1 SMP PVE 5.15.74-1 (Mon, 14 Nov 2022 20:17:15 +0100) x86_64 GNU/Linux root@pmg:~# pmgversion -v proxmox-mailgateway: 7.2-1 (API: 7.2-2/fe97dfd3...

It seems like everything, which is (also?) logged elsewhere is logged here: Mailflow (smtpd), OpenVPN (which I set up), UFW (which I set up), ...

I now set up a new PMG with Debian 11. I recognized, that/var/log/journal is increasing from day to day. It looks like no rotation or limit at all. Is this typical? Is there any solution? About 11 days running I have on a low volume system now 1.1G

I will check and report with next kernel update