J
Joel
Can anyone help with this.
When sending meeting requests between two different
versions of outlook, i.e. 2000 and XP, users are getting a
garbled mess (displaying the underlying code rather than
the actual form) on the receiving end. The problem
appears to be happening more on the 2000 end than anywhere
else. example follows;
-----Original Message-----
From:
Sent: Friday, November 21, 2003 8:51 AM
To:
Subject: Updated:
Return-Path:
Received:
Subject: Updated:
Date: Fri, 21 Nov 2003 08:51:10 -0500
Message-ID:
MIME-Version: 1.0
Content-Type: text/calendar; method=REQUEST;
charset="utf-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
X-UIDL: 1730
BEGIN:VCALENDAR
PRODID:-//Microsoft Corporation//Outlook 10.0 MIMEDIR//EN
VERSION:2.0 METHOD:REQUEST BEGIN:VEVENT
ATTENDEE;CN=;ROLE=REQ-PARTICIPANT;RSVP=TRUE:MAILTO:
ATTENDEE;CN=;ROLE=REQ-PARTICIPANT;RSVP=TRUE:MAILTO:
ATTENDEE;CNROLE=REQ-PARTICIPANT;RSVP=TRUE:MAILTO:
ATTENDEE;CN=;ROLE=REQ-
PARTICIPANT;RSVP=TRUE:MAILTO:ATTENDEE;CN=;ROLE=REQ-
PARTICIPANT;RSVP=TRUE:MAILTO:
ATTENDEE;CN=;ROLE=REQ-PARTICIPANT;RSVP=TRUE:MAILTO:
ORGANIZER:MAILTO:
DTSTART:20031124T190000Z
DTEND:20031124T200000Z
LOCATION:Bldg II Conf Rm
TRANSP:OPAQUE
SEQUENCE:2
UID:040000008200E00074C5B7101A82E0080000000060D7A33A72A8C30
10000000000000000100
000001922478889C58B42833F2854712477DB
DTSTAMP:20031121T135111Z
DESCRIPTION:When: Monday\, November 24\, 2003 2:00 PM-3:00
PM (GMT-05:00)
Eastern Time (US & Canada).\nWhere: Bldg II Conf
Rm\n\n*~*~*~*~*~*~*~*~*~*\n\nMeeting has been postponed
to 2:00 PM\,
Monday\, 11/24/03\n
SUMMARY:Updated: PRIORITY:5
CLASS
UBLIC
BEGIN:VALARM
TRIGGERT15M
ACTION
ISPLAY
DESCRIPTION:Reminder
END:VALARM
END:VEVENT
END:VCALENDAR
When sending meeting requests between two different
versions of outlook, i.e. 2000 and XP, users are getting a
garbled mess (displaying the underlying code rather than
the actual form) on the receiving end. The problem
appears to be happening more on the 2000 end than anywhere
else. example follows;
-----Original Message-----
From:
Sent: Friday, November 21, 2003 8:51 AM
To:
Subject: Updated:
Return-Path:
Received:
Subject: Updated:
Date: Fri, 21 Nov 2003 08:51:10 -0500
Message-ID:
MIME-Version: 1.0
Content-Type: text/calendar; method=REQUEST;
charset="utf-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
X-UIDL: 1730
BEGIN:VCALENDAR
PRODID:-//Microsoft Corporation//Outlook 10.0 MIMEDIR//EN
VERSION:2.0 METHOD:REQUEST BEGIN:VEVENT
ATTENDEE;CN=;ROLE=REQ-PARTICIPANT;RSVP=TRUE:MAILTO:
ATTENDEE;CN=;ROLE=REQ-PARTICIPANT;RSVP=TRUE:MAILTO:
ATTENDEE;CNROLE=REQ-PARTICIPANT;RSVP=TRUE:MAILTO:
ATTENDEE;CN=;ROLE=REQ-
PARTICIPANT;RSVP=TRUE:MAILTO:ATTENDEE;CN=;ROLE=REQ-
PARTICIPANT;RSVP=TRUE:MAILTO:
ATTENDEE;CN=;ROLE=REQ-PARTICIPANT;RSVP=TRUE:MAILTO:
ORGANIZER:MAILTO:
DTSTART:20031124T190000Z
DTEND:20031124T200000Z
LOCATION:Bldg II Conf Rm
TRANSP:OPAQUE
SEQUENCE:2
UID:040000008200E00074C5B7101A82E0080000000060D7A33A72A8C30
10000000000000000100
000001922478889C58B42833F2854712477DB
DTSTAMP:20031121T135111Z
DESCRIPTION:When: Monday\, November 24\, 2003 2:00 PM-3:00
PM (GMT-05:00)
Eastern Time (US & Canada).\nWhere: Bldg II Conf
Rm\n\n*~*~*~*~*~*~*~*~*~*\n\nMeeting has been postponed
to 2:00 PM\,
Monday\, 11/24/03\n
SUMMARY:Updated: PRIORITY:5
CLASS
UBLICBEGIN:VALARM
TRIGGER
T15MACTION
ISPLAYDESCRIPTION:Reminder
END:VALARM
END:VEVENT
END:VCALENDAR