We're pleased to announce the release of Proxmox Backup Server 4.2.
This version is based on Debian 13.4 ("Trixie"), uses Linux kernel 7.0 as the new stable default for improved hardware support, and comes with ZFS 2.4 for reliable...
See: https://pve.proxmox.com/pve-docs/chapter-sysadmin.html#sysboot_kernel_pin
by "pinning" the kernel with proxmox-boot-tool - you tell the boot-loader which kernel to boot, you can then install/upgrade the packages, and the pinned kernel would...
Thank you for getting back to me with this.
My copy and paste didn't actually reflect the formatting I copied out of the console web edition.
I did have a space before the section tag, but also the three dots. (never trust Google)
In all...
please use code tags for config-file listings (and don't remove complete lines/whitespace, as this is quite relevant in this context)
based on that output my guess is - that there is no new-line between the last line of the section mail and...
The logs would indicate that there was a network issue while trying to connect to those machines/IPs - try each of those ip's with netcat/telnet
are the mails still in the queue? - `mailq` or the GUI (Administration->Queues) should tell you.
Thanks for looking through openzfs issues - seems like this could indeed be a fix - I'll try to reproduce the issue here.
* Does your System have `/` on ZFS?
* how does the container config look like? (`pct config <vmid>`)?
* how does the zpool...
see - https://forum.proxmox.com/threads/proxmox-zfs-lxc-docker-container-oom-results-in-kernel-bug-at-mm-usercopy-c-102.182232/ - seems potentially similar
what kind of workload is running on the machine - lxc-containers? - do you see any other...
The issue is with the format of the e-mail, which does not pass the stricter parsing introduced due to:
https://forum.proxmox.com/threads/proxmox-mail-gateway-security-advisories.149333/post-838667
The options for fixing this (in order of...
Ist derzeit (noch) nicht implementiert - siehe: https://bugzilla.proxmox.com/show_bug.cgi?id=4651
steht auf unserer TODO list - aber ich kann nicht versprechen wann wir dazu kommen es zu implementieren.
Ich hoffe das hilft!
unprivileged ist prinzipiell zu bevorzugen (aus allgemeiner security sicht) - aber PMG sollte mit beidem funktionieren.
Allerdings muss bei einem unprivileged container nesting aktiv sein (wenn das nicht ist würde es wohl die Fehler gut...
Hi @Stoiko Ivanov, thank you for your reply. You nailed it. Of course I was too dense to enable TLS and now that it's on, the mails go through in both directions... I'm facepalming real hard right now. I have a handful of other servers in my logs...
did you restore a backup from your old gateway - or set it up freshly?
one guess based on the debug-output:
- your PMG does not seem to have TLS enabled - maybe the sending servers are configured to not send mails over the internet without TLS...
da würde ich nochmal das /var/log/apt/term.log (und history.log) vom system bei dem das upgrade fehlgeschlagen ist durchsehen - da sollte stehen wo es angefangen hat schief zu gehen.
sonst auch das journal durchsehen - da steht vl. noch warum die...
Im Prinzip ist empfohlen PMG mit einer statischen IP zu betreiben, und sicherzustellen, dass PMG seinen eigenen hostnamen auch auf eine tatsächliche IP (nicht in 127.0.0.0/8) auflösen kann (das geht mit einem passenden Eintrag in /etc/hosts)...
if the user clicks on welcomelist/blocklist for a mail it is added to _their_ user-welcome/blocklist - see:
https://pmg.proxmox.com/pmg-docs/pmg-admin-guide.html#pmgconfig_welcomelist_overview
not to the global one in the rulesystem.
I hope...
Yes, it will be sent to the sender of your spam. :)
You can avoid that, see https://www.postfix.org/postconf.5.html#postscreen_dnsbl_reply_map
You need to be aware that /etc/postfix/main.cf is generated by PMG.
For your change to be persistent...