Postfix won't issue ESMTP verbs

I have a Postfix 2.1 installation on Red Hat Linux 9.0 acting as an
anti-spam/anti-virus gateway in front of my corporate MTA. Recently, I
decided to try to add TLS and SASL support for e-mail submission on the
submission TCP port (TCP port 587). In the process of troubleshooting
this and looking for the STARTTLS command when telnetted to port 587, I
noticed that Postfix wasn't returning ANY ESMTP verbs. Here's what I
get when I telnet to port 587 (the submission port):

220 mailgw.domain.com ESMTP Postfix
ehlo example.com
250-mailgw.domain.com
250-PIPELINING
250-SIZE 10240000
250-ETRN
250 8BITMIME
quit
221 Bye

This is the same list I get when I telnet to the "public" SMTP port on
TCP port 25 as well.

I do have iptables running on the Postfix server, but this seems
irrelevant to me; in any case, I have tried with iptables both on and
off. Same for any client-side firewalls--again, not that I expect any
of them would actually proxy or interfere with SMTP traffic, but just
to eliminate any possibilities.

This is a pretty "plain" configuration of Postfix (with amavisd-new to
interface to SpamAssassin and ClamAV), so I didn't post main.cf or
master.cf here. Let me know if I should post a follow up with that
information, or if there is something so patently obvious that I am
missing it.

TIA.

--
Scott Lowe

On 2004-12-27 22:29:36 -0500, Scott Lowe <me@privacy.net> said:

> I have a Postfix 2.1 installation on Red Hat Linux 9.0 acting as an
> anti-spam/anti-virus gateway in front of my corporate MTA. Recently, I
> decided to try to add TLS and SASL support for e-mail submission on the
> submission TCP port (TCP port 587). In the process of troubleshooting
> this and looking for the STARTTLS command when telnetted to port 587, I
> noticed that Postfix wasn't returning ANY ESMTP verbs. Here's what I
> get when I telnet to port 587 (the submission port):
>
> 220 mailgw.domain.com ESMTP Postfix
> ehlo example.com
> 250-mailgw.domain.com
> 250-PIPELINING
> 250-SIZE 10240000
> 250-ETRN
> 250 8BITMIME
> quit
> 221 Bye

Pardon me for responding to my own post, but I was able to resolve the
issue. Despite all indications to the contrary, the binary package
that I had used to install Postfix did not have support for TLS and
SASL. After building my own RPM from a source RPM, then installing the
newly-compiled version, everything works as expected.

--
Scott Lowe