PuTTY port forwarding corruptions
David Balazic
the ports 110 and 25 on the ssh server :
L2110 -> ssh_server:110
L2025 -> ssh_server:25
Then I use netscape 4.8 locally and set its POP3 and STMP servers to
localhost:2110 and localhost:2025.
It usually works, but sometimes this happens :
When sending a message, the message is sent, but then the send dialog of
netscape stops saying "Message sent. Waiting for reply" If I cancel the
dialog and try to send the same message again, it usually succeeds.
According to the putty logs, the message is sent to the SMTP server
and ended with a line containing a single dot, but the server does
not respond. Then netscape sends a QUIT command and the channel closes.
It might be a SMTP server problem, but the admin is not very cooperative.
The receiver receives only one copy of the message.
Another problem is corruption. Almost always when I send attachements,
the receiver receives a currupted message. It is all made up of something
that looks like base64 encoded data. The size of the message is more or
less correct. It looks like the headers were lost ( including the subject )
and he only the last 95% of the message ( including the closing boundary :
...
igAooooAKKKKACiiigApKKKADFLRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQB/
/9k=
--------------28D39B3CDC1003186D768CDE--
Yet another problem, which could be just a variation of the second , is
that sometimes the recepient receives an empty message. This happens
with shorter messages, so it could be that it is problem 2, just the
entire message was lost.
I set up putty to save log, but they do not give any clue. According to
them the message was properly forwarded to the ssh_server.
I think on writing and running a port echo program on ssh_server and test
it over PuTTY forwarding to see if any data is corrupted.
Does anyone experienced anything similar ?
Regards,
David Balazic
