Re: Remote host said: 550 5.7.1

Tech-Archive recommends: Fix windows errors by optimizing your registry

I understood everything until you said I should consider opening a case
with PSS.

I have no clue who they are...


Ben Winzenz [Exchange MVP] wrote:

I wouldn't go that far, but I might perhaps consider
uninstalling/reinstalling IIS, then reinstalling Exchange (and Exchange
SP's) again.

This also might be the appropriate time to consider opening a case with PSS.

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


<stephen.mcgahan@xxxxxxxxx> wrote in message
news:1154688026.957697.295620@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Ok, I have now reinstalled Exchange and initially I got event 418, so I
followed MS Knowledge base article
http://support.microsoft.com/kb/326854/en-us

However, when I telnet in I am still getting the same banner.

Does this mean a complete rebuild of the server ?

stephen.mcgahan@xxxxxxxxx wrote:
When I telnet internally, I am getting Microsoft ESMTP Mail Service,
version 5.0.2195.6713

From the KB article it does indeed look as if you were right and that
it is IIS listening on same port that is causing my problem

I am going to reinstall Exchange now and will let you know how I get
on...

Thanks again for everything Ben
stephen.mcgahan@xxxxxxxxx wrote:
From memory ISA does have IIS installed along with the SMTP service

I published the Exchange RPC Server using the server publishing utility
(ISA 2000) and also published SMTP service on port 25. You could well
be right that ISA is listening on 25, will check that out tomorrow
morning first thing. I do remember seeing an event 115 in system logs
on the Exchange server, but thought nothing of it as it wasn't
recurring constantly.

Thanks for all your help so far, would you mind checking this thread
tomorrow and I will let you know what I see when I telnet in

Ben Winzenz [Exchange MVP] wrote:
No. You would just need to launch setup, then when you get to the
components, select Reinstall.

I'd recommend that you go back and look at your ISA rule. Does ISA
have IIS
installed? How exactly did you publish the Exchange server? Can you
detail
what kind of rule you used? What I'm getting at here is that you
should
probably make sure that your ISA server isn't the one that is
listening on
port 25.

If you telnet to your Exchange server from the internal network on
port 25,
what is the banner that you see? Is it the same one with the same
smtp
version info? The KB article I sent you lists all the Exchange
version
numbers, so if telneting internally gets an Exchange banner, then you
know
it is a problem with ISA.

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


<stephen.mcgahan@xxxxxxxxx> wrote in message
news:1154624001.949487.240070@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
When I open IIS I see a few boxes in red, I am not at work at the
minute so can't remember them all. They are related to Exchange
though,
there's no SMTP server section there though (Red is bad, this much
I do
know, hadn't noticed this before as I thought the problem was
elsewhere)

When you say that I will have to reinstall exchange, does that mean
I
will have to remove it from Active Directory first ?

Ben Winzenz [Exchange MVP] wrote:
http://support.microsoft.com/?kbid=158530

The version number your inbound SMTP server gives does not
correspond to
a
valid Exchange version/build number. It corresponds to the IIS
SMTP
Service
(Windows 2000 SP4 I believe).

If you open IIS Manager on your Exchange server, do you see an
SMTP
Server
section? If so, that means IIS is manaing SMTP, not Exchange. To
fix
that,
you would need to reinstall Exchange (it won't touch the
databases, just
the
binary files), which will let Exchange take over managing SMTP.
This
could
be your issue.

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


<stephen.mcgahan@xxxxxxxxx> wrote in message
news:1154619118.702281.70240@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Ok, did what you suggested regarding the relay and external DNS

There is no filtering in place whatsoever on the exchange server

The firewall is an ISA server and I have published the Exchange
server
and smtp protocol in it, all seems to be fine that end. There
is no
spam filtering on the ISA server


Ben Winzenz [Exchange MVP] wrote:
Ok - thanks for the clarification.

Couple of things:
1. Unless you have multiple computers inside your subnet that
have to
relay
(Outlook doesn't count - MAPI clients don't relay), then I'd
get rid
of
your
subnet. It's a better practice to only add specific IP's of
systems
that
might need to relay. This also shouldn't be contributing to
the
problem
you
have, but it's a good thing to do.
2. Get rid of the external DNS entries under the SMTP VS
settings.
They
shouldn't be contributing to your problem, but I always
recommend to
let
the
Windows DNS client do what it is better at doing. Plus, I'm
fairly
certain
that the DNS resolver in Exchange is single-threaded (only one
query
at a
time), where the DNS client for Windows (TCP/IP settings) is
multi-threaded - basically, it's faster.
3. Do you have any filtering in place? Recipient filtering,
connection
filtering, IMF, etc.
4. Doing a DNS report on your domain doesn't bring up any
serious
issues -
you don't have a PTR record for your MX record, but that won't
cause
problem
receiving mail. It's better to have one, as you'll have
problems
sending
to
some domains if you don't, but again, not relevant to your
current
problem.
5. Your primary MX record appears to go to a Windows 2000 SMTP
server,
not
an Exchange server - have you checked on that server to see if
that is
the
problem? The banner I get when I try and connect is:
220 <your MX record> Microsoft ESMTP MAIL Service, Version:
5.0.2195.6713
ready
Do you have any anti-spam software on that box? Can you
eliminate
that
from
the picture temporarily? Set your firewall to forward port 25
directly
to
Exchange instead of the SMTP server and see if that makes a
difference.

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


<stephen.mcgahan@xxxxxxxxx> wrote in message
news:1154614779.064217.184080@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Yes Ben this is my domain, I also have another you see which
I have
been sending from to test it.

The domain in question is itxpni.com

SMTP Virtual server settings are as follows

General tab, IP Address is All unassigned
Access tab, authentication; anonymous, basic and integrated
windows
authentication all checked
connection control, nothing configured
relay restrictions, only the list below and I have configured
that
for
the subnet address I am using with allow all computers that
successfully authenticate to relay, regardless of list above
checked

message tab, default settings

delivery tab, outbound security is for anonymous access
outbound connection, default settings
advanced delivery, no smart host and just the name of the
exchange
server in fully qualified domain name
i have also got the external dns addresses of the isp
configured.





Ben Winzenz [Exchange MVP] wrote:
I'm confused - is this *your* domain that you are talking
about, or
a
remote
domain you are having problems sending to? The beginning
seems to
indicate
it is your domain, but you also seem to hint that it's a
remote
domain.

If it is your domain, what is the domain name?

Also, what do you have set in the SMTP Virtual Server
settings?
Detail
all
of them, please, not just the Relay settings.

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


<stephen.mcgahan@xxxxxxxxx> wrote in message
news:1154611696.932110.211120@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
hi folks

basically the situation is, I have an Exchange server
which I
have
recently installed, MX records are in place on the ISP
side, can
send
internally and externally.

The problem arises when I send to any address in the
domain and I
get
the following

xxx.xxx.xxx.xxx does not like recipient
Remote host said: 550 5.7.1.Unable to relay for
j.bloggs@xxxxxxxxxxxx

I have checked recipient policies and all is fine there,
also I
have
used metaedit and deleted the LM\DS2MB key, then restarted
the
appropriate services

Yet I am still getting this error when I try to email the
domain
in
question.

Anyone have any other ideas on how to solve this ?






.

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)