------- You are receiving this mail because: -------
You are the QA contact for the bug.
http://bugs.exim.org/show_bug.cgi?id=508
--- Comment #6 from Jeremy Harris <jgh146exb@???> 2015-01-17 22:02:09 ---
Reading between the lines somewhat, the referenced forcing of SQL_ASCII was
needed so that a consistent base for quoting rules was there.
Are quoting rules different for different encodings?
Exim does not have an overall encoding concept for a message. There are
related
concepts made available by MIME-handling ($mime_charset,
$mime_content_transfer_encoding) but Exim only provides them to the config
file writer. Use of pgsql is also entirely under the control of the config
file
writer including any data transferred, so if we are to provide control over the
DB encoding it seems that a per-call option is needed.
We maintain (possible multiple) cached connection(s) so we'd need to include
the encoding as part of the connection label. We'd also need to worry about
the quoting issue (above).
--
Configure bugmail:
http://bugs.exim.org/userprefs.cgi?tab=email
