Meeting invitations behaving as normal e-mail.

[BenB]

Version: 2008
Operating System: Mac OS X 10.4 (Tiger)
Processor: Intel
Email Client: Exchange

Hi everyone.

I found some older posts about this issue, one of them even had a work around posted. However, after some some discussion, no official resolution is ever mentioned. In this thread, <http://www.officeformac.com/ProductForums/Entourage/5230/0> Entouragy says they have a ticket open with MS about this issue. I have a user that is still experiencing this issue with 12.1.5. Has any progress been made at MS? The work around is to control click on the e-mail as it is in the inbox and use the contextual menu to accept or decline this message.

Any help would be greatly appreciated.

 

[William Smith [MVP]]

I found some older posts about this issue, one of them even had a
work around posted. However, after some some discussion, no official
resolution is ever mentioned. In this thread,
<http://www.officeformac.com/ProductForums/Entourage/5230/0>
Entouragy says they have a ticket open with MS about this issue. I
have a user that is still experiencing this issue with 12.1.5. Has
any progress been made at MS? The work around is to control click on
the e-mail as it is in the inbox and use the contextual menu to
accept or decline this message.

I worked briefly with someone to troubleshoot this and we learned that
messages sent to me were fine while sent to others were missing the
Accpet/Tentative/Decline links. This tells me the problem is probably
within the sender's server system but I have no idea beyond that.

I appreciate learning about the contextual menu workaround. That's
helpful to know.

--

bill

Entourage Help Page <http://entourage.mvps.org/>
Entourage Help Blog <http://blog.entourage.mvps.org/>
YouTalk <http://nine.pairlist.net/mailman/listinfo/youtalk>
Twitter: follow <http://twitter.com/meck>

 

[BenB]

I don't think this would be from within the sender's system. We are currently using Exchange 2003, and these meeting requests are all internal to our system. Additionally, this never happened when we were using office 2004. So far only one user of about a dozen using Office 2008 has this problem. We shall see if the problem grows as we continue rolling out office 2008.