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...
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...
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...
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...
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...
Hi all
disclaimer: I work for Fujitsu, this is a semi-official posting but I hope it is not considered as advertising. ;)
I found a couple of discussions in this forum around recommended hardware and components for Primergy servers, so maybe...
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!
7.0 and 6.8 already contained the fix, 6.17 with the fix is on pve-test at the moment:
- proxmox-kernel-6.8.12-31-pve
- proxmox-kernel-6.17.13-16-pve
- proxmox-kernel-7.0.6-2-pve
Ok, problem gelöst.
Der Prozess pmg-smtp-filter läuft unter dem user pmg-smtp-filter der Mitglied der Gruppe pmg ist.
Nachdem man der Gruppe pmg schreibrechte auf den Ordner gibt, funktioniert das wieder.
Das Verhalten ist aber definitiv anders...
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.
https://app.opencve.io/cve/CVE-2026-53359
This won't get fixed in the 7.0.x kernel tree, but is fixed in kernel versions:
* 6.1.177
* 6.6.144
* 6.12.95
* 6.18.38
* 7.1.3
* 7.2-rc1
Reference...
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!
You may create a "Feature Request / Bug" over at https://bugzilla.proxmox.com/ (after looking if there is one similar already). That's the recommended place as it is more closely watched by the developers than this forum.
There are staff...
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 -...
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...