Re: Remote host said: 550 5.7.1

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

  • Re: Exchange 2003 installation
    ... Configured on the NIC of the server. ... "Meinolf Weber" wrote: ... Is the ISP's DNS ... Old exchange removed - I don't know the ...
    (microsoft.public.win2000.active_directory)
  • 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)
  • Re: Help! Being Used As A Relay
    ... Make sure that your Guest account is disabled. ... Installing malwares on the server that could enable me to ... Oh, remove Relay completely. ... address that exists in your org, your Exchange will deliver the mail. ...
    (microsoft.public.exchange.admin)
  • RE: Exchange Fails to start after a reboot.
    ... this problem appears to be caused by DNS ... please try the steps below on Exchange server. ... Microsoft Online Partner Support ...
    (microsoft.public.exchange.admin)
  • Exchange 2003 SP2 - able to send but not receive email
    ... OWA already setup and running - My whole goal is to setup this server to ... DNS has example.org setup in Forward lookup zone along with MX record / A ... Now onto Exchange System Manager ... SMTP - Started - Settings below ...
    (microsoft.public.exchange.admin)
Loading