Michael Monnerie wrote: > On Freitag, 1. Juni 2007 Aaron Stone wrote: >> It has to be in UTF-8. If the umlauts are in the database as latin1, >> the Sieve behavior is not defined. > > On Dec. 15, 2006, you wrote in thread [UTF-8 encoding issue]: >> UTF-8 encoding does not work and cannot be used for DBMail 2.2 at all. > > That's why I changed my db to latin1 then. Is utf8 better now? Then I'd > like to switch again...
The utf8 interfaces are just fine when it comes to messages and their cached headers. But that doesn't yet apply to dealing with the sieve-scripts. That part still needs to be done. I'm already working on generalizing the approach as done for messages to all input/output interfaces: file or terminal or network <A> dbmail <B> db esp the <B> boundary should be dealt with asap. -- ________________________________________________________________ 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
