> Would you stop this nonsense about the Memphis RPM screwing up things like
> "the default behavior of telnet" already? As I recall, you had
> some sort of
> termcap problem with the Windows telnet client, which is about as far
> removed from the Memphis RPM and tcpserver as can be. The firewall has
> nothing to do with it either.
I'm pretty sure I didn't say "screwing up". I think I said affecting.
There's a difference.
Besides, the problem was not with the Windows Telnet client.
The default behavior with my telnet server had been that
if you dialed in with a Windows Telnet client it was
unnecessary to set the term to be vt100. That is a telnet
server default behavior. After installing the Memphis RPM
that step became necessary.
This raises an obvious question?
Is the installation of the Memphis RPM and the change
in the behavior conincidental or correlative?
I would like to test to find out the answer. But I'm
not that interested in seriously affecting my small
user base.
So the big question is: If I RPM -e the Memphis RPM at 2:00 am or something,
test the default behavior of my telnet server (i.e. conduct an experiment to
confirm a field observation), then reinstall the Memphis RPM (and perform
Stuart's K to S tweak in the rc3.d directory) will mail sent to my system
during the
experiment bounce?
This is also relevant in that when I finally get everything working with the
Memphis RPM I'd like to reconstruct everything necessary to get QMail
running without an RPM using a tarball which I was unsuccessful at
originally. It would be nice if the mail didn't bounce during the down
times.
P.S. I could care less about how good the windows client is.
If I grant shell access to a 15 year old I trust who wants
to learn html, I want to give her a clear set of instructions
and not direct her to some commercial software. How do you
think I found out that the default behavior of my telnet
server had changed? What had I done between the time she logged
in successfully and ran pico and when she did not log in
successfully and run pico? I installed the Memphis RPM. It's not grasping at
straws to notice that. For all I know, the Memphis RPM could have a
bizillion unwanted side effects that have nothing to
do with it's intended functionality. That's what a side effect
is. I KNOW that telnet has nothing to do with email, nor does
solitaire, but if I left my machine alone, then installed solitaire and
found out that something bad happened right then
I'd reasonably wonder if installing solitaire caused the side effect. I
would then want to know if others had made the same field observation and
possibly run an experiment to confirm or deny it.
> -----Original Message-----
> From: Chris Johnson [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, June 30, 1999 3:47 PM
> To: Alex Miller
> Subject: Re: Perhaps I missed it the first time ...
>
>
> > I think that the restrictions of the firewall are the reason
> > I was getting side-effect problems when installing the Memphis RPM,
> > such as the default behavior of telnet changing!
>
> Would you stop this nonsense about the Memphis RPM screwing up things like
> "the default behavior of telnet" already? As I recall, you had
> some sort of
> termcap problem with the Windows telnet client, which is about as far
> removed from the Memphis RPM and tcpserver as can be. The firewall has
> nothing to do with it either.
>
> If you can show how your installation of the RPM and tcpserver
> messed things
> up, then I'm sure that Dan and the guy who put the RPM together would like
> to hear about it. Keep the speculation to yourself (because it's wrong).
>
> Chris
>
>
