> Any suggestion?
There is no "better" answer to this question. You are advised to
read "The Unix and the Echo"[1], by Doug McIlroy, and Russ Cox's
adaptation for our system, "The Plan 9 and the Echo"[2].
If you need different behavior than what's there, you want
something other than echo.
[1]
Hello Fans,
When echo(1) is invoked with -n and no or empty arguments, it calls
write(2) with zero length. When writing to a pipe, the other end of the
pipe read()'s zero byte, which causes it thinks it's got to the end and
close the pipe, and commands after the "echo -n" would fail to write. I
st
>> The farthest I have gotten is getting smtp to issue 220 Ready to Start
>> TLS, and then it exits, that's running smtp with the -d flag.
>> /sys/log/smtp reveals a bunch of bad thumbprint x509 lines. I have tried
>> adding the sha1 hash to /sys/lib/tls/mail, but this has had no effect.
>
> For
> The farthest I have gotten is getting smtp to issue 220 Ready to Start
> TLS, and then it exits, that's running smtp with the -d flag.
> /sys/log/smtp reveals a bunch of bad thumbprint x509 lines. I have tried
> adding the sha1 hash to /sys/lib/tls/mail, but this has had no effect.
For outgoing
> The farthest I have gotten is getting smtp to issue 220 Ready to Start
> TLS, and then it exits, that's running smtp with the -d flag.
> /sys/log/smtp reveals a bunch of bad thumbprint x509 lines. I have tried
> adding the sha1 hash to /sys/lib/tls/mail, but this has had no effect.
you might tr
