From owner-freebsd-advocacy Sun Jan 30 13: 1:52 2000 Delivered-To: freebsd-advocacy@freebsd.org Received: from bytor.rush.net (bytor.rush.net [209.45.245.145]) by hub.freebsd.org (Postfix) with ESMTP id 731B415274; Sun, 30 Jan 2000 13:01:45 -0800 (PST) (envelope-from lynch@bsd.unix.sh) Received: from localhost (lynch@localhost) by bytor.rush.net (8.9.3/8.9.3) with ESMTP id QAA15933; Sun, 30 Jan 2000 16:01:41 -0500 (EST) Date: Sun, 30 Jan 2000 16:01:40 -0500 (EST) From: Pat Lynch X-Sender: lynch@bytor.rush.net To: John Purser Cc: chat@FreeBSD.ORG, freebsd-advocacy@FreeBSD.ORG Subject: Re: @home.com's e-mail problems In-Reply-To: <000301bf6a95$1b984aa0$40390918@vncvr1.wa.home.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-advocacy@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 29 Jan 2000, John Purser wrote: > > I sent an e-mail expressing my frustration and pointed out that even MS > doesn't use NT for heavy duty e-mail service. I suggested they look into > FreeBSD as a way of upgrading their technology and reliability. > > If they receive this suggestion from enough people they might start > listening. Especially now. Wednesday when I called in the second tier > support person I spoke to told me that the @home e-mail was down for the > entire US and they didn't know why! If they received multiple e-mails > suggesting FreeBSD as an alternative with helpful contacts at Yahoo, Walnut > Creek, or HotMail then we might get another large commercial user to join > the ranks! > > John Purser > This is very surprising considering most of the people I know who work at @home are heavy UNIX users, but then again, most everyone I know is NOC or networking people. Although I can;t see where it would be even close to inconcievable for @home to look at FreeBSD, they are probably using it at some points already. -Pat __ Pat Lynch lynch@rush.net lynch@bsdunix.net lynch@unix.sh lynch@blowfi.sh Systems Administrator Rush Networking To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-advocacy" in the body of the message