Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site codas.ATT.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!whuxl!whuxlm!akgua!akguc!codas!mikel
From: mikel@codas.ATT.UUCP (Mikel Manitius)
Newsgroups: net.mail
Subject: Re: Mail overload and so-called "smart" mailers
Message-ID: <428@codas.ATT.UUCP>
Date: Fri, 10-Jan-86 16:10:52 EST
Article-I.D.: codas.428
Posted: Fri Jan 10 16:10:52 1986
Date-Received: Sun, 12-Jan-86 00:34:22 EST
References: <17623@styx.UUCP> <3080@sun.uucp> <313@fear.UUCP> <219@gould9.UUCP> <393@packard.UUCP> <317@fear.UUCP>
Distribution: net
Organization: AT&T Information Systems, Altamonte Springs, FL
Lines: 22

> Anyway, There are several ways to look at the problem.  I mostly
> approach it from the perspective of a user trying to get mail safely
> and quickly form one place to another.  When looking at things this
> way, sites like ihnp4, with its unbelievable mail load, and dual
> (which has been characterized as "well-connected, but the phones are
> always busy") are more of a hazard than help.  I mean no slight on
> the people running these sites -- but the fact is, mail moves through
> them very slowly, and they are best avoided if you want your messages
> delivered quickly.
> 
> 		Robert Plamondon

I have been moving mail trough ihnp4 (amongst other gateways) for some
time, and haven't really noticed any long delays. I am currious to see
any statistics anyone may have about the volume of trafic that goes
through such machines (mainly ihnp4), and how many lines such a site
may have dedicated to gateway.

(I for one, am very appreciative of the service ihnp4 offers)
-- 
			Mikel Manitius @ AT&T-IS Altamonte Springs, FL
			...{ihnp4|akgua|bellcore|clyde|koura}!codas!mikel