Re: [Sqlgrey-users] More on sqlgrey stop/recover issue

[Lionel B. <lio...@bo...>]

Andrew Diederich wrote the following on 18.12.2006 21:14 :
> Dec 18 12:32:43 tango sqlgrey: dbaccess: warning: couldn't do query: UP=
DATE from_awl SET last_seen =3D NOW(), first_seen =3D first_seen WHERE se=
nder_name =3D 'man=C3=83=C5=A1genervy' AND sender_domain =3D 'abyss.wesn.=
sun.com' AND src =3D '81.215.189.168': ERROR:  invalid byte sequence for =
encoding "UNICODE": 0xe86765 , reconnecting to DB
>  =20

Hum, did you try to use a database with ASCII instead of UNICODE?=20
SQLgrey doesn't try to speak utf-8 with the database but only pure=20
ASCII. If you receive adresses with characters outside the utf-8 space,=20
this behavior is expected with a UNICODE database.

Nothing to do with unicode domain names (these ones are encoded in ASCII=20
anyway, so Postfix and SQLgrey don't need to be aware of them). You=20
can't configure Postfix easily to solve this and to solve it in SQLgrey,=20
we would have to make it aware of the database encoding and call iconv=20
to make sure everything fits, assuming the original encoding is always=20
ISO-8859-1 for the Return-Path.

ASCII at the database level is your best bet, you should dump your DB,=20
create another one with ASCII encoding, restore the original DB in the=20
new one, change SQLgrey's database in sqlgrey.conf and restart SQLgrey.

Lionel