On Wed, Jun 17, 2009 at 09:22:31AM -0400, Brian Evans - Postfix List wrote:
> Simon wrote:
> > Hi Blake, thanks for the reply.
> >
> > The Mysql server that the postfix configuration is on indeed does have
> > default-character-set=utf8 set and this was changed not so long ago..
> > but we need to have it as such for reasons. I have moved the config to
> > another mysql server (without default-character-set=utf8) for the mean
> > time, but is there a way we can still have default-character-set=utf8
> > on the mysql server and have the postfix config on it?
> If you convert the map to the Postfix 2.2+ syntax, you can force the
> character type using the query itself.
>
> user = mail-in1
> password = ******
> dbname = postfix
> hosts = 210.48.XX.XXX
> query = SELECT transport from transport where domain = _utf8'%s'
This is wrong, the data that Postfix replaces '%s' with is raw
binary data. It is NOT UTF-8, and saying that it is, is asking
for all kinds of trouble. SMTP is an ASCII protocol, there is
no unambiguous meaning to 8-bit data in envelopes and headers.
Use an encoding where all 8-bit patterns are valid, and ASCII
is mapped verbatim into the lower 7-bits. Any ISO-8859-X will
do. Multi-byte encodings (like UTF-8) are right out.
--
Viktor.
Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the "Reply-To" header.
To unsubscribe from the postfix-users list, visit
http://www.postfix.org/lists.html or click the link below:
<mailto:majord...@postfix.org?body=unsubscribe%20postfix-users>
If my response solves your problem, the best way to thank me is to not
send an "it worked, thanks" follow-up. If you must respond, please put
"It worked, thanks" in the "Subject" so I can delete these quickly.
