aljasPOD

I've encountered a similar issue (and spent a few hours debugging). In my case the EINVAL was coming from the linux connect call (all the way from [here](https://github.com/proftpd/proftpd/blob/b724aea82cf281447aae1f70f0a0e8eb4e79640c/src/inet.c#L1430)). Doing strace...