The final outcome of this issue was issuing a .columns property at the initiation of the telnet session. The server i was connecting to was truncating at 80 columns and sending a /r/n which broke up the data. I'm using .columns=150 which now allows the full data string to be sent without truncation and all is well.
Complete thread:
![[*]](themes/default/images/complete_thread.png "Open whole thread"){kind=small}
I would highly recommend this to anyone who needs a good quality SFTP solution.
Just thought you'd like to know that my gateway app with your SMTP Server component held the line against a DDOS attack today...
Thank you very much for the rapid responses. I was a little nervous about dealing with a company that is on a different continent from me. You have proven my concerns to be unfounded.
May I say how nice it is to work with components so complete and self-explanatory that using them in my application is as instinctive as though I wrote them myself?
Just thought you'd like to know that my gateway app with your SMTP Server component held the line against a DDOS attack today...
Brilliant, even works on the mobile phone...
The wodCrypt product is great and we appreciate your effort to add support for UNIX Crypt.
...what I really like is that wodSSH and wodSFTP components work excellently and are constantly being improved...
You made it so simple for us to integrate SFTP - a technology we had little experience with...
Your support is fantastic.