user

workaround with maildrop [http://www.courier-mta.org/maildrop/](url), that works with base64 encoded headers and message body maildrop configuration `$ cat ~/.mailfilter if ( /^Subject:.*(путевка|тунис|романтика)/ ) { EXITCODE=5 exit } else { EXITCODE=0 exit...

>brace yourself the winter is coming and we all waiting for something GPUseful on ARM SoC's, please make it yuq, you're our only hope

ldap2json would certainly benefit from that! )

in LDAP case base64 being used for Cyrillic strings. Exec variant is too slow ` $ echo "b64==YT3Qv9GA0LjQstC10YIsYj3QvNC40YA=" | mlr --idkvp --ips '==' --ojson --no-jlistwrap put 'func base64d(s) { return...

Return only string, "valid" or hexfmt like !? https://pkg.go.dev/unicode/utf8#ValidString

@johnkerl Sir, adding `bytes` would bring much joy to parsing ms LDAP dns entries, etc. Now it is os execute with `base64 | dd | iconv ` pipe, could be...

 same