On Tuesday, 7 February 2012 13:52:59 Alfie John wrote:
Hi Dieter,
On Tue, Feb 7, 2012, at 08:56 AM, Dieter Klünter wrote:
Never modify a standard track attribute type, all you can do is to create a subtype of mail. On the other hand, your intention does not comply to RFC-5322 which requires that header fields MUST be composed of printable US-ASCII characters.
As far as I can tell, the issue is not to be able to have UTF-8 in the mail attribute, but allow the client's search to succeed, where it uses a filter of the form:
(|(cn=%s)(sn=%s)(mail=%s))
In the case where the user tries to search for a UTF-8 character (which is present in the target entries cn or sn values), the client sends UTF-8 in the mail=%s portion.
Unfortunately I'm not in control of what mail clients users are running.
That doesn't prevent you from filing bugs on said mail clients. Please file a bug with Thunderbird.
This particular case was Thunderbird, but I assume that Apple Mail is also sending bogus UTF-8 mail attribute values.
Because one implementation has a bug, other implementations of similar functionality *must* have it?
Regards, Buchan