Yes, we're dealing with this issue right now in trying to support Japanese encoding in the mailreplytext.
Would it help if we added an LDAP attribute for mailreply that added the appropriate Content-type header? I know this wouldn't help with the actual encoding portion since we'd have to either change how LDAP stores the mailreplytext or encode it after the fact. On Fri, 2 Aug 2002, Claudio Jeker wrote: > On Thu, Aug 01, 2002 at 06:47:57PM +0200, Kurz, Robert wrote: > > hello, > > > > i use qmail with qmail-ldap-1.03-20020501a.patch and openldap-2.0.23. > > > > everything works fine, except that if i want to include german-umlauts in > > mailreplytext: > > > > the text i put in "mailreplytext" is "test ���", and if i look at the field > > with any ldap-browser, it looks fine (shows me: "mailReplyText: test ���"). > > > > but the reply-mail contains "test öüä" and a lookup with > > qmail-ldaplookup -m user shows > > > > qldap_lookup: succeeded, found: > > uid: user > > ... > > deliveryMode: localdelivery > > reply > > mailReplyText: test öüä > > > > > > does anybody know, what to do? > > > Umlauts and other non ASCII chars are not correctly supported. > There are 2 problems to solve: > 1. ldap encoding (for qmail-ldap all ldap fields are ascii encoded and > need no special handling) > 2. mail encoding (allmost all operating systems use different encodings so > mails need a correct Content-Type header field and a correctly encoded > mail) > > At the moment I know that for 1 the ldap docu could help and for porblem 2 > a new reply program needs to be written and a few rfc need to read. > > -- > :wq Claudio >
