Couple of issues with SMTP_CHECK

Chris Adams <[email protected]>
Newsgroups gmane.linux.keepalived.devel
Message-ID <[email protected]>
I'm running keepalived 1.2.13 on CentOS 6, and I have a couple of issues
with SMTP_CHECK (I checked the changelog for 1.2.14 and 1.2.15 but
didn't see these addressed; please let me know if I missed them).

First, SMTP_CHECK doesn't quite follow the SMTP standard when testing.
It looks for a response code by looking at the first three characters of
a line, and then sends a response.  However, if the fourth character is
a "-", it is a continuation line, and you are supposed to keep reading
for a line with 3 digits followed by a " ".  I ran into this when
checking a Postfix server running postscreen (solved on the Postfix side
by whitelisting the keepalived servers).

The second issue is a bigger problem.  The SMTP_CHECK always connects to
port 25, no matter the configured real_server port, or even connect_port
setting in the SMTP_CHECK config section.  For example, port 587 is used
by clients, 10025 is common with Postfix and spam filtering, etc.  Right
now, the only way to handle those cases is with an external checker or
just a TCP_CHECK.

-- 
Chris Adams <[email protected]>


------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.