[GroupDAV] Funambol GroupDAV connector: OGo ATTENDEE fields
get stripped away
Adam Tauno Williams
groupdav@opengroupware.org
Mon, 25 Feb 2008 08:46:45 -0500
--=-pqHD0aXbUhpTb8CagBj/
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
> >>>> I noticed that ical4j dies if Zidestore serves an email address=20
> >>>> containing scandinavian characters. Of course Zidestore shouldn't do=
=20
> >>>> that, but it does.
> >>> Could you elaborate?
> >> Of course. I had a OGo user which had email "=C3=A4ksy@tietoteema.fi" =
as a
> >> participant in an event. The corresponding ATTENDEE line probably=20
> >> looked like this:
> >> ATTENDEE;CUTYPE=3DINDIVIDUAL;PARTSTAT=3DNEEDS-ACTION;ROLE=3DREQ-PARTIC=
IPANT;RSVP=3DFAL=20
> >> SE;CN=3DTesti Henkil=C3=B6:MAILTO:testi.henkil=C3=B6@tietoteema.fi
> > OK, just had a look on how iCal.app encodes it:
> > ---snip---
> > ATTENDEE;CN=3D"John =C3=9Cml=C3=A4ut";CUTYPE=3DINDIVIDUAL;ROLE=3DREQ-PA=
RTICIPANT:mailto:
> > testi.henkil%C3%B6@tietoteema.fi
> > ---snap---
> > Looks like we need to encode the email address but keep the CN.
> Shouldn't email addresses be plain ASCII only?=20
Yes. RFC2822 section 3.4.1. I just had this argument with someone
about something else. But since non-ASCII DNS is now allowd, I'm not
certain how that should work. But I suppose that is a separate, not
really GROUPDAV, issue.
> >> In addition the scandinavian character in the email and CN seemed to=20
> >> be encoded in ISO-8859-1, not UTF-8.
> > That would be wrong in any case (though I'm a bit surprised).
> Our OGo database has a long history behind it, so I'm not surprised at=20
> all :). Our users authenticate from LDAP and it's quite possible that=20
> the invalid email address came from there.
Have you converted your database from from LATIN-1 to UTF-8 (really an
OGo-Users@ and not a GroupDAV one)?
--=20
Adam Tauno Williams <adam@morrison-ind.com>
--=-pqHD0aXbUhpTb8CagBj/
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4-svn0 (GNU/Linux)
iD8DBQBHwsbFLRePpNle04MRAmFzAJ0W5996n9S7ACbG7UZMAu2v/mjGDACcDXVA
Wl7CESqP7ZMHtGNkDSh/fNg=
=Hcmm
-----END PGP SIGNATURE-----
--=-pqHD0aXbUhpTb8CagBj/--