<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:media="http://search.yahoo.com/mrss/">
<channel>
<title>CheckCentral RSS: Handling emails that are not routine</title>
<atom:link href="https://www.checkcentral.cc/Discussions/RSS/?TopicID=07235960-b6fa-4605-9d39-86937597740f" rel="self" type="application/rss+xml" />
<link>https://www.checkcentral.cc/Discussions/RSS/?TopicID=07235960-b6fa-4605-9d39-86937597740f</link>
<description>CheckCentral RSS: Handling emails that are not routine</description>
<lastBuildDate>Mon, 25 May 2026 22:29:49 GMT</lastBuildDate>
<language>en</language>
<sy:updatePeriod>hourly</sy:updatePeriod>
<sy:updateFrequency>1</sy:updateFrequency>
<generator>https://www.checkcentral.cc/Discussions/RSS/?TopicID=07235960-b6fa-4605-9d39-86937597740f</generator>
<item>
<title>RE: Handling emails that are not routine</title>
<link>https://www.checkcentral.cc/Discussions/View/handling-emails-that-are-not-routine/?ID=07235960-b6fa-4605-9d39-86937597740f#4</link>
<pubDate>Wed, 03 Feb 2021 19:34:24 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.checkcentral.cc/Discussions/View/handling-emails-that-are-not-routine/?ID=07235960-b6fa-4605-9d39-86937597740f#4</guid>
<category>CheckCentral</category>
<description><![CDATA[@rrnworks: I know we already chatted about this over email, but I'm going to post here in case anyone else comes across this thread as well
What I usually do in these cases is set the default status to failure, and don't set anything for the success criteria. That way any email that comes in tri...]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
@rrnworks: I know we already chatted about this over email, but I'm going to post here in case anyone else comes across this thread as well <img src="https://www.checkcentral.cc/MediaCommon/SVGs/FontAwesome/face-smile.light.svg" alt=":)" style="box-sizing:border-box;position:relative;overflow:hidden;vertical-align:middle !important;width:16px;height:16px;" HelpButtonData=":)" HelpButtonDataAlign="BelowMiddle" /><br/>
<br/>
What I usually do in these cases is set the default status to failure, and don't set anything for the success criteria. That way any email that comes in triggers the failure status. Then you can manually review the alert, and force the status back to success when it's been resolved.
</div>
]]></content:encoded>
</item>
<item>
<title>RE: Handling emails that are not routine</title>
<link>https://www.checkcentral.cc/Discussions/View/handling-emails-that-are-not-routine/?ID=07235960-b6fa-4605-9d39-86937597740f#3</link>
<pubDate>Wed, 03 Feb 2021 17:48:58 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.checkcentral.cc/Discussions/View/handling-emails-that-are-not-routine/?ID=07235960-b6fa-4605-9d39-86937597740f#3</guid>
<category>CheckCentral</category>
<description><![CDATA[I'm looking for similar functionality. My specific scenario:
We have intermittent email alerts generated from NinjaRMM with "bad block" in the body.  We'd like to create a check that shows success when no email alert is received and failure when a match is made?
Thank you!
Chris]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
I'm looking for similar functionality. My specific scenario:<br/>
We have intermittent email alerts generated from NinjaRMM with "bad block" in the body.  We'd like to create a check that shows success when no email alert is received and failure when a match is made?<br/>
Thank you!<br/>
Chris
</div>
]]></content:encoded>
</item>
<item>
<title>RE: Handling emails that are not routine</title>
<link>https://www.checkcentral.cc/Discussions/View/handling-emails-that-are-not-routine/?ID=07235960-b6fa-4605-9d39-86937597740f#2</link>
<pubDate>Tue, 15 Dec 2020 20:07:14 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.checkcentral.cc/Discussions/View/handling-emails-that-are-not-routine/?ID=07235960-b6fa-4605-9d39-86937597740f#2</guid>
<category>CheckCentral</category>
<description><![CDATA[There isn't a built-in pass-through type of rule, but there are a couple of existing options that should work.
You could create a new check that matches those non-backup emails from the NAS and is set to "Unscheduled" with a default status of Failure. That way any email that comes in to that che...]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
There isn't a built-in pass-through type of rule, but there are a couple of existing options that should work.<br/>
<br/>
You could create a new check that matches those non-backup emails from the NAS and is set to "Unscheduled" with a default status of Failure. That way any email that comes in to that check will send out a notification.<br/>
<br/>
The other option would be to expand the criteria for your existing check so that it also matches the non-backup notifications. If that check has a default of Failure, and your Success rules only match the backup notifications, then you'll get a failure notification when the non-backup ones come in.<br/>
<br/>
Hopefully that helps, if not, please let me know!
</div>
]]></content:encoded>
</item>
<item>
<title>Handling emails that are not routine</title>
<link>https://www.checkcentral.cc/Discussions/View/handling-emails-that-are-not-routine/?ID=07235960-b6fa-4605-9d39-86937597740f</link>
<pubDate>Mon, 14 Dec 2020 22:09:29 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.checkcentral.cc/Discussions/View/handling-emails-that-are-not-routine/?ID=07235960-b6fa-4605-9d39-86937597740f</guid>
<category>CheckCentral</category>
<description><![CDATA[Is there an option to redirect or forward alerts that may not match an existing rule? For example, a NAS may report a defective disk or other fauly, but the backups are still working correctly. In this case, there's a potential to miss the hardware issue, since the alerting via email won't trigge...]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
Is there an option to redirect or forward alerts that may not match an existing rule? For example, a NAS may report a defective disk or other fauly, but the backups are still working correctly. In this case, there's a potential to miss the hardware issue, since the alerting via email won't trigger anything except an unmatched reply alert?
</div>
]]></content:encoded>
</item>
</channel>
</rss>