Re: courier imap - unable to access shared folders: operation not supported
The courier documentation says this about using enhanced idle over NFS FAM (but not Gamin) also works with NFS filesystems. On NFS clientsfam transparently forwards file monitoring requests to a peer famprocess on the NFS server. Do you have a peer fam process on the NFS server? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: courier imap - unable to access shared folders: operation not supported
On 07/09/13 21:56, Mark Felder wrote: The courier documentation says this about using enhanced idle over NFS FAM (but not Gamin) also works with NFS filesystems. On NFS clientsfam transparently forwards file monitoring requests to a peer famprocess on the NFS server. Do you have a peer fam process on the NFS server? 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? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: courier imap - unable to access shared folders: operation not supported
On Tue, 09 Jul 2013 08:00:22 -0500, R Skinner ro...@herveybayaustralia.com.au 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. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: courier imap - unable to access shared folders: operation not supported
On 07/09/13 23:05, Mark Felder wrote: On Tue, 09 Jul 2013 08:00:22 -0500, R Skinner ro...@herveybayaustralia.com.au 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? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: courier imap - unable to access shared folders: operation not supported
On Tue, 09 Jul 2013 08:23:05 -0500, R Skinner ro...@herveybayaustralia.com.au wrote: 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? Oh, I misunderstood. I thought you weren't having problems until you turned on that enhanced idle feature. I'd start asking in a courier irc channel or on their mailing lists -- this sounds quite odd. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
courier imap - unable to access shared folders: operation not supported
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/shared-folder/tmp/1373338770.M51083P2034_sync.server: Operation not supported Jul 9 12:59:30 server1 imapd: FAMCancelMonitor: Broken pipe Jul 9 12:59:30 server1 imapd: shared-folders/shared-folder/tmp/1373338770.M453207P2034_sync.server: Operation not supported Jul 9 12:59:30 server1 imapd: FAMCancelMonitor: Broken pipe Jul 9 12:59:50 server1 imapd: LOGIN, user=user1, ip=IP, port=[59585], protocol=IMAP Jul 9 13:00:12 server1 imapd: LOGIN, user=user2, ip=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=user2, ip=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 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
