Recent content by Stoiko Ivanov

CVE-2026-64564 should be fixed with 7.0.14-10 - 7.0.14-11 (additionally containing a fix for CVE-2026-68480) is already available on pve-test I hope this helps!

see https://pmg.proxmox.com/wiki/Roadmap#9.1-known-issues - pmg-smtp-filter now runs as different user. modifications look ok

no - and if you want to configure the PMG - for all your users as admin - use the rulesystem - create a rule with fitting priority that has a From domain-object `other-domain.net` , a To domainobject `my-domain.com` and action accept. As written in the docs...

PMG does not ship any packet-filtering/firewall by itself (see https://pmg.proxmox.com/pmg-docs/pmg-admin-guide.html#_easy_integration_into_existing_email_server_architecture). but you can check the usual firewall/packet-filtering software on linux - if you/someone else deployed a firewall...

see: https://bugzilla.proxmox.com/show_bug.cgi?id=4405 (and quite a few threads on this topic in this forum) for discussion on this topic. currently - adapting the postfix config templates to your need (keep in mind to check that no e-mails are rejected unexpectedly due to the change (by now...

this is the list each "user" (which is a mail-address in one of your relay domains) can manage on their own: https://pmg.proxmox.com/pmg-docs/pmg-admin-guide.html#pmgconfig_welcomelist_overview so you need to write/select the e-mail address of the user for who you want to add a foreign address...

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...