Re: company name change

Yes, more than one SMTP address can be used for a single recipient policy.

I suppose what you could do here is:

1. Add new domain to Default recipient policy.
2. Make new domain Default (Reply-to) address, making sure that Exchange is
set to be authoritative.
3. Uncheck "current" domain - this will prevent Exchange from stamping new
users with an e-mail address using current domain.

As far as how you are receiving mail, I'm not sure. It isn't the CCMAIL
address (that is for Lotus Notes). Do you have some sort of POP3 connector
in place? Aside from that, if the domain isn't listed in a recipient
policy, Exchanage can't receive mail for that domain.

--
Ben Winzenz
Exchange MVP
MessageOne
Read my blog!
http://winzenz.blogspot.com
http://feeds.feedburner.com/winzenz (RSS Feed)


"Mark Clark" <MarkClark@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:3456E968-011E-412A-9008-709AD6887C5B@xxxxxxxxxxxxxxxx
http://support.microsoft.com/?kbid=289833
It would seem that more than one SMTP address can be used for a single
recip
policy. This areticle should address many of my questions.

"Ben Winzenz [Exchange MVP]" wrote:

1. That would be my guess.

3. I'm not sure how your SMTP servers are configured. It could be that
the
new domain simply needs to be configured in the Filtering software. Or,
it
could be that you need to add the new domain into the IIS SMTP server and
specify that it forward mail to the Exchange org. I'd use the existing
domain settings as a template here.

4. Do you only have 1 Recipient Policy currently? It sounds like what
you
need to do is keep the current one (so Exchange will receive mail at the
existing domain), and then create a new Recipient Policy that applies to
*all* users, that only has the new domain. The reason I say this is
because
only 1 Recipient Policy will apply to a user account, and if you create
a
new one, it will have a higher priority than the Default policy, so it
will
get applied. To answer the second part of the question, having an MX
record
is not enough. The Recipient Policy bit is what tells Exchange it is
*allowed* to receive e-mail for a domain.

5. I believe so. With the certificate, you'd have to get a new one to
resolve the errors. It isn't that OWA won't work, it's just that you'd
get
a certificate warning that the name doesn't match. Depending on how new
your current cert is, the provider *may* allow you to get it re-issued.
Since you can only have 1 certificate per website, you'd then have to
remove
the current one and then install the new one.

--
Ben Winzenz
Exchange MVP
MessageOne
Read my blog!
http://winzenz.blogspot.com
http://feeds.feedburner.com/winzenz (RSS Feed)


"Mark Clark" <MarkClark@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:F536540A-6622-48EF-85BA-7C2A7C0DECBC@xxxxxxxxxxxxxxxx
Thanks Ben, I really appreciate the input.

1. Understood for MX records. I imagine this record would point to one
of
my
smTP servers on the DMZ?

2. OK

3. We do receive email via our SMTP servers. How do I make
modifications
for
this Windows services to allow the new domain to receive emails? I did
not
notice a GUI under Start-Programs or Admin Tools.

4. Yes, we would like to make the new domain the primary address for
everyone. Our existing Recip Policy shows smtp as our current domain
used.
It
does not show an old domain we also use. (not our first name change) I
would
like to add the new domain to the Recip POlicy (as I have read in
various
articles and discussions.) However, I do not want new users to receive
the
current address, but only our new domain name. The current domain name
must
be active. Can I use the existing Recip Policy?
Do we have to have a Recip POlicy for any domain to accept email?
Slight
confusion here, obviously.
If we have a MX record pointing to SMTP/EXCHG then will email be
delievcered
so long as there is an object (mailbox) with that available domain
name,
or
is a Recip Policy a must?? Based on our current config, I notice our
current
address, but not our old and of course I will be adding a new.
Hopefully
this
makes better sense?
We tried the Recip POlicy and force update in test, but to no
prevail..yet.

5. Yes, I believe we do want to change the OWA config. I get DNS
changes
and
possible certificate issues. That should be it right? Otherwise it is
the
same old front end server? I mean OWA is just mailbox specific,not
address
specific, except for what url we use to access?

"Ben Winzenz [Exchange MVP]" wrote:

Inline...

