Re: [calsify] RFC7986 and EMAIL parameter

[Mike Douglass <[e-mail]>]

Sent from my iPhone

> On Feb 17, 2021, at 11:24, Cyrus Daboo <[e-mail]> wrote:
> 
> Hi Michael,
> 
> --On Wed, 17 Feb 2021 11:04:41 -0500 Michael Douglass <[e-mail]> wrote:
> 
> 
>> Thanks Cyrus.
>> 
>> See below
>> 
>>> As per above, no, it was never intended that EMAIL be used for iMIP.  It
>>> is important to note, that some calendar systems allow users to  "sign-
>>> up" using a 3rd party email address as their "identifier", but  generate
>>> their own mailto calendar user address for iMIP (usually with  a domain
>>> set to the calendar server host and an "opaque" identifier  for thew
>>> local part). In such a case there could be two email  addresses on a
>>> property: one in the EMAIL paramater (the 3rd party  address that could
>>> be matched to a contact record); and the other the  calendar user address
>>> value in the property.
>>> 
>> I think I meant only if the value is not a mailto:. I assume in the absence
>> of any other indication (e.g. a valid email) this might be a fallback?
> 
> Of course you can send an iMIP message to any email address and hope it gets to the right place! I think the poiunt here is that it should never have to be used as a fallback. The ORGANIZER or ATTENDEE property values should be mailto's if the intent is to use iMIP. You pasted an example iCalendar message below which illustrates the point. The EMAIL parameter has a gmail domain, whilst the CUA value is me.com. Sending an iMIP to the EMAIL address would result in the scheduling message being intercepted and stored on the Google calendar, and not the iCloud calendar.
> 
>> One of those was generated by Apple. I created an event yesterday which in
>> full is
>> 
>> BEGIN:VCALENDAR
>> PRODID:-//CALENDARSERVER.ORG//NONSGML Version 1//EN
>> METHOD:REQUEST
>> VERSION:2.0
>> BEGIN:VEVENT
>> DTEND;TZID=America/New_York:20210219T100000
>> DTSTART;TZID=America/New_York:20210219T090000
>> ORGANIZER;CN=Michael Douglass;EMAIL=[e-mail]:mailto:2_GM4T
>>  GNJSHAZTSMZVGI4DGOJTGW7UOVQIXU6S7IXFKVSLJVS4VP4YX5J2UCRWN6KC2YMIGY25PWAA
>>  [e-mail]
>> UID:E5C6F579-5003-4755-B29D-572E0FF147B1
>> DTSTAMP:20210217T051817Z
>> SEQUENCE:1
>> SUMMARY:Testing email param
>> LAST-MODIFIED:20210217T051817Z
>> CREATED:20210217T051744Z
>> ATTENDEE;CUTYPE=INDIVIDUAL;EMAIL=[e-mail];RSVP=TRUE;PARTSTA
>>  T=NEEDS-ACTION:mailto:[e-mail]
>> ATTENDEE;CN=Ken Murchison;CUTYPE=INDIVIDUAL;EMAIL=[e-mail];RSVP
>>  =TRUE;PARTSTAT=NEEDS-ACTION:mailto:[e-mail]
>> ATTENDEE;CN=Michael Douglass;CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED;ROLE=CHA
>>  IR;EMAIL=[e-mail]:/aMzkzNTI4MzkzNTI4MzkzNQPuXCcDTdG5iXfOh
>>  cljjCSqMYrUXDcs6f1z7CyXejTR/principal/
>> END:VEVENT
> 
> Well that may well be a bug!
> 
>> I believe a URI doesn't require a scheme - a simple path is sufficient
> 
> I think the syntax and associated text in https://www.rfc-editor.org/rfc/rfc3986#section-3 make it pretty clear a scheme is required.

So it does - bug then. However it may be Thunderbird - it’s very hard (at least I don’t know of a way) to get apple calendar to export a single email so I sent it and saved the attachment.

I’d need to check further


> 
> -- 
> Cyrus Daboo