Re: This is not a relay host - mail must be to or from host domain

The group is created in active directory and is a universal
distribution group

Rich Matheisen [MVP] wrote:
"ICT User" <ictuser2002@xxxxxxxxxxx> wrote:

We have a distribution group that contains external contacts. When
someone from that group receives an email and does a reply it sends the
email back to our exchange server but then they get an ndr because the
exchange server returns the error "This is not a relay host - mail must
be to or from host domain"

That's not an error that Exchange would send.

I explained the ndr incorrectly. The person who replies to the group
gets an ndr (i dont have the email with the headers so im not sure
exactly what the message is) but we certainly get the following message
appear in our postmaster account.

There was a SMTP communication problem with the recipient's email
server. Please contact your system administrator.
<our exchange server #5.5.0 smtp;551 This is not a relay
host - mail must be to or from host domain.>

We have only started getting this message since upgrading our smart
host to a newer version but this message in postmaster implies that it
has come from the exchange server and nothing to do with smart host


as it wont then send on the email to the
rest of the external contacts contained in the distribution group.

Why would you expect it to? The message isn't reaching your Exchange
server.

Do
I just need to add the domain name to the relay restrictions list under
the access tab on the smtp virtual server?

If the message is sent with the correct "From:" address (one that's in
your Recipients Policy) there should be no problem with mail delivery.

I'm being stupid but i dont know exactly what you mean by this! The
group has a from address of group@xxxxxxxxxxxxxxxxx which is in the
only recipient policy we have...

--
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

  • Multiple smtp connectors with same address space ...a bug in Excha
    ... I posted a question to the Exchange Server administration list a few days ago ... using DNS and for other users I would like it to use a smart host to relay ... The Delivery Restrictions are set differently on each connector. ... group seem to be going through the smart host instead of resolving the host ...
    (microsoft.public.exchange.admin)
  • Multiple connectors with same address space ... a bug in Exchange
    ... I posted a question to the Exchange Server administration list a few days ago ... using DNS and for other users I would like it to use a smart host to relay ... The Delivery Restrictions are set differently on each connector. ... group seem to be going through the smart host instead of resolving the host ...
    (microsoft.public.exchange.design)
  • RE: Connection Unavailable???
    ... doing an nslookup computername.domain and see which DNS server is trying to ... > From a remote site, I can ping my exchange server all day long, either by IP ... I also note that the clients at ... > about how the remote DNS/WINS server is resolving the host name. ...
    (microsoft.public.exchange.connectivity)
  • RE: Connection Unavailable???
    ... doing an nslookup computername.domain and see which DNS server is trying to ... > From a remote site, I can ping my exchange server all day long, either by IP ... I also note that the clients at ... > about how the remote DNS/WINS server is resolving the host name. ...
    (microsoft.public.outlook.general)
  • Exchange Hosting Questions
    ... server at the host and set up a VPN between our office and the host over our ... on order and will pool the bandwidth but make it so that the Exchange server ... users in Los Angeles use the OWA client provided by our host to access their ... We like our hosted solution as it gives us piece of mind knowing that there ...
    (microsoft.public.exchange.setup)
Loading