Date: Sat, 18 May 1996 20:58:53 +0200 (MET DST) From: J Wunsch <j@uriah.heep.sax.de> To: scotto@remuda.com Cc: freebsd-questions@freebsd.org, freebsd-hackers@freebsd.org, freebsd-isp@freebsd.org, freebsd-bugs@freebsd.org, a-scotov@exchange.microsoft.com Subject: Re: sendmail read errors/timeouts etc. Message-ID: <199605181858.UAA00516@uriah.heep.sax.de> In-Reply-To: <Pine.NEB.3.93.960517165856.4971A-100000@fisbin.remuda.com> from Scott Overholser at "May 17, 96 06:41:20 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
As Scott Overholser wrote: > the troublesome sites (that i know of) are microsoft.com, msn.com, and > noa.com. i *absolutely* cannot send mail to recipient@microsoft.com or > recipient@noa.com. i seem to be able to send mail to recipient@msn.com Don't know if this is related, but we recently discovered (while hunting for a problem with some self-written Winlose 95 rsh-client) that Winlose 95 doesn't know how to handle TCP connections. Not that this really suprised me, but it effectively makes any rsh command useless that tries to take data from stdin. The bug is that Winlose never sends a FIN flag, but immediately sends a package with an RST in it. This causes the remote command to be aborted (as opposed to see a closed connection, and process it as an EOF condition). Since your problems always happen while the sendmail is waiting for the QUIT handshake, it may be the same problem. Dunno if this is only apparent for some version of Winlose 95. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199605181858.UAA00516>