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"