In large environments, setting up a mailflow monitoring system can be a bit cumbersome because you could easily end up with a ‘lot of configuration items within your monitoring app.
For instance if you have multiple locations and you want to monitor the mailflow to each of the locations the amount of config items is equal the amount of locations.
With GreenLight we make your life much easier. You need to create only ONE single Mailflow sensor which covers then all your destinations. Find below the way how you can configure this.
- Create a new Domino Mailflow Analysis Sensor
- enter your Mail Gateway details
- as Mail Recipients you need to make use of a reference which is called [TargetCommonName]
in this example we choose the following recipient address: Mailflow_[TargetCommonName]@panagenda.com
- enter your Target DBT
- specify the Delay creation by and the Timeout
- specify all other remaining parameters
- on the targets tab, specify the destination servers
What does this configuration mean and what things you need to prepare on the domino server level?
The result of the reference [TargetCommonName] is that the common name of the destination server is part of the e-mail recipient address.
So if you want to monitor the mailflow between 3 servers (HUB towards two destinations/locations) you need to create two mail-in documents in your public address book with the corresponding mail database name.
In this example I have specified two targets, Sokar and Anubis, therefore I need to create on both servers a mail-in database underneath the mailflow folder Mailflow\box.nsf AND the mailin documents in the NAB.
So GreenLight sends to the following addresses an individual mailflow probe.
At the end of the day you need only two Mailflow Sensors (depending what aim you have).
One like described above and one for measuring the Internet Mail delivery time (Domino Mailflow Analysis Sensor for checking Internet mail delivery times)
One single Mailflow sensor which measures dozens/hundreds of mailflows within your organization