NMS 4.15 uses ehlo or helo?

Hi,

We have experienced this problem (NMS 4.15p3 on HP-UX).

The problem is with the SMTP Client component of Messager Express (The

Webmail component).

Messenger Express *doesn't* support Extended SMTP correctly and doesn't

fall back to SMTP correctly when talking to MTA's which don't support ESMTP.

We raised this with iPlanet Support, they have acknowledged the problem but

are not offering a solution.

Note, this is only a problem with the Webmail component (MSHTTPD) of NMS

4.15.

The MTA component (SMTPD) doesn't have any problems with ESMTP/SMTP fall

back.

In our case, the solution was to place an intermediate MTA (NMS 4.15)

between the boxes running MSHTTPD and the outside world. (A expensive brute

force solution with some *very* odd configuration, but it solved the problem

for our customer)

Cheers,

Barrie Hall

Senior Solution Architect,

Hewlett-Packard Consulting

barrie_hall@hp.com

barrieh@linuxaustralia.com (home)

"Eulogio Robles P." <erobles@mi-mail.cl> wrote in message

news:9jl6v7$4cj2@secnews.netscape.com...

> We are using NMS 4.15 SP4, and we have found several cases where the

server

> does not deliver messages to remote sites. We have found that in most

cases,

> the remote rejecting servers are Sendmail boxes, and they get errors like

> these (on the remote server) :

>

> Jul 24 20:35:39 mail-gw sendmail[4758]: NOQUEUE: my.netscape.server.com

> [xx.xx.xx.xx] did not issue MAIL/EXPN/VRFY/ETRN during connection to MTA

>

> It seems that our server is starting its SMTP sessions with a HELO command

> instead of using EHLO and it is not accepted by some sendmails. Is there a

> way to make NMS to use EHLO? It would seem easy, but there is nothing in

the

> manuals about this.

>

> Any hint will be appreciated, this is a urgent matter.

>

> regards,

>

> E. Robles

> Metropolis Intercom

>

>

708394 at 2007-6-29 17:56:08 >