[horde] Accepting iPhone generated appointment generates error
Michael J Rubinsky
mrubinsk at horde.org
Tue Mar 20 13:57:44 UTC 2012
Quoting Simon Wilson <simon at simonandkate.net>:
> ----- Message from Simon Wilson <simon at simonandkate.net> ---------
> Date: Mon, 19 Mar 2012 20:08:47 +1000
> From: Simon Wilson <simon at simonandkate.net>
> Subject: [horde] Accepting iPhone generated appointment generates error
> To: "horde at lists.horde.org" <horde at lists.horde.org>
>
>
>> My wife sent me an invitation from her iPhone (attached, and
>> below). Her iPhone is connected to Horde ActiveSync. The
>> appointment was generated in her calendar fine, and appears in both
>> iPhone Calendar and also Kronolith.
>>
>> I received this fine, and within Horde, selected Accept and Add to
>> Calendar. The Add to Calendar part worked fine, but Accept failed,
>> with Dynamic Imp generating a "Error when communicating with the
>> server" message.
>>
>> So, to try and troubleshoot, I generated a new appt in my wife's
>> calendar, in Kronolith this time. Added me as an attendee, and
>> accepted the prompted autocomplete address when I had typed Simon.
>>
>> (Incidentally, there is an issue there with autocomplete - when
>> sending, it returned:
>>
>> There was an error sending an event notification to Wilson, Simon
>> <simon at simonandkate.net>: Failed to add recipient: Wilson, Simon
>> <simon at simonandkate.net [SMTP: Invalid response code received from
>> server (code: 501, response: 5.1.3 Bad recipient address
>> syntax)][Mon Mar 19 2012 19:57:50 GMT+1000 (E. Australia Standard
>> Time)]
>>
>> It appears to be trying to send to "Wilson, Simon
>> <simon at simonandkate.net>" instead of extracting the email address.)
>>
>> Anyway, I added my email address manually instead of accepting the
>> autocomplete suggestion, and it sent the invite OK. In my email, I
>> was able to successfully Accept the invite.
>>
>> In the iPhone generated appt, the ORGANIZER line is:
>> ORGANIZER;CN="katie":invalid:nomail
>>
>> I suspect that may be the issue...?
>>
>> In the Kronolith one it is:
>> ORGANIZER;CN=Katie Wilson:mailto:katie at simonandkate.net
>>
>> Does anyone know if there is a way to resolve this? Also the error
>> message is probably not particularly intuitively helpful.
>>
>> Simon.
>> **********************************
>> Source text of iPhone invite:
>>
>> Return-Path: <katie at simonandkate.net>
>> Received: from murder ([unix socket])
>> by server04.simonandkate.lan (Cyrus
>> v2.3.7-Invoca-RPM-2.3.7-12.el5_7.2) with LMTPA;
>> Mon, 19 Mar 2012 11:06:53 +1000
>> X-Sieve: CMU Sieve 2.3
>> Received: from localhost (localhost.localdomain [127.0.0.1])
>> by mail.simonandkate.net (Postfix) with ESMTP id 21E0257698
>> for <simon at simonandkate.net>; Mon, 19 Mar 2012 11:06:53 +1000 (EST)
>> X-Virus-Scanned: amavisd-new at simonandkate.net
>> X-Spam-Flag: NO
>> X-Spam-Score: -2.892
>> X-Spam-Level:
>> X-Spam-Status: No, score=-2.892 tagged_above=-999 required=6.2
>> tests=[ALL_TRUSTED=-1, BAYES_00=-1.9, UPPERCASE_50_75=0.008]
>> autolearn=no
>> Received: from mail.simonandkate.net ([127.0.0.1])
>> by localhost (mail.simonandkate.net [127.0.0.1]) (amavisd-new, port 10026)
>> with LMTP id U6svn1BeAExm for <simon at simonandkate.net>;
>> Mon, 19 Mar 2012 11:06:48 +1000 (EST)
>> Received: from localhost (server06.simonandkate.lan [192.168.1.170])
>> by mail.simonandkate.net (Postfix) with ESMTP id F0EA357697
>> for <simon at simonandkate.net>; Mon, 19 Mar 2012 11:06:47 +1000 (EST)
>> Subject: Blossom - Dr Shipstone
>> To: "simon at simonandkate.net" <simon at simonandkate.net>
>> From: Katie Wilson <katie at simonandkate.net>
>> Message-ID:
>> <20120319110647.Horde.qnKQFNJO7vlPZoan2yGRa-A at mail.simonandkate.net>
>> User-Agent: Horde Application Framework 4
>> Date: Mon, 19 Mar 2012 11:06:47 +1000
>> Content-Type: multipart/mixed; boundary="=_cz48P9JO7vlPZoan256xa-A"
>> MIME-Version: 1.0
>>
>> This message is in MIME format.
>>
>> --=_cz48P9JO7vlPZoan256xa-A
>> Content-Type: text/plain; charset=UTF-8; format=flowed; DelSp=Yes
>>
>>
>>
>>
>> --=_cz48P9JO7vlPZoan256xa-A
>> Content-Type: multipart/alternative; boundary="=_0jpCOdJO7vlPZoan2maBa-A"
>>
>>
>> --Apple-Mail-B845CD46-B61D-464F-BD65-22AEB21B2DD4
>> Content-Transfer-Encoding: 7bit
>> Content-Type: text/plain;
>> charset=us-ascii
>>
>>
>>
>> --Apple-Mail-B845CD46-B61D-464F-BD65-22AEB21B2DD4
>> Content-Type: text/calendar;
>> charset=utf-8;
>> name=meeting.ics;
>> method=REQUEST
>> Content-Transfer-Encoding: quoted-printable
>>
>> BEGIN:VCALENDAR=0D=0ACALSCALE:GREGORIAN=0D=0AMETHOD:REQUEST=0D=0APRODID:-//A=
>> pple=20Inc.//iPhone=203.0//EN=0D=0AVERSION:2.0=0D=0ABEGIN:VTIMEZONE=0D=0ATZI=
>> D:GMT+1000=0D=0ABEGIN:STANDARD=0D=0ADTSTART:20010101T000000=0D=0ATZNAME:GMT+=
>> 10:00=0D=0ATZOFFSETFROM:+1000=0D=0ATZOFFSETTO:+1000=0D=0AEND:STANDARD=0D=0AE=
>> ND:VTIMEZONE=0D=0ABEGIN:VEVENT=0D=0AATTENDEE;CN=3D"simon at simonandkate.net";C=
>> UTYPE=3DINDIVIDUAL;PARTSTAT=3DNEEDS-AC=0D=0A=20TION;RSVP=3DTRUE:mailto:simon=
>> @simonandkate.net=0D=0ACREATED:20120317T112125Z=0D=0ADTEND;TZID=3DGMT+1000:2=
>> 0120416T172000=0D=0ADTSTAMP:20120319T010531Z=0D=0ADTSTART;TZID=3DGMT+1000:20=
>> 120416T162000=0D=0ALAST-MODIFIED:20120319T010531Z=0D=0ALOCATION:Underwood=0D=
>> =0AORGANIZER;CN=3D"katie":invalid:nomail=0D=0ASEQUENCE:1=0D=0ASUMMARY:Blosso=
>> m=20-=20Dr=20Shipstone=0D=0ATRANSP:OPAQUE=0D=0AUID:2012031718463200E00ED0070=
>> 000E90F00000A00A00000000A0D0A0E00E0=0D=0AX-MICROSOFT-CDO-INTENDEDSTATUS:BUSY=
>> =0D=0ABEGIN:VALARM=0D=0AACTION:DISPLAY=0D=0ADESCRIPTION:Event=20reminder=0D=0A=
>> TRIGGER:-P2D=0D=0AX-WR-ALARMUID:64D58714-97DB-4E51-8251-5F53C0BD5632=0D=0AEN=
>> D:VALARM=0D=0AEND:VEVENT=0D=0AEND:VCALENDAR=0D=0A=
>>
>> --Apple-Mail-B845CD46-B61D-464F-BD65-22AEB21B2DD4--
>>
>> --Apple-Mail-B845CD46-B61D-464F-BD65-22AEB21B2DD4
>> Content-Type: text/plain; charset=us-ascii
>> Content-Disposition: attachment; size=3
>>
>>
>>
>> --Apple-Mail-B845CD46-B61D-464F-BD65-22AEB21B2DD4
>> Content-Type: text/calendar; charset=utf-8; method=REQUEST; name=meeting.ics
>> Content-Disposition: attachment; size=1161; filename=meeting.ics
>>
>> BEGIN:VCALENDAR
>> CALSCALE:GREGORIAN
>> METHOD:REQUEST
>> PRODID:-//Apple Inc.//iPhone 3.0//EN
>> VERSION:2.0
>> BEGIN:VTIMEZONE
>> TZID:GMT+1000
>> BEGIN:STANDARD
>> DTSTART:20010101T000000
>> TZNAME:GMT+10:00
>> TZOFFSETFROM:+1000
>> TZOFFSETTO:+1000
>> END:STANDARD
>> END:VTIMEZONE
>> BEGIN:VEVENT
>> ATTENDEE;CN="simon at simonandkate.net";CUTYPE=INDIVIDUAL;PARTSTAT=NEEDS-AC
>> TION;RSVP=TRUE:mailto:simon at simonandkate.net
>> CREATED:20120317T112125Z
>> DTEND;TZID=GMT+1000:20120416T172000
>> DTSTAMP:20120319T010531Z
>> DTSTART;TZID=GMT+1000:20120416T162000
>> LAST-MODIFIED:20120319T010531Z
>> LOCATION:Underwood
>> ORGANIZER;CN="katie":invalid:nomail
>> SEQUENCE:1
>> SUMMARY:Blossom - Dr Shipstone
>> TRANSP:OPAQUE
>> UID:2012031718463200E00ED0070000E90F00000A00A00000000A0D0A0E00E0
>> X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
>> BEGIN:VALARM
>> ACTION:DISPLAY
>> DESCRIPTION:Event reminder
>> TRIGGER:-P2D
>> X-WR-ALARMUID:64D58714-97DB-4E51-8251-5F53C0BD5632
>> END:VALARM
>> END:VEVENT
>> END:VCALENDAR
>>
>> --Apple-Mail-B845CD46-B61D-464F-BD65-22AEB21B2DD4--
>>
>> --=_0jpCOdJO7vlPZoan2maBa-A--
>>
>> --=_cz48P9JO7vlPZoan256xa-A
>> Content-Type: text/plain; charset=us-ascii
>>
>>
>>
>> --=_cz48P9JO7vlPZoan256xa-A
>> Content-Type: text/calendar; charset=us-ascii
>>
>> BEGIN:VCALENDAR
>> CALSCALE:GREGORIAN
>> METHOD:REQUEST
>> PRODID:-//Apple Inc.//iPhone 3.0//EN
>> VERSION:2.0
>> BEGIN:VTIMEZONE
>> TZID:GMT+1000
>> BEGIN:STANDARD
>> DTSTART:20010101T000000
>> TZNAME:GMT+10:00
>> TZOFFSETFROM:+1000
>> TZOFFSETTO:+1000
>> END:STANDARD
>> END:VTIMEZONE
>> BEGIN:VEVENT
>> ATTENDEE;CN="simon at simonandkate.net";CUTYPE=INDIVIDUAL;PARTSTAT=NEEDS-AC
>> TION;RSVP=TRUE:mailto:simon at simonandkate.net
>> CREATED:20120317T112125Z
>> DTEND;TZID=GMT+1000:20120416T172000
>> DTSTAMP:20120319T010531Z
>> DTSTART;TZID=GMT+1000:20120416T162000
>> LAST-MODIFIED:20120319T010531Z
>> LOCATION:Underwood
>> ORGANIZER;CN="katie":invalid:nomail
>> SEQUENCE:1
>> SUMMARY:Blossom - Dr Shipstone
>> TRANSP:OPAQUE
>> UID:2012031718463200E00ED0070000E90F00000A00A00000000A0D0A0E00E0
>> X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
>> BEGIN:VALARM
>> ACTION:DISPLAY
>> DESCRIPTION:Event reminder
>> TRIGGER:-P2D
>> X-WR-ALARMUID:64D58714-97DB-4E51-8251-5F53C0BD5632
>> END:VALARM
>> END:VEVENT
>> END:VCALENDAR
>>
>> --=_cz48P9JO7vlPZoan256xa-A--
>>
>>
>>
>>
>> --
>> Simon Wilson
>> M: 0400 12 11 16
>
>
> ----- End message from Simon Wilson <simon at simonandkate.net> -----
>
> I have been doing some extra testing on this.
>
> My iPhone has multiple "Exchange" accounts - two that actually ARE
> Exchange, and Horde ActiveSync.
>
> If I generate an appointment on my iPhone from one of the real
> Exchange accounts with external invitees, the resultant invitations
> can be accepted and the responses return to the sending account. The
> invite is Base64 encoded.
>
> If I generate an appointment on my iPhone from / via the Horde
> ActiveSync account, the resultant VCALENDAR invitation is NOT
> acceptable, as it has the invalid:nomail organizer tag. Generating
> the appointment directly in Kronolith is fine, as it fills in the
> ORGANIZER tag correctly.
>
> Any ideas why, from iOS, MS ActiveSync generated appointments are
> OK, but Horde ActiveSync ones are not?
These emails are entirely generated by the device. Horde simply parses
it into a structure that Horde_Mail can send and pushes it on it's
way. I've tested this locally here, from my iPad and it works as
expected.
What email address is the iPhone's ActiveSync account configured with?
If you provide a wiretrace of the communication between the device and
the Horde server during the ActiveSync transaction we can be sure if
it's coming from the device, or if it's something Horde does during
processing the request.
--
mike
The Horde Project (www.horde.org)
mrubinsk at horde.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 6096 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.horde.org/archives/horde/attachments/20120320/a7957fea/attachment-0001.bin>
More information about the horde
mailing list