Hi,
I am trying to monitor the health of a couple of smtp servers (sendmail) with a xymon instance.
As part of spam prophylaxis, these servers delay the initial response to contact by a few seconds, and drop any rogue clients that forego the handshake and just start pipelining their payload. Unfortunately, xymonnet(?) does the same, gets shown the door, and sulks with "Service smtp on $server is not OK : Unexpected service response".
I tried to play with the smtp chat in protocols.cfg
[smtp] expect "220" send "ehlo xymonnet.localdomain\r\n" expect "250" send "quit\r\n" expect "221" options banner port 25
without success. tcpdump(8)ing the communication, I was quite surprised to find that whatever I entered for the smtp chat, I always see xymon sending a 'quit', and sendmail returning a "220" banner.
This is confirmed by the xymon banner output.
My questions:
o Is it even possible for the xymon client to first wait for the server's "220" greeting before shooting off its mouth? o Where in the code does the smtp client communication happen? o What could have gone wrong for xymon to ignore the configuration in protocols.cfg without any trace in the logs?
Cheerio, Hauke
-- The ASCII Ribbon Campaign Hauke Fath () No HTML/RTF in email Institut für Nachrichtentechnik /\ No Word docs in email TU Darmstadt Respect for open standards Ruf +49-6151-16-21344