Search results

Check the complete journal since boot for the actual cause of pve-cluster.service (pmxcfs) not starting: `journalctl -b` share the logs if you cannot find the root-cause.

Probably related or caused by: https://forum.proxmox.com/threads/fix-failed-to-start-the-proxmox-ve-cluster-filesystem.166984/ (please do not open multiple threads for one issue - it just causes twice the work)

Set the quarantine port 443 to have it without port 8006 in the URL Plain HTTP is not supported by pmgproxy - so if you _really_ want plain http you need to configure a proxy in front of pmgproxy - see: https://pmg.proxmox.com/wiki/index.php/Quarantine_Web_Interface_Via_Nginx_Proxy I hope this...

Abwesenheitsnachnrichten werden oft mit leerem Envelope-Sender verschickt - da gibts im Trackingcenter eine eigene checkbox, die aktiviert werden muss. (und danach kann nur nach dem Empfänger gesucht werden. - Tauchen die mails dann im Trackingcenter auf? Wegen DKIM - Wenn PMG das DKIM signing...

Adding a header multiple times ensures that the signature fails if someone in the middle injects another header (e.g. from) - it's also called oversigning - e.g.: https://forum.dmarcian.com/t/oversigning-headers-what-is-it-and-how-does-one-do-it/2462/2 I hope this explains it!

Virencheck ist im default-ruleset aktiv - zumindest für inbound mails (im Regelsystem kann dieser auch abgeschaltet werden) wie wurde die eicar-mail denn zugestellt - bei meinen tests funktioniert es zuverlässig, das eicar erkannt wird.

nothing changed in those code-paths recently how do your files look like (filenames)? - keep in mind that the log-tracker only checks /var/log/syslog, /var/log/syslog.1, /var/log/syslog.2.gz.../var/log/syslog.31.gz for data...

Check the logs of your VM and of the LXC - my guess is that clamav simply gets killed due to running out-of-memory. see https://pmg.proxmox.com/pmg-docs/pmg-admin-guide.html#system_requirements

might be - but it could also be due to the newer kernel expecting some things that were fixed in more recent version of BIOS/Firmware: seems there were some updates available for the board...

Additionally the complete mount-options might be interesting: ``` mount |grep nfs ```

To route mail to the internet through some other servive (mimecast in your case) in PMG you usually just need to set a smarthost - see: https://pmg.proxmox.com/pmg-docs/pmg-admin-guide.html#pmgconfig_mailproxy_relaying I hope this helps!

see: https://bugzilla.proxmox.com/show_bug.cgi?id=2505 If you do not configure before-queue filtering, and don't enable 'Send NDR on Blocked E-mails' in the mail proxy options a Block should not be sent to the sender. I hope this helps!

This says, that 10.0.0.200 (I guess your mailserver) says that management@######.it is not deliverable -> check the logs of 10.0.0.200 I hope this helps!

welche variable soll das genau sein? `pmgconfig dump` liefert dns.domain aber nicht pmg.domain? für dns.domain ist es der erste Eintrag der search domains in /etc/resolv.conf Siehe auch: https://pmg.proxmox.com/pmg-docs/pmg-admin-guide.html#_configuration_files_overview ich hoffe das hilft!

Der Block kommt daher, dass die sendende IP auf dnsbl.dronebl.org gelistet ist - es muss daher die IP erlaubt werden. Blocken auf diesem Level (postscreen) kann mit der mailproxy-whitelist umgangen werden (GUI->Configuration->Mail Proxy->Whitelist) - siehe hierzu auch die doku...

without reproducing it explicitly - the first issue I see is that the pmg.conf is synchronized across the cluster - so both would try to invoke avast - the one node where it's not available will log errors. I would not recommend this (and it's not supported) I hope this helps!

There is an article in the PMG wiki describing changing the hostname or ip - linked from the getting started page: https://pmg.proxmox.com/wiki/index.php/Getting_started_with_Proxmox_Mail_Gateway#Changing_Hostname_or_IP please try following this (and report if you run into issues, so we can...

Thanks! - my mistake - the module-load fails, thus i guess that zfs version fails. Do you get any more output from `modprobe zfs` ?

sent: https://lore.proxmox.com/all/20250414145705.1262110-1-s.ivanov@proxmox.com/T/#u

Thanks for the trace-file! I think the issue might be related to the following lines: 1109 14:24:25.334871 access("/dev/zfs", F_OK) = 0 ... 1109 14:24:25.335151 openat(AT_FDCWD</root>, "/dev/zfs", O_RDWR|O_EXCL|O_CLOEXEC) = -1 ENODEV (No such device) which I cannot reproduce locally. * Is...