On 2/4/2011 10:50 AM, Matteo Cazzador wrote:
> Sure, thank's a lot everybody, i think the problem is related to:
>
> warning: mysql query failed: Illegal mix of collations
> (latin1_swedish_ci,IMPLICIT) and (utf8_general_ci,COERCIBLE)
> operation '='
> that cause
>
> warning: transport_maps lookup failure
>
>
> Someone suggest to forse use latin 1 in sql
>
> like =CONVERT('%s' USING latin1) for mysql transport table
>
> but is it correct?
>
> In reality i don't use mysql-transport table can elide it.
http://dev.mysql.com/doc/refman/5.1/en/charset-literal.html
Postfix allows sql/ldap queries in transport_maps, but it is discouraged
for this very reason.
If you have a small list of transports, use a static hash/dbm/cdb lookup.
You can update these using a script if they are dynamic.
Don't postmap a hash transport table if it is quite long as overwrites
the old one in-line. Postmap to a temporary name or use cdb instead.
>
>
> Il 04/02/2011 16:39, Reindl Harald ha scritto:
>> Am 04.02.2011 16:32, schrieb lst_ho...@kwsoft.de:
>>> So you have a local caching-resolver on the Postfix box?
>>>
>>> If so it should not fail because of traffic as long as your system
>>> resources are not exhausted.
>>> If your system resources are exhausted using a different resolver
>>> does not help.
>>>
>>> You might playing tricks with a local caching-resolver used by
>>> internal clients and
>>> pointing /etc/resolv.conf to
>>> some second (external) resolver but i doubt this is your problem at all
>> Even if dns-load would be the problem (which is not, it is mysql seen
>> some posts before)
>> the real problem should be searched because nohting is better for a
>> dns.cache as
>> a mailserver to get the cache filled
>>
>> But i never seen any machine where dns-lookups where a load problem
>>
>>
>>
>
