Re: Contact Question
- From: A P <ermitanyo@xxxxxxxxx>
- To: "[ExchangeList]" <exchangelist@xxxxxxxxxxxxx>
- Date: Wed, 23 Nov 2005 08:30:47 -0800
I'll leave the answer to why Exchange enforces uniqueness of SMTP address to
others. I can think of 1 workaround for your issue.
1. Create 1 hidden contact object with the desired external SMTP address.
2. Create 2 users with mailboxes and configure displayname as desired to
appear in the GAL
3. For both user mailboxes, configure Delivery Options to forward to the
hidden contact object you created in #1.
Arden
On 11/23/05, William Holmes <wtholmes@xxxxxxxxxxxxxx> wrote:
>
> http://www.MSExchange.org/ <http://www.msexchange.org/>
>
> Hello,
>
>
>
> I have a situation where I would like to have two different contacts send
> to the same external email address. This is a legacy issue but I was still
> interested in making it work.
>
>
>
> So what I am after is:
>
>
>
> ContactA à externaluser@xxxxxxxxxxx
>
> ContactB à externaluser@xxxxxxxxxxx
>
>
>
> If you set this up and attempt to send to either ContactA or ContactB you
> receive an NDR indicating that two recipients have the same address. My real
> question is that so long as that recipient is external to exchange why is
> this a problem and is there a way around it?
>
>
>
> I understand that this can't work for exchange recipients but for external
> ones I not sure why it should be a problem.
>
>
>
> Thanks
>
>
> Bill
> ------------------------------------------------------
> List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
> Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp
> ------------------------------------------------------
> Visit TechGenix.com for more information about our other sites:
> http://www.techgenix.com
> ------------------------------------------------------
> You are currently subscribed to this MSExchange.org Discussion List as:
> ermitanyo@xxxxxxxxx
> To unsubscribe visit
> http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
> Report abuse to listadmin@xxxxxxxxxxxxxx
Other related posts:
