This and some other experiences have convinced me that the "unexpected
char (10)" bug is just the surface manifestation of the real problem,
I think the real problem was that stunnel executed in inetd mode was sending its last line of logs to stderr, instead of the configured log output (e.g. syslog).
I have fixed this bug here:
Could you please let us know if this version fixes your problem?
Mike