October is Cybersecurity Awareness Month, which means it’s a good time for IT administrators and MSPs to review their email defenses. Email is still one of the most common ways attackers get into an organization. As we noted in our MSP post below, the FBI's Internet Crime Complaint Center logged more than $20.8 billion in reported losses in 2025, and business email compromise alone accounted for roughly $3 billion of that total.
Relying on users to configure their own mail clients can often lead to unexpected issues. A user enters the wrong port, picks STARTTLS where SSL was expected, or misspells the server name, and the result is often a help desk ticket.
Calendars are one of the features users notice most when they stop working, and one of the more common support requests from an administrator’s point of view. Where is the data stored? Which clients can connect? What do you need to back up so a restore brings calendars back intact?
On July 1, 2026, Microsoft raised list prices across most of its commercial Microsoft 365 products. This is the second consecutive year your email and productivity solution has gotten more expensive, and that has many businesses reevaluating their options.
When an MDaemon service stops unexpectedly - SMTP, Webmail, ActiveSync, or any of the others, every minute of silence is a minute your users aren’t sending or receiving mail. The good news is that you don’t need a third-party monitoring tool to catch these events. Windows ships with a built-in feature,
Performance Monitor, that can watch for a stopped service and send an email alert the moment it detects one.
Read More
This guide walks through the full setup end-to-end: creating the performance counter alert, adding it to a PowerShell script that sends you a notification email, and testing the whole chain so you can be confident it will work when you actually need it.
