I am preparing to migrate my SM instance from a Windows Server 2019 VM to a Windows Server 2025 VM.
While doing so, I am running tests to:
1) Enable automatic certificates (until now, I’ve used a single certificate for all domains—meaning one DNS name for SMTP, IMAP, webmail, etc.).
2) Put Spamfoo into production.
Regarding point 1, there are still a few things unclear to me, though I’ve opened a ticket and am awaiting a reply. However, I wanted to ask those of you already using it: which certificate algorithm are you using? The newer ES256 (ECDSA) or the older RS256 (RSA)? I’m not sure about the impact, having always used RS256 until now; I wonder how many clients are incompatible with ES256. One idea might be to keep the port binding certificate as RS256 while using ES256 for the SNI-based domain certificates.
That way, anyone experiencing issues can simply connect using the generic server DNS names.
As for Spamfoo, I’ve been monitoring it for over a month with a low threshold score of 2. Spot checks suggest it is accurate; I haven't found any false positives—though there are a few false negatives, which can be corrected through training.
That said, I still feel a dual-scoring system would be better—specifically, scores above 0.9 and below 0.9.
Currently, it only allows you to set a single threshold for spam vs. non-spam.
And what exactly does it consider "non-spam"? Below what score value?
For those already using it in production: what value have you set?
Regarding Windows Server 2025, I have to say the initial installation took a very long time—over 30 minutes. I had read on the forum here about slow installation times, including for updates. Is that confirmed?
Not so much to save money by using cheaper or slower disks, but for the benefit of faster restoration in the event of disaster recovery (read the post).