[exim-dev] [Bug 508] PostgreSQL client_encoding broken

Página Inicial
Delete this message
Reply to this message
Autor: Casey Allen Shobe
Data:  
Para: exim-dev
Assunto: [exim-dev] [Bug 508] PostgreSQL client_encoding broken
------- You are receiving this mail because: -------
You are the QA contact for the bug.

http://bugs.exim.org/show_bug.cgi?id=508




--- Comment #5 from Casey Allen Shobe <cg@???> 2015-01-17 21:16:39 ---
Really it needs more than a simple setting. A setting would not be needed
anyways since the default client encoding would be the server encoding (I
think), or worst case, it could be set for the database user by the DBA.

Say you have E-mail content encoded in BIG5 that you want to store in a UTF-8
database. It must be converted to UTF-8 prior to saving to the DB if the
client_encoding is set to UTF-8, or you could set client_encoding to BIG5 and
let the database do the translation automatically for you.

So I think that the best approach would be to set the client_encoding based
upon the encoding of the E-mail being processed. There are still cases where
something may be not encoded entirely as it states that it is - does Exim deal
with this another way already?


--
Configure bugmail: http://bugs.exim.org/userprefs.cgi?tab=email