--
Ben Winzenz
Exchange MVP
MessageOne
Read my blog!
http://winzenz.blogspot.com
http://feeds.feedburner.com/winzenz (RSS Feed)


"Mark Clark" <MarkClark@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:82D1B453-F562-4B3D-80F6-CE744A1979F1@xxxxxxxxxxxxxxxx
Hello

Our company has recently changes names. We already have two email
domains
currently in use, one set as primary for everything and another
which
was
used in the past. We have one defined SMTP address, which is primary
for
all
users. We also have another which was used int he past, but is not
listed
as
a SMTP address in EXCH system mgr, recipients policies.
Of course, I have a new domain to add as our primary smtp address
and
will
need to make the current smtp address secondary for users.
In EXCH system mgr, I do see CCMAIL and MS properties which appear
to
be
our
old email domain (not current).
I did pull the following artcile up for adding the new (third)
domain
name.
KB289833 - http://support.microsoft.com/?kbid=289833
I have many questions in this regards.....
1. We can have multiple MX records on our external dns server
pointing
to
this eXCH server?

Yes. MX records for multiple domains can point to the same host. In
your
case, as long as the new domain is configured in a recipient policy,
Exchange will accept e-mail for that domain.

2. I will need an additional A record on our internal DNS server for
the
new
email domain?

No - you shouldn't have to do this. External DNS will be fine here.

3. We have two Windows SMTP servers on our DMZ, but I do not think
anything
will need changed. EXCH is obvisouly behind our DMZ. We do use email
filtering software, which I assume will need dfined for the new
email
domain.

If your Windows SMTP servers currently accept e-mail for your other
domain(s), then you'll have to add the new domain to them as well.
Aside
from that, configuring the filtering software would be the only other
thing
I see needs to be done.

4. When following this article and creating the SMTP in
EXCH.....will
it
be
an additional smtp address? More than one in EXCH mgr? Recipient
policies
need redefined?

Yes - it would be an *additional* e-mail address. You can optionally
define
that the new address be set as the Primary (Reply-To) address, which
it
sounds like you would. This should address point 5 as well. I don't
understand the last 2 parts of this question though. More than one
*what*
in EXCH mgr? Recipient policies need redefined means what? The
article
steps you through adding this new SMTP address to your default
recipient
policy. If you have multiple recipient policies, then you need to add
it
to
the appropriate policies.

5. Any tips on changing user primary smtps and keeping the old one
as
secondary? Scripts/LDAP?

Addressed with above settings in Recipient policy.

6. OWA - we do use a front end EXCH server. Anyone have experience
changing
the https address?

This one's a bit harder. You can easily create a new A record in
external
DNS for owa.newdomain.com that points to the same IP address as the
old
OWA
server, but you will have a problem with the certificate if you do
this.
Are you wanting OWA to continue to work with the old domain?


If anyone has been through this type of change before, your
experiences
and
suggestions would be appreciated very much.

Thank you,

Mark Clark










.

Relevant Pages

  • Re: company name change
    ... I'm not sure how your SMTP servers are configured. ... Do you only have 1 Recipient Policy currently? ...
    (microsoft.public.exchange.admin)
  • Re: company name change
    ... our recipient policy or in IIS on our SMTP server. ... Add new domain to Default recipient policy. ... I'm not sure how your SMTP servers are configured. ...
    (microsoft.public.exchange.admin)
  • Re: company name change
    ... If you edit the smtp address in the policy, you'll see a section for "This ... our recipient policy or in IIS on our SMTP server. ... Add new domain to Default recipient policy. ...
    (microsoft.public.exchange.admin)
  • Recipient Update Service is it really usefull??
    ... add your other hosted domains to the default policy. ... So I move onto creating recipient policies to only dish out smtp domain ... I don't and change the the field after the RUS has already created the SMTP ... address then I force the recipient policy to update they end up with 2 SMTP ...
    (microsoft.public.exchange.admin)
  • Re: company name change
    ... I'm not sure how your SMTP servers are configured. ... Do you only have 1 Recipient Policy currently? ... Our existing Recip Policy shows smtp as our current domain used. ...
    (microsoft.public.exchange.admin)
Loading