Using with the brook proxy server

I am trying to work with the google smtp server through the brook proxy server (https://github.com/txthinking/brook), here is the sample code:

let {SocksClient} = require('socks')

const options = {
  proxy: {
    ipaddress: '35.174.27.1',
    port: 1080,
    type: 5,
    userId: 'bouncedoc',
    password: 'password'
  },
  command: 'connect',
  destination: {
    host: 'gmail-smtp-in.l.google.com',
    port: 25
  }
};

(async function test () {
  let results = 0

  for (let i = 0; i < 20; i++) {
    let info = SocksClient.createConnection(options, (err, info) => {
      if (err) return console.error(err)
      info.socket.on('data', data => {
        console.log(data.toString())
        results += 1
      })
    })
  }
  setTimeout(() => {
    console.log(`${results}/20`)
  }, 3000)
})()

Running brook on aws in container:

docker run -d -e "ARGS=socks5 -l :1080 -i 0.0.0.0 --username bouncedoc --password password" -p 1080:1080 chenhw2/brook

Sometimes the data handler receives non-ascii chars, sometimes it completely fails with Received invalid Socks5 final handshake response. Expected receiving something like 220 mx.google.com ESMTP x37si5670929qtx.226 - gsmtp

[JoshGlazebrook]

The main change is buffering all incoming data in an internal receive buffer, and processing the next steps in the SOCKS handshake when all the required data is in the buffer. Then once the SOCKS handshake is done, any excess data received is emitted as a ‘data’ event on the socket itself, so nothing should be lost.

[JoshGlazebrook]

This was fixed by #26 and is published to npm at 2.1.5