V?ctor Rubiella Monfort via Postfix-users:
> 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?.
With "smtputf8_enable = yes" in main.cf, Postfix will accept
well-formed UTF-8. However, before Postfix 3.8, the Postfix pgsql:
client code sets the client encoding to LATIN1.
The client encoding is configurable (default: UTF8) with Postfix
3.8 which is to be released soon (postfix-3.8.0-RC1 was published
a few days ago).
As for the temp error becoming persistent, the Postfix pgsql: client
code returns an error when it gets an error from all of the hosts
configured in the Postfix pgsql: client configuration file, or when
all hosts have been flagged as 'down'. If a host returns an error
then the Postfix pgsql: client code flags that host as 'down', and
resets that 'down' state after about 60 seconds.
In your case having multiple hosts configured in the Postfix pgsql:
client configuration would not help, because they would have the
same error.
Wietse
>
>
> 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
>
_______________________________________________
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org
