Brian,
> OK, that makes good sense, but the default query doesn't . . . . .
> nevermind.
>
> I opened amavisd and consequently added
> $sql_allow_8bit_address = 1;
> to amavisd.conf and it's happy now.
>
> Not sure if that is what I'm sticking with, but it does fix the problem.
Yes, it does avoid the problem:
if (!$sql_allow_8bit_address) { s/[^\040-\176]/?/g for @$keys_ref }
...
my($datatype) = $sql_allow_8bit_address ? SQL_VARBINARY : SQL_VARCHAR;
The $sql_allow_8bit_address controls the data type used in an argument
of a query, and if false, it also turns 8-bit characters into '?'.
> The database is a Postgres UTF8, and forgive my ignorance here, but will
> that cover any kind of email address with a VarChar column type, or is
> there still a need for VarBinary?
The chosen $datatype (as above) affects a type of arguments resulting
from %k and %a placeholders in a query (SQL lookups), as well as a
data type of an email address in table maddr (SQL logging, aka PenPals).
> I'm assuming that by using VarBinary I'll be losing the capability
> to do string-based queries with wildcards such as "LIKE '%domain.com'.
> Is that correct also?
I'm not sure. There is always a choice of using an SQL conversion function
on expressions in a query, or type casting.
Mark
------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables unlimited
royalty-free distribution of the report engine for externally facing
server and web deployment.
http://p.sf.net/sfu/businessobjects
_______________________________________________
AMaViS-user mailing list
AMaViS-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amavis-user
AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/howto/
