---
title: How to Use Performance Monitor to Notify an Administrator If an MDaemon Service Goes Down
description: Use Windows Performance Monitor, Task Scheduler, and a short PowerShell script to email an administrator the moment an MDaemon service stops. Step-by-step setup and testing guide.
image: https://blog.mdaemon.com/hubfs/banner-twitter.png
---

[![MDaemon Technologies](https://blog.mdaemon.com/hs-fs/hubfs/MDaemon-Technologies_logo_large.png?width=564&height=110&name=MDaemon-Technologies_logo_large.png "MDaemon Technologies")](https://mdaemon.com/)

- [Blog Home](https://blog.mdaemon.com)

# MDaemon Technologies Blog

## [How to Use Performance Monitor to Notify an Administrator If an MDaemon Service Goes Down](https://blog.mdaemon.com/mdaemon-performance-monitor-service-down-alerts)

 By [Brad Wyro](https://blog.mdaemon.com/author/brad-wyro)

- [Tweet](https://twitter.com/share)

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.

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.

## The Alert Chain at a Glance

Before diving into the configuration, here is the overall flow you will be building. Each box is a separate piece of Windows you will configure, in the order you’ll configure them.

![Architecture diagram showing the MDaemon service-down alert chain: MDaemon process stop, Performance Monitor, Task Scheduler, PowerShell, email and event log](https://blog.mdaemon.com/hubfs/Blog%20Media/mdaemon-alert-chain-diagram.jpg)

## Why Performance Monitor?

Performance Monitor (perfmon) is part of every supported version of Windows Server. It can watch a counter — such as whether the MDaemon process is running — and trigger an action when that counter crosses a threshold. Combined with Task Scheduler and a short PowerShell script, it becomes a lightweight, zero-cost alerting system that runs natively on the mail server itself.

The approach covered here works for:

- The core MDaemon service
- MDaemon Webmail (WorldClient)
- MDaemon Remote Administration
- MDaemon ActiveSync
- MDaemon XMPP Server
- Security Gateway components, where applicable

## Before You Begin

You’ll need the following in place:

- Administrative access to the Windows Server running MDaemon
- A working SMTP server **other than the MDaemon server you’re monitoring** — if MDaemon is the service that went down, you can’t send the alert through it. 
- PowerShell 5.1 or later (included with Windows Server 2016 and newer)
- An idea of which MDaemon services are business-critical in your environment

## Step 1: Identify the Process You Want to Watch

Performance Monitor tracks processes by their executable name (without the `.exe` extension). For the most common MDaemon services, those are:

- `MDaemon` — the core mail engine
- `WorldClient` — webmail
- `WebAdmin` — remote administration
- `MDSpamD` — ActiveSync service
- `WCXMPPServer` — XMPP/chat service 

Open Task Manager on your MDaemon server and confirm the exact process name under the **Details** tab. If you’re monitoring several at once, you’ll repeat the steps below for each one.

![Windows Task Manager Details tab showing the MDaemon.exe process running](https://blog.mdaemon.com/hubfs/Blog%20Media/mdaemon-task-manager-process.jpg)

Figure 1. Task Manager — Details tab, with MDaemon.exe running. The process name minus `.exe` (“MDaemon”) is what Performance Monitor will track.

## Step 2: Create the Alert Email Script

Before building the alert itself, create the PowerShell script it will run. Save the following to `C:\Scripts\Send-MDaemonAlert.ps1`, adjusting the parameters for your environment:

```
param(
    [string]$ServiceName = "MDaemon"
)

$smtpServer = "smtp.yourrelay.com"
$smtpPort   = 587
$smtpUser   = "alerts@example.com"
$smtpPass   = ConvertTo-SecureString "YOUR-APP-PASSWORD" -AsPlainText -Force
$credential = New-Object System.Management.Automation.PSCredential($smtpUser, $smtpPass)

$from    = "alerts@example.com"
$to      = "admin@example.com"
$subject = "[ALERT] MDaemon service '$ServiceName' is DOWN on $env:COMPUTERNAME"
$body    = @"
The Performance Monitor alert on $env:COMPUTERNAME has detected that the
MDaemon-related process '$ServiceName' is no longer running.

Time detected : $(Get-Date -Format 'yyyy-MM-dd HH:mm:ss')
Server        : $env:COMPUTERNAME
Service       : $ServiceName

Please investigate immediately.
"@

Send-MailMessage -From $from -To $to -Subject $subject -Body $body `
    -SmtpServer $smtpServer -Port $smtpPort -UseSsl `
    -Credential $credential
```

A few important notes:

- Storing the password in plaintext inside the script is convenient but not ideal. For a production environment, export the credential with `Export-CliXml` and import it at runtime, or use Windows Credential Manager.
- `Send-MailMessage` is marked as legacy by Microsoft but remains functional and is the simplest option for a script like this. If you prefer a modern alternative, install the `Send-MailKitMessage` module from the PowerShell Gallery and swap the cmdlet in.

Critical: don’t relay through MDaemon itself.

Point the relay at something other than the MDaemon server you’re monitoring. If MDaemon is the service that went down, an alert relayed through it will never leave the server. This is the single most common mistake people make with this setup.

Test the script on its own before moving on:

```
powershell.exe -ExecutionPolicy Bypass -File "C:\Scripts\Send-MDaemonAlert.ps1" -ServiceName "MDaemon (test)"
```

If the test email arrives, you’re ready to continue.

## Step 3: Wrap the Script in a Scheduled Task

Performance Monitor alerts trigger scheduled tasks, not scripts directly. Create the task Performance Monitor will call:

1. Open **Task Scheduler** (`taskschd.msc`).
2. In the Actions pane, choose **Create Task** (not Basic Task).
3. On the **General** tab, name it `MDaemon-Down-Alert`. Set it to **Run whether user is logged on or not** and check **Run with highest privileges**.
4. Skip the **Triggers** tab — Performance Monitor supplies the trigger.
5. On the **Actions** tab, click **New** and configure: 
     - **Action:** Start a program
     - **Program/script:** `powershell.exe`
     - **Add arguments:** `-ExecutionPolicy Bypass -File "C:\Scripts\Send-MDaemonAlert.ps1" -ServiceName "MDaemon"`
6. On the **Settings** tab, untick **Stop the task if it runs longer than** so a slow relay doesn’t cut the email off.
7. Click **OK** and supply the service account credentials when prompted.

Run the task manually once from Task Scheduler to confirm it sends the email correctly.

![Windows Task Scheduler Create Task dialog Actions tab calling powershell.exe with the Send-MDaemonAlert.ps1 script](https://blog.mdaemon.com/hubfs/Blog%20Media/mdaemon-task-scheduler-action.jpg)

Figure 2. Task Scheduler — Create Task, Actions tab. The action calls `powershell.exe` with the script path as the `-File` argument.

## Step 4: Create the Performance Counter Alert

Now the core piece: the alert that watches the process and triggers the task.

1. Open **Performance Monitor** (`perfmon.msc`).
2. In the left pane, expand **Data Collector Sets** → **User Defined**.
3. Right-click **User Defined** and choose **New** → **Data Collector Set**.
4. Name it `MDaemon Service Alert`, select **Create manually (Advanced)**, and click **Next**.
5. Choose **Performance Counter Alert** and click **Next**.
6. Click **Add**, expand **Process**, select the counter **ID Process**, and under *Instances of selected object* pick `MDaemon` (or whichever process you’re monitoring). Click **Add**, then **OK**.
7. Set **Alert when** to **Below**, and **Limit** to `1`. This means “fire the alert whenever the process has no valid ID — in other words, when it isn’t running.”
8. Click **Next**, keep the default save location, and choose **Finish**.

![Performance Monitor Create new Data Collector Set wizard, Process MDaemon ID Process counter selected with Alert when Below 1](https://blog.mdaemon.com/hubfs/Blog%20Media/mdaemon-perfmon-counter-alert.jpg)

Figure 3. Performance Monitor — Create new Data Collector Set wizard, with the `\Process(MDaemon)\ID Process` counter and **Alert when: Below 1**.

By default the alert only checks every 15 seconds. You can tighten or loosen this:

1. In **User Defined**, click `MDaemon Service Alert`.
2. In the right pane, right-click `DataCollector01` and open **Properties**.
3. On the **Alerts** tab, confirm the counter and threshold.
4. On the **Alert Action** tab, tick **Log an entry in the application event log** so you have an audit trail even when the email succeeds.
5. On the **Alert Task** tab, enter `MDaemon-Down-Alert` (the task you created in Step 3). In **Task arguments**, you can pass `MDaemon` or another label so the email identifies the specific service.
6. Set **Sample interval** (on the parent Data Collector Set’s properties) to something sensible — every 30 or 60 seconds is usually right. Too aggressive a sample adds overhead; too relaxed and you’ll wait minutes to find out.

![Performance Monitor DataCollector01 Properties dialog, Alert Task tab pointing at the MDaemon-Down-Alert scheduled task](https://blog.mdaemon.com/hubfs/Blog%20Media/mdaemon-perfmon-alert-task.jpg)

Figure 4. `DataCollector01` Properties — Alert Task tab, pointing at the `MDaemon-Down-Alert` scheduled task with “MDaemon” passed as the task argument.

Right-click the `MDaemon Service Alert` data collector set and choose **Start**. To have the alert survive reboots, open its properties and, on the **Schedule** tab, add a schedule that starts the collector when you want it running, or simply configure it to auto-start via the collector set’s **Properties → General** tab.

## Step 5: Repeat for Each Service You Care About

The same pattern works for Webmail (WorldClient), MDRemote, ActiveSync, and any other component. You can either:

- Create one data collector set per service, each pointing at a task that passes a different `-ServiceName` argument, or
- Create a single data collector set with multiple counters, one per process, and let the script log which one fired.

Most administrators find the one-per-service approach easier to reason about when something goes wrong.

## Step 6: Test It End-to-End

To test, open the **Services** console (`services.msc`), and stop the MDaemon service. Within your configured sample interval you should see:

- An entry in the **Application** event log from the `Diagnosis-PLA` source indicating the alert fired
- An email in your administrator inbox from the PowerShell script
- The Task Scheduler history for `MDaemon-Down-Alert` showing a successful run

Start the service again afterwards. If any link in the chain failed, the event log on the MDaemon server is usually the fastest place to find out which one.

## A Few Hardening Tips

Once the basics are working, a handful of small improvements make a big difference in production:

- **Configure Windows Service Recovery as a first line of defense.** In `services.msc`, open the MDaemon service’s properties, go to **Recovery**, and set the first and second failures to **Restart the Service**. This often resolves the outage before your alert ever needs to fire — but keep the alert anyway, because you want to know it happened.
- **Send alerts to a distribution list, not a single mailbox.** If the only person who gets the alert is on vacation, the alert is effectively useless.
- **Consider a second channel.** Email is fine for business hours but easy to miss overnight. The same PowerShell script can push to a Microsoft Teams webhook, trigger an SMS via Twilio, or post to a Slack channel in just a few extra lines.
- **Monitor the monitor.** Configure a weekly test; even just a scheduled run of the script with a “this is a test” subject, so you know the relay credentials haven’t expired and the script still runs.

## Wrapping Up

With Performance Monitor, Task Scheduler, and a short PowerShell script, you get the same “tell me the moment something breaks” behavior that dedicated monitoring suites provide, using only what’s already installed on the server. It takes about fifteen minutes to set up the first time and a couple of minutes to extend to each additional MDaemon component.

If MDaemon is central to how your organization communicates — and for most of our customers, it is — that investment pays for itself the first time it catches an outage before your users do.

 Tags: [MDaemon Email Server](https://blog.mdaemon.com/topic/mdaemon-email-server), [Tutorial](https://blog.mdaemon.com/topic/tutorial), [Email Server](https://blog.mdaemon.com/topic/email-server), [SecurityGateway](https://blog.mdaemon.com/topic/securitygateway), [MDaemon](https://blog.mdaemon.com/topic/mdaemon), [Monitoring](https://blog.mdaemon.com/topic/monitoring), [Windows Server](https://blog.mdaemon.com/topic/windows-server)

![Brad Wyro](https://blog.mdaemon.com/hs-fs/hubfs/Brad-2023v2.jpg?width=100&height=100&name=Brad-2023v2.jpg)

#### Written by [Brad Wyro](https://blog.mdaemon.com/author/brad-wyro)

Brad has worked in technical and marketing roles at MDaemon Technologies, where he contributes as Content Marketing Manager. Brad balances technical and creative information to develop easy to understand videos and content to educate prospects and customers.

[![BACK TO ALL ARTICLES](https://hubspot-no-cache-na2-prod.s3.amazonaws.com/cta/default/6572702/05b24dbb-70a6-4eaa-9507-321cb27f7228.png)](https://hubspot-cta-redirect-na2-prod.s3.amazonaws.com/cta/redirect/6572702/05b24dbb-70a6-4eaa-9507-321cb27f7228)

### Subscribe to Email Updates

- [Popular](https://blog.mdaemon.com/mdaemon-performance-monitor-service-down-alerts#tab-2)
- [Recent](https://blog.mdaemon.com/mdaemon-performance-monitor-service-down-alerts#tab-1)
- [Categories](https://blog.mdaemon.com/mdaemon-performance-monitor-service-down-alerts#tab-3)

### Lists by Topic

- [Email Security (72)](https://blog.mdaemon.com/tag/email-security)
- [MDaemon Email Server (45)](https://blog.mdaemon.com/tag/mdaemon-email-server)
- [Email How To (37)](https://blog.mdaemon.com/tag/email-how-to)
- [Email Best Practices (29)](https://blog.mdaemon.com/tag/email-best-practices)
- [Phishing (28)](https://blog.mdaemon.com/tag/phishing)
- [Product Updates (28)](https://blog.mdaemon.com/tag/product-updates)
- [Security Gateway for Email (27)](https://blog.mdaemon.com/tag/security-gateway-for-email)
- [Stop Spam Email (25)](https://blog.mdaemon.com/tag/stop-spam-email)
- [Cybersecurity (24)](https://blog.mdaemon.com/tag/cybersecurity)
- [Email Security Best Practices (22)](https://blog.mdaemon.com/tag/email-security-best-practices)
- [Email Server (22)](https://blog.mdaemon.com/tag/email-server)
- [Two-Factor Authentication (18)](https://blog.mdaemon.com/tag/two-factor-authentication)
- [Email Gateway How-To (17)](https://blog.mdaemon.com/tag/email-gateway-how-to)
- [Email Security Trends (15)](https://blog.mdaemon.com/tag/email-security-trends)
- [Health Care Security (12)](https://blog.mdaemon.com/tag/health-care-security)
- [SecurityGateway (12)](https://blog.mdaemon.com/tag/securitygateway)
- [Spear Phishing (12)](https://blog.mdaemon.com/tag/spear-phishing)
- [Data Leak Prevention (11)](https://blog.mdaemon.com/tag/data-leak-prevention)
- [Email Encryption (11)](https://blog.mdaemon.com/tag/email-encryption)
- [Anti-Spoofing (10)](https://blog.mdaemon.com/tag/anti-spoofing)
- [MDaemon Webmail (10)](https://blog.mdaemon.com/tag/mdaemon-webmail)
- [Email Archiving (8)](https://blog.mdaemon.com/tag/email-archiving)
- [Email Management (8)](https://blog.mdaemon.com/tag/email-management)
- [Email Privacy (8)](https://blog.mdaemon.com/tag/email-privacy)
- [Email Spoofing (8)](https://blog.mdaemon.com/tag/email-spoofing)
- [Business Email Compromise (7)](https://blog.mdaemon.com/tag/business-email-compromise)
- [Anti-Virus (6)](https://blog.mdaemon.com/tag/anti-virus)
- [Email Software (6)](https://blog.mdaemon.com/tag/email-software)
- [Tutorial (6)](https://blog.mdaemon.com/tag/tutorial)
- [Update (6)](https://blog.mdaemon.com/tag/update)
- [Collaboration (5)](https://blog.mdaemon.com/tag/collaboration)
- [Email Authentication (5)](https://blog.mdaemon.com/tag/email-authentication)
- [Compliance (4)](https://blog.mdaemon.com/tag/compliance)
- [Email Remote Administration (4)](https://blog.mdaemon.com/tag/email-remote-administration)
- [MailStore Archive Server (4)](https://blog.mdaemon.com/tag/mailstore-archive-server)
- [Microsoft 365 Exchange Alternative (4)](https://blog.mdaemon.com/tag/microsoft-365-exchange-alternative)
- [Passwords (4)](https://blog.mdaemon.com/tag/passwords)
- [Software update (4)](https://blog.mdaemon.com/tag/software-update)
- [Archive (3)](https://blog.mdaemon.com/tag/archive)
- [Attachments (2)](https://blog.mdaemon.com/tag/attachments)
- [Business Email (2)](https://blog.mdaemon.com/tag/business-email)
- [Cloud (2)](https://blog.mdaemon.com/tag/cloud)
- [DMARC (2)](https://blog.mdaemon.com/tag/dmarc)
- [Industry Insight (2)](https://blog.mdaemon.com/tag/industry-insight)
- [MDaemon (2)](https://blog.mdaemon.com/tag/mdaemon)
- [insider threats (2)](https://blog.mdaemon.com/tag/insider-threats)
- [msp (2)](https://blog.mdaemon.com/tag/msp)
- [Anti-Relay (1)](https://blog.mdaemon.com/tag/anti-relay)
- [BEC (1)](https://blog.mdaemon.com/tag/bec)
- [Backscatter (1)](https://blog.mdaemon.com/tag/backscatter)
- [Bayesian Learning (1)](https://blog.mdaemon.com/tag/bayesian-learning)
- [Content Filter (1)](https://blog.mdaemon.com/tag/content-filter)
- [DNS-BL (1)](https://blog.mdaemon.com/tag/dns-bl)
- [Disaster Recovery (1)](https://blog.mdaemon.com/tag/disaster-recovery)
- [Email Collaboration (1)](https://blog.mdaemon.com/tag/email-collaboration)
- [Email Software Reviews (1)](https://blog.mdaemon.com/tag/email-software-reviews)
- [Encrypt (1)](https://blog.mdaemon.com/tag/encrypt)
- [External Email Threats (1)](https://blog.mdaemon.com/tag/external-email-threats)
- [Gateway (1)](https://blog.mdaemon.com/tag/gateway)
- [Inbox (1)](https://blog.mdaemon.com/tag/inbox)
- [Inbox Zero (1)](https://blog.mdaemon.com/tag/inbox-zero)
- [Macros (1)](https://blog.mdaemon.com/tag/macros)
- [Monitoring (1)](https://blog.mdaemon.com/tag/monitoring)
- [Quarantine (1)](https://blog.mdaemon.com/tag/quarantine)
- [RelayFax (1)](https://blog.mdaemon.com/tag/relayfax)
- [Software (1)](https://blog.mdaemon.com/tag/software)
- [Training (1)](https://blog.mdaemon.com/tag/training)
- [Troubleshooting (1)](https://blog.mdaemon.com/tag/troubleshooting)
- [Upgrade (1)](https://blog.mdaemon.com/tag/upgrade)
- [Web Conferencing (1)](https://blog.mdaemon.com/tag/web-conferencing)
- [Windows Server (1)](https://blog.mdaemon.com/tag/windows-server)
- [internal email threat (1)](https://blog.mdaemon.com/tag/internal-email-threat)
- [ssl (1)](https://blog.mdaemon.com/tag/ssl)
- [tax scams (1)](https://blog.mdaemon.com/tag/tax-scams)

see all

### Posts by Topic

- [Email Security (72)](https://blog.mdaemon.com/tag/email-security)
- [MDaemon Email Server (45)](https://blog.mdaemon.com/tag/mdaemon-email-server)
- [Email How To (37)](https://blog.mdaemon.com/tag/email-how-to)
- [Email Best Practices (29)](https://blog.mdaemon.com/tag/email-best-practices)
- [Phishing (28)](https://blog.mdaemon.com/tag/phishing)
- [Product Updates (28)](https://blog.mdaemon.com/tag/product-updates)
- [Security Gateway for Email (27)](https://blog.mdaemon.com/tag/security-gateway-for-email)
- [Stop Spam Email (25)](https://blog.mdaemon.com/tag/stop-spam-email)
- [Cybersecurity (24)](https://blog.mdaemon.com/tag/cybersecurity)
- [Email Security Best Practices (22)](https://blog.mdaemon.com/tag/email-security-best-practices)
- [Email Server (22)](https://blog.mdaemon.com/tag/email-server)
- [Two-Factor Authentication (18)](https://blog.mdaemon.com/tag/two-factor-authentication)
- [Email Gateway How-To (17)](https://blog.mdaemon.com/tag/email-gateway-how-to)
- [Email Security Trends (15)](https://blog.mdaemon.com/tag/email-security-trends)
- [Health Care Security (12)](https://blog.mdaemon.com/tag/health-care-security)
- [SecurityGateway (12)](https://blog.mdaemon.com/tag/securitygateway)
- [Spear Phishing (12)](https://blog.mdaemon.com/tag/spear-phishing)
- [Data Leak Prevention (11)](https://blog.mdaemon.com/tag/data-leak-prevention)
- [Email Encryption (11)](https://blog.mdaemon.com/tag/email-encryption)
- [Anti-Spoofing (10)](https://blog.mdaemon.com/tag/anti-spoofing)
- [MDaemon Webmail (10)](https://blog.mdaemon.com/tag/mdaemon-webmail)
- [Email Archiving (8)](https://blog.mdaemon.com/tag/email-archiving)
- [Email Management (8)](https://blog.mdaemon.com/tag/email-management)
- [Email Privacy (8)](https://blog.mdaemon.com/tag/email-privacy)
- [Email Spoofing (8)](https://blog.mdaemon.com/tag/email-spoofing)
- [Business Email Compromise (7)](https://blog.mdaemon.com/tag/business-email-compromise)
- [Anti-Virus (6)](https://blog.mdaemon.com/tag/anti-virus)
- [Email Software (6)](https://blog.mdaemon.com/tag/email-software)
- [Tutorial (6)](https://blog.mdaemon.com/tag/tutorial)
- [Update (6)](https://blog.mdaemon.com/tag/update)
- [Collaboration (5)](https://blog.mdaemon.com/tag/collaboration)
- [Email Authentication (5)](https://blog.mdaemon.com/tag/email-authentication)
- [Compliance (4)](https://blog.mdaemon.com/tag/compliance)
- [Email Remote Administration (4)](https://blog.mdaemon.com/tag/email-remote-administration)
- [MailStore Archive Server (4)](https://blog.mdaemon.com/tag/mailstore-archive-server)
- [Microsoft 365 Exchange Alternative (4)](https://blog.mdaemon.com/tag/microsoft-365-exchange-alternative)
- [Passwords (4)](https://blog.mdaemon.com/tag/passwords)
- [Software update (4)](https://blog.mdaemon.com/tag/software-update)
- [Archive (3)](https://blog.mdaemon.com/tag/archive)
- [Attachments (2)](https://blog.mdaemon.com/tag/attachments)
- [Business Email (2)](https://blog.mdaemon.com/tag/business-email)
- [Cloud (2)](https://blog.mdaemon.com/tag/cloud)
- [DMARC (2)](https://blog.mdaemon.com/tag/dmarc)
- [Industry Insight (2)](https://blog.mdaemon.com/tag/industry-insight)
- [MDaemon (2)](https://blog.mdaemon.com/tag/mdaemon)
- [insider threats (2)](https://blog.mdaemon.com/tag/insider-threats)
- [msp (2)](https://blog.mdaemon.com/tag/msp)
- [Anti-Relay (1)](https://blog.mdaemon.com/tag/anti-relay)
- [BEC (1)](https://blog.mdaemon.com/tag/bec)
- [Backscatter (1)](https://blog.mdaemon.com/tag/backscatter)
- [Bayesian Learning (1)](https://blog.mdaemon.com/tag/bayesian-learning)
- [Content Filter (1)](https://blog.mdaemon.com/tag/content-filter)
- [DNS-BL (1)](https://blog.mdaemon.com/tag/dns-bl)
- [Disaster Recovery (1)](https://blog.mdaemon.com/tag/disaster-recovery)
- [Email Collaboration (1)](https://blog.mdaemon.com/tag/email-collaboration)
- [Email Software Reviews (1)](https://blog.mdaemon.com/tag/email-software-reviews)
- [Encrypt (1)](https://blog.mdaemon.com/tag/encrypt)
- [External Email Threats (1)](https://blog.mdaemon.com/tag/external-email-threats)
- [Gateway (1)](https://blog.mdaemon.com/tag/gateway)
- [Inbox (1)](https://blog.mdaemon.com/tag/inbox)
- [Inbox Zero (1)](https://blog.mdaemon.com/tag/inbox-zero)
- [Macros (1)](https://blog.mdaemon.com/tag/macros)
- [Monitoring (1)](https://blog.mdaemon.com/tag/monitoring)
- [Quarantine (1)](https://blog.mdaemon.com/tag/quarantine)
- [RelayFax (1)](https://blog.mdaemon.com/tag/relayfax)
- [Software (1)](https://blog.mdaemon.com/tag/software)
- [Training (1)](https://blog.mdaemon.com/tag/training)
- [Troubleshooting (1)](https://blog.mdaemon.com/tag/troubleshooting)
- [Upgrade (1)](https://blog.mdaemon.com/tag/upgrade)
- [Web Conferencing (1)](https://blog.mdaemon.com/tag/web-conferencing)
- [Windows Server (1)](https://blog.mdaemon.com/tag/windows-server)
- [internal email threat (1)](https://blog.mdaemon.com/tag/internal-email-threat)
- [ssl (1)](https://blog.mdaemon.com/tag/ssl)
- [tax scams (1)](https://blog.mdaemon.com/tag/tax-scams)

See all

#### About MDaemon Technologies

MDaemon Technologies is a pioneer in developing email and email security software helping to protect customers from evolving cyber-security threats. Its products and services are trusted by thousands of organizations in over 140 countries. For more than two decades, the company’s products have been developed with the ongoing input of IT professionals who demand reliable, affordable software that requires minimal effort to manage.

The software can be deployed in virtual, hosted cloud, on-premises, or hybrid network environments. The company sells its software and services directly and through a network of global channel partners.

For more information, visit [www.mdaemon.com](https://www.altn.com/).

Copyright © 1996-2026 MDaemon Technologies.  View [privacy policy](https://mdaemon.com/policies/privacy-policy).

 

###### Contact Us

 +1.817-601-3222

[sales@help.mdaemon.com](mailto:sales@help.mdaemon.com)

 6340 Lake Worth Blvd.  
 Fort Worth, TX 76135

```json
{
  "@context" : "https://schema.org",
  "@type" : "BlogPosting",
  "author" : {
    "@type" : "Person",
    "name" : "Brad Wyro",
    "url" : "https://blog.mdaemon.com/author/brad-wyro"
  },
  "dateModified" : "2026-07-01T21:26:21.541Z",
  "datePublished" : "2026-05-12T14:29:59.000Z",
  "headline" : "How to Use Performance Monitor to Notify an Administrator If an MDaemon Service Goes Down",
  "image" : [ "https://blog.mdaemon.com/hubfs/banner-twitter.png" ],
  "mainEntityOfPage" : {
    "@id" : "https://blog.mdaemon.com/mdaemon-performance-monitor-service-down-alerts",
    "@type" : "WebPage"
  },
  "publisher" : {
    "@type" : "Organization",
    "logo" : {
      "@type" : "ImageObject",
      "url" : "https://blog.mdaemon.com/hubfs/MDaemon-Technologies_logo_large.png"
    },
    "name" : "MDaemon Technologies"
  }
}
```