Nagios Xi sending mails in MIME format instead of Plain text

[vtadisina]

Nagios xi is sending mails in MIME format instead of plain text after updating to 5.4.1. I need to revert back to plain text emails. I need to know the procedure to revert to plain text format.

[mcapra]

This is probably a change to how PHPMailer works on the back-end. We updated our PHPMailer to address a widely known exploit that affected multiple platforms. Can you show us the raw message being received by your mail server to see exactly what's being transmitted? Something like this:

Code: Select all

Delivered-To: [email protected]
Received: by 10.80.158.173 with SMTP id a42csp1474952edf;
        Mon, 30 Jan 2017 14:39:32 -0800 (PST)
X-Received: by 10.107.47.132 with SMTP id v4mr24282678iov.172.1485815972812;
        Mon, 30 Jan 2017 14:39:32 -0800 (PST)
Return-Path: <[email protected]>
Received: from xi-stable.localdomain ()
        by mx.google.com with ESMTP id i2si11745272iob.94.2017.01.30.14.39.32
        for <[email protected]>;
        Mon, 30 Jan 2017 14:39:32 -0800 (PST)
Received-SPF: softfail (google.com: domain of transitioning [email protected] does not designate as permitted sender) client-ip=;
Authentication-Results: mx.google.com;
       spf=softfail (google.com: domain of transitioning [email protected] does not designate  as permitted sender) [email protected]
Received: by xi-stable.localdomain (Postfix, from userid 1000) id 7B358898D0; Mon, 30 Jan 2017 16:39:32 -0600 (CST)
To: [email protected]
Subject: CUSTOM Service Alert - 192.168.67.101/NRPE is OK
X-PHP-Originating-Script: 1000:class.phpmailer.php
Date: Mon, 30 Jan 2017 16:39:32 -0600
From: [email protected]
Reply-To: [email protected]
Message-ID: <19ae086f9c80a1e6187dd280f2c03ef1@xi-stable>
X-Mailer: PHPMailer 5.2.22 (https://github.com/PHPMailer/PHPMailer)
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="b1_19ae086f9c80a1e6187dd280f2c03ef1"
Content-Transfer-Encoding: 8bit

--b1_19ae086f9c80a1e6187dd280f2c03ef1
Content-Type: text/plain; charset=us-ascii

***** Nagios XI Alert *****



Notification Type: CUSTOM

Service: NRPE
Host: 192.168.67.101
Address: 192.168.67.101
State: OK
Info:
TCP OK - 0.020 second response time on 192.168.67.101 port 5666
Date/Time: 2017-01-30 16:39:32

Respond: http://192.168.67.1/nagiosxi/rr.php?uid=1-197-6ffb852badc9ebe3152a7ff9b7380658
Nagios URL: http://192.168.67.1/nagiosxi/


--b1_19ae086f9c80a1e6187dd280f2c03ef1
Content-Type: text/html; charset=us-ascii

***** Nagios XI Alert *****<br />
<br />
<br />
<br />
Notification Type: CUSTOM<br />
<br />
Service: NRPE<br />
Host: 192.168.67.101<br />
Address: 192.168.67.101<br />
State: OK<br />
Info:<br />
TCP OK - 0.020 second response time on 192.168.67.101 port 5666<br />
Date/Time: 2017-01-30 16:39:32<br />
<br />
Respond: http://192.168.67.1/nagiosxi/rr.php?uid=1-197-6ffb852badc9ebe3152a7ff9b7380658<br />
Nagios URL: http://192.168.67.1/nagiosxi/<br />



--b1_19ae086f9c80a1e6187dd280f2c03ef1--

There's a few different places this could be fixed, but i'd like to be extra sure before we start monkeying around with stuff in the back-end.

[vtadisina]

Here is the attached raw message received in my mailbox.

Code: Select all

Return-Path: <[email protected]>
X-Original-To: [email protected]
Delivered-To: [email protected]
Received: from hzznagi00.nwc75.hubs (hzznagi00.nwc75.hubs [10.22.90.23])
	by hbbmail00.nwc75.hubs (Postfix) with ESMTP id A7898A0B47
	for <[email protected]>; Sat, 28 Jan 2017 06:07:43 -0500 (EST)
Received: from hzznagi00.nwc75.hubs (localhost [127.0.0.1])
	by hzznagi00.nwc75.hubs (8.14.4/8.14.4) with ESMTP id v0SB7hlF010740
	for <[email protected]>; Sat, 28 Jan 2017 06:07:43 -0500
Received: (from nagios@localhost)
	by hzznagi00.nwc75.hubs (8.14.4/8.14.4/Submit) id v0SB7hSk010739;
	Sat, 28 Jan 2017 06:07:43 -0500
X-Authentication-Warning: hzznagi00.nwc75.hubs: nagios set sender to [email protected] using -f
To: [email protected]
Subject: PROBLEM Service Alert - 75A-216.3-HUB-RACK03-esb00/esb 00- ESB Process is CRITICAL
X-PHP-Originating-Script: 500:class.phpmailer.php
Date: Sat, 28 Jan 2017 06:07:43 -0500
From: Nagios XI <[email protected]>
Reply-To: Nagios XI <[email protected]>
Message-ID: <7f3265fd3ab1784a4998273d9f01dfad@hzznagi00>
X-Mailer: PHPMailer 5.2.22 (https://github.com/PHPMailer/PHPMailer)
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="b1_7f3265fd3ab1784a4998273d9f01dfad"
Content-Transfer-Encoding: 8bit

This is a multi-part message in MIME format.

--b1_7f3265fd3ab1784a4998273d9f01dfad
Content-Type: text/plain; charset=us-ascii

***** Nagios XI Alert *****

Nagios has detected a problem with this service.

Notification Type: PROBLEM

Service: esb 00- ESB Process
Host: 75A-216.3-HUB-RACK03-esb00
Address: 10.22.93.40
State: CRITICAL
Info:
connect to address 10.22.93.40 and port 9080: Connection refused
Date/Time: 2017-01-28 06:07:43

Location: $

Service Priority: $
Host Priority: $

Service Category: $
Host Category: SW-HOST

Respond: http://Nagios-vip.lb.nwc75.hubs/nagiosxi/rr.php?uid=5-14381-08fe98934a07f47976cd2aa41ef9c0d3
Nagios URL: http://Nagios-vip.lb.nwc75.hubs/nagiosxi/


--b1_7f3265fd3ab1784a4998273d9f01dfad
Content-Type: text/html; charset=us-ascii

***** Nagios XI Alert *****<br />
<br />
Nagios has detected a problem with this service.<br />
<br />
Notification Type: PROBLEM<br />
<br />
Service: esb 00- ESB Process<br />
Host: 75A-216.3-HUB-RACK03-esb00<br />
Address: 10.22.93.40<br />
State: CRITICAL<br />
Info:<br />
connect to address 10.22.93.40 and port 9080: Connection refused<br />
Date/Time: 2017-01-28 06:07:43<br />
<br />
Location: $<br />
<br />
Service Priority: $<br />
Host Priority: $<br />
<br />
Service Category: $<br />
Host Category: SW-HOST<br />
<br />
Respond: http://Nagios-vip.lb.nwc75.hubs/nagiosxi/rr.php?uid=5-14381-08fe98934a07f47976cd2aa41ef9c0d3<br />
Nagios URL: http://Nagios-vip.lb.nwc75.hubs/nagiosxi/<br />



--b1_7f3265fd3ab1784a4998273d9f01dfad--

.

[rkennedy]

We do like to avoid working on the same issue in multiple places. As I see a ticket has been received for this, would you mind if I locked the thread so we can continue there?

[vtadisina]

Sorry i need to get this issue resolved ASAP. So i emailed support directly. Lock this thread and we can continue through email.