From owner-freebsd-questions@FreeBSD.ORG Sun Mar 20 18:30:30 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 5A98716A4CE for ; Sun, 20 Mar 2005 18:30:30 +0000 (GMT) Received: from smtp11.wanadoo.fr (smtp11.wanadoo.fr [193.252.22.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0AC0643D3F for ; Sun, 20 Mar 2005 18:30:30 +0000 (GMT) (envelope-from atkielski.anthony@wanadoo.fr) Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf1107.wanadoo.fr (SMTP Server) with ESMTP id 09D0F1C00099 for ; Sun, 20 Mar 2005 19:30:28 +0100 (CET) Received: from pix.atkielski.com (ASt-Lambert-111-2-1-3.w81-50.abo.wanadoo.fr [81.50.80.3]) by mwinf1107.wanadoo.fr (SMTP Server) with ESMTP id DB2971C00092 for ; Sun, 20 Mar 2005 19:30:27 +0100 (CET) X-ME-UUID: 20050320183027897.DB2971C00092@mwinf1107.wanadoo.fr Date: Sun, 20 Mar 2005 19:30:27 +0100 From: Anthony Atkielski X-Priority: 3 (Normal) Message-ID: <101669762.20050320193027@wanadoo.fr> To: freebsd-questions@freebsd.org In-Reply-To: <423DB62A.8030807@myunix.net> References: <423DB62A.8030807@myunix.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: MS Exchange server on FreeBSD? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-questions@freebsd.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Mar 2005 18:30:30 -0000 Christian Tischler writes: > The server side should be managed by BSD, but the client side is most > surely an heterogeneous group. The server side of what? It all depends on the complete architecture of your IT infrastructure. For some situations, sendmail and qpopper are all you'll ever need. For other situations, you'll end up buying racks of servers running Exchange. However, from what you've said thus far, it doesn't sound like Exchange would be the right choice. > So a solution to somehow emulate/simulate an exchange server on an box > (or cluster of sql horde what ever servers), and import this e.g. > calendar data into a BSD solution. As I understand the so far mentioned > products, these are quite capable of doing so. Then there would be an > easy solution to different likes in clients. Do they really need a calendar function? Remember, once you start building this sort of stuff, it rapidly gets more and more complicated. You might end up at some point realizing that it would have all been easier with Exchange. If you _must_ have functionality equivalent to Exchange, then run Exchange. But if you don't need that functionality, run something simpler. For what it's worth, even fancy Outlook clients can access standard SMTP/POP servers. You can build a backend using only simple software, and then consider something more complex only if and when users absolutely demand it. If you are forced into implementing a very complex solution, consider going to Exchange rather than trying to cobble something together, or you might spend the next ten years trying to get it all to work. -- Anthony