Hi Wietse, thanks, will test 👍🙏 -- *Best Regards,* Dmitriy Alekseev DevOps Engineer
On Sun, 29 Jun 2025, 15:57 Wietse Venema via Postfix-users, < postfix-users@postfix.org> wrote: > Dmytro Alieksieiev via Postfix-users: > > off SMTPUTF8 due to issues in postfix-postres client that with disabled > > SMTPUTF8 due to unclear reason start to speak with PostgresSQL in ASCII > > encoding and at same time tried to pass LATIN1 payload (aka ??) which > > leading to breaking DB connection for a smtp worker and 4xx error, > > Wasn't that fixed in Postfix 3.8, with the "encoding" setting? > > Wietse > > PGSQL_TABLE(5) File Formats Manual > PGSQL_TABLE(5) > ... > encoding > The encoding used by the database client. The default > setting > is: > encoding = UTF8 > > Historically, the database client was hard coded to use > LATIN1 > in an attempt to disable multibyte character support. > > _______________________________________________ > 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
