From owner-freebsd-questions@FreeBSD.ORG Sun Mar 20 09:58:20 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DD57E16A4CE for ; Sun, 20 Mar 2005 09:58:20 +0000 (GMT) Received: from mail.freebsd-corp-net-guide.com (mail.freebsd-corp-net-guide.com [65.75.192.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4E0BA43D31 for ; Sun, 20 Mar 2005 09:58:20 +0000 (GMT) (envelope-from tedm@toybox.placo.com) Received: from tedwin2k (nat-rtr.freebsd-corp-net-guide.com [65.75.197.130]) j2K9wUb20946 for ; Sun, 20 Mar 2005 01:58:30 -0800 (PST) (envelope-from tedm@toybox.placo.com) From: "Ted Mittelstaedt" To: Date: Sun, 20 Mar 2005 01:58:19 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) In-Reply-To: <372015099.20050320083658@wanadoo.fr> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478 Importance: Normal Subject: RE: MS Exchange server on FreeBSD? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Mar 2005 09:58:21 -0000 > -----Original Message----- > From: owner-freebsd-questions@freebsd.org > [mailto:owner-freebsd-questions@freebsd.org]On Behalf Of Anthony > Atkielski > Sent: Saturday, March 19, 2005 11:37 PM > To: freebsd-questions@freebsd.org > Subject: Re: MS Exchange server on FreeBSD? > > > Jerry Bell writes: > > > I'll second that the calendar/email functionality has become > a utility > > service in many organizations. Exchange/outlook, for all their > > shortcomings, have really changed the way companies work. > > They get spoiled. No they don't. Shared calendaring is a requirement once you introduce e-mail to a large organization. E-mail destroys the justification for having a company mailroom and for interoffice mail. As a result companies that go to e-mail end up removing these things and reassigning people that worked in them. Unfortunately this destroys the same system that was used for scheduling use of conference rooms, setting up meetings, etc. > I suppose there's no harm in that intrinsically, but > it does tend to lock them into proprietary solutions (which isn't > necessarily good or bad). > No it doesen't. There are open solutions that handle this well. > > There isn't any solution that will provide that kind of uptime today. Yes there is. > Application systems that provide the functionality your users want are > not sufficiently evolved or reliable to achieve utility-grade service. > And since all of them are the work of companies that have spent most of > their existence writing for PCs, I don't expect this goal to be reached > any time soon. > > Nevertheless, Exchange is at the top of the list in this respect. It > would be nice to have better, but this is the best available. > You need to learn about other solutions. There is a big wide world out there you haven't seen. Ted