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 0x.
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 plugin notify-by-email-base64.zip to the following directory
/opt/opsview/monitoringscripts/notificationson your Opsview Monitor Orchestrator server -
Update the permissions to allow the script to be executed. E.g.
chmod +x /opt/opsview/monitoringscripts/notifications/notify_by_email_base64. -
Test that the notification script works. You can do this by running the following as the opsview user:
export NAGIOS_CONTACTEMAIL=myemail@mydomain.com /opt/opsview/monitoringscripts/notifications/notify_by_email_base64You should see similar output as noted below:
Sent email!
Now you just need to configure the notification method and profile within Opsview Monitor as outlined in the following articles: