Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uflorida!haven!uvaarpa!mer6g
From: mer6g@uvaarpa.virginia.edu (Marc E. Rouleau)
Newsgroups: comp.mail.misc
Subject: Re: research.att.com SMTP mail receiver hosed?
Message-ID: <200@uvaarpa.virginia.edu>
Date: 3 Mar 89 17:19:22 GMT
References: <1498@ucsd.EDU>
Reply-To: mer6g@uvaarpa.Virginia.EDU (Marc E. Rouleau)
Distribution: usa
Organization: University of Virginia, Charlottesville
Lines: 24

In article <1498@ucsd.EDU> brian@ucsd.EDU (Brian Kantor) writes:
> Has anyone successfully delivered internet SMTP mail to host
> 'research.att.com' in the last 10 days or so?  We have been connecting
> at least every half hour for the last week+ and ALWAYS get the 
> '421 we're too busy' message [...]

I had the same experience.  Fortunately, the 421 bit is a lie.

I run MMDF, and I just changed a piece of code that went something
like this

	if (retn != 220)
		exit;
to
	if (retn != 220 && retn != 421)
		exit;

Research does one other thing strangely right now.  After the closing
'<CR>.<CR>' to indicate the end of a message, it waits for an unusually
long period of time before replying "221 All Is Well" or whatever.
I jacked up the timeout period to six minutes after observing delays
as long as 4:30.

	-- Marc Rouleau, UVA Academic Computing