you are using proxmox-boot-tool with grub, so you don't need systemd-boot and should remove it. you can then do the upgrade, and afterwards, install systemd-boot-efi and systemd-boot-tools (this is just so you can easily switch later on if you...
We are pleased to announce the first beta release of Proxmox Mail Gateway 9.0! The new version of our email security solution is based on Debian 13.1 "Trixie", but defaulting to the newer Linux kernel 6.14.11-2. The latest versions of ZFS 2.3.4...
We are pleased to announce the first beta release of Proxmox Mail Gateway 9.0! The new version of our email security solution is based on Debian 13.1 "Trixie", but defaulting to the newer Linux kernel 6.14.11-2. The latest versions of ZFS 2.3.4...
Thanks.
And yes, for the sake of anyone coming across this later on and skim reading, DO NOT do this unless there is a functional access restriction that limits the world from using your system - or it'll make you an open relay to everyone and...
to achieve your goal of letting anyone who has access to port 26 relay mails to anyone - this seems correct (did not test it explicitly)
In context of having a separate firewall which restricts access to port 26 in your setup - this can work -...
Why not (asking mostly to not overlook something)?
The only downside I currently see is that you'd need to create the DNS-entries for all domains (you can do so before switching and while keeping the record for the currently used selector in place)
We do not rely on npm for our user interfaces; the current Proxmox VE web interface uses only ExtJS and our own libraries.
Some of the projects we reuse use npm themselves though, such as xterm.js and noVNC, but we also vendor these completely...
see https://bugzilla.proxmox.com/show_bug.cgi?id=2742 - please record your interest there as this helps us prioritize which features to add in the future.
Not sure if I understand the question 100% correctly - but the scores depend on each mail:
* PMG uses SpamAssassin as its Spamdetector
* SpamAssassin gets updates to its rules quite often (they are stored in...
might be an interaction of the user's welcome list and a rule where you remove an attachment (or put it in attachment quarantine)...
could you share your ruleset and a mail which triggers the message (anonymize what you have to keep private -...
Hm - what exactly is your use-case? why is it better to drop a mail than sending it out without DKIM-signature?
Which mails in your environment are not signed (despite coming from domains of which are covered by your DKIM domains?
Maybe there's a...
Yes, my issue is solved.
You really should reword the "Sign all Outgoing Mail" option itself.
I would also like an option to block mail that pmg can't sign for any reason but that can go in another post or something.
so everything worked out? (just to make sure that was you original request).
regarding the "Sign all Outgoing Mail" - that was originally added and if it's enabled no prefix-matching is done and the mails simply take the complete domain as...
I got it!
I had to disable "Sign all Outgoing Mail" and add the apex domain to the "Sign Domains" list.
Despite sending email where both RFC5322.From and RFC5321.MailFrom were set to username@server.example.com, the signature was...
Thanks for the updates!
We adapted the pmg-api postinstallation to enable clamav-freshclam (unless it's explicitly masked by the admin):
https://git.proxmox.com/?p=pmg-api.git;a=commitdiff;h=cb8e149c9c257c47763a82f35f9eed9b4d95fc7b
I have a fresh install of Proxmox Mail Gateway that's a few weeks old now. And the service/daemon "clamav-freshclam" is NOT set to start automatically. This seems like an undesirable state of things, so I'm going to configure it to auto start...