Matthew O'Connor wrote: > Aaron Stone wrote: >> On Fri, 2006-12-15 at 12:11 +0200, VladK wrote: >>> Hi All. >>> I'm using dbmail-2.2.1; libsieve-2.2.1. >>> On the delivery stage I have got such error: >> [snip] >>> OR", 0.01000, content="FrontPage+Editor, 0.01000')] : [ERROR: invalid >>> byte sequence for encoding "UTF8": 0xb5 ] >>> Dec 15 05:00:57 tigercat dbmail/smtp[6102]: Error insert headervalue >>> failed >> [snip] >>> Please advise. >> >> UTF-8 encoding does not work and cannot be used for DBMail 2.2 at all. > > I think that is a rather drastic statement and not what I understood. > There are problems when a message has a header that is UTF8 encoded, but > I believe that is against the spec isn't it?
Yep. Headervalues are /supposed/ to be us-ascii, but 8bit strings are increasingly common (anyone using outlook?), so we will have to accomodate them. Also, supporting utf8 is just the-right-thing to do. Late in the 2.1 sequence I experimented with casting the encoding to utf8 for all caching table values. This led me to conclude that such an approach is flawed. By storing values as-is in encoding neutral fields will allow us to defer conversion to when we actually need it. We can do that relatively easily and without triggering any regressions. -- ________________________________________________________________ Paul Stevens paul at nfg.nl NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31 The Netherlands________________________________http://www.nfg.nl _______________________________________________ DBmail mailing list [email protected] https://mailman.fastxs.nl/mailman/listinfo/dbmail
