Hi Jorge, Just tried the latest svn code, and still no luck :(
Naomi On Nov 15, 2007 10:01 AM, Jorge Bastos <[EMAIL PROTECTED]> wrote: > Paul seamns to have fixed something about it. > > Can you update to last svn and try? > > > > > > *From:* [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] *On > Behalf Of *Naomi Carson > *Sent:* quinta-feira, 15 de Novembro de 2007 17:14 > *To:* DBMail mailinglist > *Subject:* Re: [Dbmail] encoding problem - nonascii chars in subject > > > > Thanks for the reply Paul, > > I created the database with utf8, and set encoding=utf8 in dbmail.conf, > and had the same error. I tried having them both latin1, and same thing :( > > Any other ideas? > > Thanks, > > Naomi > > On Nov 15, 2007 12:37 AM, Paul J Stevens <[EMAIL PROTECTED]> wrote: > > Naomi Carson wrote: > > Hi there, > > > > Since upgrading to dbmail 2.2.7 from 2.2.5, we've been having problems > > with emails with latin1 characters such as é (e with accent accute) in > > the subject line. Other non-ascii characters such as Arabic or Thai > > seem to work fine. > > > > Before I try to store the message in dbmail, a subject line of "ééé" is > > encoded to "=?utf-8?b?w6nDqcOp?=". > > > > When I try to store the message, I get the following error: > > > > Error:[sql] dbpgsql.c,db_query(+287): query failed [INSERT INTO > > dbmail_subjectfield (physmessage_id, subjectfield) VALUES (60,'ééé')] : > > [ERROR: invalid byte sequence for encoding "UTF8": 0xe9e9e9 HINT: This > > error can also happen if the byte sequence does not match the encoding > > expected by the server, which is controlled by "client_encoding". ] > > > > I was able to store this subject no problem using dbmail 2.2.5. Any > ideas? > > The 'encoding' parameter in dbmail.conf needs to be the same as the > encoding in your database. > > So if you created your database with: > > createdb -E latin-1 dbmail > > then the 'encoding' specified in dbmail.conf must also be 'latin-1' (or > iso-8859-1, which is the same). > > The default dbmail.conf uses 'encoding = utf8'. But you must only use > utf8 in the encoding parameter if your database was also created with > utf8 encoding (createdb -E utf8 dbmail). > > > > -- > ________________________________________________________________ > 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 > > > > _______________________________________________ > DBmail mailing list > [email protected] > https://mailman.fastxs.nl/mailman/listinfo/dbmail > >
_______________________________________________ DBmail mailing list [email protected] https://mailman.fastxs.nl/mailman/listinfo/dbmail
