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}
Thank you so much for your hard work and commitment in producing well thought-out solutions. WeOnlyDo is very committed to customer satisfaction!
WeOnlyDo!COM will be the first stop I make should I require any further off-the-shelf components.
It was no small factor, however, that your support in getting me up and running made me buy from you.
Your professionalism is reflected into your email, your product and your web site. I am confident that these will make the difference.
We are having great success with your component ... email server that has over 750 000 mailboxes back ended by a SQL server...
Just thought you'd like to know that my gateway app with your SMTP Server component held the line against a DDOS attack today...
You did a great job on wodSSH and wodSSHServer! I got a lot for very little money. Thanks!
Many thanks for your excellent support service. I can see why you have a long list of excellent testimonials on your website.
Your professionalism is reflected into your email, your product and your web site. I am confident that these will make the difference.
You have been great as far as offering support is concerned and has been extremely responsive to both support requests and suggestions for product enhancements.