Primary E-Mail Address Policy - Microsoft Exchange

Hi,

This should help:
http://support.microsoft.com/default...b;en-us;319759

Leif

"Bob" <86c6c2e6-2146512712@news.postalias> wrote in message
news:F33477D3-4BB2-4E4F-BFD1-42E50F2D5358@microsoft.com...
> Hi, I have Exchange 2003 at the latest maintenance and I read in Exchange
> Help that the primary address found in the generation rules of my default
> recipient policy is "the address that appears in the From field of the
> e-mail
> message". However, it seems to me that it does a little bit more than
> just
> this.
>
> I'm sure I'm using Exchange in an unorthodox way, but here is what I have
> and the problem it is causing.
>
> I continue to use my outsourced email hosting site and therefore the MX
> record points to it and not Exchange. At the hosting site, I then forward
> the
> email to Exchange. My published email address is JohnDoe@published.com
> and I
> forward that to JohnDoe@MyExchangeServer.dyndns.info.
>
> One reason it is set up this way is because I don't have all the
> @published.com users on Exchange and they continue to use POP to get their
> messages directly from the host site. And as the domain name implies, I
> have
> a dynamic IP address from my ISP and I don't want to take a chance on
> bounce
> backs in case DynDNS.org fails to work for me some day. (We're a homeless
> shelter and don't have the $$). Lastly, if Exchange dies, we can use the
> hosting site as backup as we don't have IT support; just volunteers like
> me.
> (Microsoft kindly donates the s/w).
>
> The Exchange default policy has @published.com set as primary and
> @MyExchangeServer.dyndsn.info as a secondary (if that is the correct
> term).
>
> The result is users send email from Exchange using a return address of
> JohnDoe@published.com and receive it from
> JohnDoe@MyExchangeServer.dyndns.info.
>
> Although this seems to work fine, I find that Exchange users get bounce
> backs when they send email to those at published.com that are not on
> Exchange. I assume this is happening because Exchange feels that if
> @published.com is primary then all @primary.com users are on Exchange and
> to
> stay within Exchange to find the user. I suspect the bounce backs are
> coming
> from Exchange as the message is not sent out to the internet.
>
> I can "fix" this by making @MyExchangeServer.dyndns.info my primary and
> removing @published.com as a secondary, but this requires more effort when
> I
> create email accounts for my users as I have to edit over the defaults.
>
> So as I initially wrote at the top of this post, I'm thinking the primary
> email address policy does a bit more than just determine the "from"
> address
> in email.
>
> Is there a better way to accomplish what I trying to do? i.e. is there a
> setting in Exchange that can tell it to go out on the internet to find
> users
> it doesn't find them in-house?
>
> Thanks!
> --
> Bob

Hi Bob,

Thanks for posting here. Many thanks for Leif's input.

Yes, the solution outlined in the KB article 319759 can resolve your
problem. Please refer to the steps to perform.

More information is addressed in the following articles:

Authoritative and nonauthoritative domains in Exchange 2000 Server and in
Exchange Server 2003
http://support.microsoft.com/default...b;en-us;823158

321721 XCON: Sharing SMTP Address Spaces in Exchange 2000 Server and
Exchange
http://support.microsoft.com/?id=321721

Please let me know if you have further question on the issue. I am glad to
be assistance to you and look forward to your reply.

Sincerely,
Jenny Wu, MCSE 2000/2003, MCSA 2000/2003, MCDBA, MCSD
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
>From: "Leif Pedersen [MVP]" <Leif.pedersenNO-SPAM@get2net.dk>
>References: <F33477D3-4BB2-4E4F-BFD1-42E50F2D5358@microsoft.com>
>Subject: Re: Primary E-Mail Address Policy
>Date: Mon, 25 Sep 2006 21:28:15 +0200
>Lines: 76
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.2900.2869
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
>X-RFC2646: Format=Flowed; Original
>Message-ID: <ug5GIjN4GHA.4820@TK2MSFTNGP06.phx.gbl>
>Newsgroups: microsoft.public.exchange2000.setup.installation
>NNTP-Posting-Host: 194.192.108.171
>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP06.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.exchange2000.setup.installation:36253
>X-Tomcat-NG: microsoft.public.exchange2000.setup.installation
>
>Hi,
>
>This should help:
>http://support.microsoft.com/default...b;en-us;319759
>
>Leif
>
>"Bob" <86c6c2e6-2146512712@news.postalias> wrote in message
>news:F33477D3-4BB2-4E4F-BFD1-42E50F2D5358@microsoft.com...
>> Hi, I have Exchange 2003 at the latest maintenance and I read in Exchange
>> Help that the primary address found in the generation rules of my default
>> recipient policy is "the address that appears in the From field of the
>> e-mail
>> message". However, it seems to me that it does a little bit more than
>> just
>> this.
>>
>> I'm sure I'm using Exchange in an unorthodox way, but here is what I have
>> and the problem it is causing.
>>
>> I continue to use my outsourced email hosting site and therefore the MX
>> record points to it and not Exchange. At the hosting site, I then
forward
>> the
>> email to Exchange. My published email address is JohnDoe@published.com
>> and I
>> forward that to JohnDoe@MyExchangeServer.dyndns.info.
>>
>> One reason it is set up this way is because I don't have all the
>> @published.com users on Exchange and they continue to use POP to get
their
>> messages directly from the host site. And as the domain name implies, I
>> have
>> a dynamic IP address from my ISP and I don't want to take a chance on
>> bounce
>> backs in case DynDNS.org fails to work for me some day. (We're a
homeless
>> shelter and don't have the $$). Lastly, if Exchange dies, we can use the
>> hosting site as backup as we don't have IT support; just volunteers like
>> me.
>> (Microsoft kindly donates the s/w).
>>
>> The Exchange default policy has @published.com set as primary and
>> @MyExchangeServer.dyndsn.info as a secondary (if that is the correct
>> term).
>>
>> The result is users send email from Exchange using a return address of
>> JohnDoe@published.com and receive it from
>> JohnDoe@MyExchangeServer.dyndns.info.
>>
>> Although this seems to work fine, I find that Exchange users get bounce
>> backs when they send email to those at published.com that are not on
>> Exchange. I assume this is happening because Exchange feels that if
>> @published.com is primary then all @primary.com users are on Exchange
and
>> to
>> stay within Exchange to find the user. I suspect the bounce backs are
>> coming
>> from Exchange as the message is not sent out to the internet.
>>
>> I can "fix" this by making @MyExchangeServer.dyndns.info my primary and
>> removing @published.com as a secondary, but this requires more effort
when
>> I
>> create email accounts for my users as I have to edit over the defaults.
>>
>> So as I initially wrote at the top of this post, I'm thinking the primary
>> email address policy does a bit more than just determine the "from"
>> address
>> in email.
>>
>> Is there a better way to accomplish what I trying to do? i.e. is there a
>> setting in Exchange that can tell it to go out on the internet to find
>> users
>> it doesn't find them in-house?
>>
>> Thanks!
>> --
>> Bob
>
>
>

Hi Leif & Jenny,

A problem I have with Leif's procedure with regard to step 1-J and 2-K where
the instruction reads: "Click OK, and then click Yes when you are prompted to
update all corresponding recipient e-mail addresses."

Is this a mandatory step? I find in my test environment that the higher
priority policy did not revert the users back to their published address,
but rather left them with the local address. Newly created users work fine
however.

Because all my production users already have their addresses arranged the
way I need them to be, I would rather answer NO to this question. Is that
okay to do?
--
Bob

Hi Bob,

Thanks for your update. I appreciate your time.

>> I find in my test environment that the higher priority policy did not
revert the users back to their published address, but rather left them with
the local address.

To the problem, we can do as follows to apply the new recipient policy:

1. Go to Exchange System Manager -> Recipients -> Recipient Update
Services. In the right pane, right-click each item there, and select Update
Now to force RUS replication.

Note: There should be at least two RUS items, one for Enterprise
Configuration and the other for the domain.

2. Still in Exchange System Manager, navigate to Recipients -> Recipient
policies, right click the higher priority policy to choose item "Apply this
policy now" and click OK in the prompt dialog. Then please check if the
email address changed as expected.

For more information, please check into the following article:

How the Recipient Update Service applies recipient policies
http://support.microsoft.com/?id=328738

>> Because all my production users already have their addresses arranged
the way I need them to be, I would rather answer NO to this question. Is
that okay to do?

Since the email address of the users is indeed according with the recipient
policies, you can choose NO to not update the email addresses of users.
However it will not affect the current users' email addresses even you
choose to update now. For the update result of the recipient policies is
the same with the configuration of current users.

Please let me know if you have further question to the issue. I am glad to
be further assistance of you.

Have a great day!

Sincerely,
Jenny Wu, MCSE 2000/2003, MCSA 2000/2003, MCDBA, MCSD
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

--------------------
>Thread-Topic: Primary E-Mail Address Policy
>thread-index: Acbhee4BLABmMImMSL6PxLxkRQsP0w==
>X-WBNR-Posting-Host: 24.151.103.35
>From: =?Utf-8?B?Qm9i?= <86c6c2e6-2146512712@news.postalias>
>References: <F33477D3-4BB2-4E4F-BFD1-42E50F2D5358@microsoft.com>
<ug5GIjN4GHA.4820@TK2MSFTNGP06.phx.gbl>
<elKOBsT4GHA.2336@TK2MSFTNGXA01.phx.gbl>
>Subject: Re: Primary E-Mail Address Policy
>Date: Tue, 26 Sep 2006 07:42:02 -0700
>Lines: 16
>Message-ID: <1ED18BD5-B021-4052-939F-35608C4F9BC5@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.1830
>Newsgroups: microsoft.public.exchange2000.setup.installation
>Path: TK2MSFTNGXA01.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.exchange2000.setup.installation:36255
>NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
>X-Tomcat-NG: microsoft.public.exchange2000.setup.installation
>
>Hi Leif & Jenny,
>
>A problem I have with Leif's procedure with regard to step 1-J and 2-K
where
>the instruction reads: "Click OK, and then click Yes when you are prompted
to
>update all corresponding recipient e-mail addresses."
>
>Is this a mandatory step? I find in my test environment that the higher
>priority policy did not revert the users back to their published address,
>but rather left them with the local address. Newly created users work
fine
>however.
>
>Because all my production users already have their addresses arranged the
>way I need them to be, I would rather answer NO to this question. Is that
>okay to do?
>--
>Bob
>

Okay, Jenny.

I'm all set now. Thanks much!
--
Bob

Hi Bob,

Thanks for your update. I am glad to know that things are getting fine now.
I appreciate your time and effort to the issue and get this resolved.

Please do not hesitate to post in this newsgroup if you need any assistance
in the future! We are glad to help-)

Have a great day!

Sincerely,
Jenny Wu, MCSE 2000/2003, MCSA 2000/2003, MCDBA, MCSD
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
>Thread-Topic: Primary E-Mail Address Policy
>thread-index: AcbiLrKG8TQlEe9FRE6DKcg5vYqemA==
>X-WBNR-Posting-Host: 24.151.103.35
>From: =?Utf-8?B?Qm9i?= <86c6c2e6-2146512712@news.postalias>
>References: <F33477D3-4BB2-4E4F-BFD1-42E50F2D5358@microsoft.com>
<ug5GIjN4GHA.4820@TK2MSFTNGP06.phx.gbl>
<elKOBsT4GHA.2336@TK2MSFTNGXA01.phx.gbl>
<1ED18BD5-B021-4052-939F-35608C4F9BC5@microsoft.com>
<gSpAeGh4GHA.3352@TK2MSFTNGXA01.phx.gbl>
>Subject: Re: Primary E-Mail Address Policy
>Date: Wed, 27 Sep 2006 05:16:01 -0700
>Lines: 5
>Message-ID: <30F76010-5A32-486B-8B49-A5BCAFD92ED5@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.1830
>Newsgroups: microsoft.public.exchange2000.setup.installation
>Path: TK2MSFTNGXA01.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.exchange2000.setup.installation:36257
>NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
>X-Tomcat-NG: microsoft.public.exchange2000.setup.installation
>
>Okay, Jenny.
>
>I'm all set now. Thanks much!
>--
>Bob
>