Forwarding Appointments in Outlook Prepopulates “To” Field With All Attendees

Published 19 September 08 01:38 PM

We’ve had a lot of folks calling in recently about this one. The symptoms are that if you go to your calendar in Outlook and forward a meeting, the To field is prepopulated with all attendees of the meeting and the Subject field is not prefixed with “FW:.”  The common denominator of all victims of this problem is that they all had their meetings processed with CDO 1.21. This is common if you are a Blackberry user, but could happen if any application processes your appointment with CDO 1.21 before you’ve had a chance to touch it with Outlook.

The real cause of the problem is that CDO 1.21 doesn’t clear the MSGFLAG_UNSENT flag from the PR_MESSAGE_FLAGS property when it does a Respond. Because this flag is still set on the appointment item in the calendar, Outlook (rightfully) thinks the message has not yet been sent and so it treats it like a new message – essentially.

I’ve requested a fix for this issue and it is currently being worked on by our development team. I’ll update this post if/when the fix becomes available.

[UPDATE| The fix is now available and accessible here: http://support.microsoft.com/default.aspx?scid=kb;EN-US;957020.

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS

Comments

# Forwarding Appointments in Outlook Prepopulates ???To??? Field With All Attendees : EasyCoded said on September 19, 2008 1:47 PM:

PingBack from http://www.easycoded.com/forwarding-appointments-in-outlook-prepopulates-%e2%80%9cto%e2%80%9d-field-with-all-attendees/

# Jeremy said on October 30, 2008 2:55 PM:

Hi Patrick,

Is a fix available now?

# Patrick Creehan said on October 30, 2008 5:50 PM:

Yes, it was recently finished. You can request the download here: http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=957020&kbln=en-us

The corresponding KB article should be done soon.

# Patrick Creehan said on October 30, 2008 5:55 PM:

Just to clarify, the fix is for ESM which is installed on your application server where CDO.dll is used. So, if that happens to be BES, you would install it on your BES server.

If you use the ExchangeMapiCdo download, you need to wait for the next DST refresh to get the fix there.

# Jeremy said on October 30, 2008 6:06 PM:

Thanks for the link.  However, I requested the hotfix and I haven't received anything (and I'm sure it's not quarantined).  Maybe it's not available for download?

Leave a Comment

(required) 
(optional)
(required) 

  
Enter Code Here: Required

About Patrick Creehan

Patrick Creehan is an Escalation Engineer in the Office Messaging Development team at Microsoft.
Page view tracker