Recent content by DavidMerrill

Yes (hence the thank-you!), I shoud've mentioned that, glad to have the update! This kind of supply-chain vulnerability gives me the chills...

Anyone catch wind of this yet? https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-1946 https://nvd.nist.gov/vuln/detail/CVE-2020-1946 Thanks for getting the 6.4 update out!

This happened to me as well, refreshing the page (presumably refreshed the browser's cache?) resolved it.

Understood, thanks for the follow-up. Lastly (& please, take this kindly - I'm sure Proxmox folks have plenty to do), the Roadmap on the wiki is blank. I was hoping to find content related to where you hope to go as Proxmox develops or what current proxmox developments/projects...

OK great, thanks! Is there a public version of the TODO list (hate to press for things that are already in the works)?

I think for us we found this confusing because we've been asked to run the "daily" quarantine report (which reports on things quarantined "today") several times a day (and I'm now thinking that the designers intention was for deployments NOT to do this and rather depend on recipient...

Sorry, NM, found it here: - https://pmg.proxmox.com/wiki/index.php/Roadmap although it's blank, is it found elsewhere?

Thanks for confirming! Is it part of a roadmap (is there a roadmap for where PMG sees itself going)?

I was surprised to learn this (that actions in the users quarantine DON'T affect what's on the disk). It's been a couple years, Is this still how things work with quarantined spam?

Got it, /var/log/mail.log has lines like this: 552 5.3.4 Message size exceeds fixed limit

I've been trolling the logs, would I find a record of a rejection based on size in /var/log/mail.log?

Can anyone confirm if this is still the case? We'd love to get some of our clients access to the UI but want to lock them down to their domain(s).

PiotrM, did you ever sort out how to address deliveries related to domain aliases?