Mark Martinec ha scritto:
>> What MySQL makes of such data is up to the MySQL client and server
>> libraries, but Postfix does not promise that the input will be well-formed
>> UTF-8, or ISO Latin or anything of the sort. Just an array of bytes.
>>
>
> Right, as it should be. Envelope addresses are not associated with any
> character set according to RFC 5321, they are just strings of octets.
>
> For this reason an appropriate SQL data type for such fields is
> VARBINARY (or BYTEA in PostgreSQL). A data type CHAR or VARCHAR
> is inappropriate, as it associates a character set with data. SQL may
> perform validation of data according to the specified character set.
> MySQL tend to be quite premissive to such violations, but there is
> no guarantee. Also, comparing CHAR or VARCHAR strings with
> relational operators is case-insensitive and may even apply
> special (like Unicode) rules for character equivalency.
>
>
So, how i can fix that issue? Is quite annoying and results in some mail
sended or recived with a "Temporary Lookup Failure".... Any idea?
Cordially,
Claudio Prono.
--
--------------------------------------------------------------------------------
Claudio Prono OPST
System Developer
Gsm: +39-349-54.33.258
@PSS Srl Tel: +39-011-32.72.100
Via San Bernardino, 17 Fax: +39-011-32.46.497
10141 Torino - ITALY http://atpss.net/disclaimer
--------------------------------------------------------------------------------
PGP Key - http://keys.atpss.net/c_prono.asc
