ASCII mode does not work for SFTP endpoint in Camel

Issue

Endpoint is defined with binary=false option, sample:

<to uri="sftp://<hostname>/OUT?username=username&password=xxx&fileName=file.txt&autoCreate=true&binary=false"/>

The result file still contains the same line ending symbols (CRLF for Windows or CR for Unix based systems) as in the source file, i.e. it was not replaced by platform specific line ending symbols for the destination.