Check_email_delivery - O365

[r34220]

On one of my nagios clients I am having an issue with the check_email_delivery with O365.

Code: Select all

./check_email_delivery --mailto nagios@company.com --mailfrom nagios@company.com -H outlook.office365.com --smtp-server smtp.office365.com --smtp-username 'nagios@company.com' --smtp-password 'xxxxxxx' --smtp-port 587 --imap-server outlook.office365.com --username 'nagios@company.com' --password 'xxxxxx' --imap-port 993 --smtptls --imapssl

I get this error ...

Code: Select all

EMAIL DELIVERY CRITICAL - imap failed: IMAP RECEIVE CRITICAL - Could not connect to outlook.office365.com port 993: IO::Socket::INET configuration failederror:00000000:lib(0):func(0):reason(0) at /usr/local/nagios/libexec/check_imap_receive line 124.

Same command on other hosts works fine but not on this one.

[Box293]

Can you execute the plugin again but this time add --verbose at the end.

What is reported now?

[r34220]

Can you execute the plugin again but this time add --verbose at the end.

What is reported now?

There is no change in the output,

Code: Select all

 ./check_email_delivery --mailto nagios@frcompany.com --mailfrom nagios@frcompanyle.com -H outlook.office365.com --smtp-server smtp.office365.com --smtp-username 'nagios@frcompany.com' --smtp-password 'NagRules08' --smtp-port 587 --imap-server outlook.office365.com --username 'nagios@frcompany.com' --password 'NagRules08' --imap-port 993 --smtptls --imapssl  --verbose
EMAIL DELIVERY CRITICAL - imap failed: IMAP RECEIVE CRITICAL - Could not connect to outlook.office365.com port 993: IO::Socket::INET configuration failederror:00000000:lib(0):func(0):reason(0) at /usr/local/nagios/libexec/check_imap_receive line 124.

[Box293]

Does an nmap work?

Code: Select all

nmap outlook.office365.com -p 993

[r34220]

Code: Select all

nmap outlook.office365.com -p 993

Starting Nmap 5.51 ( http://nmap.org ) at 2015-11-10 20:44 MST
Nmap scan report for outlook.office365.com (132.245.193.130)
Host is up (0.036s latency).
Other addresses for outlook.office365.com (not scanned): 132.245.229.114 132.245.56.114 132.245.224.194 132.245.74.98 132.245.77.34 132.245.36.98 132.245.48.18
PORT    STATE SERVICE
993/tcp open  imaps

Nmap done: 1 IP address (1 host up) scanned in 5.67 seconds

[Box293]

The only thing I could find vaguely similar was this:
http://perlmaven.com/io-socket-inet-con ... ion-failed

What is the output of this command:

Code: Select all

yum list installed | grep Socket

[r34220]

Code: Select all

yum list installed | grep Socket
*Note* Red Hat Network repositories are not listed below. You must run this command as root to access RHN repositories.
perl-IO-Socket-INET6.noarch        2.56-4.el6            @anaconda-RedHatEnterpriseLinux-201301301459.x86_64/6.4
perl-IO-Socket-SSL.noarch          1.31-2.el6            @anaconda-RedHatEnterpriseLinux-201301301459.x86_64/6.4
perl-Socket6.x86_64                0.23-4.el6            @rhel-6-server-rpms

[rkennedy]

The version of IO-Socket-SSL appears to be updated, can you also check the output for OpenSSL?

Code: Select all

yum list installed|grep openssl

[r34220]

Code: Select all

yum list installed|grep openssl
openssl.x86_64                     1.0.1e-42.el6         @rhel-x86_64-server-6
openssl-devel.x86_64               1.0.1e-42.el6         @rhel-x86_64-server-6
openssl098e.x86_64                 0.9.8e-18.el6_5.2     @rhel-6-server-rpms

[rkennedy]

I read around for a bit, and believe the openssl version may be the culprit. Can you check the openssl version on one of the servers that is working and post the output as well?

Once again -

Code: Select all

yum list installed|grep openssl