OK, after some effort, I acquired and ran a packet logger. What I find is that
the STARTTLS command is simply never being sent to the server. Something
internal to the Microsoft TCP/IP software is capturing that particular
statement, and echoing back the 500 error, without ever sending it to the
server. (Have I mentioned how much I hate Microsoft products?)
I am guessing that I either have a broken version of whatever DLL is being used
here, or Tabor Wells suggestion of an anti-virus software intervening may be the
problem. (I do have Norton scanning all incoming and outgoing emails...)
hmm... but why is it happening from both OE and from telnet in a DOS box?
hmmm... curiouser and curiouser...
At least the problem is not with my server. As usual, the problem is probably
with Microsoft not obeying standards.
I will disable Norton and see if that helps.
Thanks.
----- Original Message -----
From: "Tamas TEVESZ" <ice@???>
To: "James P. Roberts" <punster@???>
Cc: <exim-users@???>
Sent: Tuesday, April 02, 2002 3:13 PM
Subject: Re: [Exim] Exim 4.02 TLS support
On Tue, 2 Apr 2002, James P. Roberts wrote:
> I tried telnet to port 25 of the server (puns01.punsterproductions.com), from
a
> DOS window, and got the same response to EHLO, and the same "500 Unsupported
> command" in response to typing in STARTTLS. Exim still did not report
sending
odd. i too have tried it just a few moments ago and i got a proper
"220 TLS go ahead" response.
i suggest you try dumping the network to get an independent view of
what's going on ? (that is, independent of both exim and outlook).
--
[-]
