On Wed, 11 Feb 1998 16:58:44 -0500, Michael Smith <[log in to unmask]>
wrote:

>Our LSMTP ....

Questions about the LSMTP mailer product are best sent to a different list:

  [log in to unmask]

For those interested, here is Juan's response to Michael's problem:

Michael,

Ben Parker forwarded your message to me (I don't usually read LSTSRV-L).
In the future, you may want to write to [log in to unmask] or LSMTP-L...

>      Our LSMTP (LSMTP Lite for Windows NT v1.1a) is having a problem
>      sending e-mail to a specific domain (VISUS.JNJ.COM), but our corporate
>      e-mail system gateway (IMA) is able to send to that domain with no
>      problem. Below is a clip from the LSMTP log file. These entries fill
>      the log file for the last five days, so it's been trying every 10
>      minutes since last week. It finally gave up today.
>
>      Any help would be very much appreciated.

I could reproduce your problem.  The logging data below comes from a
newer version of LSMTP (which isn't available yet), and which optionally
allows to dump the data received in hexacedimal:

  11:57:43 (  1)O opened VISUS.JNJ.COM mail-gw2.jnj.com
  11:57:43 mail-gw2.jnj.com(  1) rd 48
  11:57:43 000000 323230205468752C20534D5450203132 220 Thu, SMTP 12
  11:57:43 000010 2046656220313939382030363A30303A  Feb 1998 06:00:
  11:57:43 000020 3535202D303530302028455354290D0A 55 -0500 (EST)..
  [...]
  11:57:43 mail-gw2.jnj.com(  1) rd 25
  11:57:43 000000 35303020436F6D6D616E6420756E7265 500 Command unre
  11:57:43 000010 636F676E697A65640A               cognized.
                                  ^^

At least part of the problem is due to mail-gw2's not finishing his
reply with CRLF as mandated by the SMTP protocol (RFC 821), but just
with LF (`a la Unix').  With LSMTP Classic (i.e. non-Lite) you could
possibly bypass this problem by disabling the EHLO command to the
site (assuming this error only occurs with the reply to EHLO).  The
"proper" way to fix the problem, however, is to contact the postmaster
of VISUS.JNJ.COM and ask him to fix the problem.

.. Juan
=====
So, Pete, your comment about unusual screen position is related to the same
thing.