Re: Unable to relay to a.asn.au

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

But not the end of it.

I've cleaned out my recipient policies: I now have
only one, default, with the filter (mailnickname=*)

It includes @a.asn.au
It does not include @e.com.au

But I am able to receive mail sent from hotmail to
david@xxxxxxxx
and not able to receive mail sent from hotmail to
david@xxxxxxxx

Testing from www.dnsreport.com, I get
[Could not connect: Got an unknown RCPT TO response: 550 5.7.1 Unable to
relay for david@xxxxxxxxxxxxxxxxxxx there it is: I am able to receive on a
domain that is not in any recipient policy, but not able to receive on a
domain that is in the recipient policyany thoughts?(david)"david epsom dot
com dot au" <david@epsomdotcomdotau> wrote in message
news:uAZQdP6gGHA.1612@xxxxxxxxxxxxxxxxxxxxxxx
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.

That's odd, but yes.

-------

Okay, I found three policies, so I've added the domains to another policy,
and now it is working.

Thanks to both of you.

details below:

(david)

The 'first administrative group' policy priority is set to highest and
includes all the domains.
"first" is (&(mailNickname=*)(legacyExchangeDN=/O=C/OU=First
Administrative Group/*))

I do not have an administrative group called "First Administrative Group"


I see two other policies, 'staff' and 'Default'
'staff' priority is set to '1', and staff is defined as
(&(&(& (mailnickname=*) (|
(&(objectCategory=person)(objectClass=user)(!(homeMDB=*))(!(msExchHomeServerName=*)))(&(objectCategory=person)(objectClass=user)(|(homeMDB=*)(msExchHomeServerName=*)))(&(objectCategory=person)(objectClass=contact))(objectCategory=group)(objectCategory=publicFolder)
))))

The 'staff' policy email address policy does not include the dysfunctional
domains.
Something else odd: the 'first' policy generates a warning about
propagation to Exchange 5.5, and the 'staff' policy does not.

It should be ok with just the first policy shouldn't it? Just as a test,
I've added the domains to the 'staff' policy, but it's had no effect yet:
do I need to restart? I'm testing from Hotmail... It works now, I didn't
have to restart, but evidently there was a minor propagation delay
somewhere.


'staff', which I am a member of, was created by someone here.



"Nuevo" <imaneophyte@xxxxxxxxx> wrote in message
news:el7L054gGHA.4368@xxxxxxxxxxxxxxxxxxxxxxx
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

  • Re: Unable to relay to a.asn.au
    ... I understand that the 'relay' list is only for other ... it should accept mail for several internet domains? ... Our exchange server answers as exchange.c.net, ... Are you using Outlook to send mal internally? ...
    (microsoft.public.exchange.admin)
  • Re: Unable to relay to a.asn.au
    ... primary mechanism for telling Exchange to accept mail for any given domain. ... I understand that the 'relay' list is only for other ... it should accept mail for several internet domains? ... Our exchange server answers as exchange.c.net, ...
    (microsoft.public.exchange.admin)
  • Re: Unable to relay to a.asn.au
    ... Okay, I found three policies, so I've added the domains to another policy, ... to Exchange 5.5, and the 'staff' policy does not. ... it should accept mail for several internet domains? ... Our exchange server answers as exchange.c.net, ...
    (microsoft.public.exchange.admin)
  • email sent but not received
    ... 3-Create an Recipient Policy using the System Manager. ... For every domain you want to host on your exchange server ... to send e-mails to the internet. ...
    (microsoft.public.exchange2000.connectivity)
  • Re: Perimeter server
    ... email for that domain the Exchange Server address. ... But your description of the original problem talks about messages from ... Exchange to the Internet via this relay. ...
    (microsoft.public.exchange.admin)