Hi again,
I realized than same error is raised when database is in utf8 if email
contains utf8mb4 characters.
Which is the convenient database collation for postfix? We can force
postfix to accept only utf8 characters?.
El 13/4/23 a las 18:36, Víctor Rubiella Monfort via Postfix-users escribió:
When mysql_table lookup is executing nonascii characters and database
is in latin1, not only fails query, all sesion/connection is corrupted
and produces a lot of "temporary lookup table" errors until sesion is
recreated (about 1 minute later).
Today some external ip was trying to deliver an email with special
character on one on my legacy servers (with latin1) and produces this
errors.
I can understant that lookup fails for query with special characters,
but main issue was for all raised failures for other accounts and
lookups during 1-2 minutes. This is a knew issue?.
I deploy an workaround using "CONVERT('%s' using ascii)" until not
pass all database tables to utf8.
The main problem debuging this issue was "proxy:mysql" , "proxy" was
hiding original collation error and only shows regular lookup errors
on postfix log, when user "postmap" to debug, I only see root cause
when execute without "proxy".
postfix versions tested:
postfix 3.5.17-0+deb11u1
postfix-mysql 3.5.17-0+deb11u1
postfix 3.5.15-0+deb11u1
postfix-mysql 3.5.15-0+deb11u1
_______________________________________________
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org
_______________________________________________
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org
