Search results

could you also try if the opt-in kernel 6.14 is affected? (`apt install proxmox-kernel-6.14` ) This information would indeed be helpful (and which driver is used)

Thanks for the effort and work! We found a system where we could potentially reproduce the issue - and will try to backport the patches you mentioned: https://lore.kernel.org/all/20250203162511.911946-1-Basavaraj.Natikar@amd.com/ Will post an update if there's any progress

Die Frage wird prinzipiell nur Domainfactory beantworten können - beim Blogpost scheint der Fehler zu sein, dass nicht das Templateing system verwendet wurde: https://pmg.proxmox.com/pmg-docs/pmg-admin-guide.html#pmgconfig_template_engine sonst hab ich noch folgendes gefunden (wahrscheinlich...

The issue with Realtek NICs is that their individual models actually represent quite a large array of slightly different NICs - which gain support eventually in the mainline 8169 driver - e.g. for some systems I've seen - a Realtek 8125 from Q2 2024 is supported by r8169 since kernel 6.2, while...

The quarantined data is not included in the backup - and can not be moved in this way. In general this is not an issue, as it's transient anyways and you can ask your users to release what they need before you do the switch (or keep your old install around for 30 more days) as the data is both...

The "Include empty Sender" includes mails sent with an empty Envelope-from (SMTP-level sender/ MAIL FROM.. - see https://en.wikipedia.org/wiki/Bounce_address) - the Tracking Center in general does look only at the syslog, and postfix usually does not log the from header. I hope this explains it

that is usually done by the postfix cleanup-daemon: https://www.postfix.org/cleanup.8.html glad you found the issue by yourself!

the complete journal of a failing boot (`journalctl -b` after you tried to start the VM and it fails) would help for beginning to debug this.

did you select the checkbox "Include Empty Senders" in the Tracking Center?

These settings are not exposed by PMG - so you need to adapt the postfix configuration. to make changes permanent use the templateing system: https://pmg.proxmox.com/pmg-docs/pmg-admin-guide.html#pmgconfig_template_engine I hope this helps!

das freut zu lesen! - Danke fürs Feedback!

There's a patch on the pmg-devel list that would add Auto-Submitted: auto-replied to the generated mail - this should suppress the autoreply as well: https://lore.proxmox.com/pmg-devel/20250310180612.21877-1-s.ivanov@proxmox.com/T/#t once this or an improved version has been applied an packaged...

Siehe ein paar Zeilen weiter unten (bei https://pmg.proxmox.com/wiki/index.php?title=Roadmap): sprich - einfach eine admin-mail-from Adresse eintragen, die signiert werden würde: https://pmg.proxmox.com/pmg-docs/pmg-admin-guide.html#_options Ich hoffe das hilft!

without checking explicitly if i remember correctly the database-sync (containing those entries) happens after the files are synced - so I'd first fix the one error you're having and then see if this resolves the issue what's the output of the command that files when run in a root-shell...

They are synchronized with the cluster-sync usually - do you see any errors with the sync in the past? could you share: * the output of `pmgcm status`? * journal from pmgtunnel and pmgmirror for a longer timeframe - and while you add one entry for one user ? * the output of `pmgsh get...

The complete logs of PMG are (like most modern Linux systems) in the journal - see `man journalctl`. For a particular mail the Tracking center also provides the logs. from the config you sent I really don't see how a mail sent from 151.248.236.202 to your PMG on the internal port would not be...

do you have modifications to the postfix config (mostly master.cf.in ) - that might rename postfix services? the Tracking Center is quite fast, but at the expense of being tightly relying on the logs having the expected formats ... I hope this helps!

If you have a subscription of level Basic or above - open a ticket at https://my.proxmox.com - there you'll get responses within a certain time frame - help in this forum is on a best-effort basis. else please share (in code-tags): * contents of /etc/postfix/main.cf * contents of...

you have selected "All Match" for your Whitelist who object... - that is most likely the issue

How are the priorities and configuration of your actual rules? - what is Quarantine/Mark Spam (Level 6), what is your Whitelist rule? (`pmgdb dump --rules active` provides a text overview)