Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!decvax!decwrl!ucbvax!QUABBIN.SCRC.SYMBOLICS.COM!DCP
From: DCP@QUABBIN.SCRC.SYMBOLICS.COM.UUCP
Newsgroups: mod.protocols.tcp-ip
Subject: failed mail from DCP
Message-ID: <860630095315.5.DCP@FIREBIRD.SCRC.Symbolics.COM>
Date: Mon, 30-Jun-86 09:53:00 EDT
Article-I.D.: FIREBIRD.860630095315.5.DCP
Posted: Mon Jun 30 09:53:00 1986
Date-Received: Mon, 30-Jun-86 18:09:23 EDT
References: <860630094220.1.JOSEPH@HARLEM.SCRC.Symbolics.COM>
Sender: jason@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 16
Approved: tcp-ip@sri-nic.arpa


    Date: Mon, 30 Jun 86 09:42 EDT
    From: Joseph R Goldstone <joseph@SAPSUCKER.SCRC.Symbolics.COM>

	TOPS-20 isn't the only SMTP server that is fussy about this.  Even some
	Unix-based servers insist upon compliance to the spec here.

    Someone at a 4.2bsd site told me this "enforcement" took the form of many,
    many sendmail processes going into hard loops, pushing the load average up
    around 13 and chewing up more than 90% of the machine.  The loopy processes
    have to be shot.  He wasn't happy about it.

(-: What a great way to bring down a Unix! :-)  I assume he was less
happy about the Unix software than he was about ours.  Malformed data
should elicit responses about malformed data.  TOPS-20 did the right
thing.