From owner-freebsd-chat Thu Feb 3 17: 4:44 2000 Delivered-To: freebsd-chat@freebsd.org Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by builder.freebsd.org (Postfix) with ESMTP id 351FD3D77; Thu, 3 Feb 2000 17:04:34 -0800 (PST) Received: (from daemon@localhost) by smtp01.primenet.com (8.9.3/8.9.3) id SAA08917; Thu, 3 Feb 2000 18:04:41 -0700 (MST) Received: from usr06.primenet.com(206.165.6.206) via SMTP by smtp01.primenet.com, id smtpdAAAJoaawr; Thu Feb 3 18:04:38 2000 Received: (from tlambert@localhost) by usr06.primenet.com (8.8.5/8.8.5) id SAA00335; Thu, 3 Feb 2000 18:04:38 -0700 (MST) From: Terry Lambert Message-Id: <200002040104.SAA00335@usr06.primenet.com> Subject: Re: @home.com's e-mail problems To: johnmpurser@home.com Date: Fri, 4 Feb 2000 01:04:38 +0000 (GMT) Cc: jcm@dogma.freebsd-uk.eu.org ('Jonathon McKitrick'), jasone@canonware.com ('Jason Evans'), chat@FreeBSD.ORG, freebsd-advocacy@FreeBSD.ORG In-Reply-To: <000001bf6e63$bfdfdc00$40390918@vncvr1.wa.home.com> from "John Purser" at Feb 03, 2000 08:28:48 AM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > All I know is they can't keep an e-mail server up for one week straight to > save their souls! And when I call in and listen to the areas having trouble > I learn that they are NORMALLY having trouble with 5 to 10 states and > recently the support tech told me that AT&T e-mail was down for the entire > United States. It took four days get service up and running normally again > after that. AT&T Global Net, or AT&T @Home? I know that AT&T Global Net runs on i.Mail servers from Software.COM. Jon Postel was on the board of directors; these guys are not slackers when it comes to email. If they are having problems, then the problems are operational, not software. I also know from personal experience that we (IBM iwebconn.com) have not had a service outage not related to network connectivity, period (we had one outage related to network connectivity, and it was quickly corrected, with no users complaining about lost service; in other words, it's possible to know precisely when something like this happens, and fix it immediately. It was a network sevice provider outage, btw: not on our end, and we have since put in place plans to avoid this in the future). On the minus side, we are running on AIX, on software ported from FreeBSD, rather than on a FreeBSD developement environment, since we wanted to delegate the responsibility for maintaining the systems to someone else, and only deal with the applications. The point is, it's possible to provide reliable service; it's just a matter of will. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message