From owner-freebsd-stable@FreeBSD.ORG Tue Jun 5 06:24:05 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4943E106564A for ; Tue, 5 Jun 2012 06:24:05 +0000 (UTC) (envelope-from daniel@digsys.bg) Received: from smtp-sofia.digsys.bg (smtp-sofia.digsys.bg [193.68.3.230]) by mx1.freebsd.org (Postfix) with ESMTP id BD7C88FC0C for ; Tue, 5 Jun 2012 06:24:04 +0000 (UTC) Received: from dcave.digsys.bg (dcave.digsys.bg [192.92.129.5]) (authenticated bits=0) by smtp-sofia.digsys.bg (8.14.5/8.14.5) with ESMTP id q556O1xJ047763 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Tue, 5 Jun 2012 09:24:01 +0300 (EEST) (envelope-from daniel@digsys.bg) Message-ID: <4FCDA601.3000605@digsys.bg> Date: Tue, 05 Jun 2012 09:24:01 +0300 From: Daniel Kalchev User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:10.0.4) Gecko/20120528 Thunderbird/10.0.4 MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <20120601121555.GF5335@home.opsec.eu> <4FC8B67D.5090208@digsys.bg> <31DFBF41-37EC-43CF-A555-2D4E46F1F6E2@ee.ryerson.ca> <4FCCD919.2080502@digsys.bg> <20120604233308.25183995@vixen42.vulpes.vvelox.net> In-Reply-To: <20120604233308.25183995@vixen42.vulpes.vvelox.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Why Are You NOT Using FreeBSD ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jun 2012 06:24:05 -0000 On 05.06.12 07:33, Zane C. B-H. wrote: [on Exchange wiping devices] > From a enterprise perspective, it makes sense. Lets say a device goes > missing, it allows one to wipe it the next time it calls home. This is supposed to be handled by the device management software. Not by your e-mail server. Because it does not belong to the mail server, this is why you will not find this functionality implemented in any "open" mail server or calendaring or groupware software. As you involved "enterprise" and your previous statement on Apple, they "surprisingly" do have such device deployment and management solution. You can either use their own Apple Configurator, or any third party MDM as described in http://www.apple.com/ipad/business/integration/mdm/. I would not call this technique "proprietary". Ok, it only works on iOS ;) > The usefulness of such a feature is better disconnected from the > debate of proprietary v. non-proprietary though, given the different > nature of both issues. With this I fully agree. I hope you too agree, than when you disconnect the e-mail handling features of Exchange, from the lock-in technology Microsoft integrated there (ActiveSync), Exchange is no different than any other non-proprietary mail server. The point here is that in order to have more freedom, one has to set expectations and setups right, from the begining. Separate the MDM and e-mail functionality and you are no longer locked with Microsoft or anyone. You can easily replace each component of your system and use the best software for the task. Not make compromises. Daniel PS: Yes, I don't like Microsoft's offerings. I understand why they do this, but this doesn't mean I agree and since I have plenty of other choices... I prefer the best. My enterprise(s) have been running on BSD UNIX for good over 20 years now. No Microsoft stuff. Not needed, not missed.