Re: inbound SMTP problem

From: S.Y. Paul Lai (syplai_at_hotmail.com)
Date: 08/04/04


Date: Wed, 4 Aug 2004 22:54:00 +0800

Please note that you can't use BackSpace key when you are using Telnet. The
BackSpace key will send to the server and the server might respond with "500
5.3.3 Unrecognized command" or "501 5.5.4 Invalid Address". Please make
sure you type your key correctly and no BackSpace is allowed; see whether
you get something like "550 5.7.1 Unable to relay for foreign@domain.com".

-- 
S.Y.P. Lai
MCSE+Internet NT4
MCSE+Security Win2K
MCSE+Messaging Win2k3
<anonymous@discussions.microsoft.com>
news:c0cb01c47a27$03e9e570$a301280a@phx.gbl
> Here is the output when telnetting in, the user is correct
> and mail enabled (even tried creating new users with the
> same effect):
>
> 220 server.mim.ca Microsoft ESMTP MAIL Service, Version:
> 6.0.3790.0 ready at  We
> d, 4 Aug 2004 08:17:15 -0500
> helo
> 250 server.mim.ca Hello [205.200.65.129]
> mail from: <ken@allcodatacomm.com>
> 250 2.1.0 ken@allcodatacomm.com....Sender OK
> rcpt ken_e@mim.ca
> 501 5.5.4 Invalid Address
>
>
>
> >-----Original Message-----
> >You need to use the files from the Exchange2k3 CD.
> Win2k3 SMTP is not
> >compatible with Exchange 2k3 SMTP.  If you use SMTP
> service from Win2k3 CD,
> >you will find all the incomming emails saved in
> C:\Inetpub\mailroot\drop
> >folder.  Exchange will not process the emails in that
> folder.  They will not
> >arrive users' mailboxes.
> >
> >I suggest you re-install Exchange 2003 and check the
> settings on SMTP
> >virtual servers and SMTP connectors.
> >
> >-- 
> >
> >S.Y.P. Lai
> >MCSE+Internet NT4
> >MCSE+Security Win2K
> >MCSE+Messaging Win2k3
> >
> >
> >"ken" <ken@allcodatacomm.com>
> >news:becc01c47a20$ab62d660$a601280a@phx.gbl
> >> Thanks but I dont think that is it.
> >>
> >> the SMTP connector isnt responding properly. After
> >> getting local and external bound mail working, and
> >> restarting the SMTP virtual server, telnetting in shows
> >> the banner BUT any command you type in is responded with
> >> a "Invalid Address"
> >>
> >> Im going to try replacing the SMTP files with that
> >> included on the install CD.
> >>
> >> >-----Original Message-----
> >> >As I remember, the default setting of Exchange allow
> >> incoming message to
> >> >your organization without authentication.  Outgoing
> >> message to domains not
> >> >in your organization need authentication.
> >> >
> >> >Your setting 2 should be the exchange default setting.
> >> However, you might
> >> >have incorrect settings about the domains in your
> >> organization.   Messages
> >> >to the domains in your organization might have been
> mis-
> >> identified as
> >> >messages to foreign domains and rejected due to no
> >> authentication.
> >> >
> >> >Please read the following docuements and verify your
> >> settings:
> >> >http://support.microsoft.com/default.aspx?scid=kb;en-
> >> us;260973
> >> >
> >> >-- 
> >> >
> >> >S.Y.P. Lai
> >> >MCSE+Internet NT4
> >> >MCSE+Security Win2K
> >> >MCSE+Messaging Win2k3
> >> >
> >> >
> >> >"Ken" <ken@allcodatacomm.com>
> >> >news:b95701c47996$33c7e490$a301280a@phx.gbl
> >> >> Win2k3 exchange 2k3, brand new installations.
> >> >> 1) The only way that I can get SMTP service to
> respond
> >> to
> >> >> incoming mail (Even telnetting to port 25) is to
> >> >> uninstall and reinstall the service from Add/Remove
> >> >> programs - Windows Components. Once I do that the
> >> service
> >> >> responds properly and messages are "sucessfully sent"
> >> as
> >> >> far as the service is concerned.
> >> >> 2) BUT local users cannot receive any mail (its like
> >> >> there is just no mail to receive), AND if they try to
> >> >> send mail to other local users it goes out, but no
> one
> >> >> ever receives thier internal mail. The only way I can
> >> get
> >> >> that to work is to reinstall Exchange. Then users can
> >> >> send mail internally and externally, but will never
> >> >> receive external mail becuase of the SMTP problem
> >> listed
> >> >> above.
> >> >>
> >> >> Oh Exchange 2k3 SP1 doesnt make a difference in
> >> >> correcting these problems
> >> >>
> >> >> HELP!
> >> >> Ken
> >> >
> >> >.
> >> >
> >
> >.
> >


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)