On 2011-04-07 at 12:48 +0100, Mark Adams wrote:
> I fixed other encoding issues I had by adding :rfc2047: in as follows
>
> ${quote_pgsql:rfc2047:$h_subject:}
Assuming you mean ${rfc2047:...} then that encodes data. I'd expect you
to normally want to decode data. As written though, that does not
change the characters at all. Perhaps:
${quote_pgsql:${rfc2047:$h_subject:}}
Build Exim with HAVE_ICONV=yes and either HEADERS_CHARSET="UTF-8" at
build time or headers_charset="UTF-8" in the main section of the config.
> However this doesn't seem to work for the pound sign.
Which exists in ISO-8859-1, the default header charset.
> Whats the best way to sort out encoding issues with postgres so anything
> that comes through exim can be inserted in to postgres?
Kick Exim to do more work in UTF-8 instead of Latin1.
I *think* that will work. Don't have time to thiunk deeply right now.
--
## List details at http://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/
