Check_smtp

[Marc Powell]

What version of the plugins are you using? This is an old problem with exchange that was fixed about this time last year if I remember correctly. It had something to do with the plugin sending \r\n and exchange expecting \r\r but I don't remember the specific details at the moment. You can search the archives if you're interested. Are you experiencing this with the latest plugins?

--
Marc

________________________________________
From: nagios-users-admin at lists.sourceforge.net [mailto:nagios-users-admin at lists.sourceforge.net] On Behalf Of Lydia Leung
Sent: Wednesday, December 22, 2004 10:25 PM
To: nagios-users at lists.sourceforge.net
Subject: [Nagios-users] Check_smtp
Importance: High

Hi,
 
I am using Check_smtp to check mail service.
 
Anyone knows how check_smtp works?
 
When I use the internal IP address, I get 0 sec response, which returns a critical warning in the web.
./check_smtp -H 192.168.250.10 -t 4
SMTP OK - 0 second response time
Socket timeout after 4 seconds
 
But when I use external IP address, it is ok.
./check_smtp -H 202.61.212.25 -v
SMTP OK - 0 sec. response time, 220 itumailsrv.itu.local Microsoft ESMTP MAIL Service, Version: 6.0.3790.0 ready at  Thu, 23 Dec 2004 15:03:51 +1100
 
I dont know what is socket timeout means?
 
If I use telnet 192.168.250.10 25, I can see the smtp service is ready. And I can ping 192.168.250.10 without problem.
 
Can anybody explaain it to me?
 




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null