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 be multiple characters
>
> I think that TAB would be safe for your case, unlikely to conflict
> with anything in a username or password.
My vote is for this one.
> There are other approaches, like protecting text with quotes, like
> "foo:bar":password, or prepending a length to each field value, like
> 7:foo:bar8:password.
Any votes for JSON? :-)
{ "account": "user:foo", "base64password": "AAAABBBBCCCC" }
which could admit future extensions (per-user mechanism filter???), but
is likely over-engineered. Base64 encoding avoids questions of text
encoding for strings with non-ASCII characters.
--
Viktor.
_______________________________________________
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org
