Re: Basic Design Question on Windows Domain Vs Internet Domain Names

Tech-Archive recommends: Fix windows errors by optimizing your registry

Wow, that sounds really simple, Asher. Thanks!

I have a follow on question, though it may go a little beyond the realm of
the original issue.

As you might have guessed by now, our Exchange is sitting inside our
network, behind the firewall, using a private static IP address. I've
already configured it as our SMTP server. So all POP3 accounts in Outlook
clients point to it for outgoing server.

Now what steps do I need to take in order to have our outside mail directly
come to the Exchange and simply bypass the POP3 boxes, currently hosted by
our Domain Name registrar (AIT)?

Regards,



"Asher_N" <ashernat@xxxxxxxxx> wrote in message
news:Xns99E8A6CA44CD61203214562@xxxxxxxxxxxxxxxx
Go to the recipient policy. On the e-mail address tab, click new. Select
SMTP. In the address field, type in @xyz.com, select 'This Exchange
organization is responsible...'. Click OK.

Select the new address, clisk on 'Set as Primary'.

You're done. Whenever you create a new user, he will get a @abc.local,
@xyz.com and a X.400 address with the @xyz.com as primary.

"Tom Bombadill" <Genius_poster@xxxxxxxxx> wrote in
news:OFkRl3vJIHA.3356@xxxxxxxxxxxxxxxxxxxx:

Thanks for following up with me, Bharat!

So let's see if I got this straight.

Our internal domain name: abc.local
Our Internet domain name: xyz.com

I went to Exchange System Manager | Recepients > Recepient Policies >
Default Policy > Properties > E-mail Addresses (Policy) tab and here's
what I see:

SMTP @abc.local
X400 c=us;a= ;p=abc;o=Exchange;

Both entries are checked.

Are you saying I need to make a change here to somehow replace the AD
domain name with the xyz.com domain name? If so, what changes do I
need to make?

Thanks again.


"Bharat Suneja [MVP]" <bharat@xxxxxxxxxx> wrote in message
news:eCjxOXvJIHA.1208@xxxxxxxxxxxxxxxxxxxxxxx
- Your AD namespace can be the same as your registered external
domain(s) or it can be a different namespace, perhaps unregistered or
even invalid (using a suffix like .local for instance... ).
- In the former case, no issues.
- In the latter case, the default Recipient Policy picks up your AD
domain and uses it to create email addresses.
- You can modify it to use the external/registered domain.
- Regardless of email addresses, it's not like you're using one set
of addresses to communicate internally, and another set to
communicate with internet senders/recipients. Internally, Exchange
looks up AD to resolve recipients. If recipients have email addresses
using the registered domain (set as default), regardless of all other
email addresses they may have (or not), it works for both internal
and internet mail. - As a sidenote, the only use for the registered
domain (and email addresses using those) is for inbound mail sent by
internet senders - the domain part is used to perform DNS lookups to
route messages to your designated server(s). Outbound internet mail
works regardless of email address used, but you won't be able to get
replies if the address is invalid.
--
Bharat Suneja
MVP - Exchange
www.zenprise.com
NEW blog location:
exchangepedia.com/blog
----------------------------------------------


"Tom Bombadill" <Genius_poster@xxxxxxxxx> wrote in message
news:eaKcAZuJIHA.3916@xxxxxxxxxxxxxxxxxxxxxxx
Hi Bharat,

Forgive my ingnorance, but could you please elaborate on the idea a
little further? We have an Exchange 2003. What modification do you
need to make to the Recipient Policy, and how does it help address
the problem? The way I see it, your AD based email addresses still
remain unresolvable through Public DNS. So I still do not understand
how you can use your AD based accounts for external communication.

If you know of any links that may shed light on this issue for me, I
would grealy appreciate it.

Thanks,

"Bharat Suneja [MVP]" <bharat@xxxxxxxxxx> wrote in message
news:O4s%23lrmJIHA.3400@xxxxxxxxxxxxxxxxxxxxxxx
You simply modify the Recipient Policy (in Exchange Server
2003/2000) or Accepted Domain and EmailAddressPolicy (Exchange
Server 2007) to reflect the external/registered domain.
--
Bharat Suneja
MVP - Exchange
www.zenprise.com
NEW blog location:
exchangepedia.com/blog
----------------------------------------------


"Tom Bombadill" <Genius_poster@xxxxxxxxx> wrote in message
news:urxMXNlJIHA.3636@xxxxxxxxxxxxxxxxxxxxxxx
Hi All,

I have had a longstanding question on the proper implementation of
Exchange and how to reconcile the internal Windows Domain name
versus the publicly registered web domain name.

It was my impression that Microsoft recommended using a different
internal windows domain name, than your web domain name. In this
case, you end up with 2 sets of email addresses; one AD based
addresses which should not be used for external communication, and
another set of publicly addressable, normally POP3, email
accounts.

We like Exchange because of the conveniences that it would offer,
such as calendar sharing, mailbox management, possible central
spam management, etc...

Given the above situation, is it possible to use 1 set of exchange
hosted email addresses for both external and internal use?

I'm sure it's an issue many of you have had to deal with before.
Is there a correct way of addressing the situation?

Thanks for your help.











.

Relevant Pages

  • Re: Is Exchange relaying to local mailboxes?
    ... One Exchange 2003 Server. ... If you do not have a Recipient Policy for a domain, ... Is the Internet domain set up properly in your recipient policy? ...
    (microsoft.public.exchange.connectivity)
  • RE: Cant send or receive e-mail to POP3 users on same domain--HELP!
    ... Run the CEICW and go through the Internet and firewall option. ... If you choose to forward emails to the ISP's email server (smart ... Connector for POP3 Mailboxes' option, ... The Mailbox type is User Mailbox, and select the appropriate Exchange ...
    (microsoft.public.windows.server.sbs)
  • Re: Basic Design Question on Windows Domain Vs Internet Domain Names
    ... the default Recipient Policy picks up your AD ... communicate with internet senders/recipients. ... Internally, Exchange ... how you can use your AD based accounts for external communication. ...
    (microsoft.public.exchange.design)
  • RE: Catchall not working, EXTERNALLY?
    ... When I open the connection (over internet) to my exchange account, ... the data is stored on the Exchange server side. ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
  • Re: Basic Design Question on Windows Domain Vs Internet Domain Names
    ... the default Recipient Policy picks up your AD domain and uses it to create email addresses. ... Regardless of email addresses, it's not like you're using one set of addresses to communicate internally, and another set to communicate with internet senders/recipients. ... Exchange looks up AD to resolve recipients. ... In this case, you end up with 2 sets of email addresses; one AD based addresses which should not be used for external communication, and another set of publicly addressable, normally POP3, email accounts. ...
    (microsoft.public.exchange.design)