Skip to main content
< All Topics
Print

Outgoing Spam Monitor (OSM) is a security feature designed to detect and prevent spam emails originating from your server.

It continuously monitors outgoing email activity and helps identify:

  • Compromised email accounts

  • Malicious scripts sending spam

  • Unusual email sending patterns

By proactively detecting such behavior, OSM helps protect your server from:

  • Email abuse

  • IP blacklisting

  • Reputation damage

Control Panels Support cPGuard OSM

  • cPanel 

  • Directadmin

  • Webuzo

How to Enable OSM

By default, OSM is disabled.

To enable it go to:

App Portal → Settings → Outgoing Spam Monitor → Enable OSM switch

Once enabled, OSM will start monitoring outgoing email activity in real-time.

Where to View OSM Logs

You can view OSM activity and detections here:

Protection → OSM

OSM configuration options

and Below are the most important OSM settings typically available:

Hourly Threshold

This defines the maximum number of emails allowed per hour per domain.

If the limit is exceeded alerts will triggered. You can see the logs under Protection > OSM

This helps stop bulk spam campaigns quickly.


Minutely Threshold

This controls the number of emails allowed per minute.

It is useful for detecting:

  • Sudden bursts of spam

  • Script-based mailers

  • Compromised plugins sending mass emails instantly

Minutely limits stop attacks much faster than hourly limits.


Whitelist IPs

Allows specific IP addresses to bypass OSM checks.

Use cases:

  • Trusted external mail servers

  • API-based transactional email systems

  • Internal monitoring systems

This prevents legitimate services from being blocked.


Whitelist Email IDs

Allows specific sender email addresses to bypass spam monitoring rules.

Common examples:

Useful for protecting critical system emails from accidental blocking.


Whitelist CWD Prefixes

CWD (Current Working Directory) prefix whitelisting allows you to exclude specific application paths from OSM restrictions.

For example:

  • /home/user/public_html/whmcs/

  • /home/user/app/cron/

This is helpful for:

  • Billing systems

  • CRM platforms

  • Trusted custom applications


Spam Patterns

This setting checks only the email subject line for known spam keywords or patterns.

Example:

  • Subject: “Congratulations! You won a prize” → flagged (contains common spam keywords like “won”, “prize”)

  • Subject: “Limited time offer – Buy now” → flagged (contains “offer”, “buy now”)

  • Subject: “Meeting scheduled for tomorrow” → not flagged (normal subject, no spam pattern)

This way, only the subject line is analyzed—not the full email content.

Was this article helpful?
5 out of 5 stars

1 rating

5 Stars 100%
4 Stars 0%
3 Stars 0%
2 Stars 0%
1 Stars 0%
5
How can we improve this article?
Please submit the reason for your vote so that we can improve the article.
Table of Contents