The V3.0b upgrade is supposed to solve this problem.
Apparently it is due very soon.
We have experienced the same problem with MS Exchange Servers, which
also use emsmtp
>From: Basil McCrea [SMTP:mccrebsi @
>Sent: Monday, July 21, 1997 6:48 PM
>To: 'Teo Yoke Foong'
>Cc: 'firewalls @
>Subject: AW: Firewall-1 & ESMTP connectivity
>We had the same problem. We got around it by upgrading to sendmail v8.8.6. It
>bring the "220 ESMTP spoken here" reply, instead it replies
>220 hpxxxx ESMTP (8.8.6/xxxxxx).
>Eventhough upgrading was alot of effort just to get rid of 1 line.
>Von: Teo Yoke Foong
>Gesendet: Montag, 21. Juli 1997 04:09
>An: 'Firewalls @
>Betreff: Firewall-1 & ESMTP connectivity
>Has anyone encountered this problem before ?
>We are using firewall-1 to store and forward Email between the internet
>and our production Email server. Firewall-1 is used to download Email
>from the internet via SMTP, and then uses SMTP to forward the EMail to
>our server (I believe using Firewall-1 for SMTP proxy is standard
>practise). Firewall-1 fails to communicate with our internet providers
>SMTP server, the log file has the following error "Agent Dequeuer error
>We suspect that Firewall-1 has an incomplete parser. The
>SMTP hosts return two lines when you connect to telnet port 25. e.g.
>220-hxx0, HP sendmail ready at ...
>220 ESMTP spoken here
>it is valid with SMTP to use 220-, with the hyphen meaning more info
>lines will follow, the 220<space> denotes this is the last 220 type
>It looks like Firewall-1 reads the "220-hxx0..." line, and then issues
>its SMTP HELO, it then reads the next line expecting "250 hxx0 Hello
>...", but gets the "220 ESMTP spoken here" line (since it is still in
>the buffer). This appears to confuse Firewall-1, which fails to
>Appreciate any explanation and workaround.
>Btw, is firewall-1 is using smap and smapd ?
>Thanks in advance.