problem sending mail to new subdomain

[SyntaX TerroR]

In our Exchange 2003 I've configured a new subdomain, by adding a new SMTP
connector. As I don't know much about Exchange, I copied all the settings
from a previous SMTP connector that was working correctly.

However I'm still left with an error, even though I triple checked all
settings.

When sending a mail internally to recip...@new.domain.com, the mail
arrives without problems. When sending mails to this address from an
external source, I get this error:

----- The following addresses had permanent fatal errors -----
<recip...@new.domain.com>
(reason: 550 <recip...@new.domain.com>: Recipient address rejected:
undeliverable address: host ourexchangeserver.w...200.4] said: 550 5.7.1
Unable to relay for recip...@new.domain.com (in reply to RCPT TO command))

In the user's properies, I've added the correct e-mailaddress as SMTP.

As far as I can see, all the settings are identical to other sobdomains that
are functioning correctly. And because the error originates from our
Exchange server behind our firewall, the error is somewhere in the Exchange
server.

Can anyone help me, please?

Thanks in advance!!

[Ward Flowers [MSFT]]

On the connector, on the addess space tab you neeed to set the option to
"allow messages to be relayed to these domains". This will place the
domain address space in the accept list and allow it to accept for that
domain--by default we only accept mail for the local doman without
configuring other domains we can accept.
--
Ward Flowers (MSFT)
Microsoft Support Engineer

This posting is provided "AS IS" with no warranties, and confers no
rights.

--------------------
>Thread-Topic: problem sending mail to new subdomain
>thread-index: AcprhU3bTDNNMtKAQh+SrSWpFr67yA==
>X-WBNR-Posting-Host: 195.144.76.166
>From: SyntaX TerroR <SyntaX...@discussions.microsoft.com>
>Subject: problem sending mail to new subdomain
>Date: Sun, 22 Nov 2009 07:06:01 -0800
>Lines: 27
>Message-ID: <9ECADC16-7C3E-421A...@microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.4325
>Newsgroups: microsoft.public.exchange.admin
>Path: TK2MSFTNGHUB02.phx.gbl
>Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.exchange.admin:107675
>NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149
>X-Tomcat-NG: microsoft.public.exchange.admin

[Ed Crowley [MVP]]

Do you have a recipient policy containing new.domain.com?
--
Ed Crowley MVP
"There are seldom good technological solutions to behavioral problems."
.

"SyntaX TerroR" <SyntaX...@discussions.microsoft.com> wrote in message
news:9ECADC16-7C3E-421A...@microsoft.com...

[SyntaX TerroR]

I did set this option. As the mails didn't arrive, I even restarted our
Exchange server (had some updates to install as well). But that didn't help.

""Ward Flowers [MSFT]"" wrote:

> .
>

[SyntaX TerroR]

There is only a default policy which hasn't changed in over 4 years (ie. it
predates the other functioning subdomains).

When I look at the E-mail address policy, it lists
%m...@domain.com
%m...@domain.local
%r--%g.%r"%s...@domain.com
as well as the X400 string.

Another subdomain is ict.domain.com where I also have an e-mail address. It
works just fine...

"Ed Crowley [MVP]" wrote:

> Do you have a recipient policy containing new.domain.com?
> --
> Ed Crowley MVP
> "There are seldom good technological solutions to behavioral problems."

> ..

> .
>

[Ward Flowers [MSFT]]

Since you have the connector, I am guessing that you are routing to another
server? If the user is on the same server but just has a different address
we do use recipient policies for those situations typically.

Assuming it is routing to another server, the checkbox to allow relay
should be enough to make it work--how many total Exchange 2003 servers in
the org? You may need to try unchecking the option and reselecting it,
then restarting SMTP and the Routing Engine on all servers to make sure the
address space is getting added properly.

--
Ward Flowers (MSFT)
Microsoft Support Engineer

This posting is provided "AS IS" with no warranties, and confers no
rights.

--------------------
>Thread-Topic: problem sending mail to new subdomain

>thread-index: AcpsHQQgMHRZl7rYROKmFqOamKRCAg==

>X-WBNR-Posting-Host: 195.144.76.166
>From: SyntaX TerroR <SyntaX...@discussions.microsoft.com>

>References: <9ECADC16-7C3E-421A...@microsoft.com>
<O3QnE4$aKHA...@TK2MSFTNGP05.phx.gbl>
>Subject: Re: problem sending mail to new subdomain
>Date: Mon, 23 Nov 2009 01:12:01 -0800
>Lines: 55
>Message-ID: <648E12ED-B139-4AB8...@microsoft.com>

>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.4325
>Newsgroups: microsoft.public.exchange.admin
>Path: TK2MSFTNGHUB02.phx.gbl

>Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.exchange.admin:107689

>NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149
>X-Tomcat-NG: microsoft.public.exchange.admin
>

[SyntaX TerroR]

Because I don't know that much about Exchange, I was just following the
previous examples. But I guess those were configured incorrectly as well, as
we only have one mailserver, and 10 or so SMTP connectors.

I added the recipient policy for this subdomain, and everything is working
now.

Thanks for your help!!

""Ward Flowers [MSFT]"" wrote:

> .
>