Recent content by Stoiko Ivanov

please post the logs for such a mail - and verify that spam size is at least as large as the maximum message size.

2 minutes is the intervall in which the pmg cluster sync happens - so this is the cause here. The issue should only be cosmetic - postfix does restart (most of) its processes regularly - after a certain amount of time, and if it detects changes - and this has worked without any issue for a...

proxmox-kernel-6.17.13-16-pve-signed, which contains the fix is on pve-no-subscription. I hope this helps!

From the screenshot it seems that your rule does not have an Action object (Block or Quarantine) - thus nothing is done with the mail in that rule... I hope this helps!

Das hat sich mit PMG 9.1 geandert (davor lief pmg-smtp-filter als root) - siehe auch: https://pmg.proxmox.com/wiki/Roadmap#9.1-known-issues

systemd-boot is a boot-loader for UEFI booted systems - so for legacy BIOS boot it cannot be used anyways - you can remove it and systemd-boot-efi, systemd-boot-tools if your system is booted with legacy BIOS boot.

glad it fixed your issue! could you explain, what exactly did the trick? - just in case it's not an issue that only happened on your particular system - and there's something we can/need to improve in the postinst script? Thanks!

hmm - basierend auf den logs - sieht es so aus, als würden die mails von (potentiell übernommenen/gehackten) gmail accounts verschickt werden - nachdem in den allermeisten Situationen das blocken von gmail nicht möglich ist/keinen Sinn macht - und mails von gmail bei sonstigen Parametern sauber...

currently don't see why we'd need to run something from the temporary directories pmg uses - so `nosuid,noexec,nodev` should really not be a problem While this is a matter of taste - /opt is for third-party applications - and for me PMG is not a third-party application on a installation - so...

done now - as it seems sensible - hope that's ok for you @MichalCirrus

on a hunch - please compare the maximal message size (in the Mail Proxy Options) with the Maximal Spam Detector size - if the second is lower the issue is that the mail is not being shown to spamassassin completely which explains the modified body ... else please provide the complete logs to...

Your blocklist object lists: * '.*@warsawexpo.e.*` as regex * warsawaexpo.eu as domain the mail's envelope sender is: 'sm.21177883674.m9f0c8k9bh6zheoe05-zaproszenie=warsawexpo.eu@emsgrid.com' and does not match your object (there is no @ before warsawaexpo.e - so the regex does not match, the...

might indeed be the cause - check your configured LDAP profiles in the gui (and in /etc/pmg/ldap.conf) - is everything in place as it should be? EDIT: I just also checked your term.log - this one does state that the upgrade ran into errors: so probably explains the error - please try setting...

Could you please share: * the journal since the upgrade ran * /var/log/apt/history.log (from the time of the upgrade) * /var/log/apt/term.log (from the time of the upgrade) * `ls -laR /etc/pmg` * `ls -laR /var/lib/pmg` Thanks!

please do not double-post as this just splits the discussion into 2 places - posting a link here to the thread in the PVE forum for reference - and closing this one: https://forum.proxmox.com/threads/pve-cli-pc-%E2%80%94-a-remote-first-cli-for-proxmox-ve-and-datacenter-manager.184650/