🚀 go-pugleaf

On Tue, 6 May 1997 bofh@snoopy.virtual.net.au wrote:

> >I've got a wierd problem with poppassd from windows machines. I'm running
> >Debian 1.2 with the poppassd .deb installed.
> 
> >When I try and change passwords using Eudora, it times out with error
> >messages. So I tried telnet to port 106 (used by poppassd according to
> >/etc/services and /etc/inetd.conf), and I got different things depending
> >on what OS I was running.
> 
> >I always "see" the poppassd prompt come up, and from a linux machine, I 
> >can type responces and see what I type echoed back. But from windows,
> >anything I type seems to go nowhere. It's like windows treats port 106 on
> 
>    Check the local echo settings of the telnet client software to get it to
> display what you type.  You may have to explicitely enable local echo on
> the Windows telnet program.
> 
local echo in the telnet client is not the problem. When telneting from
linux, I have local echo disabled, and the poppassd at the other end does
the echo for me. Under windows, I have the same setup, but nothing echoes
back, because poppassd is not getting anything. 

I know poppassd is not getting anything, because under linux, if I type an
invalid responce and hit enter, poppassd sends back a message about
"invalid responce, username expected" and terminates the connection. 

Under windows, I can type crap all day and nothing happens. If local echo
was turned off, typed characters should still get through, right? When I
do a "ps -ax" on the poppassd end, I can see the poppassd process hanging
there waiting for a responce. This is consistant with Eudora timing out
waiting for a responce.

ABO