Why Am I Not Receiving Alert Emails?

When alert emails aren't arriving, it can leave you in the dark about critical server issues. This guide walks through the most common causes and solutions, starting with the most fundamental checks.

1. Verify SMTP Configuration Exists

Server Scout requires SMTP settings to send any emails. Without proper SMTP configuration, no alert emails can be delivered.

To check:

1. Navigate to the Users page in your dashboard
2. Look for the SMTP settings section
3. Ensure SMTP is configured with all required fields filled

Fix: If SMTP isn't configured, you'll need admin privileges to set it up. Only account administrators can configure SMTP settings.

2. Check SMTP Settings Are Correct

Incorrect SMTP configuration is the most common cause of email delivery failures.

Verify these settings:

• SMTP Host: Must match your email provider's requirements
• Port: Typically 587 for modern SMTP with TLS
• Username: Usually your full email address
• Password: Your email account password or app-specific password
• Encryption: TLS is recommended for security

Common configurations:

• Gmail: smtp.gmail.com, port 587, TLS encryption
• Office 365: smtp.office365.com, port 587, TLS encryption
• Outlook.com: smtp-mail.outlook.com, port 587, TLS encryption

Note: Many providers require app-specific passwords instead of your regular account password, especially with 2FA enabled.

3. Test SMTP Configuration

Once SMTP is configured, test it immediately to confirm it's working.

To test:

1. Go to the SMTP settings page
2. Click the Test Send button
3. Check the specified test email address for delivery
4. Review any error messages that appear

Fix: If the test fails, double-check your SMTP credentials and try again. Error messages often indicate specific issues like authentication failures or connection problems.

4. Check Spam and Junk Folders

Email providers frequently flag monitoring alerts as spam, particularly when you first start receiving them.

Check these locations:

• Spam/Junk folder in your email client
• Quarantine folder (for business email systems)
• Blocked senders list

Fix: If you find Server Scout emails in spam, mark them as "Not Spam" and add the sender address to your safe senders list. This helps train your spam filter.

5. Verify Email Notification Channel

Alert conditions need notification channels to deliver emails. Missing or misconfigured channels prevent alert delivery.

To check:

1. Go to Notifications settings
2. Verify an email notification channel exists
3. Confirm the recipient email address is correct
4. Ensure the channel is enabled

Fix: If no email channel exists, create one with the correct recipient address. If the address is wrong, edit the channel to fix it.

6. Test Notification Channel

Test your notification channel independently of actual alerts.

To test:

1. Find your email notification channel
2. Use the Test Channel feature
3. Check for email delivery within a few minutes

Fix: If the test fails, review the notification channel configuration and your SMTP settings again.

7. Review Alert Condition Configuration

Improperly configured alert conditions may not trigger when expected.

Check these settings:

• Thresholds: Are they set to realistic values?
• Sustain period: How long must the condition persist before alerting?
• Cooldown period: How long between repeat notifications?

Fix: A sustain period that's too long means conditions must persist longer before triggering. Adjust thresholds and timing to match your monitoring needs.

8. Check Cooldown Status

If an alert recently fired, the cooldown period prevents immediate repeat notifications.

To check:

1. Review recent alert history
2. Check when alerts last triggered
3. Compare against your cooldown settings

Fix: Wait for the cooldown period to expire, or adjust cooldown settings if they're too long for your needs.

9. Review Notification History

The notification log shows delivery attempts and failures, providing insight into what's happening behind the scenes.

To check:

1. Navigate to notification history/logs
2. Look for recent delivery attempts
3. Review any error messages or failure reasons

Fix: Error messages in the log often point to specific issues like SMTP authentication failures, network connectivity problems, or recipient address issues.

Still Having Issues?

If you've worked through these steps and alerts still aren't arriving, contact our support team with:

• Your SMTP configuration (without passwords)
• Recent notification log entries
• Specific alert conditions that should be triggering

Our AI support bot responds within approximately one minute and can help identify configuration issues quickly.