Re: SMTP Sharing HELP!!




Do I need a recipient policy for the @otherlocation.companyname.com
contacts???or does the SMTP connector route according to the address space
assigned to each contact??

"Bharat Suneja [MVP]" wrote:

The targetAddress is populated when you create the Contact and specify an
external email during the Contact creation.

This does show up in the email addresses tab - which is a view of the
proxyAddresses attribute in AD. The targetAddress gets inserted in the
proxyAddresses - so you will see it there, and it will be the default
address (uppercase - i.e. SMTP:joe.contact@xxxxxxxxxxxxxx) - and also in the
"mail" attribute shown on user's properties General tab as e-mail.

If your Recipient Policy applies to Contacts, it will also generate email
addresses from that policy - so you will see additional email addresses from
your smtp domain(s) also in the email addresses tab.
--
Bharat Suneja
MVP - Exchange
www.zenprise.com
NEW blog location:
www.exchangepedia.com/blog
----------------------------------------------


"matthew_h" <matthewh@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:2219C608-032B-4D21-830E-70018F3B49EE@xxxxxxxxxxxxxxxx
Thanks again Bharat!

Are there any KB articles for setting up the Exchange Server on the
receiving end as pertaining to KB article 315511? I looked but did not
find
anything.. Is it necessary or recommended to centralize the outbound SMTP
traffic from the other locations through my central location?

Just to make sure I understand KB 315511.
Regarding mail recipients outside of my local domain/organization, I
should
create Contacts in AD Users & Computers. In Properties for the new
Contact,
on the Exchange General tab, the email address will be set to
user_name@xxxxxxxxxxxxxxxx And then on the Email Addresses tab, I set the
Primary SMTP address to user_name@xxxxxxxxxxxxxxx and the "target" (not in
bold) or secondary SMTP address would be
user_name@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx (for example). I would then set up
the SMTP Connector to forward the @otherlocation.companyname.com mail to
the
smart host at the "other location". Does that sound right?

THANKS BHARAT!!!

"Bharat Suneja [MVP]" wrote:

The centralized smtp domain sharing method will work better, imo.
--
Bharat Suneja
MVP - Exchange
www.zenprise.com
NEW blog location:
www.exchangepedia.com/blog
----------------------------------------------


"matthew_h" <matthewh@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:54B340C4-BF59-42AF-9744-436ED2AB70A4@xxxxxxxxxxxxxxxx
Thank you so much Bharat. I appreciate your time & expertise!

Given that my Exchange server is already configured to the
specifications
of
KB article 321721....

I have two IPs listed in "Forward all mail through this connector to
the
following smart hosts". One of those will be Authoritative. The
non-authoritative Exchange server will not be set to forward to the
end-of-line Authoritative server.

Is that configuration acceptable??... to have two IPs as smart hosts?

Or do you think the "Centralized SMTP Domain Sharing" would be the
better
method?




"Bharat Suneja [MVP]" wrote:

Responses inline.

--
Bharat Suneja
MVP - Exchange
www.zenprise.com
NEW blog location:
www.exchangepedia.com/blog
----------------------------------------------


"matthew_h" <matthewh@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:72978ED6-13DE-43ED-884E-B2D0176C87A0@xxxxxxxxxxxxxxxx

SMTP Address Space Sharing

I have set up a 2003 Exchange server for SMTP Address Sharing as
described
in KB article 321721.
http://support.microsoft.com/Default.aspx?id=321721

My Exchange server will be the first point of contact and then
forward
SMTP
mail to 3 other locations. Each location is independent and a
completely
separate domain. We only share the @companyname.com address space.
Would
someone PLEASE clarify a few things for me???

I have configured Exchange exactly as described in KB 321721. I have
created
mailboxes for all mail-enabled users at MY location, set up the
Recipient
Policies and the SMTP connector. I have tested and confirmed
successful
internal mail flow and outgoing mail, but I have not yet tested the
SMTP
sharing.

1. Do I need to create mailboxes for each of the users at the other
geographic locations???

My understanding is that when Exchange receives an incoming message
it
looks
through Active Directory for a matching mail account. When Exchange
does
not
find the correct recipient, Exchange then forwards the email to the
IP
addresses listed in the SMTP connector (located at "Forward all mail
through
this connector to the following smart hosts") to search for the
recipient.
If
a recipient is not found, the end-of-line Authoritative Exchange
server
returns a non-delivery report to the sender.

Mailboxes for users at those locations will/should be created at those
locations, not within your system.


2. Someone told me that I have done this all wrong and that I should
have
to
create individual routing groups for each geographic location along
with a
mailbox for each user, but according KB 321721 that is not correct.
Am
I
right or do I need to start all over????

If all your Exchange servers are in the same AD Forest, you may look
into
Routing Groups - but were that the case, this wouldn't be a case of
sharing
address space - all your Exchange servers would be in the same
Exchange
Org - in other words, Exchange Orgs span the AD Forest = each Forest
can
only have one.

The assumption here is that you're not in the same Forest.


3. Regarding the SMTP Connector, in the box "Forward all mail
through
this
connector to the following smart hosts", this is where I enter the
static
IP
addresses of the other locations, correct????

Please let me know if I have misunderstood anything. Thanks in
advance
for
your time and help!


Correct - and when you type IP addresses, these should be in square
brackets - [1.2.3.4]

Please note, the above solution works if you intend to send from one
Org
to
another mail system, which may or may not be authoritative for the
namespace. If it's not, it forwards it to the third system, which may
be
authoritative and thus the last mail system that will handle the
message
and
generate NDRs for any recipients not found/resolved in that system -
sort
of
like a chain.

If you want to implement a central "mail-switching" infrastructure
where
your first domain is like the central message routing hub, receives
inbound
mail, and handles delivery to different other mail systems (rather
than
passing it to the second mail system/Exchange Org, which passes it on
to
the
3rd... ), please refer to the following KBA:

XADM: How to Set Up Centralized SMTP Domain Sharing in Exchange 2000
Server
for Independent Organizations
http://support.microsoft.com/default.aspx?scid=kb;en-us;315511










.



Relevant Pages

  • [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: Display question in Outlook/Exchange
    ... I would like to explain the behavior of multiple SMTP addresses first. ... The name will be the same because Exchange server ... How many recipient policies you configured in ESM? ... Click other recipient policy to check what the primary email address ...
    (microsoft.public.windows.server.sbs)
  • 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: Delay
    ... If you edit the metabase incorrectly, ... Right-click "Microsoft Exchange System Attendant", ... Add a new Recipient Policy ... Click Add to add a new SMTP address. ...
    (microsoft.public.exchange.admin)