Email Notifications converted to unreadable attachments
By default, the Opsview Monitor email notification profile uses a plugin called
notify_by_email. With most email servers you’ll likely never run into any issues. However, if your email is being processed through an Exchange server at any point along its journey you may run into problems with the text being converted to a binary attachment.
This can happen due to Exchange mistakenly reading the content of your email and believing that the way your email text is organized is actually some form of attachment. This is most common when you have service check results that include error messages starting with
To get around this there is another email notification script that you can use which is linked from this FAQ. It Base64 encodes the email content for you which prevents Exchange from converting the email content to an attachment. Follow the steps below to install this modified email notification method:
Download the following notification script notify-by-email-base64.zip and install it using the
orchestratorimportscriptscommand line tool on your Opsview Monitor Orchestrator server:
/opt/opsview/orchestrator/bin/orchestratorimportscripts notifications /path/to/script
Execute the Apply Changes action in the Opsview Monitor User Interface.
NoteIn a clustered environment (multiple clusters and collectors) scripts should be uploaded to the Master Monitoring Server and ALL collectors. To do this, follow the steps above, and then use the sync_monitoringscripts playbook to copy to the collectors.
Test that the notification script works. You can do this by running the following as the opsview user:
export NAGIOS_CONTACTEMAILfirstname.lastname@example.org /opt/opsview/monitoringscripts/notifications/notify_by_email_base64
You should see similar output as noted below:
Configure the Notification Method and Profile within Opsview Monitor as outlined in the following articles: