[Date Prev][Date Next]
Re: Chinese characters in mail search causes failed assertion in slapd
- To: firstname.lastname@example.org
- Subject: Re: Chinese characters in mail search causes failed assertion in slapd
- From: Alfie John <email@example.com>
- Date: Tue, 07 Feb 2012 22:52:59 +1100
- Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:from:to:mime-version :content-transfer-encoding:content-type:in-reply-to:subject :date; s=smtpout; bh=Un2+OjxYB5vi2p1Pr1vr/vYXI/s=; b=YoKbi++YUZk cF6Cnwj9Kzc+Cc+NS0F87/YFe5eB8kFRze3d8jGjQd9jvNEHNHOXi1MQ31Ik3hKH iMCz9RvsmpaQptZL9j1mB/Wmzcnevw7/M0bq8H3iGNfLm5xArQ1J8OU+Ok7bc30d NuvJ4Nh3UP7DLJky+Gk/ggFcO0e3AFbQ=
- In-reply-to: <firstname.lastname@example.org>
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.
Unfortunately I'm not in control of what mail clients users are running. This particular case was Thunderbird, but I assume that Apple Mail is also sending bogus UTF-8 mail attribute values.