Claudio Prono wrote: > Uhm, i have another information about that case: the mail are sended to > postfix from an antispam appliance (Symantec). Can be a problem of > config of that antispam results illegal characters are sended to postfix? > Can i add something to solve that problem?
That is possible, but more likley illegal characters appear in the original received mail and the appliance just lets them through. Until such novelty as UTF8SMTP gets some traction (not anytime soon it seems), I still think the cleanest and safest way is to treat envelope addresses as strings of bytes with no associated character set. That means declaring data type of such SQL fields as VARBINARY or BYTEA, and letting a client use a data type SQL_VARBINARY (or PG_BYTEA for PostgreSQL) for passing such data to SQL. This avoids all the fancy magic in SQL, like verifying compliance to a given character set, and using collations associated with a character set (including making compares case-insensitive). Mark
