> On 23 Feb 2022, at 2:50 pm, Wietse Venema wrote:
>
>>>
>>> TWO settings to enable UTF8? Bah.
>>
>> No, because the second one would be *ON* by default.
>
> And that would be an incompatible change from LATIN1?
Only if also "smtputf8_enable = yes". That is, with "smtputf8_enable = yes"
we'd
Viktor Dukhovni:
> > On 23 Feb 2022, at 6:38 am, Wietse Venema wrote:
> >
> > TWO settings to enable UTF8? Bah.
>
> No, because the second one would be *ON* by default.
And that would be an incompatible change from LATIN1?
> It would probably be better named "utf8_disable" and then
> be "off"
> On 23 Feb 2022, at 6:38 am, Wietse Venema wrote:
>
> TWO settings to enable UTF8? Bah.
No, because the second one would be *ON* by default.
It would probably be better named "utf8_disable" and then
be "off" by default.
--
Viktor.
Phil Stracchino:
> On 2/23/22 06:38, Wietse Venema wrote:
> > TWO settings to enable UTF8? Bah.
>
> I have to admit that my feeling on this is "Let LATIN1 die". The future
> is encoded in UTF8/UTF16.
Agreed, for the longer term. But the patch was for the stable release.
Wietse
On 2/23/22 06:38, Wietse Venema wrote:
TWO settings to enable UTF8? Bah.
I have to admit that my feeling on this is "Let LATIN1 die". The future
is encoded in UTF8/UTF16.
--
Phil Stracchino
Babylon Communications
ph...@caerllewys.net
p...@co.ordinate.org
Landline: +1.603.293.848
TWO settings to enable UTF8? Bah.
Wietse
On Tue, Feb 22, 2022 at 07:10:44PM -0500, Wietse Venema wrote:
> There are two #ifdef SNAPSHOT blocks.
>
> - The one in dict_pgsql_lookup() returns not found when SMTPUTF8
> is enabled, but a query is not valid UTF8.
>
> - The one in plpgsql_connect_single() sets the PgSQL client encoding
>
Viktor Dukhovni:
> On Tue, Feb 22, 2022 at 01:41:00PM -0800, Nathan Van Ymeren wrote:
>
> > I have enabled UTF8 in postfix as per the instructions here:
> > http://www.postfix.org/SMTPUTF8_README.html#enabling , which you can
> > see in the following config info:
>
> This enables UTF8 in SMTP, bu
On Tue, Feb 22, 2022, 14:49 Viktor Dukhovni
wrote:
> On Tue, Feb 22, 2022 at 02:32:29PM -0800, Nathan Van Ymeren wrote:
>
> > > So UTF8 is only used in development snapshots and not in release
> builds.
> > > This code needs to be made either conditional on EAI (UTF8) being
> > > enabled, or a ne
On Tue, Feb 22, 2022 at 02:32:29PM -0800, Nathan Van Ymeren wrote:
> > So UTF8 is only used in development snapshots and not in release builds.
> > This code needs to be made either conditional on EAI (UTF8) being
> > enabled, or a new user-settable PgSQL table parameter.
> >
> > > How do I get po
On Tue, Feb 22, 2022, 14:29 Viktor Dukhovni
wrote:
> On Tue, Feb 22, 2022 at 01:41:00PM -0800, Nathan Van Ymeren wrote:
>
> > I have enabled UTF8 in postfix as per the instructions here:
> > http://www.postfix.org/SMTPUTF8_README.html#enabling , which you can
> > see in the following config info:
On Tue, Feb 22, 2022 at 01:41:00PM -0800, Nathan Van Ymeren wrote:
> I have enabled UTF8 in postfix as per the instructions here:
> http://www.postfix.org/SMTPUTF8_README.html#enabling , which you can
> see in the following config info:
This enables UTF8 in SMTP, but does not presently affect the
Hello,
I am trying to set up postgresql-based virtual domains. I am on
FreeBSD 13. When I try to test my domain mapping, I get a strange
error about character encodings:
# postmap -v -q example.org
pgsql:/usr/local/etc/postfix/pgsql-virtual-mailbox-domains.cf
postmap: name_mask: ipv4
postmap: n
13 matches
Mail list logo
