From owner-freebsd-questions@FreeBSD.ORG Tue Jul 9 13:23:07 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id C45CA781 for ; Tue, 9 Jul 2013 13:23:07 +0000 (UTC) (envelope-from rocky@herveybayaustralia.com.au) Received: from mail.unitedinsong.com.au (mail.unitedinsong.com.au [150.101.178.33]) by mx1.freebsd.org (Postfix) with ESMTP id 7F81D1F9E for ; Tue, 9 Jul 2013 13:23:07 +0000 (UTC) Received: from laptop3.herveybayaustralia.com.au (laptop3.herveybayaustralia.com.au [192.168.0.181]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.unitedinsong.com.au (Postfix) with ESMTPSA id 74B942731C; Tue, 9 Jul 2013 23:23:06 +1000 (EST) Message-ID: <51DC0EB9.2060604@herveybayaustralia.com.au> Date: Tue, 09 Jul 2013 23:23:05 +1000 From: R Skinner User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130530 Thunderbird/17.0.6 MIME-Version: 1.0 To: Mark Felder Subject: Re: courier imap - unable to access shared folders: "operation not supported" References: <51DB8403.6070000@herveybayaustralia.com.au> <51DC0966.6040908@herveybayaustralia.com.au> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Questions X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Jul 2013 13:23:07 -0000 On 07/09/13 23:05, Mark Felder wrote: > On Tue, 09 Jul 2013 08:00:22 -0500, R Skinner > wrote: > >> No, I don't. But then it was something I thought might help the >> situation and another feature to start playing with. Bit of a stretch >> really... but I was getting desperate. >> Would that have anything to do with the main problem though? > > I'm honestly not sure. The doc seem to indicate that it won't work > without a fam daemon on the NFS server, so maybe that's the root of > the errors. Ok. I'll give it a try. But why would it work with the NFS server - before the repair and without FAM - and not now?