From: Anton Yuzhaninov (citrinrambler-co.ru)
Date: Thu Jun 22 2006 - 12:12:57 CDT

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Hello, Victor.

You wrote on Thursday, June 22, 2006, 8:56:15 PM:

> strict_rfc821_envelopes = no

As I can see this strict_rfc821_envelopes don't turn check if code > 127 or
not.

>> This parameter used in query to mysql, and when smtp client send utf-8
>> string a got error: Illegal mix of collations
>> (utf8_general_ci,IMPLICIT) and (latin1_swedish_ci,COERCIBLE)
>> for operation '='

> What version of Postfix is this? You should not avoid using localized
> databases for Postfix address lookups. With the upcoming 2.3 release
> the PgSQL client charset is explictly set to LATIN1 (1-byte in 1-byte out).
> Perhaps a similar change should be made to the MySQL driver, so that it
> does not implicitly assume that the input is UTF-8.

postfix2.2 + mysql4.1

>> I suppose postfix should reply with "Bad address syntax" when
>> localpart or domain contain symbols with code > 127, and don't try to
>> use this bad address to query mysql...

> I think you can guess how to make this setting (hint: smtp_ and lmtp_
> parameters are not for smtpd(8)).

pcre pattern in smtpd_recipient_restrictions? This has some cpu
overhead.

We use "= binary" in mysql query as workaround.

--
WBR,
 Anton Yuzhaninov
 Rambler

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]