Re: Default SMTP virtual server "Current Connections" Stuck

Whether it is true or not has nothing to do with why it works with Exchange
5.5.

You are comparing Exchange 2003 to a 10 yr old mail server (Exchange 5.5)
that isn't even supported any more. I can't tell you why it works with 5.5,
but I can say that the reason it isn't working with 2003 is because the
scanner isn't issuing a HELO (or EHLO) command. That is how SMTP works, per
the RFC's. Perhaps 5.5 didn't stricly follow the RFC's in this regard (it
wouldn't surprise me). I don't have a 5.5 server handy to telnet to.
Relaying has nothing to do with it at this point. If your scanner isn't
RFC-compliant and isn't going to issue a HELO command (EHLO isn't
necessary), then it isn't going to send mail (relaying or not) through
Exchange 2003.

You've seen this exact error stated in the error logs, that you need to send
a Hello (HELO or EHLO) first before attempting to specify the other parts of
the conversation.

I'd recommend that you read through RFC's 2821 and 2822, both of which deal
with SMTP. I'll quote from RFC 2821. The last sentence is the part that
your scanner is not doing.

A client SMTP SHOULD start an SMTP session by issuing the EHLO
command. If the SMTP server supports the SMTP service extensions it
will give a successful response, a failure response, or an error
response. If the SMTP server, in violation of this specification,
does not support any SMTP service extensions it will generate an
error response. Older client SMTP systems MAY, as discussed above,
use HELO (as specified in RFC 821) instead of EHLO, and servers MUST
support the HELO command and reply properly to it. In any event, a
client MUST issue HELO or EHLO before starting a mail transaction.


--
Ben Winzenz
Exchange MVP
MessageOne
Read my blog!
http://winzenz.blogspot.com
http://feeds.feedburner.com/winzenz (RSS Feed)


"Wayne Plotkin" <WaynePlotkin@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:16CF7A28-A83C-473A-8BCC-63148A85D24B@xxxxxxxxxxxxxxxx
If that is true then why does the scanner work when sending to my 5.5
server
and not Ex 2003. The only configuration I changed was the IP address to
point to 5.5 instead of the Ex2003 server. If I point it at the Ex 2003
server it sits in the SMTP current connections queue and never sends. I
have
verify that this network subnet is able to relay thru the Exchange 2003.

"Ben Winzenz [Exchange MVP]" wrote:

That's bogus, and the developer doesn't know what he's talking about.
Any
server that supports ESMTP will also support the standard SMTP verbs. If
you telnet to your Exchange server, you can issue either a HELO or an
EHLO
(Extended HELO). The problem, as was pointed out, is that your scanner
doesn't even issue the HELO command. Any app that doesn't issue a HELO
first isn't going to be able to send mail.

--
Ben Winzenz
Exchange MVP
MessageOne
Read my blog!
http://winzenz.blogspot.com
http://feeds.feedburner.com/winzenz (RSS Feed)


"Wayne Plotkin" <WaynePlotkin@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:CDE8449E-73C1-4A5C-A724-88C3A4F59361@xxxxxxxxxxxxxxxx
Yes users are scanning from the machine itself. I have talked Lanier
about a
firmware, but have gotten passed around between supposed "techs". I'm
currently waiting to hear back from one that is supposed to be the
expert
on
these devices.

I found an SMTP test utility that did the same thing as the scanner and
this
is what the developer told me when I questioned why:

"Your Exchange server is running ESMTP (Extended SMTP) and not SMTP.
Your printer (and our test app) does not fulfill the ESMTP standard as
it
does not perform the EHLO handshake.

We are working on the app and ESMTP will be supported in the next
release.

SCT Support"



"Ben Winzenz [Exchange MVP]" wrote:

The better solution would be to fix the scanner. Just because it
isn't
following RFC's for sending messages doesn't mean that the problem is
with
Exchange. Check with the company that makes the scanner to see if
there
are
any updates, or if anyone else has encountered this problem.

As far as your question, there is no way that I know of to make
Exchange
2003 "emulate" a 5.5 server.

Are you scanning\e-mailing from the machine itself?

--
Ben Winzenz
Exchange MVP
MessageOne
Read my blog!
http://winzenz.blogspot.com
http://feeds.feedburner.com/winzenz (RSS Feed)


"Wayne Plotkin" <WaynePlotkin@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:D68EC71E-E619-4C94-8424-343BC35D3287@xxxxxxxxxxxxxxxx
Oliver,

This scanner does work when sending to a 5.5 server. Is there any
why
to
make Exchange 2K3 eSMTP emulate a 5.5 server or do something similar
to
this?

"Oliver Moazzezi" wrote:

You're program is not saying 'HELO'.

When you initiate a smtp transfer you have to start the
'conversation'
by
HELO (or EHLO for eSMTP).

Try it from the command prompt. Telnet to any SMTP server you can
think
of
(do an MX dig on some random domains) and you will not be able to
send
a
mail without typing HELO first.

Order:

HELO
MAIL FROM: yoursmtpaddress@xxxxxxxxxxxxxx
RCPT TO: whoyouwant@xxxxxxxxxxxxxxx
data
type what you want
..
quit

"Wayne Plotkin" <WaynePlotkin@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:4C13B353-A5DE-4DF3-BF45-CE76C74BD383@xxxxxxxxxxxxxxxx
Hello,

I have a Lanier email\scanner that will not send via the Exchange
2003
Default SMTP virtual server I can see the connection in the
"Current
Connections" but it just sit there and never sends.

If I change the scanner to send to my old 5.5 server the messages
send
without a problem. Also other scanners on different subnets are
working
fine.

I did some testing and this is where it gets stuck.

220 emailserver.domain.com Microsoft ESMTP MAIL Service, Version:
6.0.3790.1830 ready at Tue, 12 Sep 2006 23:03:05 -0400
MAIL FROM:Administrator@xxxxxxxxxx
503 5.5.2 Send hello first

Thanks for the help!













.

Relevant Pages

  • [NT] Vulnerability in Exchange Server Could Allow Arbitrary Code Execution (MS03-046)
    ... Get your security news from a reliable source. ... In Exchange Server 5.5, a security vulnerability exists in the Internet ... an unauthenticated attacker to connect to the SMTP port on an Exchange ...
    (Securiteam)
  • RE: SMTP error (only from Outlook)
    ... This issue appeared on specify user or all SMTP clients? ... If yes, in Exchange System ... Is there any local bridgehead server listed in "Local ... to over three dozen open relay block lists. ...
    (microsoft.public.windows.server.sbs)
  • RE: strange email errors
    ... you to check the relay configuration on the SBS server. ... please restart the SMTP virtue server and Exchange ... Please also refer to the following steps to create a new SMTP Connector to ...
    (microsoft.public.windows.server.sbs)
  • Re: Exchange issues
    ... Are you up to date on all your Service Packs, both Windows and Exchange? ... > all traffic on port 25 to the SBS Exhange server. ... I suspected SMTP relaying becuase ... > You should verify that the server really isn't an open relay: ...
    (microsoft.public.exchange2000.admin)
  • Filtering email on ISA
    ... Unless you choose to create a new IIS SMTP Virtual ... Server, ordinarily you will want to Server Publish ... directly to the Exchange SMTP, ...
    (microsoft.public.isa)