Wietse Venema via Postfix-users:
> If we change the syntax of smtp_sasl_password_maps entries, then
> that will require a new configuration parameter to indicate how the
> lookup result should be parsed.
>
> My preference would be:
>
> smtp_sasl_password_map_result_delimiter
I implemented a
Hi,
> Am 13.08.2023 um 02:06 schrieb Wietse Venema via Postfix-users
> :
>
…
> My preference would be:
>
> smtp_sasl_password_map_result_delimiter
>printable character or C escape (like \t for TAB)
>default = : (for backwards compatibility)
>must not be empty
>must not be
Wietse Venema via Postfix-users:
> There is a tool that given a JSONschema will generate a parser in
> C that populates a C structure, at github.com/badicsalex/json_schema_to_c
> (~300 LOC). This depends on github.com/zserge/jsmn (~500 LOC). The
> generated parser is much bigger, over 35 kLOC for
Viktor Dukhovni via Postfix-users:
> On Sun, Aug 13, 2023 at 01:47:05PM -0400, Wietse Venema via Postfix-users
> wrote:
>
> > > Any votes for JSON? :-)
> > >
> > > { "account": "user:foo", "base64password": "" }
> >
> > Before other people start to chime in, let me set some
On Sun, Aug 13, 2023 at 01:47:05PM -0400, Wietse Venema via Postfix-users wrote:
> > Any votes for JSON? :-)
> >
> > { "account": "user:foo", "base64password": "" }
>
> Before other people start to chime in, let me set some expectations.
My suggestion of JSON is largely in
Viktor Dukhovni via Postfix-users:
> On Sat, Aug 12, 2023 at 08:05:52PM -0400, Wietse Venema via Postfix-users
> wrote:
>
> > My preference would be:
> >
> > smtp_sasl_password_map_result_delimiter
> > printable character or C escape (like \t for TAB)
> > default = : (for backwards
On Sat, Aug 12, 2023 at 08:05:52PM -0400, Wietse Venema via Postfix-users wrote:
> My preference would be:
>
> smtp_sasl_password_map_result_delimiter
> printable character or C escape (like \t for TAB)
> default = : (for backwards compatibility)
> must not be empty
> must not
zonie via Postfix-users:
>
>
> > Wietse Venema via Postfix-users :
> >
> > ?zonie via Postfix-users:
> >> Hello,
> >>
> >> currently it's not possible to specify a username containing a colon ?:?
> >> inside a ?smtp_sasl_password_map?, as the colon is used to split username
> >> and
> Wietse Venema via Postfix-users :
>
> zonie via Postfix-users:
>> Hello,
>>
>> currently it's not possible to specify a username containing a colon ?:?
>> inside a ?smtp_sasl_password_map?, as the colon is used to split username
>> and password from each other.
>>
>> Is this limitation
>> Hello,
>>
>> currently it's not possible to specify a username containing a colon ?:?
>> inside a ?smtp_sasl_password_map?, as the colon is used to split username
>> and password from each other.
>>
>> Is this limitation intentionally or was it just overlooked?
>
> Just like the UNIX
zonie via Postfix-users:
> Hello,
>
> currently it's not possible to specify a username containing a colon ?:?
> inside a ?smtp_sasl_password_map?, as the colon is used to split username and
> password from each other.
>
> Is this limitation intentionally or was it just overlooked?
Just like
11 matches
Mail list logo
