Yup. The fact that it still has history and markers indicates there still is information in PMG to process, even if it isn't the full E-Mail message itself.
I don't see how that gives me what I was speaking to at all. I'm talking about going back through message log history, which clearly exists in PMG, and marking said content as "actually spam" (or equivalent) so that future spam analysis can be...
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...
So when I find a message in the logs that showed it was accepted/sent to the recipient, but it was actually spam, how can (in the webGUI) I mark said message as actually spam for PMG to learn from it? I'm not yet finding a way to do that (via...
This isn't about making it more secure, this is about NOT making it less secure by placating a bad idea which would tangibly make the supply chain of software less secure. I'm not going to sit here and give you the education you need on why...
This aspect SHOULD NOT rely on a third party from the Proxmox group itself. Those scripts are well intentioned, but are NOT sufficiently vetted for security functions. Proxmox VE clusters are used in many sensitive environments and this can lead...