https://bugs.exim.org/show_bug.cgi?id=2409
--- Comment #1 from Simon Arlott <bugzilla.exim.simon@???> ---
It looks like the reason I'm getting non-ASCII data in sx.buffer is because
it's never initialised and never used because of the failure to start TLS in
SMTPS mode, so the first character of the buffer needs to be initialised to 0
in case it's not used.
This doesn't prevent the remote server from sending us non-ASCII data that we
then relay in the verification message.
--
You are receiving this mail because:
You are on the CC list for the bug.
