Inbound email processing error

[gwakem]

XI 5.6.2 on RHEL 7.5
I have enabled inbound mail settings, tested successfully, and verified xi is removing emails after reading them.

However, I only get a reply email stating "Could not submit command due to missing hash data. Did you reply with the full email?"

Here is a sample of the reply I sent:

ack
Testing ack by email


On Thu, 2019-06-06 at 13:59 -0400, Nagios XI wrote:
---- Respond above this line ----

Date/Time: 06/06/2019 13:59:58
Notification Type: PROBLEM

Service: Service status for: firewalld
Host: xxxx
Address: x.x.x.x

Additional Info: CRITICAL: firewalld is stopped (should be running)

Notification Author:
Notification Comment:

Respond: https://xxxxxxxxxxxx/nagiosxi/rr.php?oi ... 5e8c49793d

Nagios URL: https://xxxxxxxxxxxxx/nagiosxi/

-----

To reply, keep the following data in your response email.

##YWRiMmRkNjJmZTY4NTcyMVN2aUtXaUtkRVV5cVN2ajl0dVhTUzIxU05NL29EQjFhMURRMlRKT3ltU2pVcVZWVDBXSGErdVhCT29LK3FabThhVTZDckVGMGRHVGoyd2NTZG4yWXJRPT0=##

Is there a way to further debug what is going wrong? For clarity, I also tried with the hash directly below the ack and comment, but no luck their either.

[npolovenko]

Hello, @gwakem. What email client are you using to acknowledge notification emails? On the nagios server please tail the cleaner log:

Code: Select all

tail -f /usr/local/nagiosxi/var/cleaner.log

And while this command is running, respond to a notification email with:

ack
Testing ack by email

And see what kind of errors the command will show.

[gwakem]

I am using Evolution on a Fedora 29 system. I will try via webmail and exchange on a windows 10 system also.

I will do additional testing with the other email clients and OS's later today/early next week and report back.

The error that I found in the logs stated this for Evolution.

Error - Could not find a valid hash in the email sent
PHP Catchable fatal error: Object of class stdClass could not be converted to string in /usr/local/nagiosxi/html/includes/components/xicore/xicore.inc.php on line 550

[npolovenko]

@gwakem, Sounds good. Please try a different mail client and let us know.