Without this, data without a newline (e.g., from a lone CR protocol violation
detected by the parser) stays in the buffer indefinitely. This prevents the
server from ever detecting client disconnect, causing a deadlock where both
sides wait for the other.
The post-login server-side client_skip_line() in managesieve-client.c already
handles this correctly by always calling i_stream_skip().
Gbp-Pq: Name 0002-managesieve-login-client_skip_line-Discard-data-when.patch
}
}
+ i_stream_skip(client->input, data_size);
return FALSE;
}