From owner-freebsd-questions@FreeBSD.ORG Tue Jul 9 03:38:36 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 7B200D4C for ; Tue, 9 Jul 2013 03:38:36 +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 31BA013A4 for ; Tue, 9 Jul 2013 03:38:35 +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 BD0322736C for ; Tue, 9 Jul 2013 13:38:28 +1000 (EST) Message-ID: <51DB8403.6070000@herveybayaustralia.com.au> Date: Tue, 09 Jul 2013 13:31:15 +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: FreeBSD Questions Subject: courier imap - unable to access shared folders: "operation not supported" Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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 03:38:36 -0000 I'm really tearing my hair out here, this was working until I had to do a repair on the server hdd and rebuild it, and now I cannot work out why this has been working at all- no amount of googling even hints at what could be wrong. I'm trying to access shared folders on a courier-imap server and the client simply does nothing, the logs are very obscure as well, and it is on these that I have been focusing my searches on and then trying generalisations: Jul 9 12:59:29 server1 imapd: FAMCancelMonitor: Broken pipe Jul 9 12:59:30 server1 imapd: shared-folders//tmp/1373338770.M51083P2034_sync.: Operation not supported Jul 9 12:59:30 server1 imapd: FAMCancelMonitor: Broken pipe Jul 9 12:59:30 server1 imapd: shared-folders//tmp/1373338770.M453207P2034_sync.: Operation not supported Jul 9 12:59:30 server1 imapd: FAMCancelMonitor: Broken pipe Jul 9 12:59:50 server1 imapd: LOGIN, user=, ip=, port=[59585], protocol=IMAP Jul 9 13:00:12 server1 imapd: LOGIN, user=, ip=, port=[30542], protocol=IMAP Jul 9 13:03:44 server1 imapd: end from FAM server connection Jul 9 13:03:59 server1 imapd: FAMPending: timeout Jul 9 13:05:18 server1 imapd: couriertls: read: Connection reset by peer Jul 9 13:05:18 server1 imapd: DISCONNECTED, user=, ip=, headers=0, body=0, rcvd=314, sent=25847, time=306, starttls=1 I cannot find any references anywhere on this at all. The server has a mail store over NFS located on a ZFS fileserver, nothing has changed as such in the transition and it was working before the hdd repair was done. The only change I tried in the past 5 mins was turning the enhancedidle switch in the conf, and all that produced was the FAM errors you can see. Does anyone have any clues to this? Cheers