Re: Unable to relay to a.asn.au

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Have you added all these domains to your recipient policy? This is the
primary mechanism for telling Exchange to accept mail for any given domain.
Of course Exchange will want to stamp this domain name as an email address
on all user accounts included in the LDAP filter of your recipient policy.

Nue
"david epsom dot com dot au" <david@epsomdotcomdotau> wrote in message
news:%2385Qpm4gGHA.3572@xxxxxxxxxxxxxxxxxxxxxxx
I need to receive mail for c.com.au and c.net and
a.asn.au and w.com and e.com.au (and a few others).

I can receive mail for c.net and c.com.au, but other
mail gets refusal to relay.

I understand that the 'relay' list is only for other
servers inside my network, and I should remove the
ineffective entries that have been made to that list.

Why would I be getting error 550 5.7.1? What should
I do about it? How do I tell the Exchange Server that
it should accept mail for several internet domains?

(david)


1) No, we are not using SMTP internally. The internal
mail test was the only way I could think of to test
exchange and active directory: the destination exists
but the path is faulty.

2) I support the internet domains c.net and c.com.au and
a.asn.au Our internal Windows domain is c.net, and we use
the same name servers for both the internal windows c.net
domain and the external c.net internet domain (don't blame
me for that, and no, I can't change it).


3) The mx records all point to mail.c.net

4) Our exchange server answers as exchange.c.net, which is
a private address. That is, when you connect to mail.c.net,
the ehlo indicates exchange.c.net. This does not in
general prevent us from receiving mail on c.net and c.com.au


I control the name servers for these domains. The A
records point to my name servers and mx record points
to my exchange server. My exchange server answers,
and refuses to 'relay' for these domains.


"Rich Matheisen [MVP]" <richnews@xxxxxxxxxxxxxxxxxxxxx> wrote in message
news:i7ul72hilnq9g9erpi899j90vhel8j2a8f@xxxxxxxxxx
"david epsom dot com dot au" <david@epsomdotcomdotau> wrote:

I just did a mail test and got:
mail.xxx.net. - 203.xxx.xxx.xxx [Could not connect: Got an unknown RCPT
TO
response: 550 5.7.1 Unable to relay for postmaster@xxxxxxxxxxxxxxxxxxxx
is
our exchange server.

So, is a.asn.au a domain or a FQDN? The way you typed that information
it isn't clear if mail.xxx.net is part of the domain you're trying to
send to or a separate name.

If I look at the 'default virtual smtp server'
properties, relay restrictions, I see that"select which computer may
relay
through this virtual server" is set to "only the list below" which
includes
a.asn.au

If a.asn.au is the target and it's not on your network, it has no
business being there. What you want in that list are the IP
addresses/networks/fqdn of machines, typically on *your* network, that
you want to let relay through your server.

Internally I'm able to send mail to postmaster@xxxxxxxx, but it
fails from external sources.What is likely to cause this problem?

Are you using Outlook to send mal internally? Outlook, configured to
use Exchange server doesn't use SMTP to send message.

Where else
should I look?(david)



--
Rich Matheisen
MCSE+I, Exchange MVP
MS Exchange FAQ at http://www.swinc.com/resource/exch_faq.htm
Don't send mail to this address mailto:h.pott@xxxxxxxxxxxxx
Or to these, either: mailto:h.pott@xxxxxxxxxxxxxxx
mailto:melvin.mcphucknuckle@xxxxxxxxxxxxx
mailto:melvin.mcphucknuckle@xxxxxxxxxxxxxxx




.

Relevant Pages

  • Limiting a users sending capabilities
    ... Most Exchange servers are used as Internet mail systems, ... Create a new SMTP Connector on the Exchange Server and associate ... since connector restriction is turned off by default for Exchange 2000. ...
    (microsoft.public.exchange2000.admin)
  • Re: smarthost authentication
    ... We have a small group of users on an Exchange 2003 server. ... clients to directly handle internet stuff. ... The second account is the Exchange Server account. ...
    (microsoft.public.exchange.setup)
  • [NT] Vulnerability in Exchange Server Allows Remote Code Execution (MS05-021)
    ... A remote code execution vulnerability exists in Microsoft Exchange Server ... their choice in the security context of the SMTP service. ...
    (Securiteam)
  • Re: Unable to Receive Email from the internet
    ... Exchange Server 2007: internet email without Edge servershttp://exchangepedia.com/blog/2006/07/exchange-server-2007-internet-e ... ... It seemed to install fairly clean. ... see I'm running into a RELAY problem. ...
    (microsoft.public.exchange.setup)
  • Re: MS EXchange behind NAT
    ... > server as an Exchange server if we have to. ... >> 1) open smtp on your firewall to internal Exchange. ... >> gateway in your dmz, open smtp from Internet to that box in dmz, open ...
    (microsoft.public.exchange.design)