I've search this forum / the wiki / crackberry & Google for a solution to this issue.
Here is my problem:
Blank Calendar Appointment Invitations
When a user on a Blackberry (we only have Blackberry Tours) sends a calendar appointment invite the invitation data is sent but there is no plain text for the invitee to read in the zimbra web client so they do not know when the appointment is for. They can accept/tentative or decline the meeting. If they look in their calendar, the meeting invite is in the right time and date slot.
If you view the original content of the email you can see the meeting invite data and any notes entered but not a plain text version of the calendar invite.
Software Versions:
Zimbra 5.0.18_GA_3011.RHEL5_64
ZimbraConnectorForBES/5.0.2719.19
Blackberry Professional Server 4.1.4.40
Here is the contents of the invitation sent from the Blackberry to the Zimbra user:
Is there an option I'm missing. Is anyone else getting plain text meeting invites from a BES in the Zimbra web client?Code:Return-Path: sender Received: from server (LHLO server) (172.16.1.7) by server with LMTP; Mon, 26 Oct 2009 10:30:29 -0400 (EDT) Received: from localhost (localhost.localdomain [127.0.0.1]) by server (Postfix) with ESMTP id BAF3A1A48CE7 for <receiver>; Mon, 26 Oct 2009 10:30:29 -0400 (EDT) X-Virus-Scanned: amavisd-new at server X-Spam-Flag: NO X-Spam-Score: -4.213 X-Spam-Level: X-Spam-Status: No, score=-4.213 tagged_above=-10 required=6.6 tests=[ALL_TRUSTED=-1.8, AWL=0.185, BAYES_00=-2.599, HTML_MESSAGE=0.001] Received: from server ([127.0.0.1]) by localhost (server [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SSMNVOCweaSM for <receiver>; Mon, 26 Oct 2009 10:30:29 -0400 (EDT) Received: from server (server [172.16.1.7]) by server (Postfix) with ESMTP id 6953C1A48C43 for <receiver>; Mon, 26 Oct 2009 10:30:29 -0400 (EDT) From: "sender name" <sender> To: "receiver name" <receiver> Subject: Test3 Date: Mon, 26 Oct 2009 10:30:29 -0400 (EDT) Message-ID: <000001ca5648$d2945150$77bcf3f0$@org> MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 12.0 X-Mailer: Zimbra 5.0.18_GA_3011.RHEL5_64 (ZimbraConnectorForBES/5.0.2719.19) Thread-Index: AcpWSNI3WPIM/lO+SgmPCr4DwLfN4A== Content-Type: multipart/alternative; boundary="------------Boundary-00=_AML44Y7kX93yP9uUPRhg" X-Originating-IP: [172.16.1.21] --------------Boundary-00=_AML44Y7kX93yP9uUPRhg Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: base64 Tm90ZXMgdGVzdA0K --------------Boundary-00=_AML44Y7kX93yP9uUPRhg Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable <=21DOCTYPE HTML PUBLIC =22-//W3C//DTD HTML 3.2//EN=22> <HTML> <HEAD> <META HTTP-EQUIV=3D=22Content-Type=22 CONTENT=3D=22text/html; = charset=3DWindows-1252=22> <META NAME=3D=22Generator=22 CONTENT=3D=22MS Exchange Server version = 08.00.0681.000=22> <TITLE>Test3</TITLE> </HEAD> <BODY> <=21-- Converted from text/plain format --> <P><FONT SIZE=3D2>Notes test</FONT> </P> </BODY> </HTML>= --------------Boundary-00=_AML44Y7kX93yP9uUPRhg Content-Type: text/calendar; method=REQUEST; charset="utf-8" Content-Transfer-Encoding: 7bit BEGIN:VCALENDAR PRODID:-//Microsoft Corporation//Outlook 12.0 MIMEDIR//EN VERSION:2.0 METHOD:REQUEST X-MS-OLK-FORCEINSPECTOROPEN:TRUE BEGIN:VEVENT ATTENDEE;CN="receiver name";RSVP=TRUE:mailto:receiver CLASS:PUBLIC CREATED:20091026T143009Z DESCRIPTION:Notes test DTEND:20091027T033000Z DTSTAMP:20091026T143009Z DTSTART:20091027T023000Z LAST-MODIFIED:20091026T143010Z LOCATION:Test loc field ORGANIZER;CN="sender name":mailto:sender PRIORITY:5 SEQUENCE:0 SUMMARY:Test3 TRANSP:OPAQUE UID:040000008200E00074C5B7101A82E00800000000303D37D24856CA01000000000000000 010000000DEFA85ECABEBA2419A8C0CAF8826792D X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE X-MICROSOFT-CDO-IMPORTANCE:1 X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY BEGIN:VALARM TRIGGER:-PT15M ACTION:DISPLAY DESCRIPTION:Reminder END:VALARM END:VEVENT END:VCALENDAR --------------Boundary-00=_AML44Y7kX93yP9uUPRhg--


LinkBack URL
About LinkBacks

