Re: share address space

From my understanding, the recipient Policies in Ex2k/Ex2k3 has 3 functions:

1. Auto add (not remove) email address to mail enabled recipients in your
organization

2. Assign Mail Box Manager Settings to mailboxes in your organization

3. The UN-DOCUMENTED FUNCITION not found from most Microsoft Learning
Products:
Tell ALL the SMTP servers in your organization, to which email domains, the
emails from Anonymous senders should be accepted. One Recipient policy
accepts one email domain. If the mailboxes in your organization uses 3
different email domain subfix, you need to add 3 Recipient policies. One
for each of the email domain. The domain subfix must be bold (Set as
Primary) in the corresponding Recipient Policy, no matter whether the "This
Exchange Organization is responsible for all mail delivery to this address"
checkbox is selected or not (Authoritative or not).

In most case, function 1 and function 3 can share the same Recipient Policy.
You just add a LDAP query filter to the Recipient Policy and the users
catched by the filter (when the recipient policy has the highest priority)
will get new email address with the corresponding email domain suffix. Of
couse you can also use %g %s etc to change the format of the email.

Sometimes, instead of using LDAP query (function 1), you need to manually
assign email address to mailboxes that need a certain domain subfix. In
that case, you MUST NOT delete the Recipient Policy with that email domain
suffix set as primary, but you leave a blank LDAP query filter in it.

Darren's case is not the same as above. From what I've read, his parent
domain doesn't has any mailbox using the second domain's email subfix. He
only wants the emails for second domain "pass through" the SMTP on the
parent domain. Therefore, he doesn't need a Recipient policy for the second
domain. Just a SMTP connector connecting to the SMTP server of the second
domain with "Allow messages to be relayed to these domains" enabled is
enough. MX SMTP servers will accept both primary email domains on Recipient
Policy and email domains listed on relay enabled SMTP Connectors.


PL


Hi Darren,

Thank you for posting and thanks PL's input.

I am sorry for the delay in response due to the weekend, thanks for the
understanding. From the description, I understand this issue is that you
shared address space with your parent domain, but users in your parent
e-mail domain are now been stamped with this new e-mail address. If I am
off base, please don't hesitate to let me know.

Base on my experience, this issue is caused by entering any LDAP query. By
default, Exchange Server is authoritative for an SMTP address space when
the address space is added to a recipient policy. The correct way is to
configure your LDAP query in your parent server. To do so, please refer to
the following step in general:

1: Modify the primary SMTP address for the default recipient policy

If you want to share the SMTP address space that is specified as the
primary SMTP address space in the default recipient policy, you must
create
a new SMTP address space to act as the primary SMTP address space in the
default recipient policy. The new primary SMTP address space that you
create does not have to be valid in the Internet DNS. You can use a
private
SMTP address space such as @localhost or @example.local. This address
space
is the SMTP address space that Exchange will use to route internal e-mail
messages.

2: Configure the shared SMTP address space

3: Modify the SMTP virtual server properties to remove message forwarding
for unresolved recipients

4: Configure an SMTP connector for the shared SMTP address space

After you configure the shared SMTP address space, you must specify the
means for Exchange to determine where to route messages that do not
resolve
to an object in Active Directory. To do this, create an SMTP connector
that
has the shared SMTP address space in the Add Address Space dialog box of
the connector object. If you do not add the SMTP connector with the shared
address space, any incoming e-mail that is destined to the shared SMTP
address space is interpreted as an attempt to relay. In this situation,
Exchange does not accept the incoming e-mail. Additionally, you must
specify a server to which Exchange will forward unresolved e-mail. You can
specify this destination server by using its host name or by using its IP
address.

5: Restart the Routing and SMTP services

For detailed steps, please refer to the following article:

How to share an SMTP address space in Exchange 2000 Server or in Exchange
Server 2003
http://support.microsoft.com/?id=321721

Authoritative and nonauthoritative domains in Exchange 2000 Server and in
Exchange Server 2003
http://support.microsoft.com/kb/823158/

Please try these steps and see how everything is going.

I appreciate your time. I am happy to be of assistance to you and look
forward to your reply.

Have a nice day!

Best regards,

Inn Jin (MSFT)

Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security
=====================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:

http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

When opening a new thread via the web interface, we recommend you check
the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In
doing
so, it will ensure your issues are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.
Any input or comments in this thread are highly appreciated.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no
rights.



.

Relevant Pages

  • Re: Send E-Mails to 2 SMTP Server
    ... You can configure the exchange server to host multiple SMTP mail domains on ... Click to expand the Recipients container and then click Recipient ...
    (microsoft.public.windows.server.sbs)
  • Re: Display question in Outlook/Exchange
    ... recipient policy properties page and click the E-Mail Addresses ... If you have several recipient ... Overview of the ExchDump tool for Exchange 2000 Server and for Exchange ... I would like to explain the behavior of multiple SMTP addresses first. ...
    (microsoft.public.windows.server.sbs)
  • Re: Send On Behalf Of
    ... > user did not have permission to send to this recipient. ... > specify a user in the From field. ... > Simple Mail Transfer Protocol (SMTP) virtual server. ...
    (microsoft.public.exchange.misc)
  • What order do recipient policies fire in/help with non-authoritative domains please.
    ... Our Exchange server is non-authoritative for the SMTP domain and we're ... Routing Guide and ended up with two recipient policies as follows: ... Default Recipient Policy ...
    (microsoft.public.exchange.admin)
  • Re: company name change
    ... RUS (Recipient Update Service). ... After adding the new SMTP domain in Recip Policies and making it primary, ... Re: uncheck - yes. ... If you furthermore choose to Apply the policy Now ...
    (microsoft.public.exchange.admin)
Loading