Subject: help! carriage return problems?

From: [email-masked] (Richard S Guse)
Date: 23 Nov 1994 02:08:58 GMT

I recently compiled pine3.91 on a next system running MachBSD.  I used
the command 'build nxt' and it built just fine.  It tests out fine on the
NeXTs.  However, connecting to that computer from a macintosh (IIci) running
system 7.0.1, everytime I hit 'return' to input a field in the compose section
(ie: to, Cc, Subject,Attchmnt), it asks for an attachment.  Control-C only
works correctly if I set the interrupt-process control-character to something
other than control-c.  Why is this?  oh, I'm connecting via telnet through
NCSA Telnet 2.6.
do the macintoshes have a different CR-LF set-up?  I connected to a pine
I know works, and it worked just fine, so it must be specific to my program.
Anyone know anything that I need to change?  I'd like to get it working
correctly before installing it.  Thanks lots, Scott.

--
Physicist by Choice,         #define SYSOP GOD
Mathematician by Accident,   #define REALITY NULL
CS student by Mistake,       #include "universe.h"
Brilliant by act of God,          e-mail:     [email-masked]
Poor by act of Congress...                          or [email-masked]

---

From: Mark Crispin <[email-masked]>
Date: Tue, 22 Nov 1994 20:27:03 -0800

Your NeXT system has a broken telnet server.  Most NeXTs do.

Try replacing the /usr/etc/telnetd binary with the fixed version on 
ftp.cac.washington.edu:pub/next-fix/telnetd

-- Mark --

---

From: [email-masked] (Robert Allan Sutton)
Date: 30 Nov 1994 03:53:32 GMT

In article <[email-masked].
EDU>,
>> correctly before installing it.  Thanks lots, Scott.

I'd be very interested in hearing if this actually fixes the problem. We have
noticed the exact same symptoms here on one of our BSDI systems. The problem 
only occurs from certain Macintosh clients. However, those same clients can
connect to other systems with no problems, and other machines can connect to
our BSDI system and run pine (and pico) with no problems. Perhaps someone
(Mark?) could explain just exactly what it is that is broken in the NeXT
telnetd and whether the problem has also been seen elesewhere. I looked at 
file Mark mentions above, however it does not include any explanation or
source code or I might try to compile it here. If anyone has any insights as
to what is going on, I would be very appreciative.

Thanks,

Allan Sutton
[email-masked]