On Sat, 24 Feb 2001, Mark Edward Reed wrote:
> Hello Fred
> On 19-Feb-01, you wrote:
>
> > If you don't want to use servers at all, just edit telserd.conf and
> > comment out the lines that aren't already comments.
>
> OK, where would I put this? I do have Genesis off of the OS 3.9 CD
> installed and it assigns itself as AmiTCP:
It goes in AmiTCP:db/, where the Telser installer should put it.
> > There's not really too much that you *have* to set up, and it's pretty
> > well documented. The main issue in using it with Miami is that it expects
> > AmiTCP: and some of its subdirectories to exist. Some people map AmiTCP:
> > to Miami:, but I personally prefer to keep them separate.
>
> Since I had recently installed Genesis and I noticed later that it assigned
> itself as AmiTCP, it may work sing it also has some of the directories
> there as well.
Yes, that saves having to create the directories for it.
> I was forced to register AmTelnet due to a problem our club prez was
> having with his ISP.
>
> He is a rabidly fanitical C64/128 user, that doesn't gripe about the
> Amiga (much.)
>
> He logs on via a direct-dial Unix shell that our ISP has provided along
> side the PPP/SLIP access. One day things were working and the the next...
>
[...]
>
> He was on for a few days, using Pine (his normal email client on the ISP,)
> to try to sort through the horde of email on his system. One day Pine
> started to lock up on loading.
>
[...]
>
> We tried using Termite to access his account, (and I tried accessing mine
> as well,) problem was duplicated. (It freezes up at some point between
> opening up Pine or opening up your folder list or Inbox.)
>
> I tried AmTelnet and with a straight telnet connection, I was also able to
> duplicate this problem. The interesting thing is that this problem does not
> appear when I try connecting using the SSH. I have no idea why this is so,
> but the SSH does something to get around the problem.
I wonder if Pine might be sending a "clear output buffer" at some point.
This normally translates into a Telnet SYNCH sequence, which uses TCP
urgent data. Due to some inconsistencies in the specs and non-robustness
in the recommended Telnet command handling, this can sometimes cause
output to become permanently "muted" with certain software combinations.
Since SSH doesn't really support the whole urgent data concept, you
wouldn't see trouble with it. I.e., it's really a bug that happens to
have a useful effect in this case.
SSH port forwarding also lacks urgent data support. Have you tried
forwarding a Telnet connection through SSH?
> I had this ISP since it's shell access was a backup incase my A4000 blew
> up. Now i think I'm gonna hunt for a new one. (How to I get my email
> forewarded until I can get the notice of of the address change???)
On most Unix systems, you can simply create a .forward file in your home
directory, with the desired target email address as the contents. If you
ever switch back, be sure not to have both ISPs forwarding to each other.
:-)
FRed Wright
--
To unsubscribe send "unsubscribe miami-talk-ml" to
"[EMAIL PROTECTED]". For help on list commands send "help" to
"[EMAIL PROTECTED]".
