Calendar items can't be forwarded

23 Jan 2009 8:09 PM

CK

I have a users who was exmerged from one Exchange 2k3 sp2 org to another one.
Now when that user tries to forward meeting requests back to users he get's
the following NDR.

Your message did not reach some or all of the intended recipients.

      Subject:    FW: Asia IT meeting
      Sent:    1/23/2009 11:24 AM

The following recipient(s) cannot be reached:

      Chris Kahn on 1/23/2009 11:24 AM
            You do not have permission to send to this recipient. For
assistance, contact your system administrator.
            <mail1.osi-systems.com #5.7.1>

Any ideas on what we can do to fix this? It only affects this one user....
unfortunately it's my boss.

23 Jan 2009 8:25 PM

Ed Crowley [MVP]

By "forward back" do you mean "reply"? Please explain exactly the steps
he's taking.

If he's trying to reply to messages that were in his mailbox before he was
moved, many of them won't work because the internal address is an X.500-type
address of the legacyExchangeDN attribute, and that's not in the target
directory to which you migrated the mailbox, right? This is a typical
migration problem with the method you chose to use.

--
Ed Crowley MVP
"There are seldom good technological solutions to behavioral problems."
..

Show quoteHide quote

"CK" <C*@discussions.microsoft.com> wrote in message
news:4A09B5CA-D0E7-4961-B2E8-D154F26D7FED@microsoft.com...
>I have a users who was exmerged from one Exchange 2k3 sp2 org to another
>one.
> Now when that user tries to forward meeting requests back to users he
> get's
> the following NDR.
>
> Your message did not reach some or all of the intended recipients.
>
>      Subject: FW: Asia IT meeting
>      Sent: 1/23/2009 11:24 AM
>
> The following recipient(s) cannot be reached:
>
>      Chris Kahn on 1/23/2009 11:24 AM
>            You do not have permission to send to this recipient. For
> assistance, contact your system administrator.
>            <mail1.osi-systems.com #5.7.1>
>
> Any ideas on what we can do to fix this? It only affects this one user....
> unfortunately it's my boss.
>

23 Jan 2009 10:17 PM

CK

If that is the case, could I add an additional X.500 address that emulates
his old address? What is a better method for migrating to a different
Exchange org? Is there anything that I can do to mitigate this in the future?
Are X.500 addresses necessary? If I removed them, wouldn't that route
everything via smtp?

24 Jan 2009 12:00 AM

Ed Crowley [MVP]

Yes, you can. Add a new "other" address, type is "X500" (no dot or quotes)
and the address will look something like
/o=org/ou=site/cn=Recipients/cn=MailboxDN.

The best way to handle this in a migration is to perform a directory
synchronization that maps the legacyExchangeDN to a proxy address of the
type described above.

All versions of Exchange use internal addressing in the X.500-type (it's not
pure X.500 for various reasons) format. You cannot remove them.

--
Ed Crowley MVP
"There are seldom good technological solutions to behavioral problems."
..

Show quoteHide quote

"CK" <C*@discussions.microsoft.com> wrote in message
news:1F08FA3F-CFD3-48F6-9DDC-56E2340F7499@microsoft.com...
>
> If that is the case, could I add an additional X.500 address that emulates
> his old address? What is a better method for migrating to a different
> Exchange org? Is there anything that I can do to mitigate this in the
> future?
> Are X.500 addresses necessary? If I removed them, wouldn't that route
> everything via smtp?