Email Scout
From Documentation
Revision as of 01:26, 17 November 2006 Daniels (Talk | contribs) ← Previous diff |
Revision as of 01:33, 17 November 2006 Daniels (Talk | contribs) (→How to set up Email Monitoring) Next diff → |
||
Line 1: | Line 1: | ||
== How to set up Email Monitoring == | == How to set up Email Monitoring == | ||
+ | |||
+ | The email monitor is set up under Linux/Unix using the .forward feature of your mail system. The Functional Monitoring server sends a specifically constructed email to an address that is created for the purposes of monitoring. We recommend something easily remembered such as monitor@company.com, or webscout@company.com | ||
+ | |||
+ | |||
+ | Using the .forward file, Functional Software will provide a script that runs whenever mail is received to ensure it matches the specific structure we are looking for, so as to avoid accidentally answering spam, or randomly targeted emails. This same script will then add the timestamp (UTC) of when the mail was received by your remote server, and send it back to Functional Software. The timestamp is only collected for informational purposes. It is not used as a monitoring metric, as we cannot guarantee that your email server will be set to the same time as our monitoring server. | ||
+ | |||
+ | When the returned email is received by our monitoring email account, another script builds the information required to measure the round-trip email time, and reports that to the sentinel3G Agent. |
Revision as of 01:33, 17 November 2006
How to set up Email Monitoring
The email monitor is set up under Linux/Unix using the .forward feature of your mail system. The Functional Monitoring server sends a specifically constructed email to an address that is created for the purposes of monitoring. We recommend something easily remembered such as monitor@company.com, or webscout@company.com
Using the .forward file, Functional Software will provide a script that runs whenever mail is received to ensure it matches the specific structure we are looking for, so as to avoid accidentally answering spam, or randomly targeted emails. This same script will then add the timestamp (UTC) of when the mail was received by your remote server, and send it back to Functional Software. The timestamp is only collected for informational purposes. It is not used as a monitoring metric, as we cannot guarantee that your email server will be set to the same time as our monitoring server.
When the returned email is received by our monitoring email account, another script builds the information required to measure the round-trip email time, and reports that to the sentinel3G Agent.