You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 13, 2020. It is now read-only.
for attendeeProp in calendar.getAllAttendeeProperties():
params = attendeeProp.params()
cutype = params.get('CUTYPE', (None,))[0]
if cutype == "INDIVIDUAL" :
cn = params.get("CN", (None,))[0]
cuaddr = normalizeCUAddr(attendeeProp.value())
if cuaddr.startswith("mailto:"):
mailto = cuaddr[7:]
if not cn:
cn = mailto
else:
emailAddress = params.get("EMAIL", (None,))[0]
if emailAddress:
mailto = emailAddress
else:
mailto = None
if cn or mailto:
attendees.append( (cn, mailto) )
But reading RFC5545 there is the following:
Description: This parameter can be specified on properties with a
CAL-ADDRESS value type. The parameter identifies the type of
calendar user specified by the property. If not specified on a
property that allows this parameter, the default is INDIVIDUAL.
Applications MUST treat x-name and iana-token values they don't
recognize the same way as they would the UNKNOWN value.
Therefore the following patch should be applied:
Index: twistedcaldav/mail.py
===================================================================
--- twistedcaldav/mail.py (Revision 7047)
+++ twistedcaldav/mail.py (Arbeitskopie)
@@ -835,7 +835,7 @@
for attendeeProp in calendar.getAllAttendeeProperties():
params = attendeeProp.params()
cutype = params.get('CUTYPE', (None,))[0]
- if cutype == "INDIVIDUAL":
+ if cutype == "INDIVIDUAL" or cutype is None :
cn = params.get("CN", (None,))[0]
cuaddr = normalizeCUAddr(attendeeProp.value())
if cuaddr.startswith("mailto:"):
The text was updated successfully, but these errors were encountered:
mail@… originally submitted this as ticket:417
Creating events with Thunderbird the attendees were missing in the invitation mail.
Looking at the events the following difference can be seen: iOS:
Lightning:
in mail.py the following is done:
But reading RFC5545 there is the following:
Therefore the following patch should be applied:
The text was updated successfully, but these errors were encountered